Login  Register

Re: Headless ImageJ2-rc2 - Analyze Particles returns no result

Posted by Paul van Schayck on Jun 26, 2014; 6:40am
URL: http://imagej.273.s1.nabble.com/Headless-ImageJ2-rc2-Analyze-Particles-returns-no-result-tp5008127p5008441.html

Hey Johannes,

On Thu, Jun 26, 2014 at 1:00 AM, Johannes Schindelin
<[hidden email]> wrote:

> On Wed, 25 Jun 2014, Paul van Schayck wrote:
>
>> This already is a print("hello") script. Which is being run like this:
>> ./ImageJ-linux64 --headless -macro scripts/short.js
>>
>> For bsh script this only happens when being run with the -macro
>> options.
>
> Does it also happen if you run
>
>         ./ImageJ-linux64 --headless -batch scripts/short.js
>
> ?

Ehmm.. well when using -batch there is no output in the terminal, or
any other indication that the script is being run. Also, the delay in
closing is still there. Actually, when just running (so not script
specified):
./ImageJ-linux64 --headless -batch
The same delay is present in returning the command.

>> Is it possible to clear up the --help message a bit? The --ij1 and --ij2
>> options are quite confusing, and not clear to me. The ij1 -macro and
>> -batch options are not mentioned. The type of <files> could be
>> mentioned, so both image files and bsh script files.
>
> Well, the launcher has its own options and passes all others to the
> program to be launched. So -macro and -batch are actually not options that
> the launcher really knows about... About the scripts accepted, it seems
> that there is a bug and only --js is mentioned, but that documentation
> actually mentions .js files explicitly:
>
>         --js
>                 start Javascript (the Rhino engine) instead of
>                 ImageJ (this is the default when called with a
>                 file ending in .js)

Yes, fiji does show this extra option. However ImageJ2 does not. And
while I (now!) understand the technical reasons why the -macro option
is not mentioned it makes for a very confusing user experience. Right
now, for someone new to IJ it's very difficult to understand the
relation between IJ1 and IJ2. The help of the commands not being
complete adds to that.

Paul

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html