Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Decision on how to deal with "faulty" data #12

Open
jenna-tomkinson opened this issue Jan 13, 2025 · 0 comments
Open

Decision on how to deal with "faulty" data #12

jenna-tomkinson opened this issue Jan 13, 2025 · 0 comments

Comments

@jenna-tomkinson
Copy link
Member

I had been removing this set manually.

What is the best way to clean these "faulty" data? Should we have a README to document these?

Originally posted by @MikeLippincott in #9 (comment)

This is a great point. We should decide how to report this data, especially since I have noticed for other patients that there are whole well/sites missing all channels and zslices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jenna-tomkinson