Hi Stefan, Thanks for submitting these important issues. In the divide and conquer department, my suggestion is that the e-support forum works best when one issue is submitted at a time with supporting documentation (bundles, stack traces, etc.). In addition, precise steps on how to arrive at the errors is also greatly appreciated. I detect at least four separate issues below, and each one will require (probably a fair bit) of follow up discussion. Keeping these as one issue will become unwieldy. Again, many thanks for your valuable input. -Julien > Full Name: Stefan Cecelski > Email Address: address@hidden > Organization: University of Maryland > Package Version: 2.9u4 build date:2011-04-13 07:13 UTC > Operating System: Mac OS X > Hardware: Java: home: > /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home version: > 1.6.0_24 j3d:1.5.2 fcs (build4) > Description of problem: Hi all, > > I have some suggestions based on my work using the nightly build. Whenever I > create a new projection, no map shows up in the view box to set the domain. > Furthermore, when I go to edit the projection after saving it, I get a java > exception error. A suggestion I would like to make is to allow users to set a > projection not just based on the map, but by entering lat/lon to define the > box. This would be helpful since I know the lat/lon box of my WRF runs, and > would just like to set the projection based on that, without having to mess > around with a map. > > I am also having issues when capturing images and movies. I have a computer > monitor attached to my laptop. I have the dashboard display on the laptop > screen with the maps on my external monitor. When I go to capture an image, > it will try to capture the images from my laptop screen and not the other > monitor where my actual display is located. This yields saved images that are > completly black. Does the image capture default to the screen where the > dashboard is located? Is it possible for the IDV to capture images off an > external display, or by selecting which screen the maps are on? > > I am getting suprious lines even with the suprious line fix plugin. I have > figured out that when plotting streamlines of flow vectors in IDV, changing > the density of the streamlines can create suprious streamlines. I end up > tweaking the density around until I find a density that doesn't have any > suprious streamlines. This can be tricky, and the spurious lines tend to > occur when the density is above medium, and is especially prevelant when > nearing high streamline densities. Furthermore, fast rendering contours and > maps also generates spurious streamlines. If I fast render any of the global > country maps, I get supruious streamlines. > > Finally, I am having some stability issues with IDV. I am running my laptop > with 6gb of RAM, and dedicate at least 2gb to IDV. The memory isnt the issue > however, its the processor(2.4Ghz dual core 64bit). Whenever I go to render a > derived product(such as potential vorticity), my processor kicks in majorly. > This is understandable for when the data is processing, especially for larger > data sets. What is odd is that after the data is done processing and is > displayed on the screen, IDV is still using 75-80% of my processor. This is > true even after the display and data is removed. Its like the IDV thinks it > needs to use my CPU when really there is nothing happening. What I end up > doing is close out IDV, let my CPU calm down and then start IDV back up > again. This alleviates the issue until I try to display a derived quantity > again. Not sure why IDV thinks it needs to keep using my processor like crazy. > > Thanks for your attention to this matter! > > V/R, > > Stefan Cecelski > > > > Ticket Details =================== Ticket ID: ZEO-881615 Department: Support IDV Priority: Normal Status: Closed
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.