Use the Application Editor to create Leginon applications » History » Version 13
Anchi Cheng, 12/18/2017 04:45 PM
1 | 8 | Anchi Cheng | h1. Use Application Editor in Leginon to create or edit Leginon applications |
---|---|---|---|
2 | 1 | Amber Herold | |
3 | 3 | Eric Hou | # Start a leginon session |
4 | |
||
5 | # Select Menu/Application/Edit...> to start a new application |
||
6 | |
||
7 | # Or Select Menu/Application/Load> to load an existing application for editing |
||
8 | |
||
9 | 6 | Anchi Cheng | # Save the application through Application/Save> or Save As> |
10 | |||
11 | h2. What you can do: |
||
12 | |||
13 | 9 | Anchi Cheng | h3. Create a new application based on an existing one |
14 | |||
15 | 12 | Anchi Cheng | h2. The reason for doing so is to keep settings separate among different scopes and camera, so that you don't have to change settings every time you switch scopes. Leginon settings are defined by the node class and the instance name (called node alias in Application Editor), not by application. Therefore, you can setup your presets in "Presets Manager" node of Calibrations application and then close that and get the same presets in "Presets Manager" node of MSI-T application. |
16 | |||
17 | 9 | Anchi Cheng | # Load the existing application |
18 | # Rename the application |
||
19 | # Make changes of node alias, binding and etc. |
||
20 | # *IMPORTANT* Left click Application/Save As> and check the application name before confirmation. |
||
21 | |||
22 | 11 | Anchi Cheng | h3. Rename an application, a launcher, or a node |
23 | 10 | Anchi Cheng | |
24 | 1 | Amber Herold | First selecting the item with left click and then click on it again to edit. |
25 | |||
26 | 13 | Anchi Cheng | h3. Use a different node class for an existing node alias |
27 | |||
28 | For example, you have a good Application that uses JAHCHoleFinder (the hole template finder). You want to replace the JAHCFinder of Exposure Targeting Node to RasterFinder class. |
||
29 | |||
30 | # left click the node in the application loaded in Application Editor |
||
31 | # right click on it to get Property dialog |
||
32 | # Select your desired Class field and accept it with OK button. |
||
33 | # left click on the Application name and change it. |
||
34 | # After the change, click on any other item so that gui register the change. |
||
35 | # Save the application from menu. |
||
36 | |||
37 | 9 | Anchi Cheng | h3. Add a Launcher. |
38 | 10 | Anchi Cheng | |
39 | 3 | Eric Hou | ** Right-click and hold on the name of the application to select "Add Launcher". |
40 | 1 | Amber Herold | ** Rename the launcher to your choice by selecting the launcher name with left click and then click on it again to edit |
41 | 10 | Anchi Cheng | |
42 | 1 | Amber Herold | h3. Add a node within a Launcher. |
43 | 10 | Anchi Cheng | |
44 | 3 | Eric Hou | !addnode.png! |
45 | 1 | Amber Herold | ** Right-click on the launcher to select "Add Node" |
46 | 3 | Eric Hou | ** Enter an descriptive Alias name for the node. For example, "Instrument" for the "EM" node. |
47 | 9 | Anchi Cheng | ** Choose the Node Class from the pull-down list. |
48 | 10 | Anchi Cheng | |
49 | 3 | Eric Hou | h3. Add Event Bindings between nodes. |
50 | 10 | Anchi Cheng | |
51 | 3 | Eric Hou | ** Right-click on the node the event binding is originated from to select "Bind Event..." |
52 | ** Add a Presets Manager node aliased as "pm" in the same launcher. |
||
53 | ** Select in the pull-down menu where the event is bound to under "To Node". |
||
54 | 2 | Amber Herold | ** Select the event to bind from the pull-down list of the valid event bindings. |
55 | |||
56 | 1 | Amber Herold | ______ |
57 | 2 | Amber Herold | |
58 | 7 | Anchi Cheng | [[Edit an existing application as an xml file|Edit an existing application as an xml file >]] |
59 | 2 | Amber Herold | |
60 | ______ |