Never Let the rMOT get below 1.5. And always try to get it back to normal before starting.

Sedlik2024

Sedlik2023

Sedlik2022

1.105V rMOTIntensity(0.264V on PID)
red:(T1,T2,UP):(810, 880,260 )uW

0.28V stirIntensity
Stir:(T1,T2,UP):(69.2, 51.5, 24.6)

Holzworth: 333,056 → 333,069 kHz

294.980355399

294.880355452

294.866679222

found a mf at 294.981269646… its was the +7/2

Z;57.6mW |(2D1,2D2):(3.2,2.96)mW |(T1,T2,UP,DOWN):(4.2, 2.1, 1.05, 0.62)mW

Holzworth: 333,018 → 333,025 kHz

clock holzworth: 294.911385044 MHz

14.7uW 14.1uW 9.8uW

SP:0.525, 0.61, 0.695, 0.78, 0.865,0.95

Clock Holzworth: 294,8425 MHz

Believe we found the issue with the holzworth. the 5V GND cable was poorly connected to the back and it came off. The holzworth has been working all day now.

We use the P9 Pins on the BBG. According to the the back of the holzworth. Its pin is shown below, when face the pins head on

The campus had a complete electric shutdown. That caused a power surge and our Transducer broke. What most likely broke is the Zener Diode. I can receive up to 19V before breaking. Next are the steps I took to safely replace the bitter coils.

1. Ordered List Item

497 aom works,497 AOD works

turned on the 698 clock drift at 4:00pm

because the tables lost pressure, there is a good chance optics got shaken

This is updated to

the code to run is ./tweezer_single

located in file tweezer@tweezer-desktop:~/scapp/cuda_rdma/rdma_fifo_kernel_DA_20230606

we had a campus wide power shutdown over the week end. Lost the Bitter coils transducer. Also los the wiki, for the day. Had some issues with reboot the Sr computer. I'll write here, how we fixed it.

1. Make sure all usb devices are unplug, except for a wired keyboard
2. If computer Entered emergency mode. Use claroq…. pwd for normal login
3. 
4. run “blkid” to get the /devs
5. 
6. run “journalctl -p err” to find the ones with errors
7. 
8. run “dmesg” to see if there are other errors
9. 
10. run “dmesg | grep err” to see if there are more errors
11. 
12. finally run “fsck -y /dev/<the error one from running 'journalctl -p err'>
13. run “reboot”
14. 
15. hit enter
16. Should be able to login to paul@localhost command line

-6.70dBm

1. HWP: -7.60dBm /-7.25dBm :174uW/188uW: 92.6%
2. 461 QWP: -7.20dBm/-6.70dBm: 191uW/214uW 89.3%
3. 698/689 QWP: -9.1dBm/-6.70dBm: 123uW/214uW: 57%
4. (436)HWP: -7.0dBm/-6.70dBm: 199uW/214uW: 93.0%
5. (689)QWP: -6.80dBm/-6.70dBm: 209uW/214uW: 97.7%
6. (497)HWP: -6.85dBm/-6.70dBm: 207uW/214uW: 96.7%

old 481:

481.322200nm : 622.851920THz

481.322500nm : 622.851530THz

this is 390MHz change.

at scan knob of 2, OD is 1.22. at a scan knob of 2.8, the OD is 1.35(max)

Khang said his MOT is lower and effect by my change in the 481. I Adjusted the 481 to be 200MHz, 481.322350nm:622.851730THz at scan knob 2.

I got an OD of 1.12, but Khang mention, timing is important. For example, if im on resonate, and i repump TOO many atoms, the rmot might not be able to capture all the atoms, so we should adjust the timing.

I added the Sw481 to the BlueMOT.py. the Initial turn on timing is more sensitive then the turn off timing.

• ER before adjusting fiber orientation
• ER After adjusting
• place PD at 481 window to check stabilization
• leave aom ON and use shutter
• remove AOM and use shutter
• check more with 461

• Add a ER measurement Guide

using the circular power meter, here are the 481 powers and Effs:

• 8mW into the AOM
• 7.2mW out of AOM(NO-RF)(10% insertion-loss)
• 6.4mW into +1st-order(80% Total Eff)
• 6.4mW into the fiber
• 3.9mW out of fiber(61% Eff)
• 2.9mW at the window
• Wavelength 481.322630nm at scan of 2.8

481 powers before alignment(no scanning)

input fiber:8.15mW output fiber:4.2mW experiment:3mW

481 powers after alignment(no scanning)

input aom:8.4 output aom(off):7.7 1order aom: 6.5mW input fiber:6.5mW output fiber:mW experiment:mW

