User`s Manual for MagIC-e2v and LOUI Version 1.5.4
Contents
1. directory on the observer com puters Transfer data from magic e2v see 9 1 The sixth frame in file number 273 taken in occul mode can be displayed with the command display ut090423_0273 fits 6 1 One may then use one s favorite IRAF commands e g imexam to take a quick look at the data Once in imexam put the cursor on a star and type acomma You will get the peak count total count sky background FWHM ellipticity and position angle without IRAF opening an unwanted plot window Another useful command is findgain which uses 2 flats and 2 biases to determine the gain and the read noise An example of good read noise Flats flat009 201 250 201 250 amp flat010 201 250 201 250 Zeros dark009 201 250 201 250 amp dark010 201 250 201 250 Gain 0 53 electrons per ADU Read noise 5 22 electrons Other IRAF favorites include imstat imhead and hselect 20 9 3 Useful image header keywords Header Keyword Description OBJECT OBSTYPE OBSERVER OBSAFFIL DATE OBS FILENAME CRDELT3 EXPTIME TRIGGER UTCSTART SUBARRO1 FILTERT FILTERB AIRMASS CAMMODE TRIGNOM TRIGCNT NAXIS1 NAXIS2 NAXIS3 POSTSCAN LST OBS TELRA TELDEC HA ZA COMMENT object name what you typed in object flat bias etc observer name you entered observer affiliation you entered UT date yyyy mm dd of observation original location on instrument computer Integration Interval from occul mode Actual integration time s s2. ooa ee a ee ee a es 11 2 1 The trigger time is too short ogee hw in bike a 11 2 2 Incorrect observer name institution other info ooa aa 11 2 3 Exposure times incorrect in hard occul mode headers 11 2 4 Blank Fields or Surprise Values for LOUI inputs 11 3 Problems for which we as yet have no solution 11 3 1 Timing Board Failure or LOUI is stuck on TIM downloading 11 3 2 Missing bad header times oaoa 004 LD oa Pattern Noise eiry a ede Ek Oe ee et Bed SR BOs SAR eed Gee ee 12 Version History A Resetting or checking the PC104 clock using Telnet B Minimum Exposure Times in occul Mode 20 20 20 21 21 22 23 23 23 23 23 23 24 24 24 24 24 25 25 25 25 25 26 26 26 27 29 1 Preamble and History As originally conceived the Magellan Instant Camera henceforth MagIC was to have either two or three CCDs in its focal plane each intended for a somewhat different use For a variety of reasons including the availability of devices MagIC was delivered to Magellan with only one CCD a SITe 2048x2048 device While useful for most of the programs for which MagIC was originally intended the SITe device and its associated electronics and control system are ill suited to high time resolution and precisely timed imaging In June 2007 MagIC was removed from the Clay telescope returned to Cambridge Massachusetts and outfitted with an e2v 1024x1024 frame transfer
3. 0 Rows per Bin Roo i Columns per Bin Number of Frames Over Scan Trigger Type hra Exposure Time s 0 1 Integration Interval s Number of Exposures 1 Frame Type dark le Object Title FITS Comment testing subframe Figure 6 Single top and occul bottom mode control panels 16 7 7 The status window The information in the status window is for the previous completed exposure it will not update until your exposure is entirely finished The Console is therefore the only way to keep track of how much time you have left One sees messages of the sort 20 01 46 Level _2 Num Pixels 10103296 90 00 The percentages do not corre spond to an integral number of frames but suffice to let you know whether you have time to deal with the side effects of prudent desert altitude hydration The following lines indicate that an exposure is finished 03 17 14 Level_1 Number of Exposures Left 0 03 17 14 Level_4 Instrument threads have been reactivated 03 17 14 Level_4 Telescope threads have been reactivated The status window can be misleading The bar at the time of the frame indicates the percentage time remaining on the current frame not on the exposure Moreover after an exposure is complete the bar reports the progress of a phantom frame You may start a new exposure before this phantom frame finishes in which case the bar will try to report simultaneously on the progress of the first new frame and the phanto
4. 3 In IRAF type cl gt epar mvmagic 4 Enter the coordinates of the pixel you wish to center your object on 5 type go to execute mvmagic 6 Select the star you want using the donut cursor 7 Confirm this offset both verbally with the telescope operator and on the computer 19 9 Your e2v data 9 1 Transferring Data to the Observer Computer from magic e2v Data are written to a directory on magic e2v specified by using the storage tab on the LOUI display They are also displayed frame by frame time permitting in an SAOimage DS9 window that magic e2v projects onto the observer computer The data are not automatically transferred to the observer computer A file transfer program Transmit is available in the Applications folder on the observer computers Trans mit allows for syncing of folders on a remote computer with a directory on the observer computer Caveat it is possible to accidentally sync the wrong directories with disastrous results Additionally one must hit the refresh button when new files are added and have the proper computer s files hi lighted when doing so We strongly advise against transferring data while LOIS is taking new data This is known to crash the SITe data acquisition computer and may also crash magic e2v Why tempt fate 9 2 Data display and quick look On the observer computer start IRAF and SAOimage no you can t use the one that LOUI popped up IRAF s login cl file is found in the iraf
5. CCD MagIC returned to Magellan in August 2007 and was installed on a folded port on the Baade telescope in November 2007 MagIC was still limited in the speed and efficiency with which it could take data because the old data acquisition software the Lowell Observatory Instrument System henceforth LOIS could not run the e2v frame store mode In February 2009 a new version of LOIS was installed but with the Lowell Observatory User Interface henceforth LOUI wrapped around it The new LOIS LOUI system can exploit the frame transfer mode of e2v and can produce precise GPS timing Since 2010A MagIC has been retired as a facility instrument and was removed from its folded port on the Baade In June 2010 MagIC was reinstalled on a Nasmyth port of the Clay The SITe mode of the camera is still available for proposals while the e2v is a PI instrument This manual describes the operation of the e2v camera alone 2 MAGIC SITe and MAGIC e2v Instrument Setup To first order users should think of the SITe and e2v CCDs as two separate instruments They share a common dewar a common shutter and a common filter wheel But they have parallel data acquisition systems including separate electronic boxes at the telescope and separate data acquisition computers called magic site and magic e2v running differ ent data acquisition software the old LOIS software and the new LOIS LOUI software Switching between instruments requires shutting down t
6. MAGICEIIV R command ticks 0 0 22 17 34 Level_2 first QMM Unix secs is 1 22 17 34 Level_2 QMMAhead offset 0 secs 0 usecs 22 17 34 Level_2 QMM time is O days O hours O minutes and 0 000000 seconds ahead 22 17 34 Level_5 Sending trigger halt If left in this state LOIS will use software triggering Use the ctime tset command as described in 86 5 to start the PC104 clock Alternatively if the PC104 clock was running you will see 21 47 00 Level_2 attempting to sync time to QMM 21 47 01 Level_4 MAGICEIIV R command ticks 1243547220 1243547221 and trycount 21 47 01 Level_5 synctrig systicks 1243547220 633604 1243547221 236479 21 47 01 Level_2 first QMM Unix secs is 1243547221 21 47 01 Level_2 QMMAhead offset 0 secs 64959 usecs 21 47 01 Level_2 QMM time is O days 0 hours O minutes and 0 064959 seconds ahead 21 47 01 Level_5 Sending trigger halt In this case the master clock is running 0 06 seconds ahead of magic e2v 6 5 Start and set the master clock on the PC104 Unless you are absolutely certain that the PC104 has the correct time and is ticking sync the PC104 In the command editor type ctime tset and you will see the following in the Console window 01 13 48 Level_4 Setting the QMM TOD clock 01 13 49 Level_4 QMM Set to Fri May 29 01 13 49 2009 for time of day clock The command ctime calculates the number of seconds since 1970 01 01 00 00 00 and syncs the PC104 to magic e2v which is in turn synched by NTP We believ
7. e2v Configuration Because the e2v chip is a PI instrument MagIC should be returned to SITe mode after an observing run is over e Exit LOIS and LOUI as described in 810 e Go into the computer room and move the rainbow wired cord from the back of magic e2v to magic site e You should be able to start LOIS and connect to MagIC via magic site If not try resetting the PCI card white button on the back of magic e2v or cycling the power on the filter wheel see 11 1 6 e A very polite person may consider updating the IRAF magic packages to reflect the CCD switch see 8 5 Starting up the e2v 5 1 Software Triggering no GPS Make sure the PC104 magic backup is turned off It is located in a cabinet in the ground level utility room and is connected to KVM button A as of June 2010 Clay An on off toggle switch is located at the bottom left of the back of the PC104 A green LED indicates that the PC104 is on If the PC104 crashes and goes into kernal panic LOIS will hang up Thus though the PC104 does not interfere with data aquisition it is recommended that the PC104 be turned off if only software triggers are to be used Why push your luck 5 2 Hardware GPS Triggering 5 2 1 Starting the PC104 Hardware triggering giving precise timing is accomplished by interrogating a GPS receiver This is mediated by an RTD PC104 running linux named magic backup All three com puters magic site magic e2v and magic backup are h
8. files can be found at home observer lois logs on magic e2v 11 2 4 Blank Fields or Surprise Values for LOUI inputs If a field is left blank LOUI will dredge up the last used value from somewhere Whenever LOUI is started and restarted be sure to check the fields for observer affiliation file location number of frames in occul mode object and fits comments and make sure they are not blank or have not been set to something else While having someone else s name in your FITS headers is relatively harmless setting LOUI to take the wrong number of frames is not 11 3 Problems for which we as yet have no solution 11 3 1 Timing Board Failure or LOUI is stuck on TIM downloading During the execution of source loissetup tcl the command window may not progress further than TIM downloading This error is preceded by Level_0 Unable to reset 25 the Controller and indicates a failure of the timing board to initialize If the timing board is working properly the script will not pause at TIM downloading at all Unfortunately while this problem has been overcome the cause and the precise sequence of tinkering that leads to its resolution has not been pinned down If you experience this error you should start everything up from scratch by doing the following 1 Reboot computers 2 Power cycle instrument electronics 3 Reset PCI card on the back of the Suns The fiber connections SHOULD be fine do not pull at the cables H
9. included for the sake of completeness and diagnostic purposes but preferred and very much simpler method for resetting the clock is through LOUI as described in section 6 5 1 Find yourself a reliable clock The UTC clock in the control room in the rack next to the operator is safest but requires two people When properly synched the clocks on the observer computers seem to be ok One must however set the system preferences to display seconds 2 Check the time on the PC104 Open an xterm on the observer computer and telnet into the captive process on the PC104 magic backup and check the time telnet magic backup 3112 Trying ip address Connected to magic backup lco cl Escape character is CTRL Q O 2009 073 19 27 30 Q O 2009 073 19 27 35 Q O 2009 073 19 27 40 xX 0 CTRL telnet gt quit Connection to magic backup lco cl closed Note that you must exit the captive process cleanly by typing x or you will crash the system The captive process responds with a 0 if it carried out an instruction 27 successfully and with a 1 if it was unsuccessful Exiting telnet is with CTRL is also essential Note that the captive process did not require a password If you are HAPPY with the synchronization you may skip the next step Set the time on the PC104 Open an xterm on the observer computer and telnet into the captive process on the PC104 magic backup and give the PC104 the correct time te
10. lois logs 7 9 Subframes A subframe is set with the command subframe sub 1 xpix lt col center gt ypix lt row center gt xsize lt number of columns gt ysize lt number of rows gt More simply one can fill in those values in at the bottom of the GUI window pictured in figure 6 BE SURE TO CLICK DEFINE after entering in values for your subframe 8 Telescope Pointing the magic IRAF package The installation of IRAF on the observer computer contains special package aptly titled magic During observing functions in this package are used to offset the telescope so that your object is centered on the correct CCD as well as adjust the pointing of the telescope Be sure to check with the telescope operator when you execute a script that will offset the telescope After starting IRAF on the observer computer type magic to load the magic package 8 1 tomagic centering on the e2v Edit the parameter file to indicate which CCD you are using ecl gt epar tomagic Set ccdname to e2v or site Select yes to send offsets to the telescope control system TCS and no to performing a coordinated offset Type q to exit Run the script any time you move to a new target ecl gt tomagic The magnitudes of the offsets to the two CCDs are constant and have been set in tomagic to be 50 5 for the SITe and 92 6 for the e2v note that the SITe is in the opposite direction from the center of the e2v These values are given in arcseconds along th
11. retaking an image at the listed minimum could cause errors to occur It is recommended that a chosen binning and subframe be further tested and that your cadence be slower than the listed minimum The minimum times listed in Table 3 were the shortest measured times in which a GROSS error did not occur that is one more trigger was permissible Since the line between gross errors and one additional trigger was not sought a less than sign indicates the lowest exposure time tested Binning was tested for 1x1 2x2 and 4x4 While 8x8 binning was tested this binning is not supported by the camera Binning up 5x5 should be supported but 3x3 and 5x5 were not analyzed in this test Some of the highly binned small frame exposures show an x instead of an exposure time These settings caused LOUI to give errors at exposure times that were much longer than were reasonable for a frame of small size It is assumed that the software cannot handle these tiny frames It is recommended these subframes not be used at all or be tested by the user prior to nightfall One of the most startling results of Table 2 shows that extreme binning or extreme subframes do not decrease exposure times in proportion to the number of associated pixels 30 Table 1 Sizes of various subframes Field size assumes approximate 40 field of e2v chip Table 2 Frame fraction FOV 1x1 2x2 4x4 Center 512 256 128 Full Frame 40 1052x1028 526x514 264x258 1 0
12. the bottom of 13 the image Fast mode has not been verified on the e2v Don t even bother with pipeline mode o Status X A Observer E Adams MIT Path home observer data ut090315 Total 58346341 KB Next File Name 20090315_0026 fits Used 9014803 KB Last File Stored 20090315_0025 fits Available 49331538 KB Object Title dark 0 UT Date 1970 01 01 FITS Comment testing Start Time 00 00 00 00 End Time 00 00 50 0 mode 45 Frame Type 3 Exposure Time ms 4986 Exposure Time us 841 Interval between Image Starts ms 5000 Interval between Image Starts us 0 Number of Exposures Trigger Type 102 Number of Rows per Bin 2 Number of Columns per Bin 2 a Overscans 40 Overclocks 0 M Figure 5 The status window Note that the information for the previous exposure 200903150025 is displayed and that this frame has a bad UT Date and start time 7 4 Aborting Images DO NOT ABORT IMAGES While a button exists on the GUI it is not believed to be a stable abort for the system Aborted exposures on other LOUI LOIS systems have not only caused the instrument computer not just the program to crash but have made restarting the system difficult afterwards more details are not available this will be tested sometime in the future meanwhile recovery is NOT supported 7 5 Observing in occul mode To use the frame transfer capabilities you must use the occul mode The names of the parameters
13. 0 x 1 00 40 1024 512 256 0 75 x 0 75 30 768 384 192 0 50 x 0 50 20 512 256 128 0 25 x 0 25 10 256 128 64 0 125 x 0 125 He 128 64 32 0 06125 x 0 6125 2 5 64 32 16 Minimum Exposure times for the e2v chip in seconds All data were tabulated using an overscan region of 16 pixels and a centralized subframe An x indicates subframes that should not be used and the exposure time at which further testing was abandoned For all listed times the listed time minus 0 05 seconds was tested and found to yield additional triggers Frame fraction FOV Ixl 2x2 4x4 Full Frame 40 6 00 2 90 0 95 1 00 x 1 00 40 6 00 2 90 0 90 0 75 x 0 75 30 4 70 1 80 0 70 0 50 x 0 50 20 2 80 0 85 0 50 0 25 x 0 25 10 0 85 0 45 0 45 0 125 x 0 125 5 0 45 0 50 x 0 06125 x 0 06125 2 5 0 50 x x Table 3 Minimum Exposure times for the e2v chip in seconds Assumes that 11 12 triggers is valid A less than sign indicates that times of 0 05 s shorter was not tested Some times remains the same as above because a gross triggering error occurred at 0 05 s shorter Frame fraction FOV Ixl 2x2 4x4 Full Frame 40 6 00 lt 2 85 lt 0 90 1 00 x 1 00 40 6 00 lt 2 50 0 85 0 75 x 0 75 30 lt 4 00 1 80 0 65 0 50 x 0 50 20 lt 2 50 0 85 lt 0 50 0 25 x 0 25 10 0 85 lt 0 40 lt 0 40 0 125 x 0 125 5s 0 40 lt 0 40 x 0 06125 x 0 06125 2 5 0 50 lt 0 40 Xx 31
14. Imaging is further complicated for successive cubes of the same size where the triggering message may be different each time The messages are correlated with trigger speed Imaging too fast will cause a gross error imaging slower will cause additional triggers to be received while slow enough trigger speeds will cause exactly the number of expected triggers to be received The variation in message received is probably based on a variable readout speed though the exact cause is unknown The inconsistent readout makes it difficult to determine an minimum exposure time To determine approximate minimum exposure times five sets of 10 images were taken in a variety of frame sizes and bins See Table 1 for the size of each frame in terms chip area pixels and arcseconds While nominally a 1024 x 1024 chip the e2v has actually reads out 1052 by 1028 pixels and so a distinction was made between a 1024x1024 chip and a full frame Each frame can be defined in LOUI as xpixel ypixel xsize ysize or the center coordinates and edge length The center coordinates are constant for each binning group The minimum exposure times listed in Table 2 were the shortest times in which five images could be taken such that the exact number of expected triggers were received in all five frames Every minimum exposure time was calculated in intervals of 0 05 s such that if 0 85 s is listed as the minimum time using 0 80 s had caused an error It is perfectly possible that
15. Instead the data is clocked into the frame storage area of the detector this takes roughly 3 ms and data begins to accumulate in the active half of the CCD An exposure consists of multiple frames written out as a single 3D FITS file A less specialized name for this button might have been continuous SDOTS This permits multiple exposures on the array after shifting the charge by some amount It permits old style focus frames stepping through focus and shifting the charge FIND This gives continuous video signal FDOTS Like SDOTS only faster 12 e STRIP Time delay integration data acquisition Unless you are on the equator you will need to track the telescope in a great circle 7 3 General instructions for all observing modes e Select a trigger hard uses times from the PC104 soft uses the internal clock on magic e2v e Enter an object name and a comment If you do not enter an object name or fits comment it will use the previous values even if the entry line looks blank e Enter an overscan if desired Be sure to enter some overscan value 32 and 40 pixels commonly used Overscans are especially useful since the noise levels on the e2v are known to sometimes change with time Adding an overscan will slow the readout time though this effect is most pronounced on binned subframes e Binning Binning the chip will allow for faster exposure times and smaller file sizes in occul mode The chip can be bi
16. User s Manual for MagIC e2v and LOUI Version 1 5 4 Last Modified by Amanda Zangari August 4 2010 Contents 1 2 Preamble and History MAGIC SITe and MAGIC e2v Instrument Setup Switching to the e2v from the SITe Configuration Switching to the SITe from the e2v Configuration Starting up the e2v 5 1 Software Triggering no GPS 6400445584 c544 42465 44 64 404 5 2 Hardware GPS Triggering hsb kiede in Renker ge dh ah iether tard Ent Ye ee ee Se Sed 5 2 1 Starting the POIMA cins 4 p 4 sepals ook a Sa Re Ale bly pln A 5 2 2 Resetting the master clock on the PC104 Launching the e2v Data Acquisition Software LOUI LOIS Gil Star lO We a wo tee by ese chr abot he ete oe eee ine Nets Oe ete te Bos 6225 OLE LOIS ese adain a aa e Ae te a his oe A Bg A ad Ses hn ES oe Hee On LOULO OTe Je og ese ok Wo eee oh Se ha fee eed at eed oO a a 6A Cons le messages ce ee aang tenia e fee wep e are a tie ine ee 6 5 Start and set the master clock on the PC104 0 6 6 Check the data path and reset if necessary 2 004 6 7 Enter observer information and first fle number Recording Data with the e2v 7 1 Choose your filter ot at oS ko a ee EOE GE SERS ee 7 2 Choose the data acquisition mode oaoa eS Gee Se ee We Soe Wed 7 3 General instructions for all observing modes TA AUSPICES jena gs Ne r aS asp er ce a Qh geen vp ibe Sock PHRMA HAO BU BS 7 5 Ob
17. achine comes back online you log in as root and do a soft reboot su root sync sync reboot You may also want to restart the PC104 at the same time 11 1 6 The filter wheel does not initialize The filter wheel on at least one occasion got confused with all the crashing and restarting of LOIS and LOUI and failed to initialize If LOUI hangs on the following line for more than a minute or so you should power cycle the filter wheel 14 15 19 Level_3 MagICfilt Module Opening please wait The filter power is easily reachable on the Nasymth port of the Clay For a folded port you would need the help of a ladder In either case you should consult an instrument specialist before cycling the power on the filter wheel The filter wheel power is controlled by a large red button below the filter wheel electronics box The outward and downward position is on while inward and upward is off To cycle the power push upwards on the red button You may need to twist for the button to come back down 11 1 7 LOUT is stuck on TIM downloading See 11 3 1 11 2 Problems that can be avoided 11 2 1 The trigger time is too short The LOIS console reads something like Gross error in triggering expected 3 got 15 This means you need to either 1 increase your integration time or 2 bin more 24 because you are trying to run faster than the system can handle See Appendix B for a discussion of minimum exposure times 11 2 2 Incorrect
18. alize LOIS the filter wheel and the telescope modules eee LOU MagIC E2V o E F Camera Control Remote User Button W Dashboard E Camera Control perspective A Camera Control 53 User Button O Storage Config Observer Info i o f fird fdots sdots strips occul Observer ase Path ae Total OKB Next File Name Used OKB Last File Stored Available 0 KB Object Title UT Date FITS Comment Start Time End Time mode Frame Type Command far E Amplifier L E Subframe 0 Rows per Bin 1 Exposure Time ms Number of Exposures Number of Rows per Bin Interval between Image Starts ms Exposure Time ys Trigger Type Number of Columns per Bin Interval between Image Starts ps E Over Scan 0 x 7 Trigger Type hard oa Tal Exposure Time s 0 1 Filter Wheel amp Focus 33 E Telescope Telemetry Abort Columns per Bin 1 Over Clock 0 Number of Exposures 1 object B Frame Type Object Title FITS Comment xpix ypix xsize ysize Define subframe Console Gx BE ef B rg 0 E Console 8 El Console LOIS log Figure 1 LOUI screen just after launch You will probably want to resize some of the sections especially the Console log and the Camera Control To do this click on the thin area be
19. are somewhat confusing Warning The value for Number of Frames defaults as a blank LOUI will happily ask MagIC to use the last used value Given the nature of occultation mode it is very possible this number could be something like 2000 Given that aborting images IS NOT POSSIBLE be very very sure to check that this field is properly filled in 7 5 1 Hard triggers in occul mode With hard triggers occul mode produces an image cube After a time specified by the integration interval a frame is transferred to the frame transfer area and read out In the meantime integration is under way for the next frame The total number of frames 14 gives the depth of image cube When starting LOUI this field will be left blank If not filled in LOUI will default to the last used value which may be anything An exposure is then an image cube not a single frame Each exposure produces a new FITS file which is three dimensional Setting the number of exposures to something greater than unity gives more than one image cube The shutter opens at the beginning of an exposure and closes at the end of an exposure Note that if you have selected a hard trigger you cannot set the exposure time 7 5 2 Soft triggers in occul mode With a soft trigger occul mode also produces an image cube It is much the same as with a hard trigger It differs principally in that the time per frame is entered a
20. cess 11 Troubleshooting the e2v 11 1 Connection and Setup Issues 11 1 1 Trouble initializing LOIS If you have an important looking red error in LOIS particularly early e g the timing board fails to initialize you may find it goes away when you restart If you have just restarted the magic e2v computer it may take a while for everything to wake up and be ready The ActiveMQ server in particular takes 1 2 minutes longer to start up than magic e2v takes to become available for ssh access but the timing board and other components may need some time as well As a first recourse to most problems restart LOUI and LOIS and try again 11 1 2 Problems with SAOimage DS9 DS9 sometimes does not link properly to LOUI Sometimes the latest frame will not display other times only every other frame in an exposure will show up It s not clear why Restarting LOIS and or LOUI may help 11 1 3 The PC104 magic backup is down common The PC104 is not the most stable of machines and tends to crash if left on for longer than a day or so It also can crash if it gets confused perhaps if something went wrong with LOUI LOIS and there was a crash or a forced quit It will crash if you do not exit telnet cleanly after setting the time Sometimes it just crashes for no discernible reason You can tell it needs rebooting if a you cannot ping telnet etc it and or it says it is in kernel panic or b you can telnet in but it returns no time w
21. d then it will be noted as such in the log but the system will not consider an error to have taken place While the chip is reading out the software will ignore any triggers received and simply wait for the next trigger to transfer the next frame resulting in a clean image albeit one taken at the exposure time longer than specified It is difficult to locate these lines while images are being taken The lock button second to the the left see Figure 9 allows you to turn off automatic scrolling of the console log E Console El Console EI Console Bille e o LOIS log Figure 9 Console log window Clicking lock button giant arrow allows you to stop auto matic scrolling of the console log This button is very handy if you want to look through the log for triggering messages while you are imaging 29 If the log is not available to you don t forget to copy it over along with your images it s automatically written to home observer lois logs with the current date the number of triggers expected and received are stored in the image header as keywords TRIGNOM and TRIGCNT The authors of the LOUI software have asserted that receiving a small number 1 2 of excess triggers with no gross error thrown does not indicate a too greedy choice of cadence though such errors indicate the user is near the line of what is acceptable Placing a subframe in the lower left corner of the chip may also allow for faster read times
22. e detector axes and the corresponding values in cardinal directions depend on the rotator angle For example on the Baade folded portfor the e2v in EQU 0 0 an object to the south will be offset 92 W and 6 N while for the SITe the same object would be offset 50 E and 5 N Which offset to use is determined automatically so long as the correct CCD is specified in the parameter file The new offsets should have been updated for the SITe and e2v when MagIC was brought to the west Nasmyth port 18 r 0009 X IRAF xgterm 0 0 Image Reduction and Analysis Facility PACKAGE magic TASK tomagic cedname e2v Move to CCD center site or e2v queryl yes Send RA DEC offset to TCS query3s no Do coordinated offset mode ql f magic gt J Figure 7 Parameter file for IRAF script tomagic Set ccdname to either site or e2v 8 2 mvmagic object centering The IRAF routine mvmagic quickly and powerfully allows the user adjust the telescope pointing to within the CCD frame Generally the user selects a pixel on the frame such as the center or nice and far from the amplifier seam and then opens an image in DS9 and selects a star such as your object Then mvmagic will calculate and execute the telescope offset so that the star will now be located on the specified pixel 1 Transfer the most recent image over to the observer computer See 89 1 for instructions on how to do this 2 Load this image into DS9
23. e this to be reliable The fractional seconds are governed by GPS 6 6 Check the data path and reset if necessary LOIS remembers some of the settings from the previous time it was run Unfortunately the directory path may not be correct A common behavior is the truncation of the last digit so that home observer data ut090315 becomes home observer data ut09031 Since LOIS will create the directory if it does not exist all of your data will be stored to 09031 instead of where you actually want it to go Do not use a trailing Be sure to hit Apply Possible solution the disappearing directory path problem goes away if one sets the Root Filename to the same as the name of the data directory e g Dir Path home observer data 20090518 and Root Filename 20090518 It works all the time if the Storage Configuration is reset after linking LOUI to LOIS In June 2010 AMZ did not get this to work 10 6 7 Enter observer information and first file number The system does a better job of remembering observer info and the next file number These are entered using the observer info and config tabs E Camera Control O User Button T Observer Info O O Camera Control 0 User Button 0 Storage Config 0 xI iu 2 I Observer Name E Adams Directory Path home observer data ut090315 Observer Affiliation MIT Root Filename 20090315 Initial Image Number 118 Apply Reset Clear M Fits Extensi
24. f it has not B Minimum Exposure Times in occul Mode The e2v software LOUI does not calculate a minimum exposure time for hardware triggered images Triggering faster than the readout time does not produce a known software failure When the e2v is triggered faster than the minimum readout time messages are put in the LOUI logs that inform the user that he or she was too greedy with the cadence Meanwhile the system with happily take images taking as much time as it needs to read out The program will list the UTC start time and UTC end time in the image headers as what the start and end time should have been had the system been capable of taking images at the rate requested There are two particular lines that one needs to look for in the LOUI logs to see if a cadence that was too quick was selected One will appear before the imaging begins and it states that the Occul hard triggered itime is too short This line only appears if the trigger line is much too short However a second message will always appear after all the images in a set are taken It will state that a certain number of triggers were expected and a certain number of triggers were received If all is well those two numbers should be identical and a message similar to Triggering expected 11 got 11 will appear If the cadence is too fast a Gross error in triggering will occur and many more triggers will be received than expected If 1 2 more triggers were received than expecte
25. he data acquisition program mov ing the rainbow colored filter wheel controller cable from one acquisition computer to the other and starting up the appropriate data acquisition program This should take less than 10 minutes perhaps less than 5 However switching to the e2v from the SITe has proved to be an unstable process and should not be done in time sensitive situations Often an error will occur such as a timing board failure that takes several hours to debug Additionally the e2v electronics may need to be restarted to remove pattern noise In addition if and only if precise timing is needed one must start up a third computer magic backup a PC104 that serves as the interface between the GPS timing system and magic e2v To use the e2v one must be ssh d into magic e2v from one of the observer computers in the Magellan warm room At the Clay these computers are known as zorro and guanaco The Baade computers are burro and llama Scripts to start LOUI and offset the telescope are installed directly on the observer computers so it is not possible to observe from another computer such as a laptop brought to the summit by an observer When the term observer computer is used in the text it refers to guanaco or zorro For the June 2010 installation on the Clay Nasmyth west port The instrument computers magic site magic e2v and magic backup are installed in a rack in the Clay computer room The particular Cyvex KVM
26. hen you query it with Q or c the timing in LOIS starts looking funny and giving unusual QMM errors in the console log except for the QMM Start Time Error which has no solution yet The only way to fix magic backup is to hard reboot it Afterwards remember to set the time see section 6 5 11 1 4 LOUI doesn t talk to LOIS The main symptom is that the Command Editor in LOUI will not appear to work most notably on the step where you type source loissetup tcl 23 The main culprit is if the system time on the observer computer is not set to the correct UT time In theory these machines are linked to NTP servers but if for some reason they are not linked properly the machine times may drift If the time on the observer computer where LOUI runs is different from the time on magic e2v where LOIS runs by 10 sec then the two programs will not communicate properly You will need an administrative user to fix this 11 1 5 magic e2v does not respond During one exposure right after getting some odd QMM errors magic e2v stopped respond ing suddenly and dropped off the network The only solution to this is a hard reboot After verifying that the machine is truly unresponsive note that the machine is NOT hooked up to the KVM hold down the power button on the front of the magic e2v machine wait a few seconds then power it back up Because magic e2v does not like to be rebooted this way it is recommended that once the m
27. horter in occul mode Specifies whether hardware or software triggering was used Start time of your images Unbinned boundaries for subarray 01 Top Filter Position Bottom Filter Name airmass CCD exposure mode Nominal Trigger Counts Calculated Actual Trigger Counts Received number of rows number of columns number of frames size of overscan region Local Sidereal Time of exposure start TCS right ascension hh mm ss TCS declination dd mm ss hour angle zenith angle Your comments Note that the telescope name TELESCOP says Baade in the header This has been hard coded into the header but is completely unrelated to the code that tells LOIS that Thus the header telescope name is wrong but harmless The temperature of the CCD DETTEMP is also inaccurate Only the SITe can query the CCD it is talking to the Clay temperature 9 4 Checking images for pattern noise The e2v has a pattern noise problem possibly related to bad grounding of some component An extreme example is Fig 8 but there are other patterns possible Note that binning will change the pattern 21 Pattern noise was a particular problem with the e2v on Baade in 2009 but is highly setup specific You should always check for pattern noise especially if the instrument has recently moved Based on past experience the pattern noise WILL eventually go away if you power cycle the instrument but sometimes that process must be repeated multiple ti
28. in the rack does not recognize a device if the keyboard is not attached Since the Suns only accept USB input neither magic site or magic e2v is hooked up to the KVM at the time of this writing There are keyboards and mice in the computer room if one needs to directly communicate with magic e2 or magic site An additional monitor needs to be attached Note that neither Sun will recognize a monitor unless it is attached during the booting of the machine The monitor can be removed after the startup and a reattached monitor will be recognized The PC104 magic backup is fully hooked up to the KVM and can be accessed through button A 3 Switching to the e2v from the SITe Configuration e If you are still running the SITe via magic site make sure you have exited the LOIS software You may remain ssh d into magic site to copy data etc e Go into the computer room and move the rainbow wired cord from the back of magic site to magic e2v e You should be able to start LOUI and connect to MagIC via magic e2v If not try resetting the PCI card white button on the back of magic e2v or cycling the power on the filter wheel see 11 1 6 As simple as these instructions sound switching is much much flakier than it should be It is recommended that you switch to the e2v if you are planning to use it as soon as possible to leave time for debugging eg pattern noise trouble starting LOUI and restarting the system 4 Switching to the SITe from the
29. lized and in the LOIS xterm the last few lines are getback b 0 command b A 129 getback b A 129 14 command b A 0 getback bA 0 command b A 129 getback b A 129 6 Seeing a large flurry of activity in the LOIS xterm is a good sign If the LOUI LOIS log seems to hang during this process you must quit LOUI and try again See 11 1 for a list of possible sign in problems 6 4 Console messages The console log produces produces a great many messages most of which are routine and ignorable Level_ 0 messages indicate serious errors They are typed out in red and should not be ignored To stop the flow of console messages click the lock icon second from the left in the upper right hand corner of the console log window This will prevent the console log from scrolling immediately to the bottom when a new message pops up To enable scrolling back to the bottom click the lock button again If you rebooted the PC104 computer and choose on our advice not to use telnet to reset the time then when you link LOUI and LOIS you will see the following 22 16 26 Level_2 attempting to sync time to QMM 22 16 43 Level_4 MAGICEIIV R command ticks 0 O and trycount 0 22 16 59 Level_4 MAGICEIIV R command ticks 0 O and trycount 1 22 17 18 Level_4 MAGICEIIV R command ticks 0 O and trycount 2 22 17 34 Level_4 MAGICEIIV R command ticks 0 O and trycount 3 22 17 34 Level_O MAGICEIIV QMM time of day failed to turn over 22 17 34 Level_4
30. lnet magic backup 3112 Trying ip address Connected to magic backup lco cl Escape character is CTRL 1970 001 00 00 00 123456789 illustrative only lt CR gt 2009 073 19 27 30 Q 0 S 0 Q 0 Q O 2009 073 19 27 35 Q O 2009 073 19 27 40 x 0 CTRL telnet gt quit Connection to magic backup lco cl closed What happened in the above example is that the user gave the PC104 the Unix time the number of seconds since 1970 01 01 00 00 00 and hit carriage return at precisely that second The user then checked the time several times and did not neglect to exit either the captive process with an x or telnet with a CTRL Calculate the Unix time Open another xterm ssh into magic e2v and type dtt hh mm This will return some long number e g 123456789 the number of seconds since 1970 01 01 00 00 00 corresponding to a UT clock time hh mm at which you would like to synch the PC104 Hit carriage return when your reliable clock reaches this time 28 Note If typing source loissetup tcl produces no response the time on the observer computer may not match the time on magic e2v This happens when an NTP daemon is not running on the observer computer Differences as small as 11 seconds have been found to produce this response Unfortunately system administrator privilege is required to set the time on the observer computer We understand that this problem may now have been resolved we would appreciate hearing i
31. m frame 7 8 So how do you know that everything is working Look at the log Here is a example of the start of hard triggered 60 frame exposure in occul mode 04 51 57 Level_4 Starting exposure with SEX command 04 51 58 Level_2 QMM Exposure start 04 51 59 00 frames 60 total integration time 600 000000 Here is a example of the start of hard triggered in 40 frame exposure in which LOIS failed to get the proper time from the PC104 40 frame exposure in occul mode in which the 04 41 14 Level_4 Starting exposure with SEX command 04 41 22 Level_O magiceiiv QMM time of day failed to turn over 04 41 22 Level 4 magiceiiv R command ticks 1233981674 1233981682 04 41 22 Level_2 QMM Exposure start 00 00 00 00 frames 40 total integration time 600 000000 Errors of this sort appeared perhaps 10 of the time early in 2009 but have since become much rarer Notice that the start time is the zero of Unix time and is reported as such in the FITS header It is currently NOT thought that this error compromises anything other than the reported UTC start time which is also wrongly reported as 1970 01 01 00 00 00 in the image FITS headers The frames do start recording after a slight delay and they clock out at precisely the specified interval You can thus trace back the actual start times starting from the final 17 exposure times For this reason we always recommend you save your lois logs They are located on magic e2v 1lco cl at home observer
32. mes our record is 10 Power cycling the instrument means turning the instrument control power off waiting a few moments then turning it back on You should always check the readnoise levels with 2 flats and 2 biases using findgain z E is L _ rah Wav Mal all Hu i Ai m 1100 1000 960 980 1000 1020 1040 1060 1080 1100 1120 110 EAT a us ad aL ae hi data ett l A Figure 8 Bad pattern noise If you see noise with this much structure you should try to fix it as described in the text 10 Shutting Down LOIS and LOUI Before you quit LOUI the high voltage electronics in the camera need to be turned off In the future this may become part of the LOUI software but for now you must do so manually In the command editor type cam_close and hit return Then type cam_pwr power off Then you may quit LOUI via the menu or closing the LOUI window 22 Next in the LOIS xterm window on magic e2v make sure that LOIS has stopped running Hit enter to get a prompt back and type ps aef grep lois This should display any processes labelled lois that are still running on magic e2v Often times this may include the grep command you have just typed If additional LOIS processes exist you should kill them by typing kill 9 lt process number gt where lt process number gt is the first number listed for the offending pro
33. ng The time must be set because our Tru time GPS system gives an unlabeled pulse every second If the time on the PC104 is incorrect the fractional seconds reported by LOIS LOUI will nonetheless be correct The time can be set on the PC104 via two methods 1 Via telnet See Appendix A 2 In LOUL See 86 5 6 Launching the e2v Data Acquisition Software LOUI LOIS 6 1 Start LOUI LOUI can be launched on the observer computer in either of two ways 1 by typing magice2v on an xterm 2 by launching the application MagIC_E2V usr local magellan MagICE2V MagIC_E2V The LOUI GUI will launch A stored name and password should pop up Hit OK to login 6 2 Start LOIS Open an xterm on the observer computer and ssh into the data acquisition computer magic e2v with username observer The password is not printed here but is widely known The password has NOT been changed despite the move from the Baade From the home directory type startlois amp If the Active MQ broker does not start up you will need to try again the broker takes a few minutes after magic e2v reboots to come back online 6 3 LOUI to LOIS At the bottom of the LOUI window is the Command Editor where you can send instructions to LOIS Above that is the Console window which displays the live updating LOIS log your only reliable source of feedback on the status of the instrument In the Command Editor type source loissetup tcl This will initi
34. nned by 1 5 pixels in each direction The pixel scale is 0 035 arcseconds so binning 4x4 is unlikely to lead to undersampling But bright stars will then saturate sooner e Subframes To turn the subframe on enter 1 in the Subframe box At the bottom of the window enter 1 again and then your values for the subframe The boxes for xpix and ypix refer to the CENTER of the subframe while the xsize and ysize refer to the number of binned pixels on each side of your image See Appendix B for a charts for minimum exposure times for a variety of binning and subframes in occul mode The minimum exposure time for a full unbinned frame in occul mode is 6 seconds however each image file has several additional seconds of overhead for writing the image setting the PC104 talking to LOIS etc etc The time between successive files is roughly 7 seconds though this time varies for reasons unknown e Press Go to start taking data The following parameters should be left alone as we have very little experience with the alternatives and cannot vouch for data obtained using them e Command start Do not change e Amplifier L Allows you to select Left Right or both amplifiers L R LR not yet tested e Sub mode basic Other modes such as fast or pipeline allow faster readout of subframes In fast occultation mode the subframe is clocked down only the number of rows required to read the image As such any frame should be at
35. observer name institution other info LOUI remembers the last values used even though it may not display them in the dialog box where you can edit them If you do not update these values it will dredge the previous stored values from somewhere and use those instead A related manifestation of this behavior is LOUD habit of defaulting to the prior exposure time when it gets confused on the timing 11 2 3 Exposure times incorrect in hard occul mode headers This is true for hard triggered exposures in occul mode Here is the telltale output from the Console Log from April 2009 00 37 40 Level_5 MAGICEIIV starting single Exposure for 60000 0 ms 00 37 40 Level_4 sendtime to trigger host H 61 The observer requested frames of length 60 seconds but the trigger time is 61 seconds This was not the case in February 2009 but in April 2009 there were no QMM time of day failed to turn over errors during a night s worth of exposures It appears that for integration time T for an unbinned frame time of last pixel time of first pixel number of frames 1 T 1 7 seconds to read full chip It appears as if an extra second has been added to each exposure The change made to the frame time is more complicated for frames shorter than 10 seconds especially if the requested time is not an integer number of seconds As with all of our QMM errors one can work back from the log to fix the problem Save the LOIS logs along with your data Log
36. on Use Dashes for Image Number Apply Reset Clear Figure 3 The Storage Config and Observer Info tabs 7 Recording Data with the e2v 7 1 Choose your filter Select the number of the filter wheel you want noting that there are two filter wheels and that the filters are selected by their order in the wheel then hit Move For the top wheel MagIC_t0 B V R I etc are 1 2 3 4 5 etc For the bottom wheel MagIC_b0 u g 1 i etc are 1 2 3 4 5 etc Wait until the console log says Telescope threads have been reactivated The filters MagIC_b0 and MagIC_tO are open filters One open filter from either wheel should be selected at all times 11 7 2 Telescope Telemetry Sart Figure 4 The bottom filter wheel in open left and Sloan i right positions Choose the data acquisition mode LOIS offers six different data acquisition modes some of which will be of little or no interest to Magellan observers The two most likely to be of use are listed first The other modes have not been beta tested use at your own risk SINGLE This means that the shutter is opened and closed for every 2 dimensional data array taken Note that one can specify multiple exposures in which case a separate file 2D FITS file is written for each exposure OCCUL This mode allows for multiple 2 dimensional frames within a single ex posure The shutter is not closed between frames
37. oused in a cabinet with a Cybex KVM Keyboard Video Mouse switching a single monitor and keyboard with trackpad Only magic backup is hooked up to the KVM It will be necessary to manually hook up a keyboard monitor and mouse between the two Suns Check to see if the PC104 an aluminum cube roughly 10cm on a side is running A switch located at the bottom left of the back of the PC104 will reboot it 1 the easy way From a window on an observer computer type ping magic backup lco cl If the PC104 is up you will see PING magic backup lco cl IP address 56 data bytes 64 bytes from 200 28 147 22 icmp_seq 0 ttl 62 time 7 564 ms 64 bytes from 200 28 147 22 icmp_seq 1 ttl 62 time 1 052 ms Sometimes the PC104 will be ina kernal panic state but it can be pinged so checking the hard way is recommended 2 the hard way Switch the KVM to monitor A If the PC104 has a login the PC104 is up and running you may proceed If the PC104 has crashed in particular if the screen says kernel panic you will need to reboot by toggling the on off switch located at the bottom left of the back of the PC104 5 2 2 Resetting the master clock on the PC104 After rebooting the master clock that governs the exposures does not have the correct time and is not ticking You must reset the time on the PC104 after rebooting either via telnet to the PC104 or preferably using LOUI Resetting the time starts the master clock if it is not already ticki
38. owever if you suspect that loose fibers could be a problem ask an instrument specialist 11 3 2 Missing bad header times Every so often perhaps one frame in three the start time is wrong It seems likely that the correct time can be reconstructed from the LOIS log files so always save your log file Eventually we may write a script to add the correct times to the headers based on the log files Log files can be found at home observer lois logs on magic e2v 11 3 3 Pattern noise Ideally we will find the source of the pattern noise and fix it but for now if it appears you should try power cycling because that usually helps 12 Version History last modified 2010 August 04 v1 5 4 Amanda Zangari August 2010 edit 2 v1 5 3 Amanda Zangari July 2010 edit 1 v1 5 2 Amanda Zangari July 2010 post engineering update v1 5 1 Amanda Zangari June 2010 typos and organization v1 4 Elisabeth Adams June 2009 v1 3 Paul Schechter May 2009 vl 1 1 2 Elisabeth Adams Mar 2009 v1 0 Paul Schechter Feb 2009 26 Appendices A Resetting or checking the PC104 clock using Tel net The PC104 clock can be reset and checked by telnetting into a specific port that runs a rudimentary captive process That process is very unforgiving A bad keystroke or forgetting to exit the captive process will crash the system Moreover one cannot telnet into the PC104 e g to check the time once LOIS has been started The procedure described here is
39. s the parameter exposure time rather than integration interval which is unaccessible if soft triggering has been selected After a time specified by the exposure time a frame is transferred to the frame transfer area and read out In the meantime integration is under way for the next frame The total number of frames gives the depth of image cube An exposure is again an image cube not a single frame Each exposure produces a new FITS file which is three dimensional Setting the number of exposures to something greater than unity gives more than one image cube The shutter opens at the beginning of an exposure and closes at the end of an exposure 7 6 Observing in single mode The control panel is self explanatory Triggers may again be soft or hard 15 Camera Control X O User Button O Storage Config O Observer Info find fdots sdots strips occul CO Go Pause Abort Reset Command start iv Amplifier L Iv Subframe 0 Rows per Bin 1 Columns per Bin 1 Over Scan 40 Over Clock 0 Trigger Type hard Iv Exposure Time s 10 Number of Exposures 1 Frame Type object iv Object Title test FITS Comment testing subframe xpix ypix xsize ysize 53 O User Button Storage Config O Observer Info single find fdots sdots strips Pause Abort Command Amplifier Sub Mode Subframe
40. serving in occul mode 0524 sg eee Soh Fo ee Roe ee 7 5 1 Hard triggers in occul mode 64S S e Pa Be Sms Yee 7 5 2 Soft triggers in occul mode 4 2 202 bb Shae ek 7 6 Observing in single mode ooa aaa a 7 7 The status window aoaaa ke Sa eB ee 7 8 So how do you know that everything is working ee SM MPA tees dk Yale cle Ut Ae tel ke Ss Peart hs oe i os ie NS ate we Telescope Pointing the magic IRAF package 8 1 tomagic centering on the e2v ud cep ar oe Se Pa Se See S 8 2 mvmagic object centering oe ok ee a Be a Be eR ee al Your e2v data 9 1 Transferring Data to the Observer Computer from magic e2v 9 2 Data display and quick look 4 4 4 aa ee Be PA pe 9 3 Useful image header keywords 0 00000 teen 9 4 Checking images for pattern noise 0 2 0000 eee 10 Shutting Down LOIS and LOUI 11 Troubleshooting the e2v 11 1 Connection and Setup Issues she ton cp oy cecal dw er Pa deotne 4 eee 3 11 1 1 Trouble initializing LOIS 2G 2k Rk ee ee eR ee ele 11 1 2 Problems with SAOimage DS9 2 4 21 ce ge Bebe me ated 11 1 3 The PC104 magic backup is down common 11 1 4 LOUI doesn t talk to Os git dose ae ae ee Be eve se oe b 11 1 5 magic e2v does not respond 25 44k 28 eh a a AR 11 1 6 The filter wheel does not initialize 11 1 7 LOUI is stuck on TIM downloading 0 4 4 6 2 4 65404 512 Ge a 11 2 Problems that can be avoided
41. tween module windows and drag Burrot obs5 ssh observer magic e2v Password Last login Sat Mar 14 11 28 46 2009 from burro lco cl Sun Microsystems Inc SunOS 5 10 Generic January 2005 observer magic e2vz startlois Loading the DSP PCI filet pci lod addr OxO00B7E data Ox0471C1 PCI file successfully loaded ROM Loaded rmt No match rmt No match rmt No match 1 992 Hello all this is a c cout command Lois Home directory set ast home lois local LOIS LOISDIR environment variable not set using HOME environment variable Adding LOIS Exit Event Handler LOIS Command interpreter initialized Loading the LOIS Console Module LOIS Signal Thread Waiting Creating Console command Adding LOIS Queue Event Handler Starting connection to Active MO broker localhost on port 61616 with machine magic e2v Logging Module Loaded Starting the LOIS Console Figure 2 startlois and its output before linking to LOUI The filter wheel takes a few minutes to initialize and there is no explicit statement that the system is ready you will have to watch the logs The last commands displayed in the LOUI LOIS log Console window are 19 35 26 Level_3 TELE RA 02 22 28 61 DEC 29 05 40 5 19 35 26 Level_3 TELE airmass 1 000 00 19 35 26 Level_3 TELE epoch 2000 00 19 35 26 Level_3 TELE rotator 046 000 19 35 26 Level_4 DS9 Xpa Module Rev 1 0 19 35 26 Level _4 DS9 Xpa Module Initia
Download Pdf Manuals
Related Search