This repository was archived by the owner on Jun 9, 2023. It is now read-only.
Add check for missing index parameter to BallCover.R #14
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 developing some additional cover options (as discussed in #7), I noticed that level sets were being constructed multiple times per Mapper construction for the BallCover but not the FixedIntervalCover.
This seems to be because FixedIntervalCover only constructs
self$level_sets
when theindex
parameter is missing or null (i.e. when the cover is initially constructed). BallCover does not check whetherindex
is null before constructingself$level_sets
, so the computation may be performed more than once.Addition of this check for null/missing speeds up BallCover considerably without affecting the level sets or complex that is generated.
For example, using data and filter
I ran the following code using the current version of the
master
branch of Mapper:Then I ran the same code after loading the current version of this
ballcover_optimization
branch:And compared the resulting complexes and level sets: