System testing: Difference between revisions

From HELIOS Digital DAQ
Jump to navigation Jump to search
Line 21: Line 21:


Values for TraceBd, TraceLen, TraceChan, etc set in screen, where are these in a file? Start search:
Values for TraceBd, TraceLen, TraceChan, etc set in screen, where are these in a file? Start search:
  cd "/global/devel/gretTop/9-22/dgsIoc/iocBoot/iocArray/"

Revision as of 00:03, March 6, 2018

Now that we have a working system and Digitizer Tester, we need to learn and test the attributes of the system. To do this, a list of possible test needs are below. These should be organized and the work divided for people to gain experience as well.

List of tests to perform

No particular order at this point just vomiting ideas...

  • Data collection:
i) single channel ii) multiple channels iii) HELIOS-like input data to multiple channels iv) across a number of digitizers
  • Data processing:
i) GEBMerge and GEBSort tests ii) simple data processing framework iii) online??
  • Full feature tests:
i) GammaWare buttons do what they are supposed to and are understood ii) equivalent epics commands are identified and tested iii) Bug Reports
  • Trigger tests:
i) how to implement trigger system tests into data ii) HELIOS-like multi-channel input tests
  • Rate tests:
i) trigger and channel rate tests of both low and high rate data ii) data throughput checks and throttle checks iii) total disk space usage for typical experiment

TRACES Trace EDM window plots DAQ$(CR)_CS_Trace where CR = VME# (1,2,3....)

Values for TraceBd, TraceLen, TraceChan, etc set in screen, where are these in a file? Start search:

 cd "/global/devel/gretTop/9-22/dgsIoc/iocBoot/iocArray/"