Re: X window requirement for batch jobs: not just for plotting [message #78477] |
Wed, 23 November 2011 06:42  |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
Ed Hyer writes:
> So, we all know that if you have a job that generates a plot, and you
> need it to run automated, you have to either:
> 1) use the Z buffer for everything;
> 2) use the X virtual frame buffer to "spoof" an X terminal;
>
> But this requirement is clearly triggered by commands that have
> nothing to do with plotting. The obvious example is widgets, but I am
> currently dealing with a piece of code that has no plotting and no
> widgets, but at a certain point in the code it insists on having an X
> terminal available, and crashes if there is none.
>
> Tomorrow's job is to identify exactly what call is the culprit (I'm
> wondering if it isn't maybe READ_TIFF), and figure out a solution
> along the lines of #1 above, but I thought I'd ask:
>
> What other types of commands, that I wouldn't expect, might be asking
> for an X terminal?
Oh, my gosh, the list seems endless! Anything that has to
deal with device coordinates (coord_convert, etc.) comes
to mind. Anything that deals in any way with the OS.
Practically anything you write! I would look everywhere. ;-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
Re: X window requirement for batch jobs: not just for plotting [message #78528 is a reply to message #78477] |
Wed, 30 November 2011 12:10  |
MarioIncandenza
Messages: 231 Registered: February 2005
|
Senior Member |
|
|
Hi folks,
OK, I have done some debugging, and found that what is happening is
that a call to MESSAGE wants, for some reason, to use DIALOG_MESSAGE,
and it wants an X window despite an upstream call in the same routine,
with no graphics in between, to SET_PLOT,'Z'. Has anyone seen this
problem before?
Thanks in advance,
--Edward H.
|
|
|