Difference between revisions of "FADC250 Firmware Versions"

From GlueXWiki
Jump to: navigation, search
(Digihit comparisons)
Line 2: Line 2:
  
  
== Firmware Run Ranges ==
+
= Firmware Run Ranges =
  
 
Disclaimer: The run numbers are obtained from the time of the log entry.  It is not known if the log entry was made concurrently with the changes and the log entry does not include run number.
 
Disclaimer: The run numbers are obtained from the time of the log entry.  It is not known if the log entry was made concurrently with the changes and the log entry does not include run number.
Line 45: Line 45:
  
  
== Raw Mode Runs ==
+
= Raw Mode Runs =
  
  
Line 90: Line 90:
 
* Run 71246: [https://halldweb.jlab.org/work/halld2/data_monitoring/RunPeriod-2019-11/mon_ver01/Run071246/fcal_hit_energy.png hits 1],  [https://halldweb.jlab.org/work/halld2/data_monitoring/RunPeriod-2019-11/mon_ver01/Run071246/fcal_hit_timing.png hits 2]
 
* Run 71246: [https://halldweb.jlab.org/work/halld2/data_monitoring/RunPeriod-2019-11/mon_ver01/Run071246/fcal_hit_energy.png hits 1],  [https://halldweb.jlab.org/work/halld2/data_monitoring/RunPeriod-2019-11/mon_ver01/Run071246/fcal_hit_timing.png hits 2]
  
== Version C11 and Earlier ==
 
  
These versions had random channel timing offsets of 4 ns which changed from run to run.
 
  
  
  
 +
=Firmware Versions Details=
 +
 +
== Version C11 and Earlier ==
 +
 +
These versions had random channel timing offsets of 4 ns which changed from run to run.
  
  

Revision as of 12:03, 2 January 2020


Firmware Run Ranges

Disclaimer: The run numbers are obtained from the time of the log entry. It is not known if the log entry was made concurrently with the changes and the log entry does not include run number.

Min Run Max Run Description Log entries
70000 70050 v12C on BCAL??
70051 70147 v12C on FCAL1-FCAL6 and BCAL https://logbooks.jlab.org/entry/3735323
70148 70994 v12C on all FCAL and BCAL (any others?) https://logbooks.jlab.org/entry/3738899
70995 71194 v12C on FCAL, BCAL, ST https://logbooks.jlab.org/entry/3752596
71195 71252 v13C on FCAL1-FCAL9, TPOL; v12C on BCAL, ST https://logbooks.jlab.org/entry/3756036
71253 v13C on all FCAL, TPOL; v12C on BCAL, ST https://logbooks.jlab.org/entry/3756565


Raw Mode Runs

Min Run Max Run Description Log entries
70995 71000 v12C on BCAL, FCAL, ST https://logbooks.jlab.org/entry/3752596
71137 71137 v13C on FCAL1-FCAL9, TPOL; v12C on BCAL, ST https://logbooks.jlab.org/entry/3756335
71207 71211 v13C on FCAL1-FCAL9, TPOL; v12C on BCAL, ST https://logbooks.jlab.org/entry/3756356
71243 71248 v13C on FCAL1-FCAL9, TPOL; v12C on BCAL, ST https://logbooks.jlab.org/entry/3752596

Digihit comparisons

Looking at hits on rocid==13, slot==13, channel==12

  • Run 70995 (no error): plots
  • Run 71137 (error early on): plots
  • Run 71246 (no error): plots

Monitoring Plots



Firmware Versions Details

Version C11 and Earlier

These versions had random channel timing offsets of 4 ns which changed from run to run.


Version C12

Summary

The 4ns offsets appear to be gone. There is evidence of corruption in a single event in a single channel at low probability very early (within the first few events) in the beginning of a run. Following this all data seems okay.

Evidence


Version C13

Summary

Does not appear to show any issues.

Evidence