| Re: IDL with command line like input, (in EFTS -EUMETSAT) [message #51905] |
Tue, 12 December 2006 03:48 |
Jo Klein
Messages: 54
Registered: January 2006
|
Member |
|
|
Hmm - seems your licensing isn't very robust? Things to try:
Add the license info to your batch:
@ECHO OFF
COPY /Y %1 C:\MYDATA.DAT
SET LM_LICENSE_FILE=1700@mylicenseserver
- or -
SET LM_LICENSE_FILE=c:\RSI\LICENSE\LICENSE.DAT
START /WAIT IDLDE @mybatch.pro
COPY /Y C:\MYOUTPUT.DAT %1
If that doesn't help, try START /WAIT CMD /C \path\to\IDLDE @mybatch.pro
instead of the old command, that should give you a properly set up
environment.
Cheers,
Jo
|
|
|
|
| Re: IDL with command line like input, (in EFTS -EUMETSAT) [message #51907 is a reply to message #51905] |
Tue, 12 December 2006 03:18  |
remkoxl
Messages: 5
Registered: March 2004
|
Junior Member |
|
|
Thanks Jo,
This is solution works(!) and indeed it isn't the neatest one, but
hey..
However, my license is not recognised anymore..
Wen running such a batch directly I encounter no problems at all. They
occur when I call the batch file from the EFTS package, then it opens a
demo version instead. All full path names are used.
Any suggestions how I can open the licensed version?
Remko
|
|
|
|
| Re: IDL with command line like input, (in EFTS -EUMETSAT) [message #51922 is a reply to message #51907] |
Mon, 11 December 2006 06:44 |
Jo Klein
Messages: 54
Registered: January 2006
|
Member |
|
|
Hi Remko,
An easy way to do this would be to use a batch command and a wrapper
script. Since command_line_args aren't available in older IDL versions
and you can't pipe in your commands with Windows versions (I still have
hopes that, one day, we'll have command line IDL for Windows), it may be
easiest to first copy (or move) the data EFTS generates to a
prespecified file name and run an IDL batch file with that file name
hard-coded.
So, you'd have a wrapper script wrap.bat that would go like this:
@ECHO OFF
COPY /Y %1 C:\MYDATA.DAT
START /WAIT IDLDE @mybatch.pro
COPY /Y C:\MYOUTPUT.DAT %1
This would put the data into some place for IDL, wait for it to finish,
and overwrite the data generated by EFTS with IDL's output (in case you
want to import the results back into that programme - I have no idea
what EFTS does).
mybatch.pro would contain something like
.run MYPROGRAM.PRO
EXIT,/NO_CONFIRM
I realise this is a bit through the nose, maybe someone else can provide
a more elegant solution.
Hope this helps,
Jo
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
