Changes for page Experiment control

Last modified by fwilde on 2018/04/09 09:39
From version 2.1
edited by fwilde
on 2016/04/14 17:10
Change comment: There is no comment for this version
To version 5.1
edited by fwilde
on 2016/04/14 17:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,10 +3,22 @@
3 3  Beamline control at the P05 µCT hutch uses TANGO server as backend for most applications. At P05 the Interactive Data Language (IDL) serves as user interface to the TANGO servers. IDL procedures and functions provide the functionality to control the µCT experiment and beamline optics components conveniently. A couple of general remarks should facilitate to work with IDL at P05.
4 4  
5 5  * IDL has a command history (use arrow keys to browse through recent commands)
6 -* IDL has tab completion (start typing a command e.g. refl<TAB> to complete reflex_opt taken from the command history), Multiple presses on tab will browse through history commands staring with what you typed.
7 -* IDL makes a difference between PROCEDURES and FUNCTIONS. A procedure is a piece of code that is executed without delivering a return value
6 +* IDL has tab completion (start typing a command e.g. refl<TAB> to complete reflex_opt taken from the command history), Multiple presses on tab will browse through the filtered command history.
8 8  * (((
8 +IDL makes a difference between PROCEDURES and FUNCTIONS. A procedure is a piece of code that is executed without delivering a return value whereas a function does. A procedure's (optional) arguments are separated with commas. Functions need to be called with brackets and optionally a comma separated argument list inside the brackets.
9 +
10 +{{code title="Procedures and functions"}}print, 'hello world.'
11 +i=quick(300)
12 +{{/code}}
13 +)))
14 +* (((
9 9  In IDL you can chain commands with the & sign
10 10  
11 11  {{code title="Chaining commands"}}i=quick(300) & tv, bytscl(bin(i,4),0,65000){{/code}}
12 12  )))
19 +* (((
20 +When IDL is ready to accpt commands, the IDL> prompt is printed in a roman font. When IDL is busy doing something (e.g. waiting for a motor to end its move), the //IDL>// prompt is printed in  an italic font.
21 +
22 +{{info title="Warning"}}When IDL is busy, you **can** enter a new command, but it will not be executed until the last command is finished. In order to avoid confusion always wait until IDL is ready to accept commands before typing a new command.{{/info}}
23 +)))
24 +* Scripts can be written inside the IDL IDE and saved as .pro files. A script will not be automatically compiled after saving. Press the compile button in IDL in order to make changes in your code applicable.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -34023846
1 +34026562
URL
... ... @@ -1,1 +1,1 @@
1 -https://confluence.desy.de/spaces/P5I/pages/34023846/IDL@P05 user guide
1 +https://confluence.desy.de/spaces/P5I/pages/34026562/IDL@P05 user guide