PDF (double-sided) - Physics Department, UCSB - University of ...
PDF (double-sided) - Physics Department, UCSB - University of ... PDF (double-sided) - Physics Department, UCSB - University of ...
7.5.3 DC Rack Server The DC Rack Server implements the binary protocol used by the different bias cards to provide access to all features offered by the cards. It allows other Modules in the LabRAD system to select active cards and change their settings, e.g. initialize the reference DAC on a PreAmp-Card, control the behavior of the front-panel LEDs, set the monitor channels, etc. One instance of this Server manages all DC bias racks that are accessible from the LabRAD system via Serial Servers that provide the actual hardware link. 7.5.4 Serial Server The Serial Server provides direct access to all COM-ports of the computer that it is running on. It can list the available ports, open a port by name, select connection options like the baud-rate, byte-size, and parity, and control the state of the RTS and DTR lines. One copy of this Server is run on every computer that needs to share access to its ports. To give each of these Server Modules a unique name, “Serial Server” is prefixed with the name of the computer that it is running on. 156
7.5.5 Grapher At the far left of the connection diagram (Figure 7.1), the Grapher Client Module gives the user a way to view datasets as they are taken or to browse existing datasets. It offers 1D and 2D plotting capability as well as zooming and basic curve fitting (exponentials and parabolas). The Grapher also provides access to meta-data that is stored with a dataset as well as a mechanism for annotating and discussing datasets that resembles an instant messaging chat session. Multiple copies of the Grapher can be run by different users to allow for live discussion of incoming data among collaborators located anywhere in the world. The Grapher accesses the data and meta-information of different dataset via calls to the “Data Vault” Server Module. Being able to provide powerful data plotting and analysis tools as a separate module rather than as a part of each data taking script significantly simplifies the development of these scripts and thus improves experimental turn-around times. Separating the plotting from the data acquisition and processing also allows for higher data rates as the usually CPU intensive plotting does not take resources away from the data taking. In fact, even over very slow network connections, the same data rates can be achieved in remote data taking sessions as from inside the lab. This is made possible by being able to run the bandwidth intense parts of the 157
- Page 134 and 135: 6.1 Physical Quality Control during
- Page 136 and 137: 6.1.3 Atomic Force Microscopy To re
- Page 138 and 139: Figure 6.1: 4-Wire Measurement - a)
- Page 140 and 141: 6.3 Quantum Measurements at 25 mK 6
- Page 142 and 143: seems to be a box machined out of s
- Page 144 and 145: Figure 6.2: Dilution Refrigerator W
- Page 146 and 147: cessing data. This protects the vol
- Page 148 and 149: 6.3.9 Anritsu Microwave Source The
- Page 150 and 151: 122
- Page 152 and 153: ment, the scalability requirements,
- Page 154 and 155: people without any formal training
- Page 156 and 157: 7.2.4 Performance Last, but certain
- Page 158 and 159: or a Client Module. Client Modules
- Page 160 and 161: second Module talks to all these an
- Page 162 and 163: puters to talk to each other. Usual
- Page 164 and 165: 7.3.4 Performance Addressing the Pe
- Page 166 and 167: is designed such that the LabRAD Ma
- Page 168 and 169: Table 7.3: LabRAD Type Annotations
- Page 170 and 171: listed in Table 7.3. For transmissi
- Page 172 and 173: Architecture to manage network conn
- Page 174 and 175: Manager. In fact, in our lab, the o
- Page 176 and 177: waiting for their completion. The C
- Page 178 and 179: mentation of pipelining and certain
- Page 180 and 181: Since the API guarantees that all R
- Page 182 and 183: one microwave line for X/Y-rotation
- Page 186 and 187: data taking on the lab servers and
- Page 188 and 189: keys and the ability to set Context
- Page 190 and 191: a certain time. 7.5.9 Optimizer Cli
- Page 192 and 193: ters read from different sub-direct
- Page 194 and 195: efore the execution of the sequence
- Page 196 and 197: can achieve very-close-to hardware
- Page 198 and 199: type to provide a one-stop location
- Page 200 and 201: 172
- Page 202 and 203: 8.1 Squid I/V Response As explained
- Page 204 and 205: a digital signal via the use of a c
- Page 206 and 207: energy landscape (see Chapter 2.2.3
- Page 208 and 209: Figure 8.3: Squid Steps Failure Mod
- Page 210 and 211: At this point, the squid ramp can b
- Page 212 and 213: starts to tunnel to the neighboring
- Page 214 and 215: Figure 8.5: General Bias Sequence -
- Page 216 and 217: Figure 8.7: Spectroscopy - a) Bias
- Page 218 and 219: Figure 8.8: Rabi Oscillation - a) B
- Page 220 and 221: ensemble with respect to each other
- Page 222 and 223: Figure 8.10: T 1 - a) Bias sequence
- Page 224 and 225: Figure 8.11: Ramsey - a) Bias seque
- Page 226 and 227: phase shift into the middle of the
- Page 228 and 229: photon excitation behaves similarly
- Page 230 and 231: is desirable to modularize the cont
- Page 232 and 233: sequence was run. This allows for t
7.5.5 Grapher<br />
At the far left <strong>of</strong> the connection diagram (Figure 7.1), the Grapher Client<br />
Module gives the user a way to view datasets as they are taken or to browse<br />
existing datasets. It <strong>of</strong>fers 1D and 2D plotting capability as well as zooming and<br />
basic curve fitting (exponentials and parabolas). The Grapher also provides access<br />
to meta-data that is stored with a dataset as well as a mechanism for annotating<br />
and discussing datasets that resembles an instant messaging chat session. Multiple<br />
copies <strong>of</strong> the Grapher can be run by different users to allow for live discussion <strong>of</strong><br />
incoming data among collaborators located anywhere in the world. The Grapher<br />
accesses the data and meta-information <strong>of</strong> different dataset via calls to the “Data<br />
Vault” Server Module.<br />
Being able to provide powerful data plotting and analysis tools as a separate<br />
module rather than as a part <strong>of</strong> each data taking script significantly simplifies the<br />
development <strong>of</strong> these scripts and thus improves experimental turn-around times.<br />
Separating the plotting from the data acquisition and processing also allows for<br />
higher data rates as the usually CPU intensive plotting does not take resources<br />
away from the data taking. In fact, even over very slow network connections, the<br />
same data rates can be achieved in remote data taking sessions as from inside the<br />
lab. This is made possible by being able to run the bandwidth intense parts <strong>of</strong> the<br />
157