| Re: accessing IDL internal (aka "built-in") routines [message #87169 is a reply to message #87166] |
Mon, 13 January 2014 17:37   |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
Hi Luke,
Sorry for jumping the gun. I frequently have discussions with folks going through extreme efforts to save a buck or two while valuing their time far too little. I certainly underestimated the size of your problem!
I still believe that my assessment regarding the internal routines is right, so you will likely have to cook your own solution. I have no clue about your project, but have you checked whether GMT (The Generic Mapping Tool) available free at http://gmt.soest.hawaii.edu/ can help you?
Cheers,
Haje
On Monday, January 13, 2014 6:52:24 PM UTC-5, Luke Domanski wrote:
> On Tuesday, January 14, 2014 1:30:10 AM UTC+11, Haje Korth wrote:
>
>> As people say, you get what you pay for. Your time and effort required for solving this problem would likely exceed the cost of an IDL license. Life's too short, use your time wisely!
>
>
>
> Thanks Haje,
>
>
>
> 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.
>
>
>
> Short of solving this problem, or rewriting applicable portions of code using other languages or IDL functionality, there are few other options. Either of these options would still cost less in man hours, and be more valuable to us, than the cost of the number of IDL licences we would otherwise require.
>
>
>
> Luke (a colleague of Tom's)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
