- Someone with casaadm account credentials (Drew or Karlee) copies the release candidate into /home/casa/packages/pipeline.
- Copy (or remove) the old test symbolic link to a different symbolic link name; i.e. test_5.6.1.
- They then make a symbolic link to /home/casa/packages/pipeline/test; i.e. ln -sf /home/casa/packages/pipeline/<my new casa package> test.
- The pipeline is set to run on incoming data by setting the ciplRunState variable to RUN in the following file: /home/casa/capo/dsoc-test.properties
- The test pipeline gets run in parallel with the actual pipeline for a period ~ 1 week, and the results checked against those from the production pipeline.
Test pipeline (workspaces)
- As above, but note that VLASS SECI has its own version in the dsoc-xxxx.properties CAPO file: edu.nrao.workspaces.ProcessingSettings.CasaVersion.vlassSeci that you may or may not wish to change
- Workspaces has a separate CAPO property for the RUN/PAUSE/STOP of automated calibration: edu.nrao.workspaces.StandardCalibrationSettings.runState
{"serverDuration": 440, "requestCorrelationId": "ffe76815f37abf5e"}