[JHV 2.1] Uncaught exception when loading long AIA series

Bug #680827 reported by Daniel Mueller
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
JHelioviewer
Fix Released
Critical
Markus Langenberg

Bug Description

Hi,

I just loaded a 500-frame AIA 171 series (2010/08/01-2010/11/21, 6h cadence) and got the exception below. Once, JHV remained functional, but the image data was not updated any more, i.e. I could not play the series and needed to reload it. The second time, JHV displayed the same exception and the quit abruptly shortly thereafter!

Uncaught Exception detected.

JHelioviewer Version: 2.1.0

JHelioviewer Revision: 359

Date: Wed Nov 24 08:48:35 GMT 2010

Thread: Thread[J2KRender,6,J2KRenderGroup]

Message: For input string: "NAN"

Stacktrace:
java.lang.NumberFormatException
at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224)
at java.lang.Double.parseDouble(Double.java:510)
at org.helioviewer.viewmodel.view.jp2view.JP2Image.tryGetDouble(JP2Image.java:591)
at org.helioviewer.viewmodel.metadata.HelioviewerMetaData.updatePixelParameters(HelioviewerMetaData.java:134)
at org.helioviewer.viewmodel.metadata.HelioviewerMetaData.checkForModifications(HelioviewerMetaData.java:295)
at org.helioviewer.viewmodel.view.jp2view.J2KRender.renderLayer(J2KRender.java:233)
at org.helioviewer.viewmodel.view.jp2view.J2KRender.run(J2KRender.java:351)
at java.lang.Thread.run(Thread.java:680)

Tags: jhv2.1

Related branches

Revision history for this message
Markus Langenberg (markus-langenberg) wrote :

The exception was thrown during the this line (HelioviewerMetaData.java:134):

double arcsecPerPixelX = metaDataContainer.tryGetDouble("CDELT1");

The request to read the value "CDELT1" from the meta data returned "NAN" instead of a floating point value, which was not expected and thus caused the crash. From my point of view, this value is invalid and should not appear in the meta data, thus, the corrupt meta data should be corrected. Or is it really intended to get a "NAN"? Then I need to know which value should be assumed by JHV, because NaN obviously won't do the job here... As one idea: If CDELT1 is NaN and CDELT2 is not, the later one can be used. But I don't know, if this was the case here, because I don't know the exact time stamp of the corrupted frame.

Changed in jhelioviewer:
assignee: nobody → Markus Langenberg (markus-langenberg)
status: New → In Progress
Revision history for this message
Daniel Mueller (dmueller-esa) wrote : Re: [Bug 680827] Re: [JHV 2.1] Uncaught exception when loading long AIA series
Download full text (3.2 KiB)

Hi Markus,

Thanks! I don't know which frame had the CDELT1 = NAN tag (and also do not know how this can happen), Like you suggested, if CDELT1=NAN, I would try using CDELT2, and if this fails as well, use CDELT1=0.6 as the default for all AIA channels as they should all be scaled to this value (0.6 arcsec per pixel) anyway.

Thanks a lot,
Daniel

-------------------------------------------------------------
Dr. Daniel Mueller (<email address hidden>)
Solar Orbiter/SOHO Deputy Project Scientist
ESA/ESTEC (SRE-SM)
P.O. Box 299, 2200 AG Noordwijk, NL
Tel: +31 71 565 4033, Fax: +31 71 565 4697
-------------------------------------------------------------

On 24. 11.2010, at 10:41 , Markus Langenberg wrote:

> The exception was thrown during the this line
> (HelioviewerMetaData.java:134):
>
> double arcsecPerPixelX = metaDataContainer.tryGetDouble("CDELT1");
>
> The request to read the value "CDELT1" from the meta data returned "NAN"
> instead of a floating point value, which was not expected and thus
> caused the crash. From my point of view, this value is invalid and
> should not appear in the meta data, thus, the corrupt meta data should
> be corrected. Or is it really intended to get a "NAN"? Then I need to
> know which value should be assumed by JHV, because NaN obviously won't
> do the job here... As one idea: If CDELT1 is NaN and CDELT2 is not, the
> later one can be used. But I don't know, if this was the case here,
> because I don't know the exact time stamp of the corrupted frame.
>
> ** Changed in: jhelioviewer
> Assignee: (unassigned) => Markus Langenberg (markus-langenberg)
>
> ** Changed in: jhelioviewer
> Status: New => In Progress
>
> --
> [JHV 2.1] Uncaught exception when loading long AIA series
> https://bugs.launchpad.net/bugs/680827
> You received this bug notification because you are a member of
> JHelioviewer Developers, which is subscribed to JHelioviewer.
>
> Status in JHelioviewer - JPEG2000 Visualization Software: In Progress
>
> Bug description:
> Hi,
>
> I just loaded a 500-frame AIA 171 series (2010/08/01-2010/11/21, 6h cadence) and got the exception below. Once, JHV remained functional, but the image data was not updated any more, i.e. I could not play the series and needed to reload it. The second time, JHV displayed the same exception and the quit abruptly shortly thereafter!
>
>
> Uncaught Exception detected.
>
> JHelioviewer Version: 2.1.0
>
> JHelioviewer Revision: 359
>
> Date: Wed Nov 24 08:48:35 GMT 2010
>
> Thread: Thread[J2KRender,6,J2KRenderGroup]
>
> Message: For input string: "NAN"
>
> Stacktrace:
> java.lang.NumberFormatException
> at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224)
> at java.lang.Double.parseDouble(Double.java:510)
> at org.helioviewer.viewmodel.view.jp2view.JP2Image.tryGetDouble(JP2Image.java:591)
> at org.helioviewer.viewmodel.metadata.HelioviewerMetaData.updatePixelParameters(HelioviewerMetaData.java:134)
> at org.helioviewer.viewmodel.metadata.HelioviewerMetaData.checkForModifications(HelioviewerMetaData.java:295)
> at org.helioviewer.viewmodel.view.jp2view.J2KRender.renderLayer(J2KRender.java:233)
> at org.helioviewer.viewmodel...

Read more...

Changed in jhelioviewer:
status: In Progress → Fix Committed
Changed in jhelioviewer:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.