Improve ingestion of Burst cWB upload. (ingest chirp mass)
Ingest from cWB the additional information:
SOLVED BY MERGE REQUEST: !134 (merged)
- new database variable for MultiBurst [strain,mchirp,hoft,code]
- update the translator to fix the ingestion problems
- update dictionary return by the api
- update visualization
Provieded trigger examples:
- BBH: G1064199, event_time=segment[0]+chirp[7]=1369177046.0+156.851562=1369177202.851562
- AllSky: G1064211, event_time=time[0]=1369177488.7303
Roberto: The format it is ok, and the injection of new and legacy triggers works.
============. ORIGINAL REQUEST ==========
- “chirp mass”
- change the definition of “event time” of Burst-cWB-BBH
- "hoft version" to ingest the channel provided in "trigger.txt"
- instead of the d -instead of the "#significance based on the last day" we should use "#significance based on the last week"
We should add the label additional labels: cWB_XP and cWB_2G.
cWB is providing trigger.txt file with the parameters of the reconstructed event. Each string in this file is describing a parameter or an array of parameters. For example, the chirp string has an array of 9 parameters chirp[0:8], where
- chirp[1] is the reconstructed chirp mass
- chirp[7] is the CBC merger time [s] relative to the start of the analysis segment which is segment[0] in the corresponding segment string in trigger.txt The array time[0:1] gives the peak time of the event in L1 (time[0]) and H1 (time[1]) The difference between these two gives the measured time-of-flight between the detectors.Example_description__CWB.rtf
Currently, time[0], which is the peak time of the event, is used by GWcelery as the “Event time”. I think it will be wrong to hack the trigger.txt file changing the definition of time[0] to be the merger time for cWB BBH search. Instead, GWcelery should use
BBH search
- “event time” = segment[0]+chirp[7]
- “peak time" = time[0]
- “chirp mass” = chirp[1]
All-sky search
- “event time” = time[0]
- “peak time" = time[0]
- “chirp mass” = 0 (not defined for all-sky search)
RELATED issue: emfollow/gwcelery#579 (closed)