-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write and document setup_om
scripts
#42
Comments
The DAG needs "file sensors" to check whether the mask and geometry files already exist (and trigger |
From @valmar: |
From @valmar: These are usually OK! I can make an empty template and we could fill them in with the correct nodes. Or we could just use these if they are usually OK! The main problem I see is this: in order to get the available nodes, we must run wherepsana but we must run it on the DAQ machine (say cxi-daq), which might be a problem One thing we could do is have this information "somewhere" on the network where AirFlow can get it, like the queue as we discussed yesterday |
After discussing with @valmar , Murali, Wilko and Thorsten this morning, it became apparent that this use case was not adapted to Airflow DAG runs triggered from the eLog, as it requires web access, and targets the beamline operator for localized tasks rather than a general user task that could be run across multiple HPC. Instead, what needs to be implemented is:
|
setup_om
scripts
cron job now setup: [fpoitevi@pslogin01 btx]$ ./scripts/pull_repos_cron_pslogin.sh
# Date: Fri Apr 22 18:15:32 PDT 2022 | User: fpoitevi | Location: /cds/sw/package/autosfx/btx
Pulling to /cds/sw/package/autosfx/btx
Already up-to-date.
Pulling to /cds/sw/package/autosfx/mrxv
Already up-to-date.
Pulling to /cds/sw/package/autosfx/omdevteam.github.io
Already up-to-date.
[fpoitevi@pslogin01 btx]$ crontab -l
@daily /cds/sw/package/autosfx/btx/scripts/pull_repos_cron_pslogin.sh >> /cds/sw/package/autosfx/btx/cronjob.log 2>&1 |
An initial attempt at automation for the second task above was drafted in #55 However, this will probably not be used in a fully automated fashion in production, due to unpredictable issues like the one we just encountered where the monitoring nodes were weirdly defined in the DAQ config file, resulting in MPI connection weirdness that could have impacted OM's performances. |
Cron job setup on S3DF as well:
|
We need a dag that spans the following tasks:
fetch_mask
, which takes as input the detector (e.g. jungfrau4M or epix10k2M), experiment, format (crystfel, cctbx, psana), and savename. If the experiment is latest, then the latest mask from the given detector will be retrieved. After retrieving the correct mask, it will be formatted if needed and saved.fetch_geom
, which does the same as above, except retrieving / converting / saving the most recent geom file.deploy_om
, which deploys OM.The text was updated successfully, but these errors were encountered: