Changes for page Experiment control
Last modified by fwilde on 2018/04/09 09:39
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - IDL at P05 userguide1 +Experiment control - Tags
-
... ... @@ -1,0 +1,1 @@ 1 +micro_ct - Content
-
... ... @@ -3,6 +3,8 @@ 3 3 {{layout-cell}} 4 4 == {{id name="Experimentcontrol-Generalremarks"/}}General remarks == 5 5 6 +This is a detailed description of the experiment control system. A short overview of the most commonly iused commands can be found [[here>>doc:P5I.User guide\: µCT at P05.Experiment control.IDL cheat sheet.WebHome]]. 7 + 6 6 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. 7 7 8 8 * IDL has a command history (use arrow keys to browse through recent commands) ... ... @@ -12,25 +12,109 @@ 12 12 13 13 {{code title="Procedures and functions"}}print, 'hello world.' 14 14 i=quick(300) 15 -{{/code}} 17 +{{/code}}\\ 16 16 ))) 17 17 * ((( 18 18 In IDL you can chain commands with the & sign 19 19 20 -{{code title="Chaining commands"}}i=quick(300) & tv, bytscl(bin(i,4),0,65000){{/code}} 22 +{{code title="Chaining commands"}}i=quick(300) & tv, bytscl(bin(i,4),0,65000){{/code}}\\ 21 21 ))) 22 22 * ((( 23 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 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}} 27 +{{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 26 ))) 27 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. 30 + 31 +== {{id name="Experimentcontrol-IDLMacroguide"/}}IDL Macro guide == 32 + 33 +=== {{id name="Experimentcontrol-AboutIDLmacros"/}}About IDL macros === 34 + 35 +To understand the macro naming convention it helps to categorize the the acors roughly into three categories: 36 + 37 +1. Motor macros 38 +1. Info macros 39 +1. Script macros 40 + 41 +==== {{id name="Experimentcontrol-MotorMacros"/}}Motor Macros ==== 42 + 43 +Motor macros loosely follow a certain naming convention according to the [[EH2 setup>>doc:P5I.User guide\: µCT at P05.µCT setup.WebHome]]: 44 + 45 +* ((( 46 +commands contain a name for the stage: 47 + 48 +(% class="wrapped" %) 49 +|=((( 50 +command particle 51 +)))|=((( 52 +stage 53 +))) 54 +|((( 55 +o_stage 56 +)))|((( 57 +camera stage 58 +))) 59 +|((( 60 +s_stage 61 +)))|((( 62 +rotation stage 63 +))) 64 +|((( 65 +s_pos 66 +)))|((( 67 +sample stage 68 +))) 69 +|((( 70 +app_tripod or app 71 +)))|((( 72 +base stage 73 +))) 74 +|((( 75 +o_ccd 76 +)))|((( 77 +camera housing 78 +))) 79 +|((( 80 +o 81 +)))|((( 82 +microscope optics 83 +))) 84 +))) 85 +* Most commands are followed by a direction or rotation axis (x,y,z, rot_x, rot_y, rot_z) 86 +* ((( 87 +A motor command moves either relative or absolute, e.g: 88 + 89 +{{code}}goto_s_stage_z, -10{{/code}}This moves the rotation stage to the position -10 mm in z direction. 90 + 91 + 92 + 93 +{{code}}s_stage_z, 1{{/code}}This example moves the rotation stage by 1 mm up in z direction. 94 +))) 95 + 96 +==== {{id name="Experimentcontrol-Infomacros"/}}Info macros ==== 97 + 98 +These are macros that return one more values which provide information about the state of e.g. a stage or a camera. 99 + 100 +==== {{id name="Experimentcontrol-Scriptmacros"/}}Script macros ==== 101 + 102 +Script macros are a collection of lower-level commands to perform a task. The most striking script macros is probably the scan macro, which perform a complete tomographic scan without any further interaction with the user. 28 28 {{/layout-cell}} 29 29 30 30 {{layout-cell}} 31 -{{panel titleBGColor="blue" title="Table ofContents"borderColor="blue" titleColor="white"}}106 +{{panel borderColor="blue" titleColor="white" titleBGColor="blue" title="Table of Contents"}} 32 32 {{toc/}} 33 33 {{/panel}} 109 + 110 +{{panel borderColor="red" titleColor="white" titleBGColor="red" title="todo"}} 111 +Attention: this user guide is yet very incomplete. 112 + 113 +(% class="task-list" %) 114 +((( 115 +{{task reference="/Tasks/Task_1" status="Done"}} 116 +Continue IDL at EH2 user guide {{mention reference="XWiki.fwilde" style="FULL_NAME" anchor="XWiki-fwilde-IXJaI"/}}\\ 117 +{{/task}} 118 +))) 119 +{{/panel}} 34 34 {{/layout-cell}} 35 35 {{/layout-section}} 36 36 {{/layout}}
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -3402 65831 +34023196 - Title
-
... ... @@ -1,1 +1,1 @@ 1 - IDL at P05 userguide1 +Experiment control - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://confluence.desy.de/spaces/P5I/pages/3402 6583/IDL at P05 userguide1 +https://confluence.desy.de/spaces/P5I/pages/34023196/Experiment control