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

Home » Public Forums » archive » accessing IDL internal (aka "built-in") routines
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: accessing IDL internal (aka "built-in") routines [message #87175 is a reply to message #87166] Tue, 14 January 2014 04:32 Go to previous messageGo to previous message
Yngvar Larsen is currently offline  Yngvar Larsen
Messages: 134
Registered: January 2010
Senior Member
On Tuesday, 14 January 2014 00:52:24 UTC+1, Luke Domanski wrote:
> On Tuesday, January 14, 2014 1:30:10 AM UTC+11, Haje Korth wrote:

> But unfortunately your reasoning is not entirely applicable in this case. We have plenty of IDL licenses, just not enough :). The built-in parallel capabilities of IDL are insufficient for addressing the size of the problem being solved, and processing using any sensible number of IDL licenses would still consume an in-feasible amount of time.

I'm curious: since you claim to use several IDL licenses for one "parallel job", you are not using the "idl_idlbridge"? If not: why? Or rather: what limitation of idl_idlbridge is the bottleneck for you?

--
Yngvar
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: h5_parse without READ_DATA
Next Topic: name a variable with number

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

Current Time: Wed Oct 08 17:54:08 PDT 2025

Total time taken to generate the page: 0.00449 seconds