For context, the end goal is to create many 2-frame hyperstacks and get the Advanced PIV plugin up and running without any memory issues (this certainly involves closing things as we go, but that’s likely a logistics discussion for another time). It has proven to be quite the challenge to get things running. That makes perfect sense.I’ve been working to automate a lot of my labs data collection and analysis in python, so I’ve started working recently with pyimagej. But we could patch a warning into the command when a user runs it, saying that within Fiji (or an environment where ImageJ1 gets patched) you might not want to use this command. So we can’t completely remove the menu entry. To checkout nightly builds of ImageJ after being asked by Wayne Rasband to see if his changes solve their issue. Lastly, if it is not recommended to use Help>Update ImageJ, then why does Fiji have a menu entry for that? Should that menu entry perhaps be removed? Or, as an alternative, should the menu entry read something like “EXPERIMENTAL” or “DON’T USE”? The menu entry read something like “EXPERIMENTAL” or Menu entry perhaps be removed? Or, as an alternative, should Then why does Fiji have a menu entry for that? Should that Lastly, if it is not recommended to use Help>Update ImageJ, Version when it auto-updates (or Help>Update is run)? (for example, 1.51t in place of 1.51s) that it will pull in the new Just for my understanding, am I right that if and when ImageJĪnd/or Fiji decides it wants to use a newer version of ImageJ1 I will use Help>Update and/or let FijiĪuto-update itself, and I will not run Help>Update ImageJ. So my suggestion is to not run Help > Update ImageJ and let Help > Update take care of that. One reason is that we are patching ImageJ1 at runtime with ij1-patcher and this process is pretty sensitive to changes in ImageJ1 source code. Hence, you might be able to use newer versions of ImageJ1 but not necessarily. So the currently supported/tested version of ImageJ1 is: Enables: dependence on Apache Maven libraries.So the currently supported/tested version of ImageJ1 is: scijava/pom-scijava/blob/master/pom.xml#L233 This BoM defines ImageJ1 as a component here. We do have a pom-scijava project that contains a Bill of Materials with compatible versions of components. Not run Help>Update (and not permit Fiji to auto-update)?Ī word or two about what the two separate updates are for would Help>Update ImageJ…, and ignore the “There are locally modifiedįiles!” warning, and select “Keep the local version” when FijiĪuto-updates (or when running Help>Update…)? Should one Should one not run Help>Update ImageJ…? Should one run What is the approved approach to keeping a Fiji installation updated? Or perhaps it indicates that theĭoubly-updated Fiji installation is subtly broken somehow. (I don’t see anything that suggests that Fiji is messed up, but I don’tĪt a minimum, the “There are locally modified files!” warning is a Updates are in effect, as both rc-62 -> rc-65 and 1.51s -> 1.51t. If I select “Keep the local version” the update appears to runĬorrectly, and when I quit and restart Fiji, it reports as its version Warning pop-up) and click “Apply Changes”, a “Resolveĭependencies” window opens up with the choices: For this older version of Fiji there are several proposedĬhanges in the Updater window. Running Help>Update… gives the same “There are locally modifiedįiles!” warning. Help>Update… upgrades Fiji to ImageJ 2.0.0-rc-62/1.51t. I also ran this test with a clean install of an older Fiji download Is empty, probably because there are not yet any updates for the Runs the update check and then pops up a warning box, “Warning” This is on a clean install of stock Fiji, ImageJ 2.0.0-rc-65/1.51s,įirst run Help>Update ImageJ… This upgrades Fiji to
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |