Page History

...

1. Go to https://ws.nrao.edu/workspaces/active-requests and enter the EB to be processed in the "SDM ID" box at the top, hit the "Calibrate" button. Make sure Auto-calibration button at the top left is set to run (this has nothing yet to do with the automatic start of jobs, which is controlled by the CAPO profile (need to set edu.nrao.workspaces.StandardCalibrationSettings.runState = PAUSE, not STOP in /home/casa/capo/dsoc-prod.properties), will be fixed...).
2. Select the job by clicking the request on the left-hand column, this should open a request page, with the option to submit the job at the lower right. Go ahead and submit the job. 
3. The job should appear in the job list with a status of "executing".
4. Do an ls -ltr on /lustre/aoc/cluster/pipeline/dsoc-prod/spool and write down the directory name (tmpXXXXXX) of the run you just started (you may need this later; in the next version the directory name will appear on the request page).
5. At any point prior to QA you should set the SRDP status to T/F with the checkbox and assign a DA (yourself) and an AOD to the job.
6. When complete, the status will change to "Awaiting QA". Click the link to the request page in the "Request" column, or the link the email to Workapsaces-Analysts, which will take you to the request page.
7. Follow the link to the weblog and perform QA (if you need to you can go to the working directory on spool using the directory name from step 4). Keep a copy of the qa_notes file as you will need it for the email to the user later.
8. If you need to add flags, click "Create new version" on the bottom right of the page, and upload a flagtemplate.txt file. Select the latest version on the drop-down menu under "Versions", then click "Submit new version" (and again ls -ltr /lustre/aoc/cluster/pipeline/dsoc-prod/spool and write down the directory name - each version has its own directory, unlike the current CIPL system). The old version remains and you can toggle between them using the dropdown menu. Note that once uploaded, the flag file (or any other uploaded file) cannot be overwritten in subsequent versions, to add flags to later versions you will need to go to the relevant directory on spool soon after the job is started and copy or edit the flagtemplate file directly.
9. When you are satisfied, inform the AOD (always Mark Lacy for the pilot) that a job is ready for QA. The AOD will double-check the calibration and click "QAPass" (or if not, QAFail), or send it back to the DA for a rerun. QAPass will pass the current selected version and fail all the others.
10. The execution state should change to "Ingesting", then "Complete" and a , at which point you should get an email saying the request was ingested.  A "Create Image request" button appear at the bottom right of the request page. 
11. Create the image request, this will create the request and (should) take you to a new image request page (note that with some browsers/brower settings you might need to go back to the active-requests page, select the std_cms_imaging from the top-left menu and click on the request to get to the request page).
12. Submit the image request  (bottom right button on the image request page). Again, write down the directory name on spool in case you need to look at the images for QA.
13. Weblog review can be carried out in the same way as for callibration, once the state has changed to "Waiting for QA".
14. You can upload a new PPR for imaging, but currently no flagging can be applied at the imaging stage, if you need more flagging you will have to go back to step 1 and recalibrate.
15. The archive takes a while (~24hr?) to reindex and have the data appear, so wait one day, then send an email to the PI and co-Is with text as in the info box below:

...