| accessing IDL internal (aka "built-in") routines [message #87160] |
Sun, 12 January 2014 21:11  |
Tom Van Niel
Messages: 4
Registered: February 2012
|
Junior Member |
|
|
Hi All,
Has anybody figured out how to access internal IDL routines?
More specifically, I am trying to run MAP_PROJ_INIT in GDL, but get the following error:
“MAP_PROJ_INIT: Procedure not found: MAP_PROJ_GCTP_FORINIT”
MAP_PROJ_INIT.pro calls MAP_PROJ_GCTP_FORINIT on line 1195, which turns out to be an internal IDL code (which obviously has not been translated into GDL). I've tried things like "Routine_Info", and "which" to find out the location of MAP_PROJ_GCTP_FORINIT, but with no luck. I guess internal files are embedded in the executable.
If anybody has found a way to access internal routines or by chance has a copy of MAP_PROJ_GCTP_FORINIT, please let me know.
Regards,
Tom
|
|
|
|
| Re: accessing IDL internal (aka "built-in") routines [message #87162 is a reply to message #87160] |
Mon, 13 January 2014 06:23  |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
There are a number of low-level routines of the map projection engine in a DLM. Without special skills, you have no change of getting at those, and you would probably be on soft legal grounds if you could. As people say, you get what you pay for. The 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!
On Monday, January 13, 2014 12:11:44 AM UTC-5, Tom Van Niel wrote:
> Hi All,
>
>
>
> Has anybody figured out how to access internal IDL routines?
>
>
>
> More specifically, I am trying to run MAP_PROJ_INIT in GDL, but get the following error:
>
>
>
> “MAP_PROJ_INIT: Procedure not found: MAP_PROJ_GCTP_FORINIT”
>
>
>
> MAP_PROJ_INIT.pro calls MAP_PROJ_GCTP_FORINIT on line 1195, which turns out to be an internal IDL code (which obviously has not been translated into GDL). I've tried things like "Routine_Info", and "which" to find out the location of MAP_PROJ_GCTP_FORINIT, but with no luck. I guess internal files are embedded in the executable.
>
>
>
> If anybody has found a way to access internal routines or by chance has a copy of MAP_PROJ_GCTP_FORINIT, please let me know.
>
>
>
> Regards,
>
> Tom
|
|
|
|
| Re: accessing IDL internal (aka "built-in") routines [message #87163 is a reply to message #87160] |
Mon, 13 January 2014 06:30 |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
There are a number of low-level routines of the map projection engine in a DLM. Without special skills, you have no chance of getting at those, and you would probably be on soft legal grounds if you could. 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!
On Monday, January 13, 2014 12:11:44 AM UTC-5, Tom Van Niel wrote:
> Hi All,
>
>
>
> Has anybody figured out how to access internal IDL routines?
>
>
>
> More specifically, I am trying to run MAP_PROJ_INIT in GDL, but get the following error:
>
>
>
> “MAP_PROJ_INIT: Procedure not found: MAP_PROJ_GCTP_FORINIT”
>
>
>
> MAP_PROJ_INIT.pro calls MAP_PROJ_GCTP_FORINIT on line 1195, which turns out to be an internal IDL code (which obviously has not been translated into GDL). I've tried things like "Routine_Info", and "which" to find out the location of MAP_PROJ_GCTP_FORINIT, but with no luck. I guess internal files are embedded in the executable.
>
>
>
> If anybody has found a way to access internal routines or by chance has a copy of MAP_PROJ_GCTP_FORINIT, please let me know.
>
>
>
> Regards,
>
> Tom
|
|
|
|
| Re: accessing IDL internal (aka "built-in") routines [message #87166 is a reply to message #87163] |
Mon, 13 January 2014 15:52 |
luke.a.domanski
Messages: 6
Registered: January 2014
|
Junior Member |
|
|
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)
|
|
|
|
| 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)
|
|
|
|
| Re: accessing IDL internal (aka "built-in") routines [message #87170 is a reply to message #87169] |
Mon, 13 January 2014 18:55 |
luke.a.domanski
Messages: 6
Registered: January 2014
|
Junior Member |
|
|
On Tuesday, January 14, 2014 12:37:44 PM UTC+11, Haje Korth wrote:
> Hi Luke,
>
> Sorry for jumping the gun.
That's okay, thanks for the tip on GMT, we will look into it.
The code that calls MAP_PROJ_INIT is part a preprocessing step, and while fairly fast compared to the main simulation/number crunching, has a high memory or data requirement when considering the scale of problem we will be addressing.
As a work around if we cant find an alternative, we will probably run the faster preprocessing code in parallel over fewer IDL instances/licenses, then run the more time consuming simulation over a far greater number of GDL instances. Each IDL instance will then produce preprocessed results for multiple GDL instances...we will just need to schedule things careful as not to exhaust all or disk space storing TBs of intermediate files.
|
|
|
|
|
|
|
|
|
|
|
|
| Re: accessing IDL internal (aka "built-in") routines [message #87383 is a reply to message #87382] |
Thu, 30 January 2014 04:32 |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
Tom,
I am glad you found a solution. Thank you for sharing it with us.
Good luck,
Haje
On Thursday, January 30, 2014 1:08:50 AM UTC-5, mookie...@gmail.com wrote:
> Hi Everyone,
>
>
>
> Thanks Haje, Luke, and Mike for posting on this topic. The solution we came up with turns out to be quite simple. We installed GDAL and access 'gdalwarp' using 'spawn' from GDL, thus bypassing the need to use IDL internal routines for re-projecting altogether. For example from the GDL prompt to re-project a MODIS image from geographic projection (Lat/Lons) to GDA94 MGA Zone 55 (i.e., ~ UTM 55S):
>
>
>
> GDL> infn = '/tmp/MOD09GA.hdf'
>
> GDL> outfn = '/tmp/MOD09GA_MGA55.tif'
>
> GDL> EPSG='EPSG:28355'
>
> GDL> spawn, 'gdalwarp -t_srs '+ EPSG + ' '+infn + ' ' + outfn
>
>
>
> Cheers,
>
> Tom
|
|
|
|
|
|
|
|
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
