...
In addition, some of the services which facilitate processing are deployed only to NM, so that information requests (like those made for image ingestion) may be slower.
Python Virtual Environments
{needs more details}Self-contained sets of python libraries & associated commands. This is how we deploy the utilities for the AAT/PPI.
CAPO Files
The configuration details for the AAT/PPI are kept in text files in /home/casa/capo. This directory is replicated to CV via rsync on a cron job, so it is not immediately updated after an edit. There are a set of properties for each site (NM vs CV) and environment (Development, Test, Production). Included in that directory are a set of files for the VLASS project, containing configuration specific to their processing needs.
These properties define information like server names, where to process data, and what version of CASA to use as a default. They are editable by the vlapipe account, so those values which are of interest can be readily modified by the Data Analysts. It is possible (even likely) that some of those variable names may change as the system evolves. It is important to remember that the copy of the files in NM take precedence and will periodically overwrite their counterparts in CV. If you don't have access to the vlapipe account, contact one of your fellow DAs or the SSA team.
The Renaming Of The Profiles
With the addition of the Test environment, it was decided that the names of the CAPO profiles required revision. In addition to needing to distinguish among 3 environments instead of 2, the location portion of the names was changed to the site's label (dsoc/naasc), rather than the state's abbreviation. Thus we have the following mapping:
nmtest → dsoc-dev
vatest → naasc-dev
dsoc-test: No Change
naasc-test: No Change
nmprod → dsoc-prod
vaprod → naasc-prod
{needs more details}There are already symlinks , no official timeline, but be prepared for the replacement of nmprod with dsoc-prod, and nmtest with dsoc-dev the like.in place, so you can begin using the new names to ease this transition. There is not currently a timeline for the official retirement of the old names, but it will likely coincide with an official release of the AAT/PPI.
What is that source ~pipeaccount/workflows/myprofile/bin/activate command doing?
In order to function properly, the AAT/PPI utilities (both internal and external) require a stable, defined group of python libraries. In order to provide that, these tools are deployed within Python Virtual Environments. These environments evolve over time both as new tools are added, but also as the interactions (either internally or with external libraries) change. There will be times when two separate environments will be entirely incompatible, which is why we try to provide simplifications for accessing a coherent set of utilities.