I am working on nights in: /home/sco/ACM_Red1 To get moon tables to jude moon rise/set times: [astronomer@mcs ~]$ /home/mcs/astronomer/sir/newmoon/moonbrt4.x A valuable night: 20180114 Moon rise at 11:50 UT Nearly all of the night was dark (no moon) and clear. I took acm cals and a number of acm images on sky associated with LRS2 observations. This night should have all we need for dark sky surface brightness measurements. Clear at start of night, no further weather notes A valuable night: 20180115 Moon rise at 12:40 UT Took sky brightness data in grB on acm with open cluster NGC2301. Took bias and dark frames with scripts, bias=1382 (normal). Cirrus at start of night, no further weather notes A valuable night: 20180116 Bad weather, no observing. Took extensive bias+dark with stacking by scripts. A valuable night: 20180206 Moon rise at 6:10UT Took acm bias and 5sec darks that appear to be normal. Observed many targets with dark time and bright moon time. Should be excellent for sky brightness work. Took mainly B,r acm images. Notes indicate night clear A valuable night: 20180402 Moon rise at 2:50UT Pointing test night where I took 30-60 stars each night almost all in g. I also took bias/dark data sets (which appear to be at normal levels). This night had a very bright moon a day or two after full moon. Mostly clear in the time range 6:30UT to 10:20UT. Some clouds, some clear A valuable night: 20180403 Moon rise at 3:40UT Pointing test nights where I took 30-60 stars each night almost all in g. I also took bias/dark data sets (which appear to be at normal levels). Both nights had a very bright moon a day or two after full moon. Clear in early part of the night with some clouds around 6:00UT. Heavy clouds and high wind after 8:23UT. Some clouds, some clear
An efficient way to survey a night and find the bias frames is given below along with a list of useful nights on scohome. I have collections of acm image. Tow are stored along with the LRS2 imae frames, and the largest acm collection stores the acm data only.
My collection of acm images (collected by DATE) on scohome is in 3 places: /home/sco/HET_work/acm_nights == 14 nights of acm images only /home/sco/HET_work/HET_acm+lrs2/oct2017_sci == 4 nights of sci /home/sco/HET_work/HET_acm+lrs2/oct2017_eng == 4 nights of eng % acm_nights Dates.eng /home/sco/HET_work/HET_acm+lrs2/oct2017_eng I did this work on scohome, but it is setup for running on mcs. % acm_nights Dates /home/sco/HET_work/acm_nights UT date Total bias dark open 20170903 19 0 0 19 20170906 220 23 148 49 20171031 18 0 0 18 20171101 50 0 0 50 20171102 53 0 0 53 20171108 878 573 305 0 20171231 544 42 120 382 20180101 164 40 123 1 20180102 682 41 123 518 20180105 213 40 120 53 20180106 272 40 120 112 20180107 305 62 13 230 20180115 529 11 21 497 20180116 309 224 84 1 % acm_nights Dates.sci /home/sco/HET_work/HET_acm+lrs2/oct2017_sci UT date Total bias dark open 20171014 31 0 0 31 20171015 15 0 0 15 20171016 43 0 0 43 20171017 26 2 0 24 % acm_nights Dates.eng /home/sco/HET_work/HET_acm+lrs2/oct2017_eng UT date Total bias dark open 20171007 42 0 0 42 ran 4 months on mcs: UT date Total bias dark open 20170906/ 223 23 148 52 20171108/ 879 574 305 0 20171114/ 611 0 202 409 * 20171128/ 589 0 261 328 * 20171129/ 94 60 19 15 * 20171231/ 548 42 120 386 20180101/ 166 40 123 3 20180102/ 1125 41 123 961 * 20180103/ 3460 1842 0 1618 20180105/ 216 40 120 56 20180106/ 274 40 120 114 20180107/ 305 62 13 230 20180109/ 387 41 45 301 * 20171008 162 0 0 162 20171009 44 0 0 44 20171010 63 0 0 63 I ran 4 months on mcs: UT date Total bias dark open 20170906/ 223 23 148 52 20171108/ 879 574 305 0 20171114/ 611 0 202 409 * 20171128/ 589 0 261 328 * 20171129/ 94 60 19 15 * 20171231/ 548 42 120 386 20180101/ 166 40 123 3 20180102/ 1125 41 123 961 * 20180103/ 3460 1842 0 1618 20180105/ 216 40 120 56 20180106/ 274 40 120 114 20180107/ 305 62 13 230 20180109/ 387 41 45 301 * 20180112/ 517 1 55 461 * 20180114/ 352 12 27 313 * 20180115/ 529 11 21 497 20180116/ 312 224 84 4 Nights with "*" I pulled to buckaroo ACM Here is a list of nights on scohome that have good acm cals: UT date Total bias dark open 20170906 220 23 148 49 20171108 878 573 305 0 20171129 94 60 19 15 20171231 544 42 120 382 20180101 164 40 123 1 20180102 682 41 123 518 20180105 213 40 120 53 20180106 272 40 120 112 20180107 305 62 13 230 20180109 387 41 45 301 20180114 352 12 27 313 20180115 529 11 21 497 20180116 309 224 84 1 I see that acm_list is a long running code, probably becasue of my used of gethead_1card. I'll experiment: % pwd /home/sco/play % acm_list 20171108 /home/sco/HET_work/acm_nights *** 20171108 has 878 images. In early form acm_list takes 24 sec to run on scohome. I add a gethead call for a single list (but still call 1card): takes 24 sec Now I replace the 1card calls and use the list.gethead file to gather info. This version takes 7 sec (cuts time by factor of 3) Now I take out 1 rounder.sh call - 3 sec I add back re-writing the full fitname string to list.acm_alldata: 4 sec So, I go from 24sec to 4 sec (reduce by factor of 6).
To reduce a night.
% setenv BASE /home/sco/HET_work/acm_nights % cd /home/sco/HET_acm_reds/20180115/red1 % acm_list 20180115 $BASE # took a few seconds % process_acm_bias list.BIAS
I got pulled away from my mult-set acm nights work in late Jan2018. Here
is a brief reminder for when I pick this up again.
 |
A set of mean dark rates computed from 13 differnt acm nights when bias and
dark frames were taken. This early work was left uncompleted (as of Jan30,2018),
but the basic scripts and data runs were stored in:
/home/sco/HET_acm_reds /home/sco/HET_acm_reds/S Basic flow: setenv REDBASE /home/sco/HET_acm_reds setenv ACMBASE /home/sco/HET_work/acm_nights process_acm_nights nights.UT $REDBASE $ACMBASE # use nights.all for many nights |
In /home/sco/HET_acm_reds # Bmean Bmedian Bsigma Nims Date # data 1396.57130 1396.540000 0.10968 23 20170906 1383.53026 1383.480000 0.31484 573 20171108 1384.18033 1384.235000 0.18402 60 20171129 1384.89524 1384.920000 0.21137 42 20171231 1382.87850 1382.935000 0.16563 40 20180101 1387.78000 1387.820000 0.13660 41 20180102 1384.68125 1384.700000 0.14853 40 20180105 1384.21575 1384.215000 0.08118 40 20180106 1382.08129 1382.085000 0.18555 62 20180107 1383.09683 1383.110000 0.21812 41 20180109 1391.19417 1389.490000 5.73115 12 20180114 1382.80909 1382.890000 0.22456 11 20180115 1382.74129 1382.620000 0.43552 224 20180116These are not absurd variations, but on some night, for no known reason, I collect bias images with mean values .GT. 2000 adu! Something is wrong somewhere. For instance, here are some notes from my 20180205 log:
==================================================================================
eng acm calibartion test
cd /home/mcs/astronomer/sco/RA_logs/20180205/bias+darks
truss=12.1
internal=11.4
external=11.4
acm bias and darks with dome open , moon up and bright
% acm_bias_run 19
[astronomer@mcs bias+darks]$ clip_imstat.sh Bias_stack.fits 60 710 60 710
2034.1896 0.0894 58.1988 423801
# this should be around B=1385
acm bias and darks with dome closed
% acm_bias_run 19
[astronomer@mcs bias+darks]$ clip_imstat.sh Bias_stack.fits 60 710 60 710
2034.1896 0.0894 58.1988 423801
==================================================================================
Hence, opening or closing the dome shutter has absolutely no influence on
the measured "bias" levels.
This file: /home/mcs/astronomer/sco/ACM_Night/S/README.ACM_Night
Notes made 20180228 on mcs
I have a ton of notes, but I neeed a succint description of how to
process the images in a night of acm data.
acm_nigths == characterize multiple night.
process_acm_nights == perform image processing, never completeed and poorly documented
acm_list == used by acm_nigths to survey a single night (by date)
*** You get a list of bias (and other frames)
To look at the image in a list:
ds9_list_load == read the list of images. View and select images with ds9.
process_acm_nights == with a list of "good" bias images, you make the final stacked bias frame
=================================================================================================
Project_1: A good night was 20180114 - get the bias stack
[astronomer@mcs Project_1]$ acm_list 20180114 /hetdata/data
arg1 - UT date for the night (yyyymmdd)
arg2 - path to base directory
Takes about 1min on mcs, I get lost of files, but we are concerned here with: list.BIAS
To look over the images:
ds9_list_load list.BIAS
Note, use Lock (Sclae and Colorbar) to get all images on same contrast.
I see that all bias frames look aceptable. The images I mark with a
circle appear in the file: List.New
To get stats on bias and dark rates:
process_acm_bdstats 20180114
Makes a lot of files (many junk). The main thing done is a mean bias level
is determined and subtracted. The dark rates for each dark image are gathered
into a table file (Dark_Rate.table and Dark_Rate.parlab) that I can use for
plots. ******* Need to clean this script up so that is deletes junk files, etc
and makes a nice summary list of output
To make the stacked frame:
[astronomer@mcs Project_1]$ process_acm_bias list.BIAS 5 20180114
arg1 - list of input (bias) images (can be fullpath)
arg2 - identification string (usually UT date of acm night)
*** Does not work, so I will fix this on mcs
Image name: 20180114T064427.7_acm_sci_BIAS_20180114.fits
where basename at start is from first image in list.BIAS
Dates with good data:
20180114 12
20180115
20180116
20180206
On mcs:
setenv date 20180206
acm_list $date /hetdata/data
ds9_list_load list.BIAS
process_acm_bias list.BIAS 5 $date
On scohome:
setenv date 20180206
acm_list $date /home/sco/HET_work/acm_nights
ds9_list_load list.BIAS
process_acm_bias list.BIAS 5 $date
To get stats:
clip_imarith.sh 20180114T064427.7_acm_sci_BIAS_20180114.fits - 20180115T040325.2_acm_sci_BIAS_20180115.fits b1.fits
clip_imstat.sh b1.fits 60 710 60 710
0.3136 0.0147 9.5478 423801