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.
>From: "Alliss, Randall J." <address@hidden> >Organization: TASC >Keywords: 199907221406.IAA22360 McIDAS DEC Alpha Randy, >Regarding the running of McIDAS 7.6 on your Dec-Alphas have you noticed any >odd behaviour specifically dealing with graphics issues. For example, i have >a looper set up to load the most recent GOES8 image in a 5 hour series of >images. On all occassions the scheduler will load new images however, the >mcidas window becomes black or empty for that frame and i can never use that >frame again to load an image. I have to restart mcidas every time. I do not >get this condition on my IBM AIX box. >Any comments? I have not experienced this problem, but my use of a DEC is limited (I typically run on either Solaris, Solarisx86, AIX, or Linux). I do have a site that recently loaded on an Alpha, and I have not heard about any problems from him. The problem you describe sounds like some portion of memory is getting stepped on. Have you ascertained whether or not it makes a difference which frames are used for the display? >thanks, Sorry I can't be of more help. Unfortunately, I am on travel until Thursday, so I can't even try to duplicate your problem. Tom >From address@hidden Wed Oct 6 05:26:58 1999 Tom, It does not matter what frames i use. Typically i have a LB of 1 15 which gets updated every 15 minutes with new GOES imagery. Ultimately each frame gets wiped out! I do not have such a problem on my AIX box. I am thinking it may have something to do with the graphics cards on these 2 Alphas cause my older Alphas (600 series) which different cards do not have the same problem. Randy