comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: spawn issue - was: open sockets
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: spawn issue - was: open sockets [message #53096 is a reply to message #53094] Wed, 21 March 2007 10:13 Go to previous messageGo to previous message
Bringfried Stecklum is currently offline  Bringfried Stecklum
Messages: 75
Registered: January 1996
Member
Dear JD,

thanks for this advice. I am using the XPA interface for various
purposes but did not try the shm command yet. I agree that it will be
much faster. So I'll give it a try.

regards,

Bringfried

JD Smith wrote:
> 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
>
>
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Modis Georeferencing
Next Topic: Re: Big arrays, reducing data

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Oct 09 20:37:50 PDT 2025

Total time taken to generate the page: 0.23826 seconds