Skip to content
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.

Sign up for GitHub

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

Update batch.rst for slurm repos #660

Merged
merged 1 commit into from
Feb 17, 2024
Merged

Update batch.rst for slurm repos #660

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion usdf/batch.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Four "repos" have been created to apportion the batch allocation. We have yet to
- developers
- commissioning

All Rubin account holders can submit to any but the production repo. We will give guidance as it is developed on which to choose.
All Rubin account holders can submit to any but the production repo (at some point we will divide up membership between commissioning and developers; when initially set up the repos, we added all users to both). If you are new to the USDF and you find you cannot submit to the developers or commissioning repos, check `coact <https://coact.slac.stanford.edu/repos/info>`__ to see which repos you belong to. If none, request addition to the appropriate repo in the ops-usdf slack channel.

In general, using BPS is preferred to running ``pipetask`` directly since many concurrent ``pipetask`` jobs that are run like this can cause registry database contention.

Expand Down
Loading