Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
25 posts
|
Dear all,
The option "Options -> Memory & Threads -> Parallel Threads" does not get saved after shutdown. Starting a new instance of ImageJ will have reset the value to the default (number of cores available). Setting this number to 1 would be extremely useful when running ImageJ on a cluster, where the queue manages the amount of cores available. This happens in ImageJ 1.48v, but also in the daily build of ImageJ2 and Fiji. Thank you, Paul -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
25 posts
|
Dear Wayne,
I'm not sure this missed your attention, or that you didn't have time yet to reply. As this problem seems to exists in IJ1 I'm sending this also to you directly. Thank you, Paul On Mon, Jun 23, 2014 at 2:15 PM, Paul van Schayck <[hidden email]> wrote: > Dear all, > > The option "Options -> Memory & Threads -> Parallel Threads" does not > get saved after shutdown. Starting a new instance of ImageJ will have > reset the value to the default (number of cores available). Setting > this number to 1 would be extremely useful when running ImageJ on a > cluster, where the queue manages the amount of cores available. > > This happens in ImageJ 1.48v, but also in the daily build of ImageJ2 and Fiji. > > Thank you, > > Paul -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
2136 posts
|
Hi Paul,
not saving the "Options -> Memory & Threads -> Parallel Threads" is probably on purpose. When saving it in the Prefs and migrating everything (including the Prefs) to another computer, you may end up with poor performance because of an improper value. Also, it's all too easy to forget setting it properly after changing it for some tests... If you want to have a certain non-default value, why not put it into the StartupMacros.txt? You can do the same also for other options that you always want to initialize to the same value, e.g.: macro "AutoRun" { // reset options run("Colors...", "foreground=black background=white selection=orange"); run("Options...", "iterations=1 pad edm=Overwrite count=1"); run("Profile Plot Options...", "draw interpolate sub-pixel"); run("Memory & Threads...", "parallel=1 keep run"); } Michael ________________________________________________________________ On Jul 1, 2014, at 11:11, Paul van Schayck wrote: > Dear Wayne, > > I'm not sure this missed your attention, or that you didn't have time > yet to reply. As this problem seems to exists in IJ1 I'm sending this > also to you directly. > > Thank you, > > Paul > > On Mon, Jun 23, 2014 at 2:15 PM, Paul van Schayck <[hidden email]> wrote: >> Dear all, >> >> The option "Options -> Memory & Threads -> Parallel Threads" does not >> get saved after shutdown. Starting a new instance of ImageJ will have >> reset the value to the default (number of cores available). Setting >> this number to 1 would be extremely useful when running ImageJ on a >> cluster, where the queue manages the amount of cores available. >> >> This happens in ImageJ 1.48v, but also in the daily build of ImageJ2 and Fiji. >> >> Thank you, >> >> Paul > > -- > ImageJ mailing list: http://imagej.nih.gov/ij/list.html ... [show rest of quote] -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
25 posts
|
Dear Michael,
On Tue, Jul 1, 2014 at 2:05 PM, Michael Schmid <[hidden email]> wrote: > Hi Paul, > > not saving the "Options -> Memory & Threads -> Parallel Threads" is probably on purpose. When saving it in the Prefs and migrating everything (including the Prefs) to another computer, you may end up with poor performance because of an improper value. > Also, it's all too easy to forget setting it properly after changing it for some tests... > > If you want to have a certain non-default value, why not put it into the StartupMacros.txt? You can do the same also for other options that you always want to initialize to the same value, e.g.: > > macro "AutoRun" { > // reset options > run("Colors...", "foreground=black background=white selection=orange"); > run("Options...", "iterations=1 pad edm=Overwrite count=1"); > run("Profile Plot Options...", "draw interpolate sub-pixel"); > run("Memory & Threads...", "parallel=1 keep run"); > } > ... [show rest of quote] Thank you for your answer! It maybe makes sense that this option is not saved (although more options may fall under that consideration then). However a note about it in the dialog may be a good idea. I feel stupid though about not thinking about the macro call in an autorun macro. Thanks for reminding me. Thanks, Paul -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Free forum by Nabble | Disable Popup Ads | Edit this page |