<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi All,<div><br></div><div> As per Kei’s request I have implemented a system to write out selected configuration parameters</div><div>used by the digitization modules from the primary readout list. These are then read into the automated</div><div>e-log entries generated at the start of each run. The first example being here:</div><div><br></div><div><a href="https://logbooks.jlab.org/entry/3337048">https://logbooks.jlab.org/entry/3337048</a></div><div><br></div><div>The table at the bottom of the page has values that look like this:</div><div><br></div><div><pre style="font-family: 'Lucida Console', Monaco, 'DejaVu Sans Mono', sans-serif; color: rgb(49, 49, 49);"><span style="font-size: 11px;">-- rocbcal10 -- rocid:40 -- Thu Apr 30 12:29:03 2015 --
Npar:2 slot_mask:0x1e7f8 (0 0000001111 00 11111111 000)
f250_NPED = 1
f250_NSA_NSB = 60</span></pre><div>The values "(0 0000001111 00 11111111 000)” represent which slots the parameters that follow</div></div><div>apply to. The spacing is done to separate the 2 switch slots in the middle as well as the </div><div>slots not typically occupied by digitization modules on the ends. In this example, fADC250 modules</div><div>are in slots 3-10 and slots 13-16.</div><div><br></div><div>These hold the values considered critical for interpreting the data. e.g. the number samples used</div><div>for the pedestal as well as the pulse integral in the flash ADC modules and the numbers used</div><div>to calculate the bin width in the F1 TDC modules. Note that these are the same values written</div><div>into the data stream. This just gives an easy way to look up the information via web browser.</div><div><br></div><div>Please let me know if you have any questions.</div><div><br></div><div>Regards,</div><div>-David</div></body></html>