[JHV 2.0] Command line processor is broken

[Daniel Mueller]

It looks like some of the features of the command line processor/interface from JHV 1.0 ( see doc at http://achilles.nascom.nasa.gov/~alen/dev/interface.html) do not work in JHV 2.0.

Specifically:

a) Launching JHV with images:

pearbox[266]# java -jar JHelioviewer2.jar -jhv [2005/10/05;00:00:00;SOHO;EIT;EIT;EIT;284;75]
The following command-line options are available:

-jhv jhv request(s)
      allows the user to pass a comma separated list if requests of following form:

             [date;time;observatory;instrument;detector;measurement;opacity]

             opacity is an integer 1-100.

-> This launches JHV, but without the requested image.

b) Launching JHV with a JPIP connection:
pearbox[266]# java -jar JHelioviewer2.jar -jpip jpip://delphi.nascom.nasa.gov:8090/test/movies/AIA1.jpx
Exception in thread "LoadImagesOnStartUp" java.lang.NullPointerException
        at org.helioviewer.jhv.io.FileDownloader.getDefaultDownloadLocation(FileDownloader.java:156)
        at org.helioviewer.jhv.gui.ImageViewerGui.loadImagesAtStartup(ImageViewerGui.java:401)
        at org.helioviewer.jhv.gui.ImageViewerGui.access$0(ImageViewerGui.java:277)
        at org.helioviewer.jhv.gui.ImageViewerGui$1.run(ImageViewerGui.java:211)
        at java.lang.Thread.run(Thread.java:637)

c) Launching JHV + automatically opening a file downloaded via http works, but it does not show up in the layer manager:
 java -jar JHelioviewer2.jar -download http://delphi.nascom.nasa.gov/jp2/test/movies/AIA1.jpx

[Markus Langenberg (markus-langenberg)]

First of all, the behavior was correct: Your command was wrong, it contained eight arguments instead of seven (The string "EIT" appeared too often). Still, the command line processor was broken, but it is fixed now.

[Daniel Mueller (dmueller-esa)]

Hi Markus,

Thanks! b) and c) work fine now, but a) still does not work for me - can you check whether the following works for you?
java -jar JHelioviewer2.jar -jhv [2001/10/05;00:00:00;SOHO;EIT;EIT;284;75]

Thanks,

Daniel

[Markus Langenberg (markus-langenberg)]

Hi Daniel,

I just downloaded the current beta release and started it by calling the line you wrote down. Apart from the issue that my date was of by one day because of the different time zone I am living in (I just fixed it), everything worked fine: JHV started, showing me an EIT 284 image, date 2001/10/05, time 01:06:05. What happens one your machine? Still the usage information? That only happens, if the number of arguments is incorrect or the command is unknown.

[Daniel Mueller (dmueller-esa)]

Hi Markus,

It turned out that I need to escape the ";" character on OS X/bash:
java -jar JHelioviewer2.jar -jhv [2009/03/05\;00:00:00\;SOHO\;MDI\;\MDI\;magnetogram\;80]
With that, it works fine - thanks :-)

Next question: Does the following Web Start work for you?
http://achilles.nascom.nasa.gov/~dmueller/jhv/JHV2_test.jnlp
If so, does it show one or two layers? I wrote
<argument>-jhv</argument>
<argument>[2009/03/05;00:00:00;SOHO;MDI;MDI;magnetogram;100],[2009/03/05;00:00:00;SOHO;EIT;EIT;195;50]</argument>
in the jnlp file, but for me, it only shows the MDI layer, while both MDI + EIT are visible when launching the jar file from the command line with the same command (I also tried escaping the ";" in the jnlp file).

Last question: Can you load LASCO images from the command line? If so, how? Calls like
java -jar JHelioviewer2.jar -jhv [2009/03/05;00:00:00;SOHO;LASCO;C3;white-light;100]
don't seem to retrieve LASCO images, but only bring up the default EIT 171.

However, this is really *not urgent* - getting the AIA single channel+color table image to work is really on top of the list.

Thanks a lot!

Daniel

On 11 Apr 2010, at 06:29, Markus Langenberg wrote:

> Hi Daniel,
>
> I just downloaded the current beta release and started it by calling the
> line you wrote down. Apart from the issue that my date was of by one day
> because of the different time zone I am living in (I just fixed it),
> everything worked fine: JHV started, showing me an EIT 284 image, date
> 2001/10/05, time 01:06:05. What happens one your machine? Still the
> usage information? That only happens, if the number of arguments is
> incorrect or the command is unknown.
>
> --
> [JHV 2.0] Command line processor is broken
> https://bugs.launchpad.net/bugs/557505
> You received this bug notification because you are a member of
> JHelioviewer Developers, which is subscribed to JHelioviewer.
>
> Status in JHelioviewer - JPEG2000 Visualization Software: Confirmed
>
> Bug description:
> It looks like some of the features of the command line processor/interface from JHV 1.0 ( see doc at http://achilles.nascom.nasa.gov/~alen/dev/interface.html) do not work in JHV 2.0.
>
> Specifically:
>
> a) Launching JHV with images:
>
> pearbox[266]# java -jar JHelioviewer2.jar -jhv [2005/10/05;00:00:00;SOHO;EIT;EIT;EIT;284;75]
> The following command-line options are available:
>
> -jhv jhv request(s)
> allows the user to pass a comma separated list if requests of following form:
>
> [date;time;observatory;instrument;detector;measurement;opacity]
>
> opacity is an integer 1-100.
>
> -> This launches JHV, but without the requested image.
>
>
> b) Launching JHV with a JPIP connection:
> pearbox[266]# java -jar JHelioviewer2.jar -jpip jpip://delphi.nascom.nasa.gov:8090/test/movies/AIA1.jpx
> Exception in thread "LoadImagesOnStartUp" java.lang.NullPointerException
> at org.helioviewer.jhv.io.FileDownloader.getDefaultDownloadLocation(FileDownloader.java:156)
> at org.helioviewer.jhv.gui.ImageViewerGui.loadImagesAtStartup(ImageViewerGui.java:401)
> at org.helioviewer.jhv.gui.ImageViewerGui.access$0(ImageViewerGui.java:277)
> ...

[Keith Hughitt (keith-hughitt)]

I tested the above JNLP and interestingly, the first time I ran the JNLP I got the same results as you (MDI only). The second time and thereafter, however, both layers are visible.

[Andre Dau (andre-dau)]

I just discovered this old bug. Everything seems to work now. The default image is loaded when the query contains e.g. spelling mistakes and makes no sense.
So I will close this bug