Engineering 2010Oct: Difference between revisions

From Monnier Group Research Wiki
Jump to navigationJump to search
← Older editNewer edit →
Line 56: Line 56:


LT00:28 -37 And,  find fringes on Beam 2/3 with MIRC, but position moves rapidly from 179850 to 180250 (earlier found at 182150)
LT00:28 -37 And,  find fringes on Beam 2/3 with MIRC, but position moves rapidly from 179850 to 180250 (earlier found at 182150)
LT03:18 -find fringes on Beam 2/3 with MIRC, but position moves rapidly from 182350


identified bugs:  
identified bugs:  
Line 61: Line 62:
astropci: negative values in Amp-vs-OPD;  
astropci: negative values in Amp-vs-OPD;  
champGui/astropci: properly identify the panels with certain beam/telescope combinations;
champGui/astropci: properly identify the panels with certain beam/telescope combinations;
LT 03:30 - problem: MIRC sees fringes, but CHAMP cannot find fringes at known offsets

Revision as of 11:00, 8 October 2010

See last set of notes from Engineering 2010July-Aug

Daily Log:

2010 October 2:

fb: realigned champ optics and started working on fringe-jumping and coherent integration for cophasing.

2010 October 3:

fb: did a first alignment using the IR array but mostly worked on improving the software.

2010 October 4:

fb and sk

morning -- checking the alignment, CHAMP fully aligned at noon

afternoon -- trying to debug the Zaber mount repeatability problem

2010 October 5:

fb and sk

morning -- redo alignment on E1S1; problems finding pyramid center (it helps to turn on the incandescent lights); fix problems with Zaber mount motors by increasing sleeptime from 3s to 10s

afternoon -- small updates to champGui; searching for beams on wide-field image; 3-4 beams found but problems to align them

evening -- redo alignment on W1W2; found internal WL fringes on R2 using W1-W2 (Beam 1-2) at +3.95mm (see image)

2010 October 6:

fb, sk, and rmg

morning -- discuss with rafael alignment procedure

afternoon -- readjusting pyramid position to avoid bad pixels in the Q1 quadrant; new pyramid center at x=23, y=8; use for IRCam following offsets: row=5, col=20

evening -- discussing alignment tool; add functionality to Pixel_Pico.py to adjust the sign of the motion (done, but still have to determine the values)

2010 October 7:

fb, sk, and rmg

2010-09-07a: We found fringes with MIRC putting the Ealing-mount IR4s to 90615

2010-09-07b: We put the MIRC Ealing mounts to "good" position (i.e. co-phased with PAVO) and adjust Newport RETRO mounts to find fringes on MIRC. Then, we search with Dichroics to find fringes for CHAMP. Unfortunately, fringes are out of the the Dichroics range, so we have to move them away from "good".

2010-09-07c: We put the MIRC Ealing mounts to values close to the good position and adjust Newport RETRO mounts to find fringes on MIRC. Then, we search with Dichroics to find fringes on CHAMP:

IR4: 196500 (Beam 3/4), MIRC: IR3=66000 (good position), IR4=71615 (moved 2cm from good position)

IR3: 182150 (Beam 2/3), MIRC: IR2=80449, IR3=66000 (both "good" position)

IR2: (Beam 1/2), MIRC: IR1=40350 (moved 2cm from good position), IR2=80449 ("good" position); could not find fringes

LT00:28 -37 And, find fringes on Beam 2/3 with MIRC, but position moves rapidly from 179850 to 180250 (earlier found at 182150) LT03:18 -find fringes on Beam 2/3 with MIRC, but position moves rapidly from 182350

identified bugs: champGui: scaling of Amp-vs-OPD plot in bottom panel sometimes strange; astropci: negative values in Amp-vs-OPD; champGui/astropci: properly identify the panels with certain beam/telescope combinations;

LT 03:30 - problem: MIRC sees fringes, but CHAMP cannot find fringes at known offsets

Retrieved from "https://monnier.astro.lsa.umich.edu/research/index.php?title=Engineering_2010Oct&oldid=1773"