Difference between revisions of "Data decode TODO"
(Created page with "Thinks to add or correct in the decode/analysis scripts: # Keep all the chip raw data in the next steps of the decode, possibly keeping the same name (in particular the Efine...") (Tag: Visual edit) |
m |
||
| Line 1: | Line 1: | ||
Thinks to add or correct in the decode/analysis scripts: | Thinks to add or correct in the decode/analysis scripts: | ||
| − | # Keep all the chip raw data in the next steps of the decode, possibly keeping the same name (in particular the Efine | + | # Keep all the chip raw data in the next steps of the decode, possibly keeping the same name (in particular the Efine and the Tcoarse_10bit values) |
# Check for the presence of all the UDP packets for each GEMROC during decode in TM (check L1_count) | # Check for the presence of all the UDP packets for each GEMROC during decode in TM (check L1_count) | ||
# Make the first steps of the script (decode and ana) easily executable for the acquisition scripts | # Make the first steps of the script (decode and ana) easily executable for the acquisition scripts | ||
# Consequently point 3, plot some reference values after a short test acquisition to confirm the system status. | # Consequently point 3, plot some reference values after a short test acquisition to confirm the system status. | ||
Revision as of 10:21, 29 May 2019
Thinks to add or correct in the decode/analysis scripts:
- Keep all the chip raw data in the next steps of the decode, possibly keeping the same name (in particular the Efine and the Tcoarse_10bit values)
- Check for the presence of all the UDP packets for each GEMROC during decode in TM (check L1_count)
- Make the first steps of the script (decode and ana) easily executable for the acquisition scripts
- Consequently point 3, plot some reference values after a short test acquisition to confirm the system status.