ADjust laser to be 481.322250nm with Scanning knob to 2.8

4 ways to adjust the gain

1. Input voltage
2. the dip switches
3. the potiometer
4. the VVA

I saw the the BNC cable, that goes to the 497 Latt RP GPIO pin, touching the metal frame. I move it away and the +9/2 atom count went up a bit. Not where is was before, but still increased. I covered the metal BNC with the electric tape.

I noticed 2 of the wires for the MAG N92 RP wasnt plugged in. One was a GPIO and the other was a BNC. Good thing i still had the picture of it from before. The Bitter coils still worked even with these cables unplugged, I restarted the RP and plug every back it. This did not change the +9/2 atoms. Note: Grady found a ground loop with these, so i removed them too.

I checked other Metal to rf contacts, and put insolation between them

I switched over the 813 RF Amp and relabeled it 481. I test the Amp and the output power. THe AOM im using uses 200MHz at 0.9W or 29.5dBm. I measured 29.5DBM on the Spectrum Analyzer with control of the dip switches. I have not started aligning the AOM, but the RF Output cable is where the 481 optics are. I renamed the Sw813 Channel for Sw481.

I experimentally found the dip switches to have these ratings on the 481 RF Amp:

1. 5.25dB
2. 2.5dB
3. 0.75dB
4. 0.5dB
5. 0.25dB
6. 12dB

I renamed other channels and replaced them in Channels.py, Iniatializations.py, and Main.py. And made sure the experiments still works.

• Sw813 → Sw481
• OFL1_PIDTrigger → Trig698_PID
• LiftTrig → Trig679

481 in fiber :7.6mW out fiber 3.7mW

679 in fiber 13.0mW out fiber : 6.5mW

I made a chart of the Transformer channels and what RF-Amp theyre connected too. While doing so I shocked the DDSblue for both ODT outputs. Not realizng this, I restarted the RedPitayas. and traced bak tboth input signals. I found out the ODT1 input signal goes through 2 RF switches. The first one being controlled by Sw5_cont2, which need to be turned on in Steady State. Note: ODT2 Red Pitaya only has the Blue LED. NO Green or Red. Transformer Chart Here

Found to Repumped atoms to make sure nothing else was wrong. And I still see the 60Hz Peaks. Lastly, I believe all Adwin DIOs are being used in the expermient except for the 813nm. I traced the cables and its all local to the 813 RP and AOM. I plan switch it for the 481 AOM.

re took the the axial sidebands. The center carrier was at low atom count because I was spilting the mf-states. Once I stopped spilting got the signal below. This gives we an axial sidebands of (-97.5kHz, +95.kHz). thus giving us a waist of 80um.

I took a radial sidebands of +9/2mf and saw the 60Hz peaks again. Truly not sure what is causing this. The carrier is the Peak at 50Hz. Plus i found out the atoms are resonant with 679.292330nm when the laser is not being scanned.

698 PD: 70db SP0.25=10.6uW vert (12.5uW total), 40dB SP0.7= 1.15mW vert(1.33mW total) (Max and stable)

bumped the last mirror to the lattice forward beam. had to re align the lattice from stratch. I was able to do it by shining both the forward and retro beam onto the rmot, and seeing effect. I got the retro to hit the rmot. I adjusted the forward beam to overlapp the 2 beams, while keeping the retro onto the rmot. when back and forth and got the lattice. I noticed the 698 repumped atom count was low, but i did a broad scan adn saw radial sidebands at 135Hz. and Axial sidebands at 100kHz. Giving me a Waist of 82.9um. I tried going very broad with the axial (-300kHz to 300kHz) and i saw peaks, but the clock kept coming unlocked passed -300kHz.

Thing to check:

• after lattice alignement, check polariztion
• clock alignement to lattice
• lattice PD isnt covered.

at Probe PD 70odB, 2uW is at 0.05 SP

found the +9/2 mf at 430Hz from yesterdays zero

i found one of the fan for the 497 aod-Y rf amp isnt on

today i learned:

• Grady drops the lattice to make sure all atoms are gone, and then turn the lattice back on for the reference image. So its ok to see the Sw497 turn back on.
• Using a PBS to make sure your lattice and probe are vertical or hortizonal is Great. My lattice was 30% horiz. and this was lowering my repumped atoms count due to the sigm +/- transitions.
• we we an rf amp on the rate and powered, but im still going through another to test it and understand what we component does and how to power it. I just need to find a spot on the adwin and a red pitaya.
• reset the 698 holzworth at the +9/2 yesterday

since we have the data for the paper, we are moving to tweezers. Here will be a list of changes Grady amkes so I can keep a log and be able to go back and further from lattice to tweezers.

