This repository was archived by the owner on Jun 9, 2023. It is now read-only.
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Occasionally i become uncertain about what my covers are actually doing, and it's takes a while to inspect them via
.$interval_bounds()and.$level_sets, for example. It seems natural to want some methods to quickly visualize a cover, with or without the lensed data overlaid. These methods aren't very elegant, but they can very quickly reveal problems with a cover that cause unexpected and otherwise opaque problems for the nerve construction. What do you think? (I've only written a method forFixedIntervalCover.) I ran the following chunks after installing the current version of thisinspectbranch:Created on 2019-08-11 by the reprex package (v0.2.1)