PDF (double-sided) - Physics Department, UCSB - University of ...
PDF (double-sided) - Physics Department, UCSB - University of ... PDF (double-sided) - Physics Department, UCSB - University of ...
efore the execution of the sequence. This allows the Qubit Server to forward the burden of setting up the microwave generator and other involved hardware to the GHz DAC Server. As described in Section 7.5.14, this is necessary to allow for the execution of the sequences to be pipelined in the most efficient way. 7.5.13 DAC Calibration Server The DAC Calibration Server provides functions to modify signal data that is to be output via the GHz DAC boards in order to correct for imperfections in the output electronics chain. For this, the DAC Calibration Server first takes a set of calibration data that measures, for example, the response of the output electronics to a delta-function signal. This data is stored in the Data Vault to later allow for a signal to be corrected by taking the desired signal’s Fourier transform, dividing the result by the Fourier transform of the delta-function response, and inverting the Fourier transform to recover a corrected version of the data. The corrected data is returned to (in this case) the Qubit Server so that it can be uploaded to the respective GHz DAC boards. To correct for as many different electronic deficiencies as possible, the DAC Calibration Server needs to take several different calibration datasets. These include traces returned by a sampling scope as well as measurements with a spectrum analyzer. The DAC Calibration Server takes this data automatically via calls 166
to the “Sampling Scope Server”, the “Spectrum Analyzer Server”, the “Anritsu Server”, as well as the “GHz DAC Server”. 7.5.14 GHz DAC Server The GHz DAC Server plays one of the most crucial roles in the data taking process. Due to the fact that most of the data taking action is controlled by the GHz DAC boards, it handles pretty much all of the resource scheduling required to run multiple experiments at the same time on the same hardware. The GHz DAC Server can receive requests for data runs in multiple different Contexts at the same time and actively serializes them on the hardware in the most efficient way possible. It does so by allowing a Context to already prepare its run by uploading the required data onto the GHz DAC boards while the previous run is still executing. It then halts the execution of that Context until the previous run completes. This completion is detected via the arrival of all expected timing data at the Direct Ethernet Server. Before this data is actually read from the Direct Ethernet Server, though, the setup of the next run is finalized by sending out the required hardware configuration packages (see Section 7.5.12) and the run is started. This approach minimizes the amount and size of LabRAD Requests that happen between data runs as much as possible to achieve the best possible performance. Since all other processing of data happens in parallel with this, one 167
- 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 184 and 185: 7.5.3 DC Rack Server The DC Rack Se
- 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 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
- Page 234 and 235: possible to read out all qubits cor
- Page 236 and 237: simultaneous application of such me
- Page 238 and 239: Figure 9.4: Capacitive Coupling Swa
- Page 240 and 241: Figure 9.6: Capacitive Coupling Pha
- Page 242 and 243: a phase difference of 0 ◦ rather
to the “Sampling Scope Server”, the “Spectrum Analyzer Server”, the “Anritsu<br />
Server”, as well as the “GHz DAC Server”.<br />
7.5.14 GHz DAC Server<br />
The GHz DAC Server plays one <strong>of</strong> the most crucial roles in the data taking<br />
process. Due to the fact that most <strong>of</strong> the data taking action is controlled by the<br />
GHz DAC boards, it handles pretty much all <strong>of</strong> the resource scheduling required<br />
to run multiple experiments at the same time on the same hardware. The GHz<br />
DAC Server can receive requests for data runs in multiple different Contexts at<br />
the same time and actively serializes them on the hardware in the most efficient<br />
way possible.<br />
It does so by allowing a Context to already prepare its run by<br />
uploading the required data onto the GHz DAC boards while the previous run<br />
is still executing. It then halts the execution <strong>of</strong> that Context until the previous<br />
run completes. This completion is detected via the arrival <strong>of</strong> all expected timing<br />
data at the Direct Ethernet Server. Before this data is actually read from the<br />
Direct Ethernet Server, though, the setup <strong>of</strong> the next run is finalized by sending<br />
out the required hardware configuration packages (see Section 7.5.12) and the run<br />
is started. This approach minimizes the amount and size <strong>of</strong> LabRAD Requests<br />
that happen between data runs as much as possible to achieve the best possible<br />
performance. Since all other processing <strong>of</strong> data happens in parallel with this, one<br />
167
Change language