• For lattice we had +600ms to the ImageDelay, For Tweezers is +400ms
• for lattice Pol, Vertical is ~146deg, while currently its at ~97.5 deg
• Lattice: Probe ~2uW at SP=0.03, Tweezer: Probe ~810uW at SP=0.6
• lattice: 698 PD is 70dB , Tweezer: 698 PD 40dB
• lattice: probe is Vertical Polar, Tweeezers: probe is Horizontial Polar (356 deg)
• Lattice: Probe pulse times 47ms, Tweezers: probe pulse time 120ms

Image of 497Tweezer PID:

Holzworth 332,513 → 332, 518 kHz

Found the center +9/2 peak 200Hz from last night

the center of +7/2 peak is 1160Hz away from center of +9/2 peak.

the reset_count on the +9/2 center peak and now determining if 497.4362nm is magic for +7/2

Holzworth 332,508 → 332, 513 kHz

Determined 497.4362nm is magic of +9/2 and tested it with self.SpinKick=False, and its still magic.

• use the EMCCD to aligned the forward beam like normal
• use the sCMOS to align the retro beam, w/ TOF=5ms. For colder atoms
• Bitter coils went from 5A to 3A
• Grady added in gndpop to flor imaging, change to False.

i started the day checking the rmot and making sure it was where i left it. The OD started at 0.95 and slowly dropped to 0.67. i thought it was the ECD Output, b/c it did drop a little and settle, but not that much. I put the bmot in steady state and noticed the bmot was bad, but after opening the doors, the configuration for aligning everything. IT went back to normal. The bmot looked like the upward was increasing power and/or the downward was decreasing power. The upward was changing power a lot (0.95mW to 1.4mW), while the downward changed (0.49mW to 0.55mW). I i wont do another ER on the downward since i did it twice yesterday and the change it difference it low, but i will do another ER on the 3-1 fiber, specifically the upward fiber

I got the bmot back to 03/12/25. but when i closed the doors, it moved up and lowered atoms count. this is because the ER on the the upward fiber was not as good, even tho i did it twice. i confirmed with Khang that, i could optimizes alignment with the door open, then adjust the powers with them closed. So, it settles at its best combo. Also, i increased the the zeeman power at the experiment to 54 since we had the power and Nanotraps wasnt using it.

1. Put in steady state Fluorescence
2. open all the doors
3. measure the powers and match with them with the wiki
4. adjust upward beam
5. adjust downward
6. repeat steps 4 and 5, 3times
7. adjust Transverse 2 forward
8. adjust Transverse 2 retro
9. adjust Transverse 1 forward
10. adjust Transverse 1 retro
11. Repeat steps 7-10, 3times
12. adjust zeeman
13. adjust 1st 2D
14. adjust 2nd 2D
15. repeat steps 12-14, twice
16. Repeat steps 4-14 until bmot is the best
17. mark the location and intensity of the bmot
18. close the doors and let the mot settle
19. adjust the powers, to get mot back, while trying to stay away from any low ER fibers
20. if the mot looks the same with the doors closed as it did with them open(at the best), Your done

Note: in steady state, make sure Z-Shim=7.1uA, Y-Shim=1.34A, and X-Shim=100mA

found the +9/2 atoms 8.625kHz away, reset count there. i also forgot to flip the mirror to get high atom count in emccd imaging

got the bmot a little bit. the rmot OD went from 0.6 to 1.0.

my alignment process was to start on upward beam than downward (cycle 3 times). Transverse2 → retro2→ Transverse1→ Retro1→ (cycle 3 times)

at the end of day rmot OD is 0.75 . plan to work on the bmot alignment

461nm: 720mW

922nm: 2.0W

Etalon PD DC: 1.250V

Output PD: 0.791V

ECD Output: 1.080V

1. make sure you havent started qcontrol
2. ssh into shutter BBone
3. make screen: screen -S uart
4. cd into uart
5. echo UART1 > /sys/devices/bone_cape*/slots
6. echo shutters > /sys/devices/bone_cape*/slots
7. ./uartserver
8. done
9. if this doesnt work try.
10. in screen:cd into uart
11. dtc -O dtb -o UART1-00A0.dtbo -b 0 -@ UART1.dts
12. dtc -O dtb -o shutters-00A0.dtbo -b 0 -@ shutters.dts
13. mv UART1-00A0.dtbo /lib/firmware
14. mv shutters-00A0.dtbo /lib/firmware
15. echo UART1 > /sys/devices/bone_cape*/slots
16. echo shutters > /sys/devices/bone_cape*/slots
17. ./uartserver
18. done
19. then open qcontrol

bbbuart

1. after a shutdown the power will be unplugged from the wall
2. note where the GPIO pins are and unplug them
3. unplug ethernet cable
4. plug in power
5. wait 1-2 mins for start up
6. plug in ethernet
7. plug in GPIO pins
8. ssh into BBone
9. run ipython -i test.py
10. hz.get_freq()
11. hz.track_drift('on')
12. hz.get_freq()

If it doesnt power on, check power supply, could be fried

Holzworth 332,428 → 332, 445 kHz

4.4MB 0.3MB 2.0MB 1.5MB 3.3MB 5.2MB 1.7MB 3.1MB

Holzworth 332,420 → 332, 428 kHz

rmot OD was 1.20. Check the bmot and laser's ECD output and all were good, actually better then the previous days. I adjusted the 481 but no change. I noticed very subtle changes to the rmot shape. like the corners werent as pronounced. i relocked the 689 laser and got a 0.05 increase with the noise of the blue trace being lower. Alignment hadnt been touch and the powers were reaching set point. I increased the Current on the laser by steps 0.02mA and bringing back the wavelength with the piezo to get a OD of 1.46. This took about 10 steps. I didnt see the OD he higher with the last two steps. I was worried it could mode hop and i would be adjusting more and taking more take away from magic data. I decided to increase the load time of bmot. The other day Grady said I could increase it to 4s, but instead i only increased it to 3.8s and got a RMOT OD of 1.55. the DFG OD was 0.85

On friday Grady and I noticed the drift of the clock was reversing. So to mark down were i found it today, the center of the repumped 9/2 atoms were drifted +840Hz

Todays Data was taken with a Probe SP of 0.03

SP0.9 file 100, detunings = np.arange(0.0, 0.154, 0.004) SP0.7 file 101, detunings = np.arange(0.0, 0.154, 0.004) SP0.5 file 102, detunings = np.arange(0.04, 0.194, 0.004) SP0.6 file 103, detunings = np.arange(0.04, 0.194, 0.004) SP0.8 file 104, detunings = np.arange(0.04, 0.194, 0.004)

SP0.9 file 105, detunings = np.arange(0.04, 0.194, 0.004) SP0.7 file 106 detunings = np.arange(0.07, 0.224, 0.004) SP0.5 file 109,detunings = np.arange(0.07, 0.224, 0.004) SP0.5 FIle 110, detunings = np.arange(0.07, 0.224, 0.004) SP0.5 file 111, detunings = np.arange(0.33, 0.484, 0.004) SP0.5 file 112, detunings = np.arange(0.43, 0.584, 0.004)

holzworth 332,408 → 332,420 kHz

Blue laser wasnt as good. the ECD output wouldnt stay above 1.035V for a rmot of 1.44. I kept going , with Grady's permission. I learned that Grady changed the bmot load time from 7s to 3.5s, i had no idea. Couldnt find the repumped atoms but after a large scan i found them. Took 3 rounds of 497.437nm and if fit Grady orginal graph of our drift rate. we beleive the 497.436 , i took on friday, was shifted due to the cavity drift. We decided to redo 497.4360 instead of moving to 497.4365nm. The probe Setpoint was set to 0.02 instead of 0.03. i will change it back for wednesday's data

holzworth 332,404 → 332,408 kHz

Grady showed me what settings to revert the 698 FLAC back to. In hopes of fixing our atom drop issue, it worked. now the oscilloscope better reflects the 689 laser when locked as well. I took a 4 round scan at 497.4360 , while the slope looked great the cavity was drifting a lot. Not sure why this is but I will try 497.437 on monday

I did learn some things about the TA Pro and navigating through it. These are the current setting and oscillascope channels that we use. where each number on the image below correspond to a way to navigate the scope.

For this image:

1. corresponds to Turning On and Off Scan. Meaning you wont be able to Scan the AMP if this is OFF
2. Is allows you what graph to rescale when pinching the screen and what graph is fixed
3. is the Button need to get to the menu and the next Image

For this image; in order to changes what is being graphed on the scope Follow Display Setting → Trace Selection → Change Signal

Holzworth 332,392 → 332,404 kHz

I got the MOT to OD of 1.55 by only adjusting the downward beam. It's best to do this in bmot fluoresce. Originally the bmot was located where the cursor is in the image below, but the actual bmot location was below. Its OK to turn a knob to find if you mot had moved to a better location

I fully updated the Experiment_Log with new 461 and 689 powers to get our current hope, just in case we lose it again, we have a reference. I moved onto the clock/lattice. I took a large scan because I thought I saw 3-4 sidebands on either side.

698 pwr was 2.1uW at 47ms, scanned 460Hz at 4 steps.

in the event that the clock Holzworth changes its reading from 584MHz to 484MHz, you need to restart the Beagle Bone. Unplugged it and re pulled the cables

after about 15hrs the clock holzworth drift was ~500Hz shifted

Holzworth 332,359 → 332,369 kHz

With the EMCCD: Rempumped atoms, The +9/2 mf was +4.85kHz. Reset count at Hz from the +9/2

Holzworth 332,351 → 332,359 kHz

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +2.9kHz away(adjusting for the +9kHz). The +9/2 mf was +3.6kHz. Reset count at Hz from the +9/2

Today i tracked the +9/2mf while cycling through different lattice powers.(0.9, 0.7, 0.5, 0.6, 0.8, 0.9, etc). With self.SpinKick=True and Probe Pulse of 1.8uW at 47ms, i isolated the Center peak from the radial sidebands. I was able to complete 4 sets of lattice powers.

• Got a fine tune of magic at +9/2 (was slightly off)
• Got a better drift of clock (should add 15-19 mHz/s to current)
• Showed that SpinKick is working

Next is to do the same thing again on monday but at 497.433000nm, instead of 497.432100nm

Holzworth 332,345 → 332, 351 kHz

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +2.4kHz away(adjusting for the +9kHz). The +9/2 mf was +3kHz. Reset count at -50Hz from the +9/2

i work on getting magic for +9/2 and use self.SpinKicK. Grady and I noticed that some of the peaks were shift 50-60Hz, this was at 4uW of probe at 400ms, we reduced the power to abotu 1.8uW, pulse at 47ms, and shorten the steps of the scan to 2.5 hz, and found the sidebands were 60Hz. we were tracking the sidebands some times instead of the center peak. We contunie with this small scan range to know if we were magic.

Holzworth 332,351 → 332,345 kHz

Magic for +9/2, +7/2, +5/2 : 497.432100nm, 497.432900nm, 497.433600nm

so i wanted to see how the Lattice OD relates to the Vertical fluoresnce imaging. the Images below are at an OD of 7.5. The Black|WHite graph is what we use when taking data. the Rainbow graph has a better visual range to determine peak of intensity.

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +1.4kHz away(adjusting for the +9kHz). The +9/2 mf was +2.1kHz. Reset count at -400Hz from the +9/2

• Unordered List Itemtoday, the laser turned on to 698.44000nm
• i tried adjusting the piezo but it mode hops to 698.48000nm.
• I start adjusting the Master Current.
• I determined that the lower and upper range of the current is 65mA and 73mA.
• I learn from Grady that there is a small whole on the side of the laser. it fits the red 2.5mm Allen Driver
• that is only used for coarse adjustments, this should be an absolute last resort
• i set the piezo and the master current to 70.00V and 69.00mA. Adjusting the driver mode hops the laser from 698.4000 to 698.47000nm
• we realized we can change the Temp. Currently at 19.0.
• - to get the DLC to display the Temp:
  • Press the bottom right button.
  • click Top Left Parameter
  • Select Master Set Temp
  • Use image below as a reference
• starting at 698.40800nm, i increase the Temp by 0.1 or 0.2 .Never by >0.3
• on the wavemeter monitor. Click at WLM Long Term graph
• each graph corresponds to the channels. Close all except for 698
• At the Top Right, click Rest now
• you will better see the laser change has you change the current. THe sharp peaks is mode hopping. Sin curves are settling(good thing)
• I changed the current upwards to start
• The Range of the Temp of 18.5C to 21.5C , Make sure to stay away from the ends as possible!

Holzworth 332,327 → 332,351 kHz

on imaging computer to find sbench files are in: Strontium\engineering\spectrum_awg

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +6.7kHz away(adjusting for the +9kHz). The +9/2 mf was +7.6kHz. Reset count at 0Hz from the +9/2

found the resonate frqs of 689 for each Mf state. used the notebook SpectrumCardWaveformGeneration to create the bin file. in the Spectroscopy Waveform part, you just change mF= ['9/2'] to anything other spin and it will automatically generate. example file name: kick_out_-92_40segs.bin

then the list of Detunings produced by the cell, must be used when plotting the effect. in spin_kick_calibration_20250223

40 segs, means 40 imaging of atoms and 40 image of references, so on Andor, set Kinetic series to 80

the bin file then get put into SBench, you need to restore the parameters. then in Output Mode: change to Standard Multi(Replay) → 624992 S → 40 Segs → 1 Loops

we did this because because we needed to know where each of the kick out freqs are for all spin states. We actively choose not to do +9/2, and we couldnt see the +1/2

