A lot of old notes are stored here. In particular, I include my early analysis of acm bias properties from early 209, and a lot of refinement of acm photometry methods in Spring and Summer of 2020. These notes are not well edited well, but a lot of the figyres may be useful and are a good archival resource.
Sometimes we just want to see the list of commands.
# Where are the original (raw) acm images? % cat BaseDir /media/sco/DataDisk1/sco/AD/HET_work/acm_nights % cat Date 20190724 # perform ccd image processing % acm_table_markII N S1 % acm_bias_for_date none N S2 % cp ACMDAT.images ACMDAT.images_raw % paga ACMDAT N S3 % image_fullpath_list ACMDAT.images FIXUP newlist.images N % mv newlist.images_version2 ACMDAT.images # Find unique sky positions % table_onsky_sets.sh ACMDAT A N % onsky_set EX1 all Y N % ds9_list_load List.AllTargets # Optional step to see all target images # Usfeul for user: table_onsky_sets.summary and the EX1 table # Gather useful (acm only) calibration material for each position % dssbase_run_markII table_onsky_sets.RADEC 4.0 8.0 19.0 21.5 none N % dssbase_list Y % dssbase_review Y # Optional step to review dssbase data # Make detected source catalog for each image % image_catalogs List.AllTargets none Y N S4 # Graphically review the images ith iset value % point_selector EX1 uthrs im N # Note: the EX1 table has iset values assigned. # Extra random stuff % # We could isolate images in a time interval: % select_pas_images_by_time ACMDAT.images ACMDAT 07:02:22 07:04:32 START N % point_selector START uthrs im N % bigds9 START.images 1 8 Note that a lot of my development runs here wer in: /home/sco/ACM_work_Sep2019 The night of 20190724 was when I finally got a good set of offset data for deriving the HET guide camera (gc) plate scales.Return to top of page.
The fundamental list of images we use is usually the full listing of the PAS images in the data directory specified by the (BaseDir,Date) files. For instance, after a run of acm_table_markII, as shown above, we'll have a file listing the paths to the original (raw) acm images called "list.IMAGES_OLD". Later in the reduction, we might want to view the processed versions of these images. The routines image_process_list and image_fullpath_list can be used for accomplishing this. One prohibitive factor for image_process_list is that ONLY images that do not have versions in the target directory end up in the LIST.IN and LIST.OUT files. In the example below, I show how we can view the processed versions of the acm image we prepares in the previous section.
A general-purpose approach we can use follows:
% cp ACMDAT.images ACMDAT.images_raw % image_fullpath_list ACMDAT.images FIXUP newlist.images N % mv newlist.images ACMDAT.images % point_selector ACMDAT uthrs im N Usage: image_fullpath_list list.in FIXUP list.out N arg1 - Name of FITS image list (should full path) arg2 - name of process we are preparing for arg3 - name of output file listing referenced images in the process subdirectoy arg4 - run in debug mode (Y/N) The output files of interest are: newlist.images = images with names for the process subdiretory newlist.images_version2 = same as above, except original name used if image does not exist in process subdirectory FITS.BaseNames = a listing of the image basenamesHence, after we have processed images with paga, we could have the proceessed images be viewed (using point_selector) in the ACMDAT table by renaming the "newlist.images_version2" as "ACMDAT.images". Hence, if we select an image the ccd processed version will be diplayed with ds9, except if the proceesed version is not present, and then the original version is displayed. Note that I used a point_selector call like the one above to investigate some questions I had about how the CRVAL1 values are established in PAS FITS header cards. Return to top of page.
Sometimes we want to review a set of images in a interval of UT time. The select_pas_images_by_time can be used for this. This takes as input the ACMDAT table we have already created. However, if no table is present, it will build one on the fly. This way we can make multiple runs with different time intervals in a very efficient manner. Note that in the example below I do not have to be in a ceratin directory, I just have to have the local table file (ACMDAT) present.
% ls ACMDAT.images ACMDAT.images_raw ACMDAT.params ACMDAT.parlab ACMDAT.table % select_pas_images_by_time ACMDAT.images ACMDAT 07:02:22 07:04:32 START N % ls ACMDAT.images ACMDAT.params ACMDAT.table START.params START.table ACMDAT.images_raw ACMDAT.parlab START.images START.parlab % point_selector START uthrs im N % bigds9 START.images 1 8I include the call to point_selector as in the previous example, but this might be rather impractical in this case. What we might like is to be able to view all of the images at once. In fact, we might like to blink all of the images in ds9 so that we can verify that the star images do not move around to any great degree (i.e. verfiy we had stable guiding). The bigds9 is very good for this. After reviewing your images in mosaic or blink mode, you can mark certain images. At the end of the bigds9 you will have two files: ds9_list_load.mark and ds9_list_load.nomark. These are the images from the input table list (START.images) broken into sets that WERE and WERE NOT marked with a ds9 circle marker. Suppose the first two images had been marked becasue they were judged to be too far from the mean position. We could eliminate them by using the ds9_list_load.nomark file as input for our subsequent analysis. Return to top of page.