RA in FITS header is in decimal degrees causing problem with FITS Header Update

[basilr]

My CCD records the Target RA in decimal degrees (not hours) causing the DPCC module to calculate incorrect altitudes + azimuths (airmass, J2000 positions, etc.) Is there a way to tell DPCC the target RA from the FITS headeris in decimal degrees?

Extract of FITS header:

33 RA 165.7209568 [deg] Telescope pointing RA                     R
34 DEC 18.66424214 [deg] Telescope pointing DEC                   R

Log extract from DPCC

    Observatory name "Custom Lon, Lat, and Alt entry" manually selected
    Target coordinates = 21:43:05.484 +18:39:25.39 (Epoch of Observation) (from FITS header RA and DEC)
    JD = 2457871.613519 (mid-exp)
    HJD = 2457871.611227 (mid-exp)    (correction = -3.2991 minutes)
    BJD(TDB) = 2457871.612031 (mid-exp)    (correction = -2.1415 minutes)
    Altitude = -26.91 (mid-exp)
    Azimuth = 28.84 (mid-exp)
    Hour Angle = -10.20 (mid-exp)
    Zenith Distance = 116.91 (mid-exp)
    Airmass = -1.0000 (mid-exp)
    Bias corrected with mbias.fits
    Dark corrected with mdark.fits and exposure time scaling factor 10.0/10.0=1.0
    Flat corrected with mflat.fits
    Saved processed science file "C:\Temp\2\4.27.17\(138155)2000ES70\pipelineout\(138155)2000ES70_FilterA_20170428_024336_out.fits"

Thank you!
Basil Rowe

[karenacollins]

Hi Basil,

In the current daily build version of AIJ, I have added an option to specify RA in hours to the "General FITS Header Settings" panel that can be accessed in the DP panel by clicking the "Wrench" tool as shown below. When that panel opens, you should see the new "Degrees" setting next to the "Target RA Keyword" text box. Enable that option and let me know if it solves your problem properly.

To update to the AIJ daily build, follow the instructions here:

http://astroimagej.1065399.n5.nabble.com/After-a-fresh-installation-of-AIJ-be-sure-to-update-to-the-latest-build-td142.html

Karen

On 4/30/2017 5:43 PM, basilr [via AstroImageJ] wrote:

My CCD records the Target RA in decimal degrees (not hours) causing the DPCC module to calculate incorrect altitudes + azimuths (airmass, J2000 positions, etc.) Is there a way to tell DPCC the target RA from the FITS headeris in decimal degrees?

Extract of FITS header:

33 RA 165.7209568 [deg] Telescope pointing RA                     R
34 DEC 18.66424214 [deg] Telescope pointing DEC                   R

Log extract from DPCC

    Observatory name "Custom Lon, Lat, and Alt entry" manually selected
    Target coordinates = 21:43:05.484 +18:39:25.39 (Epoch of Observation) (from FITS header RA and DEC)
    JD = 2457871.613519 (mid-exp)
    HJD = 2457871.611227 (mid-exp)    (correction = -3.2991 minutes)
    BJD(TDB) = 2457871.612031 (mid-exp)    (correction = -2.1415 minutes)
    Altitude = -26.91 (mid-exp)
    Azimuth = 28.84 (mid-exp)
    Hour Angle = -10.20 (mid-exp)
    Zenith Distance = 116.91 (mid-exp)
    Airmass = -1.0000 (mid-exp)
    Bias corrected with mbias.fits
    Dark corrected with mdark.fits and exposure time scaling factor 10.0/10.0=1.0
    Flat corrected with mflat.fits
    Saved processed science file "C:\Temp\2\4.27.17\(138155)2000ES70\pipelineout\(138155)2000ES70_FilterA_20170428_024336_out.fits"

Thank you!
Basil Rowe

---

If you reply to this email, your message will be added to the discussion below:

http://astroimagej.1065399.n5.nabble.com/RA-in-FITS-header-is-in-decimal-degrees-causing-problem-with-FITS-Header-Update-tp671.html

To start a new topic under AstroImageJ, email [hidden email]
To unsubscribe from AstroImageJ, click here.
NAML

[basilr]

The new option work great. Thank you for the quick fix and clear explanation with screen shots!

Great program. Much appreciated!

Basil