This binary release was copied to the above dir, untarred, and thus we will need SCT_DAQ_ROOT=/usera/sctrod/testing_3_2_RC1/SctRodDaq
For the testing of 3.2.RC1 at Cambridge it was necessary to edit the exampleSetup.sh file. Here is a diff of the changes I needed to make the setup appropriate for Cambridge, and here is the resultant camSetup.sh script.
It was also necessary to do
export SCT_DAQ_ROOT=/usera/sctrod/testing_3_2_RC1/SctRodDaq mkdir $SCT_DAQ_ROOT/scratch mkdir $SCT_DAQ_ROOT/saved_data
prior to the first sourcing of the script or else the SCT_SCRATCH_DIR and SCT_PERSISTENT_DIR variables are reset by the startup scripts to /tmp!!
Having done the above, the setup script may be sourced. At this stage,
$SCT_DAQ_ROOT/installed/config/databases/Hardware.data.xml
still does not exist, and must be created from
$SCT_DAQ_ROOT/installed/config/databases/Hardware_template.data.xml.
This was easy enough to do and only consisted of changing "blahHost" to "pcei" except for "sbcHost" which became "vme3".
Having done all of the above, I found it was possible to start up the shoftware and do a full characterisation sequence.
No scan in the characterisaion sequence sent an error to the MRS service. All the test results look OK. The only dodgy looking result was the pipeline test for module 20220170100028 which failed due to a bad pipeline on "Chip S11". If this is a known problem with this module, then there is noting untoward to report.