| Re: Using IDL via MacX Macintosh server [message #2084] |
Tue, 17 May 1994 14:35  |
8015
Messages: 52
Registered: November 1993
|
Member |
|
|
In article <tonym.1119587059A@llyene.jpl.nasa.gov>,
Tony Mannucci <tonym@lurleen.jpl.nasa.gov> wrote:
> Frequenct crashes
Well, it's not a whole lot of words, but it says plenty...
Anyway, here are some of the things that I do while trying to keep MacX and
IDL from killing each other (and me from killing either of them):
1. Do my best not to exit IDL. Unfortunately, some things seem to be
unrecoverable and cannot be remedied with the "retall" and
"xmanager" calls.
. Switch to eXodus. (unconfirmed)
A. Remove "device" calls in $IDL_STARTUP.
3) Don't develop using widgets, images or graphics.
- Remove "loadct" calls when not needed. I used to use them to put
the color map in a known state. Now, I hope it comes up in a decent
state. It's especially frightening when it comes up in Indiana.
ii. Go the MacOS and reset the monitors control panel to set the
Macintosh color map to a known state.
o Kick someone off of the Unix system and use that until I get a
particularly troublesome piece of graphics code working.
I. Develop colorful language for when all of the above makes no
difference and the all-mighty computer gods decide I need a break.
Some or none of this works, it's hard to tell. I think it helps, but
maybe that's because I want to pretend I have a little control over
what's happening. I can confirm that the last one works quite well.
Mike Schienle Hughes Santa Barbara Research Center
mgs@sbjse0.sbrc.hac.com 75 Coromar Drive, M/S B28/87
Voice: (805)562-7466 Fax: (805)562-7881 Goleta, CA 93117
|
|
|
|
| Re: Using IDL via MacX Macintosh server [message #2136 is a reply to message #2084] |
Wed, 25 May 1994 06:47  |
fredrick
Messages: 5
Registered: February 1994
|
Junior Member |
|
|
In article <2rbdas$aes@hacgate2.hac.com> 8015@sbjse0.sbrc.hac.com (Mike Schienle) writes:
> In article <tonym.1119587059A@llyene.jpl.nasa.gov>,
> Tony Mannucci <tonym@lurleen.jpl.nasa.gov> wrote:
>> Frequenct crashes
>
> Well, it's not a whole lot of words, but it says plenty...
>
> Anyway, here are some of the things that I do while trying to keep MacX and
> IDL from killing each other (and me from killing either of them):
>
> 1. Do my best not to exit IDL. Unfortunately, some things seem to be
> unrecoverable and cannot be remedied with the "retall" and
> "xmanager" calls.
>
> . Switch to eXodus. (unconfirmed)
We switched to eXodus for this and other reasons and have enjoyed success
as far as the IDL/Mac crashes go. However, the important thing seems to
be not to use the window manager that comes with either MacX, eXodus, or
in the case of PC's, XVision. Rather, we run "mwm" from the server which
runs IDL -- once we started doing that we haven't experienced a single IDL
related crash.
> 3) Don't develop using widgets, images or graphics.
We are able to develop using widgets, images, and so forth with eXodus
running "mwm" from the UNIX server.
> I. Develop colorful language for when all of the above makes no
> difference and the all-mighty computer gods decide I need a break.
I still use #I liberally :-) but can no longer blame the Macintosh
environment for my IDL programs' failures.
--Tim Fredrick (fredrick@acd.ucar.edu)
Ntl Center for Atmospheric Research, Boulder, CO 80307-1000
|
|
|
|
| Re: Using IDL via MacX Macintosh server [message #2149 is a reply to message #2136] |
Wed, 25 May 1994 09:19 |
tonym
Messages: 14
Registered: May 1994
|
Junior Member |
|
|
In Article <2rvksv$3vu@ncar.ucar.edu>, fredrick@acd.ucar.edu (Timothy
Fredrick) wrote:
>
> We switched to eXodus for this and other reasons and have enjoyed success
> as far as the IDL/Mac crashes go. However, the important thing seems to
> be not to use the window manager that comes with either MacX, eXodus, or
> in the case of PC's, XVision. Rather, we run "mwm" from the server which
> runs IDL -- once we started doing that we haven't experienced a single IDL
> related crash.
>
I received a message from another person from NCAR confirming the robust
performance of eXodus. This person also reported crashes with MacX 1.1.7,
which has been deemed more robust than 1.2 (see the postings).
At JPL we have a site license for MacX, but in this case I think we'll
give eXodus a try. We actually were using it some years ago but found
its performance unsatisfactory. I've heard there have been major upgrades
since then...
Tony Mannucci Jet Propulsion Laboratory
tonym@lurleen.jpl.nasa.gov 4800 Oak Grove Drive
M/S 238-600
Voice: (818)354-1699 Fax: (818)393-4965 Pasadena, CA 91109
|
|
|
|
| Re: Using IDL via MacX Macintosh server [message #2957 is a reply to message #2084] |
Wed, 19 October 1994 15:29 |
tonym
Messages: 14
Registered: May 1994
|
Junior Member |
|
|
In Article <2rbdas$aes@hacgate2.hac.com>, 8015@sbjse0.sbrc.hac.com (Mike
Schienle) wrote:
> In article <tonym.1119587059A@llyene.jpl.nasa.gov>,
> Tony Mannucci <tonym@lurleen.jpl.nasa.gov> wrote:
>> Frequenct crashes
>
> Well, it's not a whole lot of words, but it says plenty...
>
> Anyway, here are some of the things that I do while trying to keep MacX and
> IDL from killing each other (and me from killing either of them):
>
> 1. Do my best not to exit IDL. Unfortunately, some things seem to be
> unrecoverable and cannot be remedied with the "retall" and
> "xmanager" calls.
>
> . Switch to eXodus. (unconfirmed)
>
> A. Remove "device" calls in $IDL_STARTUP.
>
> 3) Don't develop using widgets, images or graphics.
>
> - Remove "loadct" calls when not needed. I used to use them to put
> the color map in a known state. Now, I hope it comes up in a decent
> state. It's especially frightening when it comes up in Indiana.
>
> ii. Go the MacOS and reset the monitors control panel to set the
> Macintosh color map to a known state.
>
> o Kick someone off of the Unix system and use that until I get a
> particularly troublesome piece of graphics code working.
>
> I. Develop colorful language for when all of the above makes no
> difference and the all-mighty computer gods decide I need a break.
>
> Some or none of this works, it's hard to tell. I think it helps, but
> maybe that's because I want to pretend I have a little control over
> what's happening. I can confirm that the last one works quite well.
>
> Mike Schienle Hughes Santa Barbara Research Center
> mgs@sbjse0.sbrc.hac.com 75 Coromar Drive, M/S B28/87
> Voice: (805)562-7466 Fax: (805)562-7881 Goleta, CA 93117
Tony Mannucci Jet Propulsion Laboratory
tonym@lurleen.jpl.nasa.gov 4800 Oak Grove Drive
M/S 238-600
Voice: (818)354-1699 Fax: (818)393-4965 Pasadena, CA 91109
|
|
|
|
| Re: Using IDL via MacX Macintosh server [message #3145 is a reply to message #2957] |
Wed, 09 November 1994 16:09 |
lindaas
Messages: 3
Registered: December 1992
|
Junior Member |
|
|
I run IDL while on my PowerMAC running MacX and have had no real problems.
I used the Mark Rivers test and ran the IDL tour in the xdemo and had no
problem.
Particulars:
IDL 3.6.1a
System 7.5
MacX 1.2 -this is not accelerated.. :(
I let MacX grab 6M of RAM (it usually is only using 2M) but when
I only had 8M of RAM I ran out of memory (with a couple other
apps open) and this caused problems.
Anyways, I thought I would add my belated $0.02 worth.. :)
Steve
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
