System testing

From HELIOS Digital DAQ
Jump to navigation Jump to search

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.

Developments underway

Working with python scripts to develop universal and clean generation of cmd's, db's, templates, drivers etc. At the same time, trying to understand where and when all HELIOS files are / come from. So far, I have changed:

/global/devel/gretTop/9-22/dgsIoc/iocBoot/iocArray
vme0*.HELIOS.cmd

setup a co of the /output/ svn inside of the above directory just for the .cmd and cdCommands_HELIOS files

and (but in some strange place that does not seem to be called by the .cmd's). So also trying to put them

/global/devel/gretTop/9-22/dgsIoc/db
dgsGlobals_HELIOS_VME0*.db
dgsGlobals_HELIOS_GLBL.db

setup a co of the /output/ svn inside here as well for only the dgsGlobals_HELIOS*.db files

Not sure which .csv file to use. Notice a diff in 20160602 to 201611XX of the MasterDigitizerRegisterMap.csv (but not the MDRM.csv) ?? Try the 20160602 one...?? Seems to match what was done it the 20160602 but db files do not match what was currently on the DIGIOS disk. Will have to try it and see...

On the local digios1 daq (with the development HD in place).

Look into templates, other db, etc.!!

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/"