| X window requirement for batch jobs: not just for plotting [message #78485] |
Tue, 22 November 2011 22:26  |
MarioIncandenza
Messages: 231
Registered: February 2005
|
Senior Member |
|
|
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?
--Edward H.
|
|
|
|
| Re: X window requirement for batch jobs: not just for plotting [message #78513 is a reply to message #78485] |
Wed, 30 November 2011 16:48  |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
On Nov 30, 3:10 pm, Ed Hyer <ejh...@gmail.com> wrote:
> 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?
If you're trying to do something in batch mode, (unattended without an
X-window server attached), I will wager that executing this command
unsetenv DISPLAY
(or it's equivalent in whatever shell you use), will prevent most of
these kinds of X-window problems.
Craig
|
|
|
|
| Re: X window requirement for batch jobs: not just for plotting [message #78517 is a reply to message #78485] |
Wed, 30 November 2011 13:34 |
Kenneth P. Bowman
Messages: 585
Registered: May 2000
|
Senior Member |
|
|
In article <MPG.2940469d26adf5b6989913@news.giganews.com>,
David Fanning <news@dfanning.com> wrote:
> Ed Hyer writes:
>
>> 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?
>
> I've seen the problem many times, but not this particular
> manifestation of it. I'm not terribly surprised, though,
> are you? This is a graphics program that is designed to
> be run on a graphics computer. Why wouldn't you assume
> there might be a graphics window around when you needed
> one?
>
> Cheers,
>
> David
I don't know. This seems like a bug to me. When I call MESSAGE
I expect it to print a message on the command line. I can't find
anything in the MESSAGE man page about calling DIALOG_MESSAGE.
Ed, are you calling MESSAGE yourself, or is this in a built-in
routine?
Ken
|
|
|
|
| Re: X window requirement for batch jobs: not just for plotting [message #78522 is a reply to message #78485] |
Wed, 30 November 2011 12:57 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Ed Hyer writes:
> 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?
I've seen the problem many times, but not this particular
manifestation of it. I'm not terribly surprised, though,
are you? This is a graphics program that is designed to
be run on a graphics computer. Why wouldn't you assume
there might be a graphics window around when you needed
one?
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 #78649 is a reply to message #78513] |
Thu, 01 December 2011 15:44 |
MarioIncandenza
Messages: 231
Registered: February 2005
|
Senior Member |
|
|
On Nov 30, 4:48 pm, Craig Markwardt <craig.markwa...@gmail.com> wrote:
> If you're trying to do something in batch mode, (unattended without an
> X-window server attached), I will wager that executing this command
> unsetenv DISPLAY
Craig,
Yes! As I learned, from doing a longer search that yielded the LAST
time you came up with this correct answer:
http://groups.google.com/group/comp.lang.idl-pvwave/browse_t hread/thread/dad37fe63c582ea0/e1e6afcde66b9503?hl=en&lnk =gst&q=runtime+silent+bowman#e1e6afcde66b9503
For everyone's reference, the key here is that the RUNTIME invocation
of IDL "-rt" changes the behavior of MESSAGE and calls DIALOG_MESSAGE
instead. This behavior is not anywhere in the IDL documentation, as
far as I can tell.
Thanks for your help, both then and now!
--Edward H.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
