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

N5 Export Storage Consumption #1352

Open
AvocadoMoon opened this issue Sep 17, 2024 · 0 comments
Open

N5 Export Storage Consumption #1352

AvocadoMoon opened this issue Sep 17, 2024 · 0 comments
Assignees
@AvocadoMoon
Labels
Type: Bug bug report Type: enhancement enhance existing feature

Comments

@AvocadoMoon
Copy link
Contributor

Problem

For every export a new N5 dataset seems to be created which can lead to ballooning storage consumption for users who re-export the same simulation results.

Solution

Figure out someway to have exports that would end in the same results simply rewrite over past export.
@AvocadoMoon AvocadoMoon self-assigned this Sep 17, 2024
@AvocadoMoon AvocadoMoon added Type: Bug bug report Type: enhancement enhance existing feature labels Sep 17, 2024
@AvocadoMoon AvocadoMoon moved this to Active in vcell development Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AvocadoMoon AvocadoMoon

Labels
Type: Bug bug report Type: enhancement enhance existing feature
Projects
vcell development
Status: Queued
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AvocadoMoon