|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91047 is a reply to message #91038] |
Wed, 27 May 2015 23:44   |
MariLiza
Messages: 8
Registered: December 2011
|
Junior Member |
|
|
On Wednesday, May 27, 2015 at 3:08:09 PM UTC+3, David Fanning wrote:
> Mari Liza writes:
>
>> Do you know if it is possible to always use the same workspace for ALL IDL instances? for all loadings of IDL? so that IDL does not prompt me all the time for a new workspace?
>
> Uh, as far as I know, that's what the rest of us always do.
>
> What's amazing to me is how you ever got into a situation where you are
> using dozens of them. I must be having a failure of the imagination,
> because I can't even come up with a plausible explanation for how such a
> thing could happen. :-(
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
Dear David,
Do you mean to tell me that you are able to simultaneously load two, three, four different IDL 8.0 onwards in WINDOWS and not have IDL ask you for a new workspace each time?
PLEASE tell me how to set this up, I have tried everything, unclicked all sorts of "refresh workspace at start-up", "prompt for workspace at start-up", I have asked IDL to keep in memory 30 different workspaces, but nothing works. If IDL is running once, then from the second instance onwards it asks for a new workspace.
This includes running save files simultaneously.
Thank you!
MariLiza
|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91048 is a reply to message #91047] |
Thu, 28 May 2015 00:21 |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Thursday, May 28, 2015 at 8:44:14 AM UTC+2, Mari Liza wrote:
> On Wednesday, May 27, 2015 at 3:08:09 PM UTC+3, David Fanning wrote:
>> Mari Liza writes:
>>
>>> Do you know if it is possible to always use the same workspace for ALL IDL instances? for all loadings of IDL? so that IDL does not prompt me all the time for a new workspace?
>>
>> Uh, as far as I know, that's what the rest of us always do.
>>
>> What's amazing to me is how you ever got into a situation where you are
>> using dozens of them. I must be having a failure of the imagination,
>> because I can't even come up with a plausible explanation for how such a
>> thing could happen. :-(
>>
>> Cheers,
>>
>> David
>> --
>> David Fanning, Ph.D.
>> Fanning Software Consulting, Inc.
>> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
>
>
> Dear David,
>
> Do you mean to tell me that you are able to simultaneously load two, three, four different IDL 8.0 onwards in WINDOWS and not have IDL ask you for a new workspace each time?
>
> PLEASE tell me how to set this up, I have tried everything, unclicked all sorts of "refresh workspace at start-up", "prompt for workspace at start-up", I have asked IDL to keep in memory 30 different workspaces, but nothing works. If IDL is running once, then from the second instance onwards it asks for a new workspace.
>
> This includes running save files simultaneously.
>
> Thank you!
> MariLiza
Hi,
I'll jump in without knowing exactly what David meant, so I'll speak for myself.
*why* do you need to start more that one IDLDE session?
So here is my way of doing things. The idlde (development environment or simply DE) is made to develop code. And to develop code, one DE with one workspace is more than enough (at least for me!). If you have more persons developing code together then they will be using different PCs and you will need to manage revison/version control.
To *run* code you have *also* other options:
1) the development environment of course
2) the idl_idlbridge to run more that one process at the same time (see http://www.exelisvis.com/docs/IDL_IDLBridge.html)
3) the idl virtual machine or VM can run .sav files ( http://www.exelisvis.com/docs/StartingVirtualMachineApplicat ion.html)
4) the command prompt in windows is also another option and does not require a workspace and you can run multiple instances.
That said, here is how I use the above. I normally write code in the DE, test it or execute it within the DE and execute the final product (.sav) in the VM. In the VM I can run as many processes as I want. The idl_idlbridge is a little bit more tricky and there are loads of posts describing what it is useful and not useful for.
Hope it helps.
Cheers,
Helder
|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91049 is a reply to message #91048] |
Thu, 28 May 2015 01:29 |
MariLiza
Messages: 8
Registered: December 2011
|
Junior Member |
|
|
Hi Helder,
Thanks for the reply.
I think one of my problems might be solved with the VM hint you gave me for the save files, I just realised that the save files kept being opened with the idlde.exe and not the idlrt.exe [I run them automatically from the command line, from a little script].
Don't ask why! I am checking right now whether this finally resolves the issue.
As to your other question, well, I am used to working on a piece of code, setting it to run to check it works, getting started on another piece of code while waiting, and so on. Hence the need for multuple IDLDE sessions.
Plus we are three people working on the same windows 2008 server, but since we are all logged in from a different account, that is no problem for IDL.
Many thanks,
MariLiza
>
> Hi,
> I'll jump in without knowing exactly what David meant, so I'll speak for myself.
>
> *why* do you need to start more that one IDLDE session?
>
> So here is my way of doing things. The idlde (development environment or simply DE) is made to develop code. And to develop code, one DE with one workspace is more than enough (at least for me!). If you have more persons developing code together then they will be using different PCs and you will need to manage revison/version control.
>
> To *run* code you have *also* other options:
> 1) the development environment of course
> 2) the idl_idlbridge to run more that one process at the same time (see http://www.exelisvis.com/docs/IDL_IDLBridge.html)
> 3) the idl virtual machine or VM can run .sav files ( http://www.exelisvis.com/docs/StartingVirtualMachineApplicat ion.html)
> 4) the command prompt in windows is also another option and does not require a workspace and you can run multiple instances.
>
> That said, here is how I use the above. I normally write code in the DE, test it or execute it within the DE and execute the final product (.sav) in the VM. In the VM I can run as many processes as I want. The idl_idlbridge is a little bit more tricky and there are loads of posts describing what it is useful and not useful for.
>
> Hope it helps.
>
> Cheers,
> Helder
|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91050 is a reply to message #91049] |
Thu, 28 May 2015 03:11 |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Thursday, May 28, 2015 at 10:29:34 AM UTC+2, Mari Liza wrote:
> Hi Helder,
>
> Thanks for the reply.
>
> I think one of my problems might be solved with the VM hint you gave me for the save files, I just realised that the save files kept being opened with the idlde.exe and not the idlrt.exe [I run them automatically from the command line, from a little script].
>
> Don't ask why! I am checking right now whether this finally resolves the issue.
>
> As to your other question, well, I am used to working on a piece of code, setting it to run to check it works, getting started on another piece of code while waiting, and so on. Hence the need for multuple IDLDE sessions.
>
> Plus we are three people working on the same windows 2008 server, but since we are all logged in from a different account, that is no problem for IDL.
>
> Many thanks,
> MariLiza
>
>
>
>
>
>
>
>>
>> Hi,
>> I'll jump in without knowing exactly what David meant, so I'll speak for myself.
>>
>> *why* do you need to start more that one IDLDE session?
>>
>> So here is my way of doing things. The idlde (development environment or simply DE) is made to develop code. And to develop code, one DE with one workspace is more than enough (at least for me!). If you have more persons developing code together then they will be using different PCs and you will need to manage revison/version control.
>>
>> To *run* code you have *also* other options:
>> 1) the development environment of course
>> 2) the idl_idlbridge to run more that one process at the same time (see http://www.exelisvis.com/docs/IDL_IDLBridge.html)
>> 3) the idl virtual machine or VM can run .sav files ( http://www.exelisvis.com/docs/StartingVirtualMachineApplicat ion.html)
>> 4) the command prompt in windows is also another option and does not require a workspace and you can run multiple instances.
>>
>> That said, here is how I use the above. I normally write code in the DE, test it or execute it within the DE and execute the final product (.sav) in the VM. In the VM I can run as many processes as I want. The idl_idlbridge is a little bit more tricky and there are loads of posts describing what it is useful and not useful for.
>>
>> Hope it helps.
>>
>> Cheers,
>> Helder
Hi,
I'm the last guy to ask about this, but there are in the DE (under Window->Source Control Tools) some you will find some tools to help you develop code together with others. More info here:
http://www.exelisvis.com/docs/IDL_Features_to_Help_You_Devel op_Code.html
I would then recommend to modify your code in the IDLDE, compile it (generate a new sav) and run it by double clicking it or with a .bat or from the IDL command line. This should solve a lot of the problems you're having.
Good luck,
Helder
|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91051 is a reply to message #91047] |
Thu, 28 May 2015 03:34 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Mari Liza writes:
> Do you mean to tell me that you are able to simultaneously load two, three, four different IDL 8.0 onwards in WINDOWS and not have IDL ask you for a new workspace each time?
No, I never run two, three, or four different IDL sessions
simultaneously. I run one IDL session continuously for weeks and weeks
at a time. :-)
I've never run more than one IDL session. Nor, with the possible
exception of wanting to do something on the IDL_Bridge (which I have
never used in any real way), can I think of any reason why I would want
to run simultaneous IDL sessions. It has just never come up for me as
something I needed to do.
> PLEASE tell me how to set this up, I have tried everything, unclicked all sorts of "refresh workspace at start-up", "prompt for workspace at start-up", I have asked IDL to keep in memory 30 different workspaces, but nothing works. If IDL is running once, then from the second instance onwards it asks for a new workspace.
I just installed IDL. That's it. I didn't "do" anything to set it up.
That's just how it has always worked from the get-go.
> This includes running save files simultaneously.
Yeah, I never use save files, either. I find them confounding. In the
many years I've worked with IDL, I've found that people who use save
files are among the most confused of IDL's users. Except for saving
data, I'm not clear what (if any) their advantages are.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91052 is a reply to message #91051] |
Thu, 28 May 2015 06:41 |
MariLiza
Messages: 8
Registered: December 2011
|
Junior Member |
|
|
> Yeah, I never use save files, either. I find them confounding. In the
> many years I've worked with IDL, I've found that people who use save
> files are among the most confused of IDL's users. Except for saving
> data, I'm not clear what (if any) their advantages are.
Hello David,
So when you wish to run two, three, ten, twenty different IDL programs sequentially [or simultaneously] you write a script that launches IDL and run the *.pro file directly?
well, ok, whatever works, I guess! ;-)
I was just used to the save files, I would set the script to run them and then go home and then next morning I would have the analyses/plots/statistics ready.
Many many thanks
MariLiza
|
|
|
|
| Re: IDL 8.0 onwards: can I always use the same workspace? [message #91054 is a reply to message #91052] |
Thu, 28 May 2015 07:28 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Mari Liza writes:
> So when you wish to run two, three, ten, twenty different IDL programs sequentially [or simultaneously] you write a script that launches IDL and run the *.pro file directly?
> well, ok, whatever works, I guess! ;-)
> I was just used to the save files, I would set the script to run them and then go home and then next morning I would have the analyses/plots/statistics ready.
Ah, yes, I did it that way in the 1980s. Submitted my card deck to the
computer center, and picked up the results (almost always wrong!) the
next morning. Over and over until I finally got it right. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
