Add new SPI (GWTau) and benchmark generation script + workflow. #66
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.
In this PR, I've made the following changes:
run_datset_generation.yaml
. Upon running (via Git Actions portal), theCML7.npy
dataset will be loaded and SPIs will be computed on the same dataset for a fixed number of iterations (using a new Calculator each time). The mean and standard deviation for each SPI's output matrix (MPI) is then saved as a dictionary and uploaded as a .pkl file that can be downloaded as an artefact in Git Actions. Each time a new SPI is added, or a major change (e.g., dependency update) is made, the workflow can be manually triggered to create a new baseline set of SPI outputs.GWTau
) distance. See here for more details about the specific implementation.config.yaml
) and fast (fast.yaml
) subset configuration files to includeGWTau
.