An easy way to display images, compute statistics in user-specified image regions, and prepare input table files for codes like xyplotter_auto.
% ds9_imstats --help % ds9_imstats B.fits Y Usage: ds9_imstats a.fits Y arg1 - FITS image name arg2 - run in interactive mode (Y/N)
This is a fairly simple wrapper code that calls many routines that perform a wide variety of tasks.
1. Store the *.info and *.reg files in a local_red directory. 2) Produce a basename table file (from midodata.2) that is stored in the local_red directory. 3) Have a means of invoking the verbose/query mode 4) Incorporate the use of a mask if desired (this is a mido.sh issue really)There are other thoughts, but these are starters for now. Actually some (most ?) of these should be done outside of ds9_imstats, but this is the place where most of my thoughts started, so I document initial work here. Because the present code is buried in other scripts, I'll begin by establishng ds9_imstats_markII so that I can freely make upgrades. Not the I have the code ds9_imstats_run that runs this code on a list of image. I really should have stuck with my convention of using "fitslist" instead of "run". So, I'll build a ds9_imstats_markII_fitslist that runs ds9_imstats_markII. This way I can develop aspects of the above wish list in either script without dear of hosing up something in another script.
% ds9_imstats_markII --help Usage: ds9_imstats_markII ./S/20190711T040815.4_acm_sci.fits zscale n N arg1 - FITS image name arg2 - z1 for scaling (can be "q" for query, zscale, or minmax) arg3 - z2 for scaling (can be "n" for none) arg4 - run in verbose/debug mode? (Y/N) Examples: ds9_imstats_markII ./S/20190711T040815.4_acm_sci.fits minmax n N ds9_imstats_markII /media/sco/DataDisk1/sco/AD/HET_work/acm_nights/20190711/gc2/20190711T040819.9_gc2_sci.fits 1 5000 N
Back