DAQ Documentation 2002Apr13 J D Monnier & J P Berger 2002Dec16 J D Monnier UPDATE --------------------------------------------------------------- Contents I. Introduction II. Starting DAQ III. IDL software suite 1. Aligning IONIC3 outputs on camera 2. Setting observing parameters 3. Inspecting raw scans 4. Finding Fringes and Taking Data 5. Fiber Explorer 6. Picomotor Alignment 7. IOTA3GUI (long delay planning) IV. Common Problems. A. How to recover from crash gracefully Appendix A. Header info ---------------------------------------------------------------- In case of problems, the main authors of the DAQ system software are: Monnier, Pedretti, Millan-Gabet. Schloerb knows the shared memory structures well too. ----------------------------------------------------------------- I. Introduction The IOTA3 Data AcQuisition System (DAQ) consists of a realtime portion running on the vme computer iota-ppc2 and a user interface running in IDL on the Sun iota16. An FPGA circuit actually does the clocking and reading out of the PICNIC camera (see full description by Pedretti). The vme acquires data from the FPGA board and controls the scheduling and piezo scanning. The vme also does all the actually writing of the data to disk. The IDL processes interact with the vme entirely by reading and writing variables in SHared MEMory (shmem). We have a written number of IDL modules to aid the observer in aligning the system and taking data. This document is not meant to explain the inner working of this system, but merely to enable an inexperienced observer to take advantage of some of the advanced capabilites. Here we will describe the features and operation of each module. --------------------------------------------------------------------------- II. Starting the DAQ 1. Log in as iota on iota16 2. You must first load the code onto the vme realtime computer and start the appropriate processes. Usually one will reboot the cpu by pushing the reset button. The PICNIC camera should be on. 3. type the following at the unix prompt. Usually on the left-hand monitor % cd iotamc % daq-start 4. Now to run the idl programs all you have to do is go to the home directory of ~iota and type 'observe'. This is usually done on the left hand monitor. Its important to run this before you start any other graphical windows (such as XDisplays/Startracker2), since the flat panel displays are currently not configured properly to deal with 24-bit color. % cd % observe --------------------------------------------------------------------- III. IDL software suite You will now see a menu with a bewildering variety of modules. It should look similar to this: ------------------------------------------------------------------------ -- W E L C O M E T O T H E O B S E R V I N G T O O L -- 1. Align pixels on Picnic Camera (** OPTIMIZE FLUX ON CAMERA **) 2. Setup Observation Parameters (** SET REAOUT AND SCAN PARAMETERS **) 3. Display raw scans (** SEE RAW DATA **) 4. Find fringes (** TAKE DATA **) 5. Fiber Explorer (** ALIGN FIBER TO OPTIMIZE COUPLING ON STAR**) 6. Align Fibers on Startrackers using Picomotors 7. IOTA3GUI (** USE TO DETERMINE OPTIMAL LONG DELAY POSITIONS **) 0. End Type ? inside the above programs for list of keystroke commands ------------------------------------------------- The ordering of the modules are a bit historical and will probably someday be re-ordered. I will go through the functioning of each one briefly 1. Aligning IONIC3 outputs on camera type 1 on the DAQ main menu. One must occasionally check that the 6 outputs on the IONIC3 integrated optic are still aligned well with the pixels on the PICNIC camera. This module allows one to do this by reading out the entire quadrant. Also this program creates an 'altera_coordinates.idlvar' file which is important because it tells the FPGA circuit which pixels to readout during data acquisition. You should make sure there is plenty of light on the pixels and you should see a line of 6 bright spots, usually near the bottom. a. Click closely on the left-most spot. b. It will then ask you if you want to take background frames. This is not necessary when aligning bright spots, but if you are looking at something faint then you might have to in order to eliminate bad pixels. If you choose yes, then turn off the light source. c. It will then ask you if you want to save some frames. You don't (hit return). Three idl windows are available: a. You will see a zoom up of the chip near where you clicked, and rotated so that the pixel run up-down. Notice the 9 pixels with little squares around them. The bright ionic pixel should fill the bottom six with as little spill over as possible. The numbers on the display tell you number of counts in each pixel b. The accompanying bar plot tells you the same. c. A display of the flux on a pixel as a function of time (history) is available. This is useful when one tries to maximize the flux (** how to change the pixel ??** ) ** This display would be more useful if it told you the fraction of light falling in the center pixel out of the 3x3 grid centered on each pixel. This will be done one day. ** Hit to quit. ------------------------------- 2. Setting observing parameters type 2 on the DAQ main menu. This procedure will step you through the changable observing parameters. Hitting at each one will keep the last settings (which appear in parentheses in each one). Here is a brief description of each parameter: 'Enter NLoops': A camera parameter. Large number means longer integration time. Typical numbers are 1 3 4. There is some strange unexplained behavior like 1 and 2 give the same t_int. 'Enter NReads': Similar to above. One usually keeps this at 4. If one is interested in the true integration time check the header of the recorded file. It contains the explicit integration time corresponding to the number of reads and loops choosen. 'Enter number of points per scan': 256 is normally good for sampling the maximum optical path difference (opd). 'Enter number of bad points at beginning of scan': This is used to deal with settling time of detector after reset and also the settling time of piezo scanners. We use 70 pixels for 1 loop 4 or 20 pixels for 4 loops 4 reads. *** We should come up with an optimal sawtooth pattern that doesn't 'ring' as much after flyback.. ** 'Enter number of scans to store': 200 for 1l4r (1loop4read) or 50 for 4l4r Note that this # can be easily changed while taking data ( command). 'Enter opd range of fast piezo (microns)': max range is about 110 microns. usually use 100 for 1r4l or 60 for 4r4l. 'Enter ratio of slow to fast OPD': must be <1. We usually use 0.5 'Enter observing wavelength (microns)': Current set up to work well for H-band filter only (1.65 microns) (*) We should document how to change the threshold since this is really an important step when one wants to go to long integration times (extra noise triggers detection). ** After answering all the questions the program will output the number of pixels per fringe for each of the IONIC3 outputs. One usually want at least 4 points per fringe, which means that the opd/npoints > 4 * lambda. This program will stop and warn you if your answers to the above questions do not conform to this, though you are not forced to follow this rule. ------------------------------------------------------------- 3. Inspecting raw scans type 3 at DAQ main menu. This program will show you the actual raw data on each of the 6 IONIC3 output channels. This will give you some idea of the count level and the fluctuations. Each plot is labelled to tell you which beams are contributing (since IONIC3 is a pairwise combiner, each output has contributions from 2 beams). There is also a running history plot in a second window corresponding to user-selectable set of pixels. In this window (as with IDL modules #4 and #5), you can hit to see a list of available keystroke commands. ----------------------- Summary of keystroke commands q quit 1 2 3 Show pixel history (DL1+DL2, DL2+FIX, DL1+FIX) a Print Average counts in each Channel (background subtracted) b measure Background Counts (see -a- above) ? this --------------- q Quit this module and return to DAQ main menu 1 2 3 This will change what is displayed in the pixel history plot. if you select DL1+DL2 then this will average the counts for the 2 pixels which have only DL1 and DL2 a This will take an average of the mean counts in each pixel and report them to you with errors. This is useful for testing (like aligning polarizers) b Take a background frame. Used in conjuction with above. --------------------------- 4. Finding Fringes and Taking Data Type 4 at the DAQ main menu. This is the module where you should spend most of your night. TAKING DATA! This program reads the data in each pixel, takes scaled differences for the complementary output of each IONIC pair-wise combiner. Thus you see here 3 sets of scans (instead of 6), one for each telescope pair. To the right of each scan is the instantaneous "cross-spectrum," which is similar to the power spectrum and is used by the fringe tracker algorithm. All the axes are labeled in microns (for the scanning optical path difference) and hertz (for the pseudo-power spectrum). In the scan plots (left), you will also see a vertical dashed line which is telling you where the fringe tracker is detecting the center of the fringe packet. If its stuck at <0> then it did not detect a statistically significant fringe. Likewise, on the right-hand plots the predicated fringe frequency is plotted along with the filter width being used by the fringe tracker. If you see fringe power appearing outside this window then something must be wrong. ** We note that the fringes do tend to appear slightly lower in frequency predicted. Its not entirely clear why yet.. ** When first running this program, IDL creates (if necessary) the Data directory based on the current UT date. All data is subsequently saved here. /home/iota/Data/utdate Also IDL looks into this directory and inspects all the iota* files to make sure that the vme will not overwrite any existing data files. Hence the 'filenum' variable in shmem will be changed to reflect this. At regular intervals, approximately 10 seconds, this routine will report which file is being saved and/or which file # is next in line. Also the status of the fringe tracker (LOCKED or unlocked) is reported. There are a number of very important and useful commands which are shown to you by hitting -- see below. ------------- Commands: q quit l Lock Fringe Tracker u UNlock fringe tracker s Save File n Change Number of Scans to Save m (Matrix) Take Shutter Data (A B C NONE) r Reset power spectrum averages p Print out Camera and Scanning Parameters' x Change Camera parameters c Change fringe track algorithm t Change fringe track threshold, gains and filter width ? This Message q quit and return to main menu l If you have detected fringes in 2 of the 3 outputs, then hitting L will start the fringe tracker and you should see the fringes jump to the center (and STAY THERE). u This UNlocks the fringe tracker. Its important to unlock the tracker when there are no fringes. If you don't, this can cause a NaN error in the 'Fringe Tracker Offsets" section in the OT. (see common problems) s This will save a file with the number of scans (n) you have set up.(*) The daq script inside the OT (See Pete Schloerbs Manual) allows the observer to select the number of files to be recorded. n This allows you to change the number of scans to be saved. It is believed that you can even do this in the middle of saving and it will obey (or stop saving if you enter a number smaller than the current_scan) m matrix data. This is a really useful command. It will take so-called "shutter" data used to determine the transfer matrix. Hitting will ask you to enter the number of scans in each file (usually 50 or 100). Then it will automatically use the shutter to only expose one star at a time, taking the required datasets. It will end with a background set. One should watch to make sure the stars 're-appear' when the open, since this feature is new and there may be some problems [e.g. Tel C's drive is not so good and the star wanders alot, making re-acquiring difficult if it moves off the field ] ** We should implement the PM search before taking each data since telescope wander will rarely (if ever) move it out of tip-tilt PZ range ** r reset averages. The right plots show a running average of the power spectrum, and hitting this key resets this to zero. p print out all the camera/scanning parameters. Useful for taking logs. Also useful because if IDL crashes or you restart things, then all the camera/scanning parameters are reset to defaults and you will have to set them up again. x change camera parameters. change number of loops and reads w/o having to exit module and try option #2. c change fringe track algorithm. Used for fringe tracker tests by pedretti. Not robust. Stick with the IOTA/Pedretti algorithm. t change fringe track threshold and other parameters. When there is a lot of photometric fluctuations, you might want to increase the threshold from the default 2.0 to something higher like 3 or 4. Also, you can change the gain of the fringe tracker loop. The default is .9, which is fine for fast modes. For slow modes like (3l7r) or for large piston conditions, you might want to change this to pz gain .5 or so to avoid throwing the fringes out of the scan range. Using this module and the delay search utility in the OT is very practical way to work for most of the night after initial alignment is done. EXAMPLE: A typical observing sequence: ---------------------------------- The pixel are supposedly aligned and enough flux is coming from each beam. a. Start from the OT a fringe search in one or two of the three combination pairs. See Pete Schloerb web description. If the search is stopped because the system believes it detects the fringe although it does not. Change the fringe detection threshold. b. Once the fringe is found in one of the baselines try a second search on the two other ones. c. Once three pair of fringes visible hit to activate the fringe tracker and lock the fringes. d. Choose the number of scans per file to be saved (hit ). Typical numbers are 100-200. And save the file by hitting . If you want to save a higher number of files use the OT script daq. e. Once the fringe recording is finished hit to unlock the fringe tracker you can then proceed to the matrix elements recording by hitting . Remember to setup the number of scans per file you want to save (hit , typical values 50-100). This should create four files. At the end of the matrix sequence the program will bring the three stars back and will offer to lock the fringe tracker again. Make sure that the three stars are indeed on the CCD. ---------------------------- 5. Fiber Explorer Type #5 at DAQ main menu. This program is used to move the fiber around to optimize coupling once you are startracking. The philosophy is that you should be startracking on a single star only (block the others). This program then lets you choose which telescope you are aligning by hitting 0,1,2. Then the program will show you two windows. One window shows a 2-dimensional map of the flux detected as a function of the location of the fiber (currently the units are in ADU (0-4096) of the digital-to-analog converter but could be changed to microns or arcseconds). The other window shows the time history and the average flux in the 4 pixels with contributions from the selected telescope. You can use the top two number rows of the keypad as arrow keys: 8 4 6 5 to move the fiber around. The step size starts at 100 ADU, but one should being exploring with larger step size like 400. The typical FWHM of the pattern you find should be around 400 which is about 1.5 arcseconds on sky). You can increase step size using the +/- keys. After each image the program reports which fiber you are moving and the current ADU for the x and y axis respectively. Also the step size being used is reported. Once you have gotten a fair number of pixels in the image and can basically see the beam pattern, you can do a 2-d gaussian fit by hitting 'f'. This will report the peak flux, major and min axes (FWHM) and centroid. You can go directly to this centroid by hitting . You can always move a fiber to anyplace you want using the key and entering the (x,y) coordinates in ADU. Another important feature is the ave and estore function. This allows you to save the fiber positions in a file for future retrieval. Since rebooting the vme computers will lose memory of the locations, this feature is critical for maintaing alignment from night to night. In addition, you can name the file anything you want, so you could have different settings for different stars if it proved necessary. For instance, a star which is saturating the star tracker often requires a significantly different fiber position and so one could save files for the two cases. A list of all the commands can be found by hitting and are shown below. The only opition I didn't discuss is auto-align. This takes 15 (gaussian) random samples around the current location and attempts to do a fit. Unfortunately this method is not as efficient as a human at this point (mostly because the loop time is really slow due to the aforementioned shmem map problem). q quit 0 1 2 Choose Fiber: Fix, SD1, SD2 4 6 Move: Left Right [look at number pad] 5 8 Move: Down Up x Enter coords to GOTO (x marks the spot)' f 2-d Gaussian Fit to image (Need >8 cells) g Goto peak of fit + - Increase/Decrease Resolution of Moves and Image a Auto Align (does not work well) s save voltages on all channels r restore voltages on all channels ---------------------------- 6. Picomotor Alignment This module is accessed by typing <6> on the DAQ main menu. When one does the initial system alignment or has to tweak the startracker mirrors, then one has to re-align the fibers onto the startracker. This is necessary because the fiber positioners have a very limited range and one must get fairly close initially in order to maximize the coupling. This is done by sending light backwards through the combiner and using a retroreflector to send the beams to the startracker, just like a star. IMPORTANT: One should use the "Fiber Explorer" to make sure the piezo voltages are centered (2047 2047) before doing this. (*) There should be a default file "center_fiber" that could be loaded for that purpose by the fiber explorer. Once you see the fiber on the star tracker mirror, then you can use this program to align the fiber onto the startracker at the right spot. This program moves the picomotors which are located on the flat relay mirrors on the IONIC (IR) table. Make sure the picomotor control box is on (and the piezo positioners too!), which is located on the floor under the IONIC off-axis-parabolas. Also the cpu0 programs must be running (which includes the serial port drivers and the picomotor control daemon). This is done by running the 'vxworks-start' script. After starting this module, you will see an IDL image of the CCD/Star tracker and hopefully the image of the fiber. The this program asks you: > Which Fiber to Align: 0 = FIX, 1= SD1, 2= SD2 (anything else =quit) You have to know which fiber you are seeing -- based on where the retro-reflector was placed. Choose. You will then see some circles and an arrow (hard to see sometimes because of a color table problem with the current left-hand monitor). This is just a sanity check to make sure you know what is about to happen since one can not back out of picomotor motions 100%. You will then be repeatedly asked this: > Hit Return to Continue (0 when satisfied, 1 go auto, 2 backout): If you hit return, you will HEAR the picomotors move and then see the next CCD image, which hopefully shows the fiber moving toward the right position. You can continue hitting return and watching the progress until it stops (1/20 of pixel from target), or you can hit <1> if you trust the program and it will automatically finish the process. However if you want to stop now without sending any pulses, then hit <0>. This will bring you back to the original prompt asking for you to choose a fiber to align. If you accidentally sent picomotor commands to the WRONG mirror and you want to "Back out," you can hit <2> which will send the pulses back. Unfortunately, the picomotors have significantly hysteresis and so this will not put the mirror exactly back, but it will be better than doing nothing... ----------------------------- 7. IOTA3GUI Hitting <7> on the DAQ main menu will launch a GUI program called IOTA3GUI. After setting up the IOTA3 baseline configuration, delay configuration, observing time and target/cal choice, you can slide the LONG DELAY sliders to see a plot of the required short delay position. Since the short delay lines have to exist in a short 2-meter window (or less for SD2), this plot is useful for planning. You can try the 'Advise' button to the let the computer advise you, but this adviser is really slow at the moment and the human brain is usually faster and smarter. I hope to improve this feature someday. You can add your targets to this list by modifying the file /home/iota/Idlstuff/IOTA3_Tools/IOTA3_Catalog.ASCII There is not QUIT button, so you must kill the window when done. Press right button on title bar and choose 'Close' to return to DAQ main menu. ----------------------------- ----------------------------- IV. Common Problems. A. Most of the crashing modes in the original version have been fixed. Please report problems to monnier@umich.edu. Crashing modes: 1. Changing between quadrant readout and fringe traking. Sometimes the DAQ on the vme hangs when trying to load a new program into the FPGA board. If this happens, see below section on "Recovering from DAQ crash." 2. Sometimes when the camera is saturating and you are taking data, the DAQ hangs on the vme. This bug can be avoided by uitting out of the data taking while saturating the camera. 3. others? B. All of a sudden the short delay total offsets go crazy (NaN) in the OT. You most likely left the fringe tracker on while adjusting yaw or something. If the fringe tracker runs for extended periods of time with no fringes, it will (for an not clearly understood reason) send a NaN garbage to the short delay line, causing the total delay offset to be undefined -- stoppping the short delay motion. To recover from this, go to the OT short delay paddle. Using the pull-down menus for each SD, highlight "zero fringe tracker offsets." Do this for both delay lines. This should reset things. Be sure to reacquire fringes since you will probably have lost your SD offsets. (Note if you had 'index'ed your offsets when you get the fringes, you could try the 'recover' option in the the pull-down menu to re-acquire those offsets. --- C. Observe program starts OK but does not display flux levels or has a weird behaviour when using option #1, #3, #4 and #5. Check that the Picnic camera is plugged in and the two power switches turned on (top of vxworks rack and boxe above the optical table. --- D. RECOVERING from DAQ Crash. If the previous hints don't work for you, then the only thing left to try is the following: Here are the steps to recover from daq crash as quickly and painlessly as possible. 1. try hitting ^C. if this returns you to the IDL prompt, then you can usually recover by typing IDL> .continue If this doesn't fix your problem, continue on to... 2. So if ^C didn't work, then hit ^Z to get out of IDL. 3. Find the the idl process and kill it. % ps [*locate the number # of the idl process] % kill -9 # 4. You can TRY to restart the software (% observe) but I have found this rarely recovers. You can probably just continue with #5 below. 5. Stop the SDs from tracking ("halt" them through the OT). 6. reboot iota-ppc2, by pushing the reset button. DO not reset ppc1 or ppc0, which control the startracker and telescope/delay system. 7. You will see the SD1 positions to be NaN. You can reset this by using the Delay Paddle window, and pulling down "Zero all Offsets" for SD1 and SD2. 8. Now re-load the daq as you would from the beginning (% cd iotamc; daq-start;observe) 9. All the observing parameters will be RESET in the process so be sure to hit #2 and reset all the camera and scanning params. ** Remember to reset all your camera and fringe tracker parameters before taking more data. The fibers will NOT be reset, since their locations are stored on another computer. 10. Start your delay lines again. This actually only takes a few minutes. --- E. JPB had a problem where the fiber explorer crashed after loading an incorrect filename.. This error needs to be repeated to determine cause/solution [some IDL error due to bad values; should be an easy error to trap] --- F. Surely more to come with use. ----------------------------- ----------------------------- Appendix. The data is always stored in /home/iota/Data/UT date For each set of scans, Currently there are 3 files created. iota#.header header file (ASCII) iota#.data binary file with raw data iota#.adc readout of selected Voltages for each scan (ASCII) Currently the ADC is not properly setup but all software works iota#.ofc Not well-documented yet, but will contain parameters logged for each scan -- such as scanning piezo offset or startracker centroid The header is quite verbose and contains many many things. Hopefully all we will need. The header data is organized by type and separated by comment strings (lines start with '#'). The main format is there is a text description then a ":" then the header info which can change from file to file. I will put here an example header and a table with slightly greater description. ----------------------------------------------- EXAMPLE ----------------------------------------------- Filename : /home/iota/Data/2002Apr13/iota111.header #--------------------------------------------------------------------------- --- # TARGET INFORMATION #--------------------------------------------------------------------------- --- Star : 12_Boo Source Type : Target RA (J2000) : 14.173056 Dec (J2000) : 25.091667 #--------------------------------------------------------------------------- --- # ARRAY GEOMETRY #--------------------------------------------------------------------------- --- Site : Mt. Hopkins, Arizona (IOTA site at Whipple Observatory) Fixed Delay : B Short Delay 1 : A Short Delay 2 : C Telescope A (N, E, U) : ne15 1132.420000 985.410000 -0.230000 Telescope B (N, E, U) : se15 -985.410000 1132.420000 0.230000 Telescope C (N, E, U) : cent 0.000000 0.000000 0.000000 #--------------------------------------------------------------------------- --- # OBSERVING INFORMATION (AT START AND FINISH OF SCANS) #--------------------------------------------------------------------------- --- UT Date : 2002 04 13 2002 04 13 UT Time : 10 36 20 10 36 41 Hour Angle : 2.467873 2.473722 LST : 16.642795 16.648644 Azimuth : 267.984147 268.034215 Elevation : 56.931629 56.857016 uAB (cm) : 787.580438 788.804684 vAB (cm) : -1970.440626 -1969.928998 uAC (cm) : -428.779131 -427.141511 vAC (cm) : -1324.737570 -1325.015366 uBC (cm) : -1216.355502 -1215.942105 vBC (cm) : 645.706687 644.917266 #--------------------------------------------------------------------------- --- # CAMERA PARAMETERS #--------------------------------------------------------------------------- --- Camera : PICNIC Pixels : 6 Good Points per Scan : 180 Scans : 50 Loops : 4 Reads : 4 T_int (ms) : 1.890909 Lambda (mu): 1.650000 #--------------------------------------------------------------------------- --- # COMBINER AND SCANNING PARAMETERS #--------------------------------------------------------------------------- --- Combiner : IONIC3 Pixel 0 : SD1 SD2 Pixel 1 : SD1 SD2 Pixel 2 : FIX SD2 Pixel 3 : FIX SD2 Pixel 4 : SD1 FIX Pixel 5 : SD1 FIX PZ Stroke SD1 (mu) : 30.501088 PZ Stroke SD2 (mu) : 15.250544 OPD SD1-FIX (mu) : 60.000000 OPD SD2-FIX (mu) : 30.000000 OPD SD1-SD2 (mu) : 30.000000 Flyback (n_samples) : 40 Fringe 0 Freq (Hz) : 53.418805 Fringe 1 Freq (Hz) : 53.418805 Fringe 2 Freq (Hz) : 53.418805 Fringe 3 Freq (Hz) : 53.418805 Fringe 4 Freq (Hz) : 106.837609 Fringe 5 Freq (Hz) : 106.837609 #--------------------------------------------------------------------------- --- # FRINGETRACKER INFORMATION #--------------------------------------------------------------------------- --- FT Threshold : 2.000000 FT Filter Width (pixels) : 7 FT Piezo Gain : 0.900000 FT Short Delay Gain : 0.090000 FT Algorithm (0:Ames, 1:Iota, 2:Coast) : 1 Fringe Tracker : OFF #--------------------------------------------------------------------------- --- # DELAYLINE INFORMATION (AT START AND FINISH OF SCANS) #--------------------------------------------------------------------------- --- SD1 (cm) : -160.429572 -159.882950 SD2 (cm) : -59.998248 -59.154886 LD1 (cm) : 149.984219 LD2 (cm) : 999.979060 #--------------------------------------------------------------------------- --- # STARTRACKER INFORMATION (A B C) #--------------------------------------------------------------------------- --- Startracker : Small-format Geary CCD (all stars on same chip) ST T_int (ms) : 4 Shutters : BLOCKED BLOCKED OPEN Max Counts : 21 21 871 RMS Jitter (arcsec) : 0.236129 0.169126 0.121807 #--------------------------------------------------------------------------- --- # BASELINE AND POINTING FITTING INFORMATION #--------------------------------------------------------------------------- --- Station Delays A B C (cm) : 1501.140000 1501.140000 0.000000 Delta AB (N E U) (cm) : -0.573000 -0.128900 -0.449800 Delta AC (N E U) (cm) : -0.798700 0.605400 -0.927200 Delta BC (N E U) (cm) : -0.227500 0.740300 -0.495800 Internal Offsets AB AC BC (cm) : 55.952800 -164.513100 -220.483600 # The following two columns correspond to beginning and end of scans Internal OPD AB (cm) : 35.023091 36.116264 External OPD AB (cm) : 39.137424 40.230407 Internal OPD AC (cm) : -564.204163 -564.797751 External OPD AC (cm) : -559.277088 -559.870292 Internal OPD BC (cm) : -599.244954 -600.931715 External OPD BC (cm) : -598.414512 -600.100700 SD1 Total Offset (cm) : -1.902837 -1.902837 SD2 Total Offset (cm) : 0.017856 0.017856 Roll A (deg) : 2.913194 2.982809 Roll A Total Offset (deg) : -0.025222 -0.025265 Roll B (deg) : 3.620361 3.691561 Roll B Total Offset (deg) : 0.022186 0.022217 Roll C (deg) : 4.474476 4.546131 Roll C Total Offset (deg) : 0.124709 0.124760 Tilt A (deg) : 24.819242 24.824374 Tilt A Total Offset (deg) : 0.000866 0.000867 Tilt B (deg) : 26.111120 26.116241 Tilt B Total Offset (deg) : 0.015501 0.015501 Tilt C (deg) : 25.099847 25.104969 Tilt C Total Offset (deg) : -0.018901 -0.018903 #------------------------------------------------------------------------------ # FIBER POSITIONS BEHIND PARABOLAS #------------------------------------------------------------------------------ Fix Fiber X Y (ADU) : 10 20 DL1 Fiber X Y (ADU) : 3000 4000 DL2 Fiber X Y (ADU) : 1500 3 ---------------------------- ---------------------------- Table of what it means (although the aim is for it to be pretty self-explanatory) ----------------------------- ----------------------------- Keywords Description ---------------------------------------------------------------------------- ----- Filename Name of the file being written Star Name of Star as it appears in the OT Source Type Is the star a Target or Calibrator? RA (J2000) Right Ascension (Hours) at epoch J2000 Dec (J2000) Declination (Degrees) at eopch J2000 Site Location of the Array Fixed Delay Telescope (A or B) which has the -Fixed- Delay Line Short Delay 1 Telescope (A or B) which has the SD1 Delay Line Short Delay 2 Telescope (C) which has the SD2 Delay Line Telescope A (N, E, U) Name of Telescope, (North, East, Up) Position in cm Telescope B (N, E, U) Name of Telescope, (North, East, Up) Position in cm Telescope C (N, E, U) Name of Telescope, (North, East, Up) Position in cm UT Date Year MN Day (beginning of scans) Year MN Day (end of scans) UT Time Hour Min Sec (beginning) Hour Min Sec (end) Hour Angle in units of hours (begin,end) LST Local Sideral Time (hours) (double) (begin & end) Azimuth (deg) Predicted Position of Star in Sky (begin/end) Elevation (deg) Predicted Position of Star in Sky (begin/end) uAB (cm) Vector A->B in cm EAST at start and finish vAB (cm) Vector A->B in cm NORTH at start and finish of scans uAC (cm) Vector A->C in cm EAST at start and finish vAC (cm) Vector A->C in cm NORTH at start and finish of scans uBC (cm) Vector B->C in cm EAST at start and finish vBC (cm) Vector B->C in cm NORTH at start and finish of scans Camera Name of Camera being used (e.g., PICNIC) Pixels Number of Pixels read out and recorded per sample Good Points in Scan Number of Points during linear part of scan (recorded data) Scans Number of Scans in file Loops Number of Loops in clocking pattern Reads Number of Reads in clocking pattern T_int (ms) Integration Time in milliseconds (measured by vme) per pixel Wavelength (microns) Wavelength (in microns) Combiner Which Combiner is being used (e.g., IONIC3, CFA3) Params depend somewhat on the combiner Pixel # What Beams are in this pixel (as ordered in the data file) PZ Stroke SD1 (mu) Full STroke of piezo in Microns in the SD1 beam PZ Stroke SD2 (mu) Full STroke of piezo in Microns in the SD2 beam OPD SD1-FIX (mu) OPD difference in microns of beams sd1-fix OPD SD2-FIX (mu) OPD difference in microns of beams sd2-fix OPD SD1-SD2 (mu) OPD difference in microns of beams sd1-sd2 Flyback (samples) Number of samples it takes for piezo to ``flyback'' -- data not saved Fringe # Freqs (Hz) Fringe Frequency Expected for Pixel # in Hertz FT Threshold Signal-to-Noise Ratio of Fringe used for Fringe Detection FT Filter Width(pixels) Half-width of Fourier Filter for Fringe Detection in ``natural'' Nyquist units (pixels in FFT) FT Piezo Gain The fraction of the fringe offset to correct using the fast piezo FT Short Delay Gain The fraction of the piezo offset to unload to the short delay line each scan FT Algorithm (0:Ames, 1:Iota, 2:Coast) : Use #1 please! FT Tracker ON or OFF -- was fringe tracking locked during DAQ [ FT Jitter ] rms opd jitter in each fringe [not implemented yet] SD1 (cm) Location of Short Delay 1 in cm at start and finish SD2 (cm) Location of Short Delay 2 in cm at start and finish LD1 (cm) Location of Long Delay 1 in cm LD2 (cm) Location of Long Delay 2 in cm Startracker Name of Startracker being used ST T\_int (ms) StarTracker integration time Shutters Blocked or Open for 3 telescopes Max Counts Max Count in Each Region (SD1, FIX, SD2) RMS Jitter (arcsec) RMS Jitter in arc sec [TOTAL] Total Counts for Each Telescope [not implemented] Station Delays A B C Delays used for each station (cm) (cm) Delta AB (N E U) (cm) Baseline correction to fiducial locations Delta AC (N E U) (cm) Baseline correction to fiducial locations Delta BC (N E U) (cm) Baseline correction to fiducial locations Internal Offsets Beam combiner offsets used in cm AB AC BC (cm) Internal OPD AB (cm) Total internal opd used at beginning and end of scans in cm External OPD AB (cm) Total external opd used at beginning and end of scans in cm Internal OPD AC (cm) Total internal opd used at beginning and end of scans in cm External OPD AC (cm) Total external opd used at beginning and end of scans in cm Internal OPD BC (cm) Total internal opd used at beginning and end of scans in cm External OPD BC (cm) Total external opd used at beginning and end of scans in cm SD1 Total Offset (cm) Total SD1 offset in cm (begin/end) SD2 Total Offset (cm) Total SD1 offset in cm (begin/end) Roll A (deg) Model predicted Roll in deg for Tel A (begin/end) Roll A Total Offset Offset needed to acquire star in Tel A (begin/end) (deg) Roll B (deg) Model predicted Roll in deg for Tel B (begin/end) Roll B Total Offset Offset needed to acquire star in Tel B (begin/end) (deg) Roll C (deg) Model predicted Roll in deg for Tel C (begin/end) Roll C Total Offset Offset needed to acquire star in Tel C (begin/end) (deg) Tilt A (deg) Model predicted Tilt in deg for Tel A (begin/end) Tilt A Total Offset Offset needed to acquire star in Tel A (begin/end) (deg) Tilt B (deg) Model predicted Tilt in deg for Tel B (begin/end) Tilt B Total Offset Offset needed to acquire star in Tel B (begin/end) (deg) Tilt C (deg) Model predicted Tilt in deg for Tel C (begin/end) Tilt C Total Offset Offset needed to acquire star in Tel C (begin/end) (deg) Fix Fiber X Y (ADU) The fiber explorer positions for the FIX beam DL1 Fiber X Y (ADU) Same, for DL1 beam DL2 Fiber X Y (ADU) Same, for DL2 beam ---------------------------------------- iota3.ofs [offset file] D1 D2 Fringe locations in microns of piezo stroke. However, JDM suspects these are labeled backwards.