This shows you the differences between two versions of the page.
public:catalinas:bigelow:kuiper_61:mont4k:watcher [2019/06/07 11:39] davner created |
public:catalinas:bigelow:kuiper_61:mont4k:watcher [2024/09/19 16:36] (current) egreen updated |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Postprocessing with Watcher | + | Postprocessing with watcher |
- | Watcher | + | watcher |
- | (Note that the previous quicklook display had fatal bugs, so it is currently turned off by default at startup; you can also turn it off by typing " | + | In order to keep watcher |
- | + | ||
- | In order to make watcher | + | |
To start watcher correctly, open a terminal window, and type | To start watcher correctly, open a terminal window, and type | ||
+ | ./ | ||
- | ./ | + | This pops up a new IRAF window starting in the watcher subdirectory, |
- | This will pop up a new IRAF window that is already cd'ed to the watcher subdirectory. | + | If you aren't running an optional post-processing script, either epar watcher |
- | lpar watcher | + | If you're observing light curves, you should set extras = auto_plot, and epar auto_plot to customize it for your target. (You can see the results in a separate iraf window with "!tail -f auto_plot.log" |
- | If you don't want to run an optional script, either epar watcher | + | Before starting |
+ | | ||
- | watcher.extra="" | + | As each new image is transferred to gerard, watcher |
- | + | ||
- | If you're doing light curves, you should set extras = auto_plot | + | |
- | + | ||
- | You can either cd to your data directory first (the same directory where bigccd will send the images ) and type | + | |
- | + | ||
- | watcher . | + | |
- | + | ||
- | Or just type watcher | + | |
- | + | ||
- | and it will request the name of your data directory. | + | |
- | + | ||
- | Watcher will announce " | + | |
It is useful to reduce the watcher window to a few lines in height and place it under the ds9 image, so that you can see what it's doing as it detects, converts, and displays your images. | It is useful to reduce the watcher window to a few lines in height and place it under the ds9 image, so that you can see what it's doing as it detects, converts, and displays your images. | ||
- | If you need to stop watcher, type control-c in the watcher window, followed by a flpr or two. | + | If you need to stop watcher, type control-c in the watcher window, followed by a flpr, or better: flpr; flpr |
- | + | ||
- | Merge4k was written to work properly with images of arbitrary numbers of columns and rows and binning; it reads the header and works with whatever image size and binning exist. | + | |
- | + | ||
- | => Until the version of IRAF running on Gerard gets updated, you will see that 3x3 binned images are 1365 pixels in the x direction instead of 1364; there is an extra (junk) column on the far right | + | |
- | + | ||
- | Every now and then, watcher will miss an image. | + | |
- | + | ||
- | imhead *.fits | grep FX | + | |
- | Any unmerged or improperly merged images give an error that looks like: < | + | The current version of IRAF has a bug that would cause watcher |
- | merge4k | + | |
+ | merge4k | ||
- | Merge4k can be run in any IRAF window | + | => The M4K CCD is read out by two amplifiers; there are a few unread columns between the two sides of the CCD which are not read out, so one should either avoid placing targets of interest on the center seam or dither the telescope position with multiple exposures; 1x1, 2x2 and 4x4 binned images don't show the missing columns; 3x3 binned images have one " |
- | If you find an image that is damaged or unreadable, first check to see if the original | + | If gerard is very busy (especially if it's running firefox), watcher will (rarely) miss an image. At the end of the night, check to see whether all of your images were merged by typing " |
+ | merge4k < | ||
- | dir raw/< | + | If you find an image that is damaged or unreadable (again, rare but possible if gerard is running lots of other tasks), check to see if the original image made it to the raw subdirectory: |
- | If it is there, you can almost always successfully reprocess that image by moving the raw image to the observing directory and reprocessing it. | + | dir raw/< |
- | del < | + | If the raw image exists, you can usually successfully remerge it by deleting the botched image in the observing directory, moving the raw image back up from the raw subdirectory to the observing directory and rerunning merge4k on it: |
- | rename raw/< | + | |
- | merge4k < | + | rename raw/< |
+ | merge4k < |