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.

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

We should broaden the universe of acceptable input file names #9

Open
vreuter opened this issue Dec 3, 2024 · 1 comment
Open

We should broaden the universe of acceptable input file names #9

vreuter opened this issue Dec 3, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@vreuter
Copy link
Contributor

vreuter commented Dec 3, 2024

Right now, we expect a ZARR subfolder and a pair of CSVs, each named in a rather restrictive fashion (e.g., P0001 prefix). This is fine for the moment, but really since a broader universe of position (field of view) names is permitted, this constraint should be relaxed to accommodate the concomitant diversity that's possible for these names.

@vreuter vreuter added the enhancement New feature or request label Dec 3, 2024
@vreuter
Copy link
Contributor Author

vreuter commented Dec 3, 2024

The criteria which we should impose are that all three members (the two CSV files and the subfolder of ZARR) to read and visualise are named such that they resolve to the same position/FOV name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant