Skip to content

Commit

Permalink
Update hyperlooppolicy.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ddobrigk authored Dec 5, 2023
1 parent fa6b1d7 commit bdbb02a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/hyperloop/hyperlooppolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The image below summarizes the policy:
<img src="../images/hyperlooppolicy.png" width="95%">
</div>

In general, three categories of trains exist:
In general, four categories of trains exist:

* Trains below 30TB and taking more than 1.5y of CPU time are very strongly discouraged. In those cases, please resort to very small trains (where throughputs of even 100KB/s are allowed with autosubmission) to run.
* Trains that are lower than 1.5y in CPU usage and loop over less than 200TB are free-to-execute and can be executed on hyperloop via autosubmission. In a certain region between 30-200TB, slightly more than 1.5y in CPU time is allowed as long as performance is better than 1MB/s.
Expand Down

0 comments on commit bdbb02a

Please sign in to comment.