Changes between Version 12 and Version 13 of HowTo


Ignore:
Timestamp:
Oct 12, 2021, 9:41:46 PM (3 months ago)
Author:
holtz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo

    v12 v13  
    152152== Data and logs ==
    153153
    154 '''TIP''' - You might want to note what time you do the observations to make finding your .fits file easier. When taken with MaxIm DL,  the images are automatically named "CCD_Image_NUMBER.fit" which is usually not helpful.
     154If observing manually, you should keep a log of your observations to make finding your .fits file easier. When taken with MaxIm DL,  the images are automatically named "CCD_Image_NUMBER.fit" which is usually not helpful for identifying objects. When taken through the web interface or in robotic mode, the images are organized by program and have more meaningful names.
    155155
    156 When taken through robotic mode, the images are organized by program and have more meaningful names.
     156Data is stored on the local computer at TMO, but is automatically synced to the NMSU Astronomy servers every two hours. On the Astronomy computers, it is located at /home/tmo/, which can be accessed via the web at ​http://astronomy.nmsu.edu/tmo/.
    157157
    158 Data is stored on the local computer, and is automatically synced to the NMSU Astronomy servers every two hours. As far as I know, AAVSO also does this roughly once a day. On the Astronomy computers, it is located at /home/tmo/, which is the same as ​http://astronomy.nmsu.edu/tmo/.
    159 
    160 ACP stores logs per object; this can be pretty inconvenient if you just want an idea of what it did all night. Therefore we have a script which concatenates these logs into summary logs for each night, helpfully stored in /summary_logs/.
     158ACP stores logs per object; this can be pretty inconvenient if you just want an idea of what it did all night. Therefore we have a script that runs each morning that concatenates these logs into summary logs for each night, helpfully stored in /summary_logs/.
    161159
    162160Logs contain a lot of information; here's a quick guide. The software attempts to "plate solve", which looks at the image and tries to correlate it to a star catalog to make sure the pointing is okay. Pointing information is also included in the log; after slewing pointing error may be as high as half an arcminute, but will (hopefully) quickly be corrected with subsequent exposures. The software will also do occasional focus runs, and calculate other values of interest including plate scale, focal length, FWHM (seeing), and field of view.