This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Ian- I'm just following up on this. The Intel graphics chip seems to be prone to this problem. If you are running a 64 bit version of Windows, try using the 64-bit version of the IDV and see if you up the memory above 1Gb. Don Murray > Unidata IDV Support wrote: > > Hi Ian- > > > > > >> I am following up on my question. I look forward to your response. > >> > > > > Sorry for the delay in responding. > > > No worries > > > >> I have modified the runIDV.bat file to allow for more memory usage. > >> The computer has over 3.4 gig of RAM > >> The video card has 1024 meg of RAM. > >> I have ensured all of the drivers on the video card are up to date and > >> we are running the latest version of java. > >> > >> IDV displays information fine when memory usage is set to 512.meg > >> When I go up over 958 meg, the map display stops working properly. (the > >> default boundaries of coastlines are not displayed and I get a black > >> screen) > >> Am I limited by the video card RAM? > >> > > > > For the 32-bit version of Windows, the theoretical limit is 1.5 Gb that can > > be used by Java. On some systems, there seems to be a link between the > > system RAM and the video RAM so that moving above 1 Gb causes the problems > > you see. We do not have a solution for this at this time. What type of > > graphics card is this? > > > Hmmm, I do not know much about hardware, but the display settings under > Control Panel say Mobile Intel 4 Series Express Chipset Family . . . > does that help? > > > >> Furthermore, loading derived quantities like 1000-500 mb thickness takes > >> a tremendous amount of time. Is there something I can do to speed that up? > >> > > > > In the 2.7u2 version of IDV, to do the thickness it would have to download > > all levels of the geopotential height, then slice and do the difference. > > In the IDV nightly build (2.8a1), it now only downloads the 1000 and 500 mb > > levels and does the difference. However, if you are using a high > > resolution grid, it will still take some time to download. You could > > reduce the resolution and/or spatial extent of the grid to speed up the > > download. > > > > Please note that the nightly builds come with a "big-boy" caveat, > > especially ones labeled with an "a" (alpha). At any point, it may have > > some instability issues, but in general, we try to make sure that it > > performs well. > > > Thanks! . . . I'll explore this > > Don Murray > > > > Ticket Details > > =================== > > Ticket ID: KUJ-685967 > > Department: Support IDV > > Priority: Normal > > Status: Open > > > > > > Ticket Details =================== Ticket ID: KUJ-685967 Department: Support IDV Priority: Critical Status: Closed