(Link to PIMS/SECI Testing Plan Confluence page)
PIMSCache is a tool for managing a cache of measurement sets, it includes commands for adding a PIMS to the cache, listing whether a PIMS is in the cache, removing a PIMS and so on. This document covers setting it up and executing it.
groups
; this should list all of the user groups your account is in: if "vlapipe" isn't in that list, contact the helpdesk. Below, I've logged into a cluster node that I reserved (nmpost023) and run the groups
command, which shows I'm in the "vlapipe" user's group.Running pimscache -h
produces a message that describes its overall usage:
|
You can get further help on the commands by typing pimscache $COMMAND -h
, where $COMMAND is one of split, ls, rm, lspc. For example, pimscache split -h yields:
|
source ~vlapipe/workflows/setup_workflows.sh
activate_profile vlass.test
Notice that your prompt has changed, indicating the active profile, but vlass.t3 wasn't what you typed: each of the VLASS CAPO Profiles (vlass.prod, vlass.test or vlass.dev) has one of three different CAPO Profiles associated with it: for example, vlass.test has vlass.t1, vlass.t2 and vlass.t3. vlass.test is a shortcut that points at the currently executing profile, vlass.t3.
At this point the pimscache command should be available to your account, test that with:
which pimscache
If it says no such command or produces an error, something is wrong, seek help. If not, when you are done, either deactivate_profile or just log out.
Here I also switched over to tcsh, but a user whose chosen shell is tcsh would not have to do this step:
Here I set the CAPO_PROFILE environment variable to the profile I wish to use, vlass.test for now, and vlass.prod once pimscache is in production:
setenv CAPO_PROFILE vlass.test
Here I activate the virtual environment by 'source'ing a file in ~vlapipe/workflows/$CAPO_PROFILE/bin:
source ~vlapipe/workflows/vlass.test/bin/activate.csh
Lastly, I test to make sure pimscache is now in my PATH, as I would expect it to be:
If the command had come back with something like 'command not found', something is wrong. When I'm done using pimscache I use the deactivate command to switch off the workflow's virtual environment, or I log out.