You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(notably, you do not have to execute ramble workspace setup prior to checking the number of single-node experiments)
enforce (in the allocation modifier?) that the experiment doesn't request more experiments
I assume this should be "...doesn't request more resources": ramble on --where=... will enforce this to some degree. We allow per-experiment custom templates, and I think even without that, experiments could attempt to do their own allocations (the allocation modifier would not be able to detect either of these scenarios). In terms of requests made at the level of ramble.yaml, ramble on --where=... would be enough to control that.
The text was updated successfully, but these errors were encountered: