Issue Loading FITS Header Data into DP Coordinate Converter in AstroImageJ

Hi,

I’m currently working with some exoplanet transit images I captured last year using CCDCiel. I’m trying to load the target coordinates and observatory location into the DP Coordinate Converter directly from the FITS header, but I’m running into some issues.

I’ve already configured the appropriate FITS header keywords under General FITS Header Settings:
image

These headers are indeed present in my science images:
image

However, when I try to load this information from the header:

…the DP Coordinate Converter does not populate the fields as expected:
image

Am I missing a step, or could there be an issue with how the header keywords are defined or accessed?

Thanks in advance for your help!

Best regards,
Joaquin

Joaquin,

I can’t solve your problem directly, but there is an alternative setup in DPCC if you can’t otherwise process your data. See screenshot below.

In Observatory ID, select Custom Lon, Lat, and Alt entry. In Geographic Location of Observatory, enter your geographical coordinates and altitude manually. I also enter the ID of the target manually in the SIMBAD Object ID box near the top left, then press enter.

Roy

Roy,

Thank you very much for your response and for sharing this helpful workaround. I’ve followed your recommendation and successfully processed the images.

Joaquín

Joaquin,

You’re welcome. It’s good that it worked for you.

Roy

Hi Joaquin,
I noticed a typo in your FITS Header Input Settings: the target RA and DEC keywords are shown as OBJECTRA whereas the FITS header shows OBJCTRA, note the missing ‘E’.
I couldn’t find any obvious problem with the SITE data though.
Perhaps this will help a little.
Byron

Byron, you’re absolutely right—I had used the wrong keyword!

I corrected the keyword name, but it still didn’t work. I didn’t realize this on my own—I later learned (from a question I posted on the official forum) that AstroImageJ only loads header values once it begins processing the images.

After processing them, the RA and DEC values were correctly populated.

Thanks,
Joaquín