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

[IDV #XET-258946]: color bar and shading



> Yuan,
> 
> I tried a few things with the color bar in the ISL commands.
> 
> On my last attempt, I simply centered it just to see if the size caused it to 
> not appear.
> 
> Again, it seemed fine for the grey shaded one (i.e. it appears) but I 
> couldn't get the color-filled one to show up.
> 
> Maybe I just didn't get the combination of parameters set correctly.
> 
> I can post a wrfout_d01 one which is the only one you are missing to run my 
> xidv file.
> 
> It's about 1.3 GB - can you give me an anonymous ftp site to post it?

Try here:

http://motherlode.ucar.edu/repository/alias/idvupload

Yuan
> 
> With that file, perhaps you can duplicate my issues and see if you find bugs 
> or settings I'm not using properly.
> 
> Thanks.
> 
> John
> 
> -----Original Message-----
> From: Unidata IDV Support [mailto:address@hidden
> Sent: Thursday, July 6, 2017 3:42 PM
> To: address@hidden
> Cc: address@hidden
> Subject: [IDV #XET-258946]: color bar and shading
> 
> > Yuan,
> >
> > >Ok, the option is to add the color bar through the ISL:
> >
> > I was using that option before submitting the ticket and I couldn't get it 
> > to work.
> >
> > The first issue was setting the display ID but once I did that correctly, 
> > only the grey color bar would show up.
> >
> > I can try again but I didn't have success my first time.
> >
> > >When the offscreen is set to true, the user interface will not be 
> > >generated and will not be shown in your result.
> >
> > Yes, I understand that.  The problem with using offscreen=false (i.e. 
> > letting IDV generate the interface and save the resulting image) is that 
> > some of the images are a different size (maybe 5-10 in a batch run of 100). 
> > That doesn't make sense to me as the screen/interactive window should 
> > always be the same. This same problem has happened to me in the past using 
> > IDV 5.2 on completely different hardware.
> 
> Have you tried to specify the width and height in the bundle tag:
> <bundle clear="true" file="${islpath}/test.xidv" height="400"   width="500"/>
> You can also resize the image, not sure which is best for you.
> >
> > Not sure if it has been reported or you can reproduce the problem. Perhaps 
> > it is a setting I have not selected correctly.
> >
> > >Point cloud display uses one of the variable, if you don't want it to be 
> > >altitude, you can change it in the display control.
> >
> > That part works fine and I can change the display control. I want the 
> > points to be colored by altitude.
> >
> > However, the point cloud display color bar and attributes get "inherited" 
> > by the isosurface (plot I sent previously) which doesn't happen when I use 
> > the Gridded Fields, Point Data. The Total Cloud isosurface  should be 
> > shaded grey, not colored based on altitude of the cloud variable.
> 
> This sounds like a bug to me. Could you send me a sample file to try locally? 
> How big is your file?
> 
> Yuan
> >
> > Again, if that is a feature, I would like any guidance on the appropriate 
> > settings.
> >
> > >By the way, you may want to change the background of the display to white 
> > >or something lighter.
> >
> > Are you referring to use of the image(s) in a document?
> >
> > I'm planning to show the resulting animation online and in PowerPoint 
> > presentations where I think the black background provides better contrast.
> >
> > Thanks.
> >
> > John
> >
> > -----Original Message-----
> > From: Unidata IDV Support [mailto:address@hidden
> > Sent: Thursday, July 6, 2017 1:37 PM
> > To: address@hidden
> > Cc: address@hidden
> > Subject: [IDV #XET-258946]: color bar and shading
> >
> > > Yuan,
> > >
> > > >If the problem not solved, we have a few options to discuss later.
> > >
> > > I tried the same plot with IDV 5.4 and obtained the attached image
> > > (which does not have the color bar).
> > >
> >
> > Ok, the option is to add the color bar through the ISL:
> > http://www.unidata.ucar.edu/software/idv/docs/userguide/isl/ImagesAndM
> > ovies.html
> >
> > looking for "Add a color bar to an image".
> >
> > > I also note the following warning when running IDV 5.4 (that I don't
> > > get with IDV 5.2):
> > >
> > > "libEGL warning: DRI2: failed to authenticate"
> >
> > It is my first time seeing this warning, I think it is something related to 
> > your openGL setting. No need to worry.
> > >
> > > The correct image is shown on the full interactive IDV window image
> > > save (second attachment).
> >
> > When the offscreen is set to true, the user interface will not be generated 
> > and will not be shown in your result.
> > This is the design, not a bug.
> > >
> > > Note on the correct version, I'm using Gridded Fields, Point Data
> > > that allows me to specify a Layout Model.
> > >
> > > If I use Point Cloud, Altitude for these text plots, I don't have
> > > the issue with the color bar not showing up when offscreen=true but
> > > I run into the shading problem.
> > >
> > Point cloud display uses one of the variable, if you don't want it to be 
> > altitude, you can change it in the display control.
> >
> > By the way, you may want to change the background of the display to white 
> > or something lighter.
> > Under View > Color....
> >
> > Yuan
> > > >Not sure what you mean here with shading override all other fields.
> > >
> > > The example is shown in the third attached image (again full IDV
> > > window capture).
> > >
> > > It's not the cross section despite the name because that looks wrong
> > > based on the zoom level. Even the top view had to be zoomed way out
> > > after I added the point data so that must be a parameter I'm not setting 
> > > correctly.
> > >
> > > Anyway, the isosurface color bar is grey but the isosurface of Total
> > > Cloud gets colored apparently based on the information from the point 
> > > data.
> > >
> > > Again, I suspect that's a setting I have to change but wanted to be sure.
> > >
> > > Thanks.
> > >
> > > John
> > >
> > > address@hidden> wrote:
> > >
> > > > > Full Name: John Manobianco
> > > > > Email Address: address@hidden
> > > > > Organization: Mano NanoTechnologies, Inc.
> > > > > Package Version: 5.2
> > > > > Operating System: CentOS 7 Linux
> > > > > Hardware: 12-core Intel Xeon X5650 x86_64 Description of problem:
> > > > >
> > > > > The attached isl file produces an image using an isosurface and
> > > > > overlay of text data but the color bar is missing. This isl file
> > > > > is called from a bash script to generate about 100 images each at a 
> > > > > different time.
> > > > >
> > > > > When offscreen=false, the color bar shows up. With
> > > > > offscreen=false, some of the images generated are different
> > > > > sizes hence I want offscreen=true. The netcdf file referenced in
> > > > > the xidv file was too large to include with the ticket but I can
> > > > > post it to an anonymous ftp site if necessary.
> > > > >
> > > > > Is this a bug or is there another setting I can choose in IDV
> > > > > and/or the isl file to fix the issue?
> > > > >
> > > > This is a bug related to the Java 3D. It should be better in the
> > > > latest release. What I will suggest you is to try the latest
> > > > version. If the problem not solved, we have a few options to
> > > > discuss later.
> > > >
> > > > > In a related matter, when the same overlay is created with the
> > > > > text data using Point Cloud (Altitude) instead of Gridded Fields
> > > > > Point Data, the shading based on altitude for these observations
> > > > > transfers to the isosurface which I want referenced to a
> > > > > different color map. So far, I've been unable to find the appropriate 
> > > > > settings to make that happen.
> > > > >
> > > > > Is it possible or does a Point Cloud with shading override all
> > > > > other fields?
> > > >
> > > > Not sure what you mean here with shading override all other fields.
> > > > Can you explain a little details?
> > > >
> > > >
> > > > Yuan
> > > > >
> > > > > Thank you.
> > > > >
> > > > > John Manobianco
> > > > >
> > > > >
> > > >
> > > >
> > > > Ticket Details
> > > > ===================
> > > > Ticket ID: XET-258946
> > > > 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.
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: XET-258946
> > 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.
> >
> >
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: XET-258946
> 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.
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: XET-258946
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.



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.