NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1987 (closed feature: moved)

Opened 2013-08-19T13:54:54-05:00

Last modified 2013-08-19T13:59:01-05:00

Save & restore snapshot of ImageJ version with all plugins

Reported by: curtis Owned by: curtis
Priority: major Milestone: imagej-2.5.0
Component: Updater Version:
Severity: major Keywords:
Cc: michael@…, dscho Blocked By:

Description (last modified by curtis)

For scientific reproducibility, it must be possible to publish the exact version of ImageJ used to perform computational analysis, in a form that others can use to repeat said analysis. Unfortunately, the version of ImageJ used is not enough, since it is also paramount to know the version of all plugins used in the analysis, too.

One potential solution would be to hash all the JARs, scripts, macros, etc. -- perhaps the entire ImageJ directory structure. Then index this hash somewhere such that others can restore the same working state from it. We would need to be careful to also describe any non-managed files (i.e., files in the local working copy that aren't part of any ImageJ update site), or at least emit a caveat that these files will not be part of the saved/restored state.

After superficial consideration, I think this is a rather hard, but ultimately doable, problem. But unfortunately we probably will not have time to tackle it until after the initial release of ImageJ 2.0.0.

See  this thread on imagej-devel for the full discussion.

Thanks to Michael Doube for raising this issue!

Change History

comment:1 Changed 2013-08-19T13:56:32-05:00 by curtis

  • Type changed from enhancement to feature
  • Component changed from Analysis Plugins to Updater

comment:2 Changed 2013-08-19T13:56:56-05:00 by curtis

  • Description modified

comment:3 Changed 2013-08-19T13:59:01-05:00 by curtis

Note that the solution currently available is  Make Fiji Package. You would have to post the resultant archive somewhere so that others can download it to repeat your analysis.

The nice thing about this solution is that it includes your entire Fiji installation, including even local-only files. So in theory your analysis should be repeatable by reusing this archive. The downside is that it is less convenient than some built-in program function that gives you a short hash or something which can be published in the paper for all time.

comment:4 Changed 2014-04-30T07:31:12-05:00 by curtis

  • Status changed from new to closed
  • Resolution set to moved