Add optional pfts
argument to run.sensitivity.analysis()
(fix/workaround for #3154)
#3155
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
Adds a
pfts
argument torun.sensitivity.analysis()
to allow the user to specify a subset of PFTs in thesettings
object to run sensitivity analysis on.Also prevents this function from dumping objects into the global environment (and possibly overwriting things without any warning) by specifying the environment for
load()
Motivation and Context
Doing sensitivity analysis with a large number of PFTs generates a large number of runs and to save on compute time, I "manually" removed SA runs for PFTs I'm not interested in.
run.sensitivity.analysis()
interprets this as an there having been an error in model runs and doesn't generate all the files it is supposed to (in particular, no sensitivity.results.Rdata) (#3154).Review Time Estimate
Types of changes
Checklist: