Maintaining the application

SSH nodes

Some snippets which require to run cvmfs scripts are executed at SSH nodes(of alcauser service account). For example:

• Fetching cmsDriver configuration of given workflow ID which require to load some scripts from cmssw
• Creating and uploading configuration files from cmsDriver commands(like this)
• Submitting dqm plots for comparison

Submission threads and queues are accessible to https://alcaval.web.cern.ch/dashboard

Work areas of the ssh threads

• Production: $WORK/relval_submission
• Development: $WORK/relval_dev_submission
• DQM comparison: $WORK/dqm_comparison_submission

Workflow IDs for alca matrix

Workflow ID for alca matrix(term used for list of cmsDriver configurations) will be available at AlCaWorkflows repository.

Adding new workflows

To create new workflow follow these steps:

1. relval_alca.py: Add new workflow ID from here
2. alcaval_steps.py: Add new cmsDriver configuration from here
3. This repo is fetched by alcauser service account at this location: $HOME/private/AlCaWorkflows/. If it is not fetched automatically then do that by logging into alcauser account. Do it using git pull

NOTE to editors:

• Workflow ID should be unique real number. ALCAVAL does not differentiate between 6.10 and 6.1, so keep that in mind and avoid 0 at the end.
• Also keep key of a steps object(from alcaval_steps.py) unique.
• Convention is to keep workflow ids ending with odd number for HLT condition (e.g. 6.13, 6.15 etc) and workflow ids ending with even number for Prompt/Express conditions(e.g. 6.14, 6.16 etc)