You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation Calculate_Trace_Variables sets the cutoff, point from the right, to either the size of the array or to -994. The offset, point from the right, is set to 4000. This seems really complicated if we just want the whole trace.
The text was updated successfully, but these errors were encountered:
Unfortunately, this probably means that a station with bad data (bad PMTs, oscillations or light leaks) and probably unusable data, produces the most data because they send all of it...
Yes, but that might make it a bit easier to diagnose, because you can see the signal in the quiet parts of the trace. Lots of moderately large peaks: light leak? Lots of small peaks: PMT with discharging dynodes? Oscillations: defective cables or PMT HV unit?
Yes, however, we can usually determine these same problems from the HiSPARC DAQ. But I agree we should just keep the entire traces. That way they also remain available through the Data Retrieval tool (and API) for students to look at and diagnose such problems, and having examples of what 'bad' traces look like is also good..
The current implementation
Calculate_Trace_Variables
sets the cutoff, point from the right, to either the size of the array or to -994. The offset, point from the right, is set to 4000. This seems really complicated if we just want the whole trace.The text was updated successfully, but these errors were encountered: