Conversation
squashed old branch and restarted due to conflicts.
…b.com/CHTC/chtc-website-source into dmorales-condor-submit-quickref-guide
xamberl
left a comment
There was a problem hiding this comment.
I've made some suggestions. In general, I don't like the ./ format! But it's not a dealbreaker for me.
Also, you need to place this guide in the menu (_data/htc-guide-menu.yml)
- text: "Quick reference: HTCondor Submission commands "
url: "/uw-research-computing/condor-submit-quick-ref"
icon: "bi bi-book"
| | Command | Use | Notes and Examples | | ||
| | --- | --- |----------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | `executable = <executable.sh>` | path to the executable script | The executable script is automatically transferred to the Execution Point (EP) by HTCondor. <br><br> **Example:** <br>`executable = helloWorld.py` | | ||
| | `arguments = "<args>"` | lists arguments to be passed to the executable as part of the command line | Arguments are wrapped by quotes(") and space separated. <br><br> **Example:** <br>`arguments = "hello world"` | |
There was a problem hiding this comment.
Arguments do not have to be in quotes.
There was a problem hiding this comment.
What syntax do we want to specify on here? https://htcondor.readthedocs.io/en/latest/man-pages/condor_submit.html#arguments
| {% capture content %} | ||
| - [Introduction](#introduction) | ||
| - [Submit jobs](#submit-jobs) | ||
| - [Basic Submit File Options](#basic-submit-file-options) | ||
| - [Managing File Transfers in HTCondor](#managing-file-transfers-in-htcondor) | ||
| - [Controlling Where Your Job Runs](#controlling-where-your-job-runs) | ||
| - [Controlling How Your Job Runs](#controlling-how-your-job-runs) | ||
| - [Queue Statement Options](#queue-statement-options) | ||
| - [Glossary](#glossary) | ||
| - [Related Pages](#related-pages) | ||
| {% endcapture %} | ||
| {% include /components/directory.html title="Table of Contents" %} |
There was a problem hiding this comment.
Update this after making changes.
ChristinaLK
left a comment
There was a problem hiding this comment.
I agree with several of Amber's comments, added a few of my own.
I think we decided awhile back that titles should be in "sentence case."
| | `gpus_minimum_capability = <version>` | sets minimum GPU capability | **Example:** <br>`gpus_minimum_capability = 8.5` | | ||
| | `gpus_maximum_capability = <version>` | sets maximum GPU capability | **Example:** <br>`gpus_maximum_capability = 9.0` | | ||
| | `gpus_minimum_memory = <quantity>` | requests minimum GPU VRAM memory (Default in MB) | **Example:** <br>`gpus_minimum_memory = 3200` | | ||
| | `requirements = <ClassAd Boolean>` | sets job execution constraints | See [ClassAd reference](https://htcondor.readthedocs.io/en/latest/classad-attributes/job-classad-attributes.html). <br><br> **Example:** <br>`requirements = (OpSysAndVer == "RedHat9")` | |
There was a problem hiding this comment.
I don't think we should link the ClassAd reference. I think the Machine ClassAd reference would be more useful, but this is getting into "specify this only if you know" territory. I would err on the side of caution and remove requirements from this table.
No description provided.