Closed
Conversation
Contributor
Author
|
merged into main as of 1efa3c7 |
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 PR will optionally allow users to write the output of Jason's X point finder to disk so that repeated runs are faster. Subsequent runs using the cached files for 150 frames will load all the data in less than a minute instead of ~18 minutes when it had to run the X point finder.
For example,
python XPointMLTest.py --xptCacheDir=/path/to/cache/dirwill write a set of files per input frame to the specified path. On subsequent runs, when--xptCacheDir=/path/to/cache/diris passed, those files will be read in instead of re-running the X point finder.