Build location AND run location for an experiment
@scheibelp is already working on this.
Since Aug 14, 2025.
- Dominant language
- Python
- Stars
- 78
- Forks
- 52
- Avg merge
- 4d 19m
- Merged PRs (30d)
- 10
Description
Question for @douglasjacobsen: Can we have a build location and a run location?
Answer: Yes, build location is the workspace, use the run-directory modifier to change to run location in the filesystem.
Where does the experiment write output or read input:
-
building stuff - probably home directory, not the file system: this happens where you have your benchpark workspace. We need to make sure this is clear in the docs.
-
I/O - need to be able to indicate for this to go in the file system: see if we can enable the modifier to change directories.
-
storing logs - don't want to store in lustre because it will be slow. Need to clarify with @douglasjacobsen whether the logs will go in the workspace.
-
environment - might have to go in lustre. I don't remember what "environment" refers to in this case, leave for later.
-
Symlinks may be a solution, symlink instal to your run dir - No need for symlinks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.