Add t_pre and t_post to trun?

[mjtueros]

currently we are saving t_pre and t_post, the parameters that define the time window arround the trigger time, in t_efieldsim.

I dont see where in the data files is this going to be stored. Should it be in trun?

[mjtueros]

one aditional fact indicating this must be moved is that i gave to include efieldsim files in L1 level for DC2...this should not be needed if L1 level is equivalent to data.

[lwpiotr]

In the hardware we have, or used to have (I need to get more info about new firmware) common_coincidence_time, pre_coincidence_window_ch, post_coincidence_window_ch. "There are three time windows which control the sample of ADC values to store and read out of the channel memory. Concatenated they enclose the total time frame of the event
data that is stored and read out.". If they are still coming from the hw, it would be best to adapt info from sims to them. Perhaps with setting common coincidence window to 0.

[mjtueros]

well, i dont know about common_coincidence_time...might be the interval of time you allow for two to be in coincidence, but pre_coincidence_window_c and post_coincidence_window_ch sound very close to sims t_pre and t_post. I think we can add those to variables to trun now, and set the coomon_coincidence time to 0 as you suggest.