From: Elena Malanushenko Subject: Re: 2.5m obslog 20100911 (MJD 55451) Date: Sun, 12 Sep 2010 15:28:07 -0600 David, Dmitry said very good point. I am comfortable that I selected guider flat in SOP GUI. Craig confirmed that "noGuider" option on gotoField in similar situation. (As I know, Craig could not confirm that guider flat was not selected in SOP GUI). I saw zero guider flat exposure time defaults in SOP GUI also, but not sure if that happened when I went to field. It might be happened, and possible forced "noGuider" option on gotoField. It is easy to check during the observations. Several times I saw that boss flat and arc had reversed exposure times. It might be related problem with zero guider flat exposure time as some problem with default settings. We might need to ask Russell to check this. Anyway, guider should not use flats from other carts and MJDs if no appropriate flat has been found (as in my example as the bottom). And we need to have a very clear indicator that no appropriate flat is available. Everybody might overestimate human ability to review the process of gotoField, lamp operations, collimation, sosActor calculations for each camera, right piston moves, calibration in spec, and guider on. All this is going very fast and reporting in the scrolling log. Output is gone after we find a field, set scale, and start science. For the most of stages I assume that it is going right if no critical alert produced. We need to have auto check of this process and clear and stable report for quick view of observers. (I might try to make this report window as I can. It is good to have boss exposure flavor in boss actorkeys in status key for this, Craig might help me). Elena Malanushenko elenam@apo.nmsu.edu On 9/12/10, at 2:11 , dmbiz@apo.nmsu.edu wrote: > Sometimes "guider flat exposure time" in the sop gui turns to zero. > It might produce "noGuider" even if the guider checkbox mas checked > (?). > > Dmitry > > >> Craig has confirmed that when this has happened, that "Guider" >> was not selected in the SOP gotoField panel. The logs confirm >> that the gotoField commands in question had the "noGuider" argument. >> >> Surely, we want the default for gotoField to take the flat, and >> display >> a big, annoying warning if it is not in that mode. >> >> -David >> >> >> >> >> On Sep 12, 2010, at 11:36 AM, Elena Malanushenko wrote: >> >>> Dear all, >>> >>> We can see what flat was used for guider image reduction on raw >>> images >>> fits header (but no cart and plate IDs there): >>> gimg-0029.fits: >>> >>> DATE-OBS= '2010-09-04 04:21:48.7Z' / start of integration >>> CCDTEMP = -40.087788 / degrees C >>> FILENAME= '/data/gcam/55443/gimg-0029.fits' >>> OBJECT = 'gimg-0029' >>> DARKFILE= '/data/gcam/55443/gimg-0007.fits' >>> FLATCART= 17 >>> FLATFILE= '/data/gcam/55442/gimg-0023.fits' >>> --------------------- >>> >>> Reduced images are transferring to our workstations landru and >>> minidru >>> to directory /Documents/data/gcam/ if your guider GUI is >>> running. >>> It keeps last 100 files only and deletes them when you quit the >>> STUI. >>> Files proc-gimg-????.fits. We can see cartID and plate ID in >>> their fits >>> headers >>> also. >>> >>> DATE-OBS= '2010-09-04 04:21:55.3Z' / start of integration >>> FILENAME= '/data/gcam/55443/gimg-0030.fits' >>> DARKFILE= '/data/gcam/55443/gimg-0007.fits' >>> FLATCART= 17 >>> FLATFILE= '/data/gcam/55442/gimg-0023.fits' >>> ..... >>> NAME = '4083-55442-01' / The name of the currently loaded >>> plate >>> PLATEID = 4083 / The currently loaded plate >>> CARTID = 11 / The currently loaded cartridge >>> MAPID = 1 / The mapping version of the >>> loaded plate >>> POINTING= 'A ' / The currently specified pointing >>> -------------- >>> >>> So, in my example on 55443 when flat was not taken, the reduction of >>> guider >>> images for cart 11 silently used flat from 55442 from cart 17. >>> Indicator of the problem is large (2-5") stochastic offsets which >>> could >>> not be corrected. If we force to take a flat it will fix a >>> problem. >>> I had the same situation during my observations. >>> >>> Elena Malanushenko >>> elenam@apo.nmsu.edu >>> >>> >>> On 9/12/10, at 5:42 , Audrey Simmons wrote: >>>> >>>> We noticed that when we started the guider (without taking a guider >>>> flat) in >>>> the afternoon that the image showed the mask. Would this mean >>>> that the >>>> reason >>>> we did not notice last night that the guider flat failed was >>>> because it >>>> automatically used the last good flat from the previous plate? >>>> >>> >>> >>> DSS DSS DSS DSS DSS Digital Sky Survey DSS DSS DSS DSS DSS DSS >>> DSS *** The information posted to SDSS mailing lists is >>> proprietary *** >>> DSS This is message 5380 in the sdss-25mlog archive, URL >>> DSS http://www.astro.princeton.edu:81/sdss-25mlog/msg. >>> 5380.html >>> DSS The index is at >>> http://www.astro.princeton.edu:81/sdss-25mlog/INDEX.html >>> DSS To join/leave the list, go to >>> DSS >>> http://www.astro.princeton.edu:81/cgi-bin/mailinglists.pl/ >>> show_subscription?list=sdss-25mlog >>> DSS To post a message, mail it to sdss-25mlog@astro.princeton.edu >>> DSS >>> DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS >> >> >> >> DSS DSS DSS DSS DSS Digital Sky Survey DSS DSS DSS DSS DSS DSS >> DSS *** The information posted to SDSS mailing lists is >> proprietary *** >> DSS This is message 5381 in the sdss-25mlog archive, URL >> DSS http://www.astro.princeton.edu:81/sdss-25mlog/msg. >> 5381.html >> DSS The index is at >> http://www.astro.princeton.edu:81/sdss-25mlog/INDEX.html >> DSS To join/leave the list, go to >> DSS >> http://www.astro.princeton.edu:81/cgi-bin/mailinglists.pl/ >> show_subscription?list=sdss-25mlog >> DSS To post a message, mail it to sdss-25mlog@astro.princeton.edu >> DSS >> DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS >> > >