GeospatialScenario autobuild KDtrees and restructure files #144
+1,311
−3,336
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.
Describe your changes
Remove kdtree as a required argument from
GeospatialScenario
down-selection methods and classifiers. kdtree objects are now generated on the fly when required and saved back to the class instance so they do not have to be kept track of or rebuilt for each one of these calls.Major Organization:
GeospatialScenario
class definition moved fromscenario.py
togeopspatialscenario.py
to maintain reasonable file size for these classes.Issue ticket number and link
Fixes # (issue)
implements request from #122 "remove KDtree from downselect calls. we should generate the kdtree from the scenario's metadata at runtime"
Type of change
Breaking Change
Please delete options that are not relevant.
Checklist before requesting a review