Grady updated the way we edit the Main.py files and other for the strontium experiment. now we can open up 2 files at the Same time in EMACS. Always set the left side to Main.py and change the right side as needed. ctrl-click to each the script

In the Main.py, Now we only use Red Mot Calibration and DFG Calibration (Spin Pol).

• self.TOF=5ms or 0ms (DFG or Latt)
• self.LongEvapTime= 2.5s (Both)
• self.ImagingDelay= 6.18s + LongEvapTime (DFG) + 600ms(Latt)
• self.ODTLatticeCrossover = 6.18s + LongEvapTime

self.ODTBasic= False/True (Normal Use/ Spin Polarizing)

If im Kicking Out (Removing) all spin states except for +9/2, Set self.SpinKick=True. Otherwise dont change anything.

On the Imaging Comp, in SBench: Place test_kickouts_only_06.bin in AO-Ch0. Memsize=5624928s , Amp=+/- 850mV, Trg1=Checked

Holzworth: 332,323 → 332,327 kHz

rmot OD: 1.55

DFG OD: 1.0

Lattice OD: 0.69

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +0.8kHz away(adjusting for the +9kHz). The +9/2 mf was +1.5kHz. Reset count at -400Hz from the +9/2

497.433600nm at SP=0.9, Probe=4uW

497.433600nm at SP=0.9, Probe=4uW, with Kickouts

rmot OD: 1.72

DFG OD: 1.12

Lattice OD: 0.69

While Grady was working on Spin Pol and warming up the experiment. I start color coding the laser paths on the Main table. Julio bought colored label table. Bellow is what im coding. I finished both 679 and 481 repumpers and started 698 paths

Holzworth: 332,300 → 332,300 kHz

rmot OD: 1.75

DFG OD: 1.12

pre-aligned Lattice OD: 0.7

post-aligned Lattice OD: 0.7

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +14.5kHz away(adjusting for the +9kHz). Reset count at 0Hz from atoms

I tried getting high atom count in the all mf state dfg, by aligning the lattice better but no luck.i wanted to try checking probe alingment or repumper power but i had to leave lab.

Holzworth: 332,288 → 332, 300 kHz

I recentered my ROI on the images from fridays, the atom count did increase which was good, but hte the shape of the graphwas the same, meaning the flooring rose as well. With the existent of a red detune rdail sideband, I was not fully in the ground state, even tho there was a red sideband for the axial. I curious if it due to lattice alingment, probe alignment, probe power, or repumper alignment.

i switched the 3 channel power supply, powering the Mag N92 Red pitaya, for a linear power supply. I double checked that the Output voltage is 5V and 0.85A. Here are the following steps to successfully power down a redpitaya and reboot it.

1. Delta Power Supply (Output on/off)
2. In Strontium Computer: QuitRPs
3. SSH into 'root' user for each RP(ssh root@<IP>) using IP/Passwd on ~/PID/RPList.json
4. `shutdown now'
5. Power down all RP supplies or unplug from wall
6. Work on RP, ( i soldering the power cable to the power supply)
7. Power supplies should be ~5V and ~0.9A
8. Unplug Ethernet cable and Triggers(Make sure to note where they go)
9. remove and reinsert microSD card
10. Power on the Red Pitaya
11. wait for orange light to go away
12. plug in ethernet cable
13. plug in Trigger cables
14. run LaunchRPs and/or LaunchRPSec
15. Delta Power Supply (Output on/off)

Holzworth 332,279 → 332,288 kHz

rmot OD: 1.75

DFG OD: 1.15

pre aligned Lattice: 0.7

post aligned Lattice: 0.76

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +15.8kHz away(adjusting for the +9kHz). The +9/2 mf was +7.5kHz. Reset count at -300Hz from the +9/2

Ended day with:

rmot OD: 1.67

dfg OD: 1.1

Lattice OD: 0.7

Holzworth 332,276 → 332,279 kHz

rmot OD: 1.7

DFG OD: 1.15

Holzworth 332,264 → 332,276 kHz

rmot OD: 1.7

DFG OD: 1.1

on the friday the rmot and dfg ODs were bad, and i saw some issues. i did an extinction ratio on the 1- 3 fiber and it up'ed the rmot but lowered the dfg which was weird. Sometimes you just need to leave it alone for the weekend, because today both rmot and dfg were good to go

when the 497 light is ON/Locked, it changes the OD of the rmot and DFG, so take this into account when going back to to see the ODs.

lattice OD after alignment was 0.6

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +14.4kHz away(adjusting for the +9kHz). The +9/2 mf was +6.1kHz. Reset count at -300Hz from the +9/2

i went to get the radial sidebands. i had to decrease the probe power becuase the transition was heavily broaden. i saw the radil sideband but due to low atom count, it was a nice of an image as i wanted. I tried increasing the probe problem, but not much difference. I beleive it could be do to the bmot freq being set to 37 instead of 38-39

Holzworth 332,252 → 332,264 kHz

Holzworth 332,211 → 332,226 kHz

rmot od: 1.9

dfg OD: 1.1

1. get the dfg on the EMCCD,
2. you will have 50 gain, 8×8 binning, and TOF=0ms
3. adjust the scaling to know exactly where the center is, and mark it
4. it the lattice up and in Imaging delay: change 600ms to 12ms
5. block the retro mirror and adjust the mirror that is immediate after the HWP
6. the vertical will change the brightness and the horizontal changes the location
7. knobs are VERY sensitive
8. once the its brightest and overlapped, unblock the retro mirror
9. adjust the knobs until brightest and overlapped

lattice OD: 0.85

for probe: without the ND filters, SP=0.2 is 4.1uW, SP=0.05 is 0.7uW, and SP=0.02 is 255nW

With ND Filters, SP=0.4 is 250nW

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +3.8kHz away(adjusting for the +9kHz). The +9/2 mf was +4.5kHz. Reset count at -300Hz from the +9/2

reset count at +9.1kHz from 300hz before +9/2 state

the bitter coils werent working today, troubleshot it with Grady all the way back to the microSD card in the magN92 red pityia. Grady was able to get it started with a different SD card.

the bmot spectrosocpy power was lower. we lowered the Setpoint from 0.245 to 0.21 b/c it only went to 0.216

Holzworth 332,215 → 332,211 kHz

rmot OD: ~1.7

DFG OD: ~1

latt OD: ~0.9

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +3.4kHz away(adjusting for the +9kHz). The +9/2 mf was +4.1kHz. Reset count at -300Hz from the +9/2

Holzworth 332, 210 → 332,215 kHz

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +1.9kHz away(adjusting for the +9kHz). The +9/2 mf was +2.6kHz. Reset count at -300Hz from the +9/2

Today is a day, i feel like i dont understand this experiment. I ended Friday night with a rMOT OD 1.3. Today, THe bmot OutPut PD is 0.760V(lower then friday), the bmot pid still not at 0.245 Setpoint, the 698 noise line is larger then friday, and without adjusting the holzworth, Today's rMOT OD is ~1.7. I didnt change anything in the sequence, so i dont think its artificial.

Holzworth: 332,203 → 332, 210 kHz

Rmot OD: 1.71

DFG OD: 0.94

Latt OD: 0.83

With the EMCCD: Rempumped atoms(120mA Bitters), Found them +4.1kHz away(adjusting for the +9kHz). The +9/2 mf was +4.7kHz

I reset zero on the clock holzworth, at the mf=+9/2

Narrowing down mf=-5/2: Setpoint 0.9, 497.433600nm, steps of 25HZ, Probe powers 0.2|0.1|0.05

Rmot OD is very low ~1

i relocked the 689 laser to get a lower noise, and it increased to ~1.15. I adjust the downward 481 beam during fluorsesne, and it increased to ~1.2. I went through the sequence of what i changed wednesday, and im not missing anything. I doubt its alignment of the 689 becuase the shape of the rMOT looks the same. There is nothing blocking the pathes of 689. Their PIDs are hitting SetPoint. Humidity looks good. THere are times where the OD will spike +0.2 but then go back down to ~1.2, which makes me believe its something thermal(aom?)

Holzworth: 332,193 → 332,203 kHz

SLS cavity ion pump is at 3.3E-8 Torr

I found the repumped atoms ( not the +9/2). the bitter coils were at 120mA, their were + 11.5kHz away, but adjusting hz.set_relfreq() for the 9kHz offset the +9/2 was zero'd to on wednesday, We drifted about 2.5kHz since wednesday.

Setting the bittercoils to 5000mA, and going -9kHz from the 11.5kHz, the +9/2 mf was +3.3kHz relative to Wednesday's zero. ( went steps of 100Hz)

Went back 300Hz and reset the zero, so i can start the data collection of +9/2,

The graph was shifted to the left so i went back another 300Hz and reset to zero

tried to get all the powers at 497.433300nm, but the clock laser kepts coming unlocked ~ 30 times. the data peaks kept shifting to the right, and i ran out of space. so i ended up stopping at the -9/2 state of 0.525 SP

SP=0.9

SP=0.65

SP=0.4

SP=0.525 +9/2

Holzworth: 322,181 → 322,193 kHz

rmot was 1.5, but then immediatly went to 1.4 then 1.3, then hovered around 1.35. the bmot pd showed 0.23 even tho the setpoint was .245. I tried relocking and coupling up to the pd with no luck. the Output PD 0.782V and ECD Output PD is 1.07V.

I increase the bmot through the downward beam, help but not the 1.55 OD that i saw yesterday. I change the holzworth and it helped, but i changed it 12kHz. the DFG is ~0.9, which is close and ill move onto the lattice.

Lattice OD is ~ 0.83, about what yesterday was.

Saw the Lattice in the EMCCD, moving to the rempumped atoms.

I found the repumped atoms ( not the +9/2). the bitter coils were at 120mA, their were + 10.9kHz away, but adjusting hz.set_relfreq() for the 9kHz offset the +9/2 was zero'd to monday, We drifted about 1.9kHz since monday.

Setting the bittercoils to 5000mA, and going -9kHz from the 10.9kHz, the +9/2 mf was +2.6kHz relative to monday's zero. ( went steps of 100Hz)

Setting up Spectroscopy for 497.433300 at SP=0.9:

1. Go back Relative 200Hz
2. set new zero
3. Try set the kinetic series to 40 and run,
4. After loops, remember to turn on the Automated clock
5. set self.AutomatedClockSpec=True
6. Start running again
7. THe +9/2 seemed to close to the edge
8. 
9. i went additional -200Hz and re Zero'd
10. 
11. looks good, now moving onto other mf states
12. This is todays spectroscopy: Attempt 1
13. 
14. Files used for attempted 1 (+9/2,-9/2,+7/2,-7/2,+5/2,-5/2) are (103,104,105,106,109,110)
15. I completely forgot to do hz.return_to_zero(), had to restart
16. 

Compare to monday, some of the mf states peaks seem to shifted. But i expected a changed because Khang was running his bitter coils and/or due to not returning back to zero

checked the rmot before i left OD is ~1.6

Holzworth 332,166 → 332,181 kHz

got the new 1064 diode in and worked on setting it up with Julio. He buttcoupled it to another fiber and connected it to the wavemater. My made sure the power was below 200uW, but we did not the monitor said Underexposed. we increase the power with no luck and change the fiber to 780PM with no luck. we determiend we needed a single mode 980 PC fiber.

rmot was at 1.1, adjusting the Holzworth got me to 1.25.

Grady said he adjusted the flipper mirror, so adjusting the downward blue should help

I set the bmot fluoresnce and it help and get the rmot to 1.55. which is what grady had before

the DFG OD 0.98

Latt OD was 0.94

changed to the EMCCD, went to absorption imaging.

the acquistion is :

Kinetic Mode, Triggering: External Exposure, Shift speed: 1.13, Readout: 30MHz, bin:8×8.

To find the lattice: set gain to 0 →10 →50 → 100, you should see it.the clock repumper is the same freq(679.292500) at scan rate of 2 (not 0.5).Found the next clock at +4.5kHz away, gain was set t0 1000. The clockpulse was at 50ms, but was supposed to be at 400ms. Also, i forgot to turn on the cooling for the EMCCD.

The Lattice was 497.433300nm at 0.9SP

In Main.pys: self.AutomateClockSpec needs to be False when not automating the clock holzworth

In FlrImg.pys: ref needs to be False when not automating the clock holzworth

I recreated grady's data for the +/-(9/2,7/2,5/2) states

How to take the Data:

1. Physically change the date on the file the EMCCD is Spooling to. This will create a new file
2. Change file type Tiff, ( was orinigally set to Binary)
3. Change Kinetic Series Length to 40. 20 for the data points and 20 for their backgrounds
4. Main.pys: self.AutomateClockSpec=True
5. FlrImg.pys: ref=True
6. Bitter coils from 120mA to 5000mA
7. go -9kHz for the repumped atoms to see the +9/2. Find them in steps of 100Hz
8. do hz.set_relfreq(-0.0002)
9. Once found hz.reset_count() to make this you new starting point
10. hz.set_spec(0, 0.00091,0.00005) (this is the 20 data point scan)
11. start the camera capture.
12. loop the sequence, this should all be automated, where you just keep track of locking and wavelength drifts
13. Once Done or a data point gets messed up. YOu will restart the WHole mf state.
14. Press “Enter” in the Holzworth
15. hz.return_to_zero()
16. hz.set_spec(0, 0.00091,0.00005)
17. If you are going to a new mf state: hz.set_spec(0+<Offset>, 0.00091+<Offset>,0.00005)
18. jupyter note: magic_measurements_20241219-Reproducing

Files used for (+9/2,-9/2,+7/2,-7/2,+5/2,-5/2) are (112,113,114,115,116,117)

Data i got is below: