ReAnalyser

Usage: ReAnalyse -t <test> -m <module1> <module2> -r <run> -s <scan1> <scan2> [-v] [-n] ...
-t <test_name> name of test to analyse (one only)
-m <module1> [<module2> ...] list of modules to analyse
-r <run> set run number (can be used more than once)
-s <scan1> [<scan2> ...] list of scans for current run number
-p <testpoint1> [<testpoint2> ... ]  list of values of test points
-n dont actually do the analysis, just parse the arguments and print
--help print this help message

Health Warning

Use with caution - if you already have a TestResult for your test, then you could over-write it.

Limitations

Appropriate data (Fits, Raws) must already be in IS - use ArchivingService retrieval if necessary.

Alternatively, try cd-ing to the relevant SystemTests directory, eg

cd $SCT_DAQ_ROOT/SystemTests/AnalysisTests/MarkSpaceRatioTest

and replacing the TestData.5067.64.MarkSpaceRatioTest.gz and SctData::RawScanResult.5067.95.20220170100038.gz files there with some from a run you wish to analyze, and then try "make run".

Examples

 $ ReAnalyse -m mymodule1 -t StrobeDelayTest -r 1007 -s 3 -p 0.

 $ ReAnalyse -m mymodule1 mymodule2 -t NPtGainTest -r 1014 -s 7 8 9 -p 0.5 0.75 1.0 -r 1415 -s 0 1 2 -p 1.5 2.0 3.0
ReAnalyse test named: NPtGainTest
Modules:
        mymodule1
        mymodule2
Run, Scan, TestPoint sets:
1014, 7 -> 0.5
1014, 8 -> 0.75
1014, 9 -> 1
1415, 0 -> 1.5
1415, 1 -> 2
1415, 2 -> 3

Responsible

Alan