-
Notifications
You must be signed in to change notification settings - Fork 0
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
Derive a sample dataset #12
Comments
Images from the NDP52 project are now all published into a repository so can probably be used for this purpose. e.g. more files can be found here: |
Additionally there is 'dirty' blanks that all experimentalists will have a good collection of and could be used for this purpose (they are useless otherwise!) UPDATE (using edit ;) ): here is a folder of "interesting" blanks: https://drive.google.com/drive/folders/1-4rucSQqm1aY40rxd63e8nGEuAcHnRiA?usp=drive_link |
Brilliant, thanks @derollins I'll have a look through next week when I'm back on training development. Useless GitHub Tip : You can edit posts (pen icon at the top right of the gray bar above posts. |
Another source of material is those that are available from the Minicircle work, see figshare. This would be useful is it has both "super-coiled" (-3) and "relaxed" molecules imaged which would help show differences in the distribution of statistics that are calculated with each. |
We require a sample dataset for this tutorial so that there is a standard set of images for users to process as they work through the different stages.
I realised whilst working on #11 that we probably don't want to copy over the files and directory structure used in the Unix Shell Software Carpentry and would be better served to have a set of AFM images in a hierarchical structure which we can use to demonstrate directory structure and navigation in the Command Line sections and how TopoStats scans for images across the
base_dir
and how that in turn influences the structure of output.For this I feel we need more than just
minicircles.spm
that is used in the TopoStats test suite.It would also be worthwhile including an image that doesn't process so that we can demonstrate what happens when this arises and how to handle such cases.
If anyone has images that are not under Non-Disclosure Agreements and is able to share them please provide links in reply to this issue (or email me the Google Drive link, no need to send the image).
The text was updated successfully, but these errors were encountered: