feat: add keyword file export methods to NativeStand #6
Conversation
This file contains hidden or 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
Add get_keyword_file(), get_keyword_file_path(), and export_keyword_file() for inspecting and saving the FVS keyword file used in a simulation run.
Add get_output_file(), get_output_file_path(), export_output_file(), and list_output_files() for accessing FVS .out files after simulation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds three public methods to
NativeStandfor inspecting/exporting the FVS keyword file used in a simulation:get_keyword_file()— returns keyword file contents as a stringget_keyword_file_path()— returns the Path to the .key fileexport_keyword_file(dest)— copies the .key file to a destination path or directoryUseful for debugging, reproducibility, and archiving simulation configurations.
All existing tests pass (45 passed, 2 skipped).