comp.lang.idl-pvwave archive: archive » Re: spawn issue

Home » Public Forums » archive » Re: spawn issue - was: open sockets

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: spawn issue - was: open sockets [message #53097 is a reply to message #53096]

Wed, 21 March 2007 09:20

JD Smith
Messages: 850
Registered: December 1999

Senior Member

On Tue, 20 Mar 2007 19:35:39 +0100, Bringfried Stecklum wrote:

> It is clear now that the issue is unrelated to socket but in fact caused
> by multiple calls to spawn each of which opens a pipe to transfer the data
> like
>
> spawn,'ds9 stdin',unit=unit
> writefits,'/dev/null',image,header,unit=unit
>
> The problem is that after closing ds9 the pipe is still open. It seems
> there is no way to make IDL aware that the child process no longer exists.

DS9 uses XPA for passing all sorts of information indirectly via other
programs:

http://hea-www.harvard.edu/RD/ds9/ref/xpa.html

With it, you should be able to stuff data from IDL into a shared
memory segment, and point DS9 at that segment, setting up all view
parameters as well. Not only would this remove the pipe issues, it
would be much faster and more flexible as well.

JD

Report message to a moderator

[Message index]

		Re: spawn issue - was: open sockets By: JD Smith on Wed, 21 March 2007 10:35
		Re: spawn issue - was: open sockets By: Bringfried Stecklum on Wed, 21 March 2007 10:13
		Re: spawn issue - was: open sockets By: JD Smith on Wed, 21 March 2007 09:20
		Re: spawn issue - was: open sockets By: Bringfried Stecklum on Wed, 21 March 2007 06:39
		Re: spawn issue - was: open sockets By: Foldy Lajos on Tue, 20 March 2007 13:36

Previous Topic:	Re: Modis Georeferencing
Next Topic:	Re: Big arrays, reducing data

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 09:30:10 PDT 2025

Total time taken to generate the page: 0.79734 seconds