Bug/WA-69: Output folder adjustment for OpenSees apps #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
OpenSees app output files are not copied to archive folder.
Fix Details
OpenSees apps could have output files which are mixed with input and dependent on how TCL script writes them.
All the output files are part of the input files.
Setting the output folder for tapis to be same as execution directory to allow copying of all output files.
Tests
Tested on https://pprd.utrc.tacc.utexas.edu/
OpenSees SP: (1ae66a2e-7b00-4d7b-90ee-abb738017dea-007)
OpenSees MP: (b11dd455-1b45-472f-bf7f-2178e99bc6fb-007)
Note
The side-effect of this is that the input files are also copied. Further analysis is needed on OpenSees on how to separate output to a different folder.