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

archiving alignments #145

Open
martinschorb opened this issue Jul 31, 2023 · 1 comment
Open

archiving alignments #145

martinschorb opened this issue Jul 31, 2023 · 1 comment

Comments

@martinschorb
Copy link
Contributor

Hi,

what strategy do you currently advise to archive an alignment procedure when publishing a dataset.

I would like to make the aligned volume available using MoBIE/Neuroglancer but also the raw tile data.
In order to enable reproducing the alignment from the raw data, what Render metadata should be archived with it?

Do you just keep the tilespecs of the aligned stack after the solve? Or would you also consider the SIFT matches relevant?

Thanks!

@trautmane
Copy link
Collaborator

Hi @martinschorb,

I typically keep a binary export of the mongodb data store ( using mongodump ) because that is a relatively easy way to archive/restore things without needing compute resources.

As long as the code/process you use to import tile specs and generate matches is version controlled, the minimum you'd need to keep track of is:

  • the code repository versions,
  • the source image locations and
  • stage/scope information.
    To reproduce results, you just need to re-run everything.

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

No branches or pull requests

2 participants