-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write quickstart guide for documentation #11
Comments
imo, a new user would like to see a detailed overview of I/O from functions in the library. I found this from the source code:
This is good, but it would be handy to have a binary image of blobs and maybe an output so users can get an intuitive understanding of the library. |
That's a great idea! Do you know whether this can be added in the code itself and then referenced from some other place in the docs? I'd love to to add something like this but also want to prevent code duplication. |
Thanks! Can you add some example code as well and the actual output if you have that handy? |
viz of input: I ran this script on a few toy images and there seemed to be a correlation between resolution and detected 0 dim topological features. |
Thanks! I'll look into this. |
Just covering the basics for new users: suppose you don't care about topology at all, what's the smallest thing you can add to your code to make it 'topology-aware?'
The text was updated successfully, but these errors were encountered: