(link to PIMS Testing Punchlist)
Provided below are a set of usage scenarios for the PIMS and SECI system meant to exercise the functions of the system.
Setting up for using the pimscache command line
- log into your preferred machine with lustre visibility as vlapipe
- activate_profile vlass.test
- Note the prompt will look like:
- (vlass.t1) vlapipe@hamilton$
- Could be t1, t2, t3. Nothing to be alarmed about. vlass.test is an alias for the 'active' workflow deployment. There are 3 options to keep old workflow servers active to allow jobs to complete normally rather than be abandoned.
- Similarly for production, vlass.prod is an alias for the active deployment among p1, p2, p3
- Note the prompt will look like:
- pimscache is now in your PATH, and can be readily accessed.
Testing Scenarios
1) Standard Usage – Prepare a Tile for Imaging
- Manager: Lookup associated calibration for the tile
- Jobs Tab Name: VLASS1.2_TAAtaa.TBBtbb.TCCtcc_GvN
- Jobs Tab ID: 9999
- CLI: check the cache
pimscache ls VLASS1.2_TAAtaa.TBBtbb.TCCtcc_GvN
AmyK: works but user cannot easily copy/paste this from VlassMgr
Result: No files found
- CLI: initiate split
pimscache split -v 9999 -t TAAtaa
- Creates SECI products in WAITING state
- AmyK: products show up under "SE Continuum Image" in VlassMgr. We therefore have superfluous product type "SE Continuum" showing in Manager. That should be replaced with "SE Continuum Image" products, to preserve product order in the Type dropdown menu (i.e., SE Continuum Image should be after SE Calibration)
- AmyK: Jim reports that interrupting the command does not terminate the workflow. Perhaps we could have some sort of notification (emailed, supplied by user?) when a restore initiated by the pimscache command is complete? (if command is not interrupted, is the new "restore parameter" reported to user? I'm not sure this question makes sense, as I am still just experimenting with pimscache (March 19) and waiting to see what happens)
- AmyK: products show up under "SE Continuum Image" in VlassMgr. We therefore have superfluous product type "SE Continuum" showing in Manager. That should be replaced with "SE Continuum Image" products, to preserve product order in the Type dropdown menu (i.e., SE Continuum Image should be after SE Calibration)
- Initiates a workflow which performs a restore, and then a parallel set of Splits
- Uses the casa specified by the VLASS profile variable: edu.nrao.archive.workflow.config.CasaVersions.homeForReprocessing
- places split MSs into the cache
- Creates SECI products in WAITING state
(vlass.d3) vlapipe@wirth-vml$ pimscache split -v 8866 -t T03t30
- CLI: check cache
pimscache ls VLASS1.2_TAAtaa.TBBtbb.TCCtcc_GvN
(vlass.d3) vlapipe@wirth-vml$ pimscache ls VLASS1.1_T01t03_P22376v1
- Per Phase Center:
- Manager: Set the product status to 'Ready' and create the Job
- An execution is automatically submitted.
- Manager: image and QA loop
- Manager: Set the product status to 'Ready' and create the Job
- CLI: remove the PIMS
pimscache rm -v 9999 -p J000000-000000
- (vlass.d3) vlapipe@wirth-vml$ pimscache ls VLASS1.1_T14t05_P21842v1
/lustre/aoc/cluster/pipeline/vlass_dev/cache/pims/VLASS1.1_T14t05_P21842v1/J025021+153000
(vlass.d3) vlapipe@wirth-vml$ pimscache rm -c VLASS1.1_T14t05_P21842v1 -p J025021+153000
Removed phase center J025021+153000
(vlass.d3) vlapipe@wirth-vml$ pimscache ls VLASS1.1_T14t05_P21842v1
No files found
2) Re-using an existing Restore – Next Tile for the same calibration
When you're ready to prep the next set of images, if you have the previous restore around, you can skip the restore, saving time.
- CLI: initiate split
pimscache split -v 9999 -t TBBtbb -r /path/to/old/cms/working/directory/
(vlass.d3) vlapipe@wirth-vml$ pimscache split -v 8448 -t T01t03 -r /lustre/aoc/cluster/pipeline/vlass_dev/spool/VLASS1_2018_02_02_T17_13_54.908/working/VLASS1.1.sb34940218.eb34992438.58151.92216394676.ms
- CLI: check cache
pimscache ls VLASS1.2_ABC_GvN
- You'd expect both tile's worth of phase centers to be shown.
- Manager: imaging for each phase center as before
3) make split ms's for all tiles in a calibration
Simply leave off the "-t" option to request splitting of all tiles/phasecenters associated with a calibration.
- CLI: check the cache
pimscache ls VLASS1.2_TAAtaa.TBBtbb.TCCtcc_GvN
Result: No files found
- CLI: initiate split
pimscache split -v 9999
4) Single Image Needs to be Redone
If an image is later found to be in error, it is possible to simply create a single PIMS via the split. This is assuming that the restore needs to be redone due to removal of data previously.
- CLI: Initiate the split
pimscache split -v 9999 -p J010228-363000
(vlass.d3) vlapipe@wirth-vml$ pimscache split -v 5947 -p J025021+153000
Generated VLASS1.1.se.T14t05.J025021+153000.06.2048 in the VLASS manager database
Starting split to per-image measurement sets on VLASS1.1.sb34812068.eb34812594.58122.954574675925 with calibration VLASS1.1_T14t05_P21842v1
providing path: None
2c2fd395: No existing restore parameter; restoring from scratch (will take several hours)
2c2fd395: Extracting data from archive...
2c2fd395: Arranging for processing...
2c2fd395: Inititating the casa restore...
2c2fd395: Running CASA to split PIMS for phase center J2000 02:50:21.166 +15.30.0.0000
2c2fd395: CASA complete for phase center J2000 02:50:21.166 +15.30.0.0000
2c2fd395: Caching split for phase center J2000 02:50:21.166 +15.30.0.0000
2c2fd395: SECI split complete for uid://evla/execblock/e84e61c6-fbd3-49be-a3be-264da4f5e043
(vlass.d3) vlapipe@wirth-vml$
- Manager: create a and run a new execution & continue QA
5) Experimentation – Use a PIMS from the cache for interactive casa exploration
For validation purposes, or for investigation of a particularly difficult imaging problem, you can use the data in the cache.
- Choose your data set
- Jobs Tab Name: VLASS1.2_ABC_GvN
- Jobs Tab ID: 9999
- Phase Center: J000000+000000
- Confirm it's available:
- pimscache ls VLASS1.2_ABC_GvN | grep J000000+000000
- (vlass.d3) vlapipe@wirth-vml$ pimscache ls VLASS1.1_T03t30_P26880v1 | grep 194539-313000
/lustre/aoc/cluster/pipeline/vlass_dev/cache/pims/VLASS1.1_T03t30_P26880v1/J194539-313000
- Link it to your scratch work area:
- pimscache ln -v 9999 -p J000000+000000 /lustre/aoc/rest/of/the/path/working
- (vlass.d3) vlapipe@wirth-vml$ pimscache ln -v 8866 -p J194539-313000 /lustre/aoc/cluster/pipeline/jls_test/pims/
Successfully linked phase center J194539-313000 to /lustre/aoc/cluster/pipeline/jls_test/pims
(vlass.d3) vlapipe@wirth-vml$ ls
VLASS1.1.sb35118798.eb35120996.58169.55511674768_split.ms@
(vlass.d3) vlapipe@wirth-vml$
References
Single Tile Calibrations
- T01t03
- VLASS1.1_T01t03_P22276v1
- 8448
- T03t30
- VLASS1.1_T03t30_P26880v1
- 8866
- T14t05
- VLASS1.1_T14t05_P21842v1
- 5947
Obtaining Phase Center information
- Names of the imaging products contain the phase center
- CLI provides them by tile:
pimscache lspc T01t03
J010234-393000
J010743-393000
J011252-393000
J011800-393000
J012309-393000
J012752-393000
J010232-383000
J010736-383000
J011241-383000
J011745-383000
J012250-383000
J012741-383000
J010230-373000
J010730-373000
J011231-373000
J011731-373000
J012232-373000
J012731-373000
J010228-363000
J010724-363000
J011221-363000
J011718-363000
J012214-363000
J012711-363000
J012949-363000