[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #HRS-569883]: bundle behaves differently on IDV 5.0



> As the checkin says, fix one thing, break another.  I don't remember the
> reason for changing this, but it was to fix some other display issue.
> Maybe you can look through the support requests from around that same
> time to see if it was from a user.  Comment it out and see who
> complains. ;-)
> 
> Don
> 

I have two options here: the first one is to comment out that line and it is 
likely to break something else.
The second option is to do something like this in the toReference and 
fromReference api:

if (adjustLons) {
                t2[lonIndex] = (use360)
                               ? GeoUtils.normalizeLongitude360(latlonalt[1])
                // ? latlonalt[1]
                               : GeoUtils.normalizeLongitude(latlonalt[1]);
            }

changed to 

if (adjustLons) {
                t2[lonIndex] = (use360)
                               ? GeoUtils.normalizeLongitude360(latlonalt[1])
                // ? latlonalt[1]
                               : GeoUtils.normalizeLongitude(latlonalt[1]);
            }
else if(!use360) {
                t2[lonIndex] = GeoUtils.normalizeLongitude(latlonalt[1]);

             }



This is probably better. What do you think?


Yuan
> On 6/12/14 10:38 PM, Unidata IDV Support wrote:
> >> Thanks for checking Java 3D.  I don't think it is the contour changes.
> >> If you zoom way out, you can see the contours are way off to the right.
> >> I think it would probably be changes in MapProjectionDisplay.
> >>
> >> Don
> >
> > Don,
> >         In the MapProjectionDisplay class, you added a line to set 
> > adjustLons  = false for the TrivialMapProjection. If you comment out this 
> > line, this bundle will work. Do you remember why you
> > added this line? I don't want to fix this bundle and break others.
> >
> >
> > Yuan
> >>
> >> On 6/9/14 1:12 PM, Unidata IDV Support wrote:
> >>> Don,
> >>>
> >>> I can confirm what you are seeing, but it is not Java 7 / Java 3D (which 
> >>> is good
> >>> b/c this would be a more difficult problem to solve).
> >>>
> >>> I did the following experiment.
> >>>
> >>> I ran IDV 4.1 with Java 6 / J3D 1.5 and compared your bundle with IDV 4.1 
> >>> with
> >>> Java 7 / J3D 1.6. In both cases, the contours you describe below display
> >>> fine. This rules out Java 7 / J3D 1.6 problems.
> >>>
> >>> There has been work on the contours since IDV 4.1. I bet we could probably
> >>> isolate the emergence of this problem with a particular check in of the 
> >>> VisAD
> >>> library. We will have to keep you posted.
> >>>
> >>> Best,
> >>>
> >>> Unidata IDV Support
> >>>
> >>>> Full Name: Don Murray
> >>>> Email Address: address@hidden
> >>>> Organization: CU/CIRES
> >>>> Package Version: 5.0 build date:2014-06-01 23:09 UTC
> >>>> Operating System: Mac OS X
> >>>> Hardware: Java: home: 
> >>>> /Volumes/User/dmurray/IDV_5.0/jre.bundle/Contents/Home version: 1.7.0_51 
> >>>> j3d:1.6.0-pre9-daily-experimental daily
> >>>> Description of problem: If I load the attached bundle in IDV 4.1, it 
> >>>> works.  If I load it in IDV 5.0, the contours of sea level pressure and 
> >>>> geopotential height don't display.  A Java 3D problem?
> >>>>
> >>>>
> >>>
> >>>
> >>> Ticket Details
> >>> ===================
> >>> Ticket ID: HRS-569883
> >>> Department: Support IDV
> >>> Priority: Normal
> >>> Status: Open
> >>>
> >>
> >> --
> >> Don Murray
> >> NOAA/ESRL/PSD and CU-CIRES
> >> 303-497-3596
> >> http://www.esrl.noaa.gov/psd/people/don.murray/
> >>
> >>
> >
> > Ticket Details
> > ===================
> > Ticket ID: HRS-569883
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> >
> 
> --
> Don Murray
> NOAA/ESRL/PSD and CU-CIRES
> 303-497-3596
> http://www.esrl.noaa.gov/psd/people/don.murray/
> 
> 


Ticket Details
===================
Ticket ID: HRS-569883
Department: Support IDV
Priority: Normal
Status: Open


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.