Finding: It turns out we have no control over CCD "cleanings" in this operational mode.
These graphs should check CCD cleaning. See excerpt from Tasks doc below.
Tests 1 and 2 below should be done each time the setup is moved or significantly reconfigured, though in the future only one or two long integration time FDI scans would likely be required to confirm the absence of light leakage.
File name | Experiment |
---|---|
check CCD cleaning(He/Hg light source on, all fibers illuminated) | |
3c_10BI_01_ | Take 10 BI images @ 0.35 second integration time (Shutter Control Disabled Closed) |
3c_10LI_ | Take 10 LI images @ 0.35 second integration time (Shutter Control Normal) |
3c_10BI_02_ | Take 10 BI images @ 0.35 second integration time (Shutter Control Disabled Closed) |
3d_cleaning_1_ | Collect 1 image set at CCD cleaning settings 1 |
3d_cleaning_5_ | Collect 1 image set at CCD cleaning settings 5 |
3d_cleaning_10_1 | Collect 1 image set at CCD cleaning settings 10 |
Subject: | RE: CCD function |
---|---|
Date: | Fri, 11 Dec 2009 13:59:08 -0500 |
From: | Lichty, Alan |
To: | Mark Yarbrough |
Hi,
from talking to engineering, it is not a design flaw but a design choice. There are pros and cons for others ways to clean and we try to go the middle of the road because other applications suffer is we do the cleans differently.
If you would like to have a conference call with our product manager let me know. He can explain what we can and can’t do with cleans and the reasoning behind it.
Sincerely,
Alan Lichty
pwd: C:\zflora\mldata\MOBY2\Intital_testing\091208