Add option to reuse dumped json files in remote components - #247
Open
Asthelen wants to merge 5 commits into
Open
Add option to reuse dumped json files in remote components#247Asthelen wants to merge 5 commits into
Asthelen wants to merge 5 commits into
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
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.
This adds an option to reuse previously saved json files, if the dump_separate_json has been turned on. The new option, reuse_dumped_json, will also automatically set dump_separate_json to true. This allows you to call the same design on the client side without having to rerun the analysis on the server side. Therefore you should be able to restart an optimization or list of analyses without needing a pyoptsparse hot start file.
As a warning, json files will still be named based on the analysis number in the current run, so there may be cases where existing json files will be overwritten: for example, if you start with json files from 3 designs, and you use two of them but then try to run a third, different design, the third existing json file will be overwritten. I can try to change this if anyone prefers.