Draft: Made changes to roadmap (added graphics, new info, and changed wording)#994
Draft
daniellawright wants to merge 1 commit into
Draft
Draft: Made changes to roadmap (added graphics, new info, and changed wording)#994daniellawright wants to merge 1 commit into
daniellawright wants to merge 1 commit into
Conversation
daniellawright
changed the title
daniellawright
changed the title
xamberl
reviewed
Jul 3, 2026
| - **HTCondor** is a job scheduling software that will run your jobs out on the execution points. | ||
| - The **Execution Points** are the set of resources your job runs on. | ||
|
|
||
| High Throughput Computing systems specialize in running tens to millions small, independent jobs. On the other hand, High Performance Computing systems specialize in running a few, very large jobs that use multiple computers working together on the same problem. |
Contributor
There was a problem hiding this comment.
Suggested change
| High Throughput Computing systems specialize in running tens to millions of small, independent jobs. On the other hand, High Performance Computing systems specialize in running a few, very large jobs that use multiple computers working together on the same problem. |
| <td>X</td> | ||
| <td>✓</td> | ||
| <tr> | ||
| <td>Examples</td> |
Contributor
There was a problem hiding this comment.
Suggested change
| <td>Example tasks</td> |
| More detailed information regarding CHTC's HTC system can be found in the <a href="https://chtc.cs.wisc.edu/uw-research-computing/htc-overview">⚙️ HTC Overview Guide</a>. | ||
|
|
||
| #### Step Two | ||
| ### Step Two: Set Up Your Account and Submit Your First Job |
Contributor
There was a problem hiding this comment.
I think we should keep the logging in and submitting jobs steps separate. Originally, we wanted to merge them because the logging in section was quite short initially, but with your changes and the cool new graphic, I think it can stand in its own section.
| After following this tutorial, we <b>highly recommend</b> users review the <a href="https://chtc.cs.wisc.edu/uw-research-computing/multiple-jobs">Easily Submit Multiple Jobs</a> guide to learn how you can configure HTCondor to automatically pass files or parameters to different jobs, return output to specific directories, and other easily automated organizational behaviors. | ||
| <br> | ||
| </details> | ||
| The tutorial below shows how to run many jobs from one submit file, use different input files or settings for each job, and save output files in specific directories. |
Contributor
There was a problem hiding this comment.
Suggested change
| The tutorial below shows how to run many jobs from one submit file, use different input files or settings for each job, and save output files in specific directories. | |
| The following guide demonstrates different examples on how to run multiple jobs from one submit file, use different input files or settings for each job, and save output files in specific directories. |
| <details> | ||
| <summary>Install your Software</summary> | ||
| <br> | ||
| Our <a href="https://chtc.cs.wisc.edu/uw-research-computing/htc/guides.html">Software Solutions</a> guides contain information about how to install and use software on the HTC system. |
Contributor
There was a problem hiding this comment.
Suggested change
| Our <a href="https://chtc.cs.wisc.edu/uw-research-computing/htc/guides.html">Software Solutions</a> guides contain information about how to install and use software on the HTC system. | |
| Our <a href="htc/guides#software">software</a> guides contain information about how to install and use software on the HTC system. |
| After your test jobs finish, we recommend you check for: | ||
|
|
||
| - Jobs that were placed on hold. You can view hold messages with <code>condor_q jobID -hold</code>. | ||
| - Expected output files. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Expected output files. | |
| - Expected output files - are they in the right location, and do they show the expected output? |
|
|
||
| - Jobs that were placed on hold. You can view hold messages with <code>condor_q jobID -hold</code>. | ||
| - Expected output files. | ||
| - The size and number of output files. This helps you make sure files are being saved in the correct location and that your quota is large enough for your output data when you submit more jobs. |
Contributor
There was a problem hiding this comment.
Suggested change
| - The size and number of output files. This helps you make sure files are being saved in the correct location and that your quota is large enough for your output data when you submit more jobs. | |
| - The size and number of output files. This helps you make sure that your quota is large enough for your output data when you submit more jobs. |
| - Expected output files. | ||
| - The size and number of output files. This helps you make sure files are being saved in the correct location and that your quota is large enough for your output data when you submit more jobs. | ||
|
|
||
| If your first test job works as expected, run a small batch next, such as 5 to 10 jobs. This gives you a chance to test your workflow at a slightly larger scale before submitting everything. |
Contributor
There was a problem hiding this comment.
Suggested change
| If your first test job works as expected, run a small batch next, such as 5 to 10 jobs. This gives you a chance to test your workflow at a slightly larger scale before submitting everything. | |
| If your first test job works as expected, scale up your test by running a small batch next, such as 5 to 10 jobs. This gives you a chance to test your workflow at a slightly larger scale and ensure your pipeline works before submitting everything. |
|
|
||
| If your first test job works as expected, run a small batch next, such as 5 to 10 jobs. This gives you a chance to test your workflow at a slightly larger scale before submitting everything. | ||
|
|
||
| When the small batch finishes, review the output files and check your available storage space, also called your **quota**. This will help you estimate whether you have enough space for the files your full workflow will create. |
Contributor
There was a problem hiding this comment.
Suggested change
| When the small batch finishes, review the output files and check your available storage space, also called your **quota**. This will help you estimate whether you have enough space for the files your full workflow will create. | |
| When the small batch finishes, review the output files and [check your available storage space](check-quota), also called your **quota**. This will help you estimate whether you have enough space for the files your full workflow will create. |
|
|
||
| When the small batch finishes, review the output files and check your available storage space, also called your **quota**. This will help you estimate whether you have enough space for the files your full workflow will create. | ||
|
|
||
| If the test jobs finish successfully and your quota is large enough, you are ready to submit your full workflow! |
Contributor
There was a problem hiding this comment.
Suggested change
| If the test jobs finish successfully and your quota is large enough, you are ready to submit your full workflow! | |
| > If the test jobs finish successfully and your quota is large enough, you are ready to submit your full workflow! |
Putting this in a block quote for emphasis.
Contributor
|
@daniellawright All of this looks great! The RCF team loves how clear your graphics are, and the writing is pretty clear and organized. Most of the suggestions I made are very minor language changes, or things that RCFs wanted to emphasize that you may not have known. Beside the suggested changes, we discussed breaking this up into separate pages or keeping as one long page. For now, we propose keeping it as one page with some modifications:
I think it looks great, and we're very close to finalizing the new roadmap! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.