-
Notifications
You must be signed in to change notification settings - Fork 347
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
Document condor job env variables #513
Comments
For the help we should probably suggest to user to specify the config value to pegasus that would get this set in the dag file (as Tom Downes mentioned in the email thread). This would require a trip to the pegasus docs pages to figure out how to set variables like this in the pegasus config files. If it is then not already possible to set such a value through the PyCBC config files, I can make any necessary changes if needed. |
Yes, the right way to do this long term is to get pegasus to do it with a dagman profile.
Duncan Brown http://www.gravity.phy.syr.edu/~duncan |
The right way to do this is to add a command line option allowing the user to add profiles to the site catalog. I will fix this in the Pegasus development branch for merge #559 |
This is fixed by duncan-brown@adda8e9 which allows the user to specify arbitrary properties in the site catalog using the syntax --append-site-profile 'SITE:NAMESPACE|KEY:VALUE' to --append-site-profile 'local:dagman|maxjobs:10' A complete list of profiles is at https://pegasus.isi.edu/wms/docs/latest/profiles.php |
Some of us have wondered or asked a few times how to control the number of Condor jobs submitted/in idle/running when Pegasus is used. I think this should go into the
--help
ofpycbc_submit_dax
, or in PyCBC's docs.The text was updated successfully, but these errors were encountered: