Output Restructure/ Full Pipeline Runs / Parameter Sweeping #10
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
…ized the target data generation, simulation running and arma stats so if data has already been generated between seeds, just use the past data. Developed a meta parameter sweep script. Configure the parameters you want to sweep through in meta_params.json and meta_sweep.py
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.
Tweaked the original pipeline output file structure, reorganized the segregated output file structure.
Made scripts to run the pipeline through to completion (either original or segregated with the multiple modules)
Made scripts to run through all selected parameter permutations of gbar slices and random seeds. It can easily be configured to run through all permutations of any other pipeline parameter defined by "selected_config"
Optimized the target data generation, trace generation, and arma stats scripts to not run if there is already data from another seed. The "generate_traces.py build" step is a little more complex and needs to be optimized separately in this same manner in the future.