Remove hardcoded assumption that model output lives in outdir/out #3722
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.
Description
This PR removes hardcoded assumptions in workflow modules that model output
always lives in
file.path(settings$outdir, "out"). The affected modules nowconsistently use
settings$modeloutdir, which respects user-defined outputlocations provided via XML configuration.
A repository-wide search was performed to ensure no additional workflow
code relied on this assumption.
Motivation and Context
PEcAn already supports a configurable
<modeloutdir>setting that defaults tofile.path(outdir, "out")when not explicitly provided. However, some workflowmodules were still hardcoding
outdir/"out", causing user-specified<modeloutdir>values to be ignored.This change aligns workflow code with existing settings logic and documented
behavior, ensuring consistent handling of model output directories.
Fixes #3439
Review Time Estimate
Types of changes
Checklist: