- Idl.colors: number of color IDL can use (useful for PseudoColor devices). Idl.grdepth: Depth, in bits, of the graphics device in use. Idl.retain: default parameter retain (Backing Store selection → graphics covered by other windows): 0= none, 1= by server, 2= by IDL. Idl.grvisual: type of visual device to use.
- (1) Configure the PS device: So far, we've been using the graphics window on the screen, but there are several other graphics devices accessible in IDL (see Table 5.1 on p. 194 in your IDL text book). The default graphics device is the screen display, in our case, it is the X device (for X-windows).
QUESTION: Yikes! I just installed IDL on my machine and I notice that it takes a LOT morememory to run. My IDL 6.4 IDLDE process required 11 MBytes. My IDL 7.0 Workbench process requires 90 MBytes and JAVArequires another 30 MBytes. Are there minimum hardware requirements to run this Big Boy?
To download and install IDL: Click on the link to download the full version of IDL 7.0. Make note of the location to which you are downloading the ZIP file. If the ZIP file does not unpack itself automatically, double-click on the idl70mac.zipfile to unpack it. IDL Print, cgHasImageMagick 1 In IDL 8.x it is possible that even if you install ImageMagick correctly, you will still have trouble spawning an ImageMagick command. The solution to this problem can be found in this article. Version of IDL used to prepare this article: IDL 7.0.1. Free idl 7.0 download software at UpdateStar - 1,746,000 recognized programs - 5,228,000 known versions. It was originally introduced to Mac users in Mac OS 9.
ANSWER: Let me put it this way. When I installed IDL 7.0 on my Sony Vaio computer, which is limited (for God only knows what reason)to 512 MByte of RAM, I could either have the IDL Workbench running, or the IDLOn-line Help running, but not both simultaneously. If I tried the simultaneous thing, I got a JAVA out-of-memory error. With just the Workbench running, ittook my operating system (SUSE 10.3) about 10 seconds to respond to my request for a new terminal window.
So, I don't know what the minimum hardware requirement is, but I would guessit is a least twice the RAM I have on my poor old machine. If you have Windows Vistarunning at the same time, God help you.
Incidentally, this Sony machine had a 1024 by 800 pixel resolution display on a 14 inch monitor.The IDL Workbench, under the KDE window manager, has a rather bloated look to it.I had about 8 vertical inches of useable space on my monitor, but the Workbenchused 1/2 inch for the bottom status bar, and another 1/2 inch for the icon barat the top of the application. In addition, I had three windows (editor, console,and command line) open and stacked vertically. Each of these had a tab, whichused 3/8 of an inch of space, each. So, over 1/4 of my display was taken up with non-functioningwindow decoration. If I sized the console window so I could see 4-5 lines of output, I could see exactly 16 lines of text in my editor window with the default fonts installed.This was quite a bit less than is absolutely necessary to do useful work, so I wouldalso recommend a machine that supported higher resolution than 1024 by 800.
Perhaps Santa is bringing you a new computer this year. If so, be sure toask for that extra RAM and a powerful video card. Extra reading classes wouldn't hurt, either.Software these days is designed with the younger folks in mind!
Just to give you a sense of things. Here is my Windows Task Manager, after just startingIDL 6.4.
|The top memory users on my computer on a typical day, running IDL 6.4.|
Idl 7.0 Mac Download Brown Search Engine
And here is the same look, just after starting IDL 7.0.1. There are two processes to pay attention to here:idl_opserver.exe and idlde.exe. As you can see, IDL 7 takes considerable more memory resources to run. Without actually doing anything, IDL 7 requires over 110 MBytes of memory, as opposed to about 13 MBytes for IDL 6.4.
|The top memory users on my computer on a typical day, running IDL 7.0.1.|
Copyright © 2007 David W. Fanning
Last Updated 20 December 2007
- On-Line Docs
QUESTION: I have installed ImageMagick on mycomputer but the Coyote Graphics commands can't seem to find it. What do I need to domake it available to them?
ANSWER: The Coyote Graphics routines look forImageMagick by spawning the ImageMagick convert command inside the Coyote Libraryfunction, cgHasImageMagick. If the command is not found an error is generated and cgHasImageMagick returns a 0. If no error is generated, the function returns a 1.
This means, in general, that the shell running IDL must have its PATH environmentvariable set to include the path to the ImageMagick convert command. Otherwise, ImageMagick will not be found, even if it is installed. On Windows and UNIX machines the path is typically set up properly when ImageMagickis installed. The Macintosh computer is a special case, however,and requires a different procedure.
I don't have a Macintosh computer to test on, so I am flying a little bitblind here. This is what I have been told by people who have figured out what needsto be done. If you have a better idea or explanation, I am more than happy to hear it.
Here is how I understand the problem. On most UNIX systems, a shell is spawned to start a process. The shell has its own environment variables.This apparently only happens on Macintosh computers if a programis run from the command line. If the program is run as an application (*.app), thenthe environment variables are determined by an XML file called environment.plist.
If ImageMagick is installed via MacPorts, then the convert commandlives in /opt/local/bin/. It is this directory that needs to get onthe PATH environment variable. Users have solved this problem in a couple of ways.
- One way is to use the IDL SetEnv command in an IDL start-up file. The commandwill look like this.
- Or, you could put a softlink to the ImageMagick convert command into thisdirectory, pointing to the actual location where the command is installed.
- Or, you can open the the environment.plist file and look for the PATH keyand add the ImageMagick bin directory to the path you find there.
After restarting IDL, you can test to see if your path is set propertly by running cgHasImageMagick.If it returns 1, it has found ImageMagick. It will return a 0 if ImageMagick cannot be found.
In IDL 8.x it is possible that even if you install ImageMagick correctly, you will still have trouble spawning an ImageMagick command. The solution to thisproblem can be found in this article.
Version of IDL used to prepare this article: IDL 7.0.1.