Changes for page Experiment control

Last modified by fwilde on 2018/04/09 09:39
From version 3.1
edited by fwilde
on 2016/04/14 17:15
Change comment: There is no comment for this version
To version 10.1
edited by fwilde
on 2016/04/19 17:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -IDL@P05 user guide
1 +IDL at EH2 user guide
Content
... ... @@ -1,3 +1,6 @@
1 +{{layout}}
2 +{{layout-section ac:type="two_right_sidebar"}}
3 +{{layout-cell}}
1 1  == {{id name="Experimentcontrol-Generalremarks"/}}General remarks ==
2 2  
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.
... ... @@ -16,3 +16,84 @@
16 16  
17 17  {{code title="Chaining commands"}}i=quick(300) & tv, bytscl(bin(i,4),0,65000){{/code}}
18 18  )))
22 +* (((
23 +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.
24 +
25 +{{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}}
26 +)))
27 +* 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.
28 +
29 +== {{id name="Experimentcontrol-IDLMacroguide"/}}IDL Macro guide ==
30 +
31 +=== {{id name="Experimentcontrol-AboutIDLmacros"/}}About IDL macros ===
32 +
33 +To understand the macro naming convention it helps to categorize the the acors roughly into three categories:
34 +
35 +1. Motor macros
36 +1. Info macros
37 +1. Script macros
38 +
39 +==== {{id name="Experimentcontrol-MotorMacros"/}}Motor Macros ====
40 +
41 +Motor macros loosely follow a certain naming convention according to the [[EH2 setup>>doc:P5I.µCT setup overview.WebHome]]:
42 +
43 +* (((
44 +commands contain a name for the stage:
45 +
46 +|=(((
47 +command particle
48 +)))|=(((
49 +stage
50 +)))
51 +|(((
52 +o_stage
53 +)))|(((
54 +camera stage
55 +)))
56 +|(((
57 +s_stage
58 +)))|(((
59 +rotation stage
60 +)))
61 +|(((
62 +s_pos
63 +)))|(((
64 +sample stage
65 +)))
66 +|(((
67 +app_tripod or app
68 +)))|(((
69 +base stage
70 +)))
71 +|(((
72 +o_ccd
73 +)))|(((
74 +camera housing
75 +)))
76 +|(((
77 +o
78 +)))|(((
79 +microscope optics
80 +)))
81 +)))
82 +* Most commands are followed by a direction or rotation axis (x,y,z, rot_x, rot_y, rot_z)
83 +* (((
84 +A motor command moves either relative or absolute, e.g:
85 +
86 +{{code}}goto_s_stage_z, -10{{/code}}This moves the rotation stage to the position -10 mm in z direction.
87 +
88 +
89 +
90 +{{code}}s_stage_z, 1{{/code}}This example moves the rotation stage by 1 mm up in z direction.
91 +)))
92 +
93 +
94 +{{/layout-cell}}
95 +
96 +{{layout-cell}}
97 +{{panel titleBGColor="blue" title="Table of Contents" borderColor="blue" titleColor="white"}}
98 +{{toc/}}
99 +{{/panel}}
100 +{{/layout-cell}}
101 +{{/layout-section}}
102 +{{/layout}}
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -34023852
1 +34026591
Title
... ... @@ -1,1 +1,1 @@
1 -IDL@P05 user guide
1 +IDL at EH2 user guide
URL
... ... @@ -1,1 +1,1 @@
1 -https://confluence.desy.de/spaces/P5I/pages/34023852/IDL@P05 user guide
1 +https://confluence.desy.de/spaces/P5I/pages/34026591/IDL at EH2 user guide