llnl / llnl/maestrowf

Feature Request: Passing the output directory as a variable

Open
#446 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
161
Forks
49
PR merge metrics
No merged PRs in 30d

Description

Apologies if this is already a feature. I understand that the output directory is `output_path/prefix_date-time` where `output_path` is the relative directory or a user input. I would like to provide the output directory as a variable in order to pass it to my script during the run step. For example:
```
study:
- name: example
description: example
run:
cmd: |
python $(SCRIPT) \
--output_directory $(OUTPUT_DIRECTORY)
```
where `OUTPUT_DIRECTORY` corresponds to `output_path/prefix_date-time`.
Any suggestions would be appreciated, thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the YAML run command and the existing output_path/prefix_date-time behavior described in the issue. Trace how run-step variables are handled, then verify that the resolved output directory is available to the command and that existing workflows remain unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.