2015 Jun CHARA AO Run JDM: Difference between revisions

From Monnier Group Research Wiki
Jump to navigationJump to search
Monnier (talk | contribs)
No edit summary
Monnier (talk | contribs)
No edit summary
Line 134: Line 134:


Some things we need:  
Some things we need:  
1) TT needs to off load to telescope tracking when out of range.
*1) TT needs to off load to telescope tracking when out of range.
2) we need focus tiptilt, etc to be the same SCALE and meaning on LABAO and TELWFS.  I might be running wrong version??
*2) we need focus tiptilt, etc to be the same SCALE and meaning on LABAO and TELWFS.  I might be running wrong version??
3) need way to tweak beacon on reference offsets on camera (?) similar to LAB, SCOPE button?
*3) need way to tweak beacon on reference offsets on camera (?) similar to LAB, SCOPE button?
4) labaogtk crashed many times. more often i think when saving data.
*4) labaogtk crashed many times. more often i think when saving data.
5) terms seem affected by subapertures with low flux. how can we auotmatically set up the  clamping?
*5) terms seem affected by subapertures with low flux. how can we auotmatically set up the  clamping?
6) how to do co-adding on labao camera?
*6) how to do co-adding on labao camera?
7) when in closed loop, we should have some way to know how much defcous/astigmatism is 'tuned in"
*7) when in closed loop, we should have some way to know how much defcous/astigmatism is 'tuned in"
8) we sholdn't need to repeatedly click on 'set flat' when closing loop on labao
*8) we sholdn't need to repeatedly click on 'set flat' when closing loop on labao
9) labao rate was super slow (1 Hz) when overlaying boxes from wazoo.
*9) labao rate was super slow (1 Hz) when overlaying boxes from wazoo.
10) should we put in a safety loop so emccd can't cool down too fast and cause damage? are we supposed to keep on?
*10) should we put in a safety loop so emccd can't cool down too fast and cause damage? are we supposed to keep on?
----
----



Revision as of 09:46, 12 June 2015

John Misc To Do List:

  • (DONE)ireland recommendation
  • simulate binary for phil
  • (DONE) run the agn data through jdm pipeline
  • give phil idl pipeline
  • simulate cphase bias for mirc
  • ao to do list plan!!
  • mirc/champ paper!
  • (DONE)go through email.



John open questions

  • its hard to keep beacon totally collimatedin lab. What is effect as delay line moves?



John Goals:


John Alignment Notes:

Lab AO


  • Align green laser as normal including down the rails
  • using flat before DM, auto-retro the light back toward WFS
  • memorize flat
  • check green laser bouncing off the back of dicroic. save offsets.
  • put flat on rails and send light back. tweak blue spots into position on WFS. Blue light too weak normally but use coadd mode (if its ready) or maybe white light (TBD)
  • close servo loop. set flat a few times. Save flat. .this is now the good DM position.
Note if DM voltages are not in optimal range 0.6-0.7 V, then adjust either tiptilt of DM stage itself or figure out what is out of focus.  you can check with 2 hole mask before and after the delay line cart to try to determine what needs adjustment.
  • Now bring laser beacon into lab from telescope (first send to Tel-WFS then send to lab using dicroic).
  • focus beacon using lab WFS by moving fiber at telescope.
  • check for consistency with 2-hole mask that the tel beacon is collimated.

Instruction from Theo about how to run Tiptilt from the telWFS

If you wish to play with the WFS as tiptilt, the command "twfs" on the telescope server will toggle between listening to the old tiptilt and the new WFS for the tiptilt signal. On the WFS gui the "REOPEN TT SOCKET" should establish a conneciton. There are places to play with the gain and damping (who knows if the sign, or even X Vs Y are correct....). The TT DISP is much like the one for the old tiptilt. If you change the gain or damping you need tohit the "SEND SERVO" button. the "SCOPE DISPLAY" is like the one on the LABAO, although I don't htink it does focus etc yet. I need to add all that stuff.

use SEND button to change state and test servo offsets.

Notes from 2015Jun11.. Gain settings of tel wfs : X -0.020, -0.02 (+0.005, Y -0.005)

Fri June 12 2015

AO Testing:

Closed loop (of telescope wfs with tip/tilt) of a bright star Vega [On sky woohoo].


Saving WFS data from both wfss under various settings.

I'm calling the wfs at the telescope TWFS!

Both wfs cameras set to 200Hz. (Typically runs 194 - 206 Hz)

Loaded Def to DM in lab. Use 'Scope' to align on Lab WFS.

Saving 10,000 on LabAO. Saving 10,000 on TWFS. -> no indicator that data is being saved on TWFS. Have to check for files...

Everything is frozen on the lab side.... too many frames? out of memory?? oops.

10,000 is too many. Had to restart LabAO server.

Retrying with 200 frames: Saving 200 frames on LabAO -> looks like it is saving data. Saving 200 frames on TWFS -> looks like its doing something...maybe.


Saving 100 frames on TWFS Saving 200 frames on LabAO


File number 6 for both TWFS & LabAO. TWFS: 200 Hz CLOSED loop with TT. LabAO OPEN loop with default flat. Hangs on 1000 frames, hopefully just freezes when saved

File 7: same as 6. File 8: same as 6.

File number 9 for both TWFS & LabAO. TWFS: 200 Hz CLOSED loop with TT. LabAO CLOSED loop with default flat. Files 10 & 11 same as file 9. File 11 may have lost range on TT.

Taking 3 additional sets: 12, 13, & 14. Same as 9, 10, & 11.

Open all loops!!!!!

Some motion tests. Collecting data as it drifts. All loops open. File 15, 16, 17, & 18

Looks like the beacon was on through those tests.

file 21. moved the telescope and saved while moving. file 22. same test, opposite direction on the same axis.

at the end of the dataset1, the az/el was +65,+76.


going to new star Alp CRB (at 1:30am) az,el +264,60.

took some test files.

taking simultaneous data with default lab ao dm with tiptilt closed on telAO.

  1. 25,26,27

(note theres is a big time dealy between when we lose light in tel WFS and lose light in labAO -- artifact? latency?)

looking at beacons for reference. 28,29,30 (note tel WFS is a bit saturated)

closing loop on will repeat with star light using static-correct wavefront, will run lab WFS for beacon at 50 Hz for higher snr 31,32,33 beacon: 34 (same exact settings). missing many spots../ beacon: 35 (using default DM) (i expect to see some problems compared ot last one sincce I'm not suing the default DM)

next: I will use servo on beacon. SET FLAT

 go back to star and take some data as parallactic angle changes.
 beam seems to be vignetting on lab ao.  could be due star out of focus (tel wfs say s focus -1.4)  
    • need s2 secondary mirror motors working !! *
  36, 37,38,39

current az,el: 271, 51.


Some things we need:

  • 1) TT needs to off load to telescope tracking when out of range.
  • 2) we need focus tiptilt, etc to be the same SCALE and meaning on LABAO and TELWFS. I might be running wrong version??
  • 3) need way to tweak beacon on reference offsets on camera (?) similar to LAB, SCOPE button?
  • 4) labaogtk crashed many times. more often i think when saving data.
  • 5) terms seem affected by subapertures with low flux. how can we auotmatically set up the clamping?
  • 6) how to do co-adding on labao camera?
  • 7) when in closed loop, we should have some way to know how much defcous/astigmatism is 'tuned in"
  • 8) we sholdn't need to repeatedly click on 'set flat' when closing loop on labao
  • 9) labao rate was super slow (1 Hz) when overlaying boxes from wazoo.
  • 10) should we put in a safety loop so emccd can't cool down too fast and cause damage? are we supposed to keep on?