×

INDI Library v1.9.9 Released (30 Nov 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Question about FITS Header Entries

  • Posts: 124
  • Thank you received: 28
Hi,

EKOS writes some entries in the FITS header. Is there any chance adding entries from connected devices, too ?
I know for example the CCD Camera snoops devices, but is not going the add the values in the FITS Header. In addition some device types are even not be selectable as snoop devices (e.g. environment)

I would be nice doing so, because than you could save all the context information of an image inside the FITS file (Focuser position, outside Temp, Sky Quality, Dew etc.) This enables to make some test and calculations later (e.g. focuser positions over temp and filter)

Any ideas ?

Michel
The following user(s) said Thank You: Juan Daniel
3 years 2 months ago #43732

Please Log in or Create an account to join the conversation.

  • Posts: 120
  • Thank you received: 16
This could be great feature. I have just purchased automatic focuser (AF3) with temperature probe and I am bit disappointed with Ekos as it is not able to save the measured temperature into FITS header.
2 years 6 months ago #54974

Please Log in or Create an account to join the conversation.

  • Posts: 384
  • Thank you received: 115
FYI, while not changing FITS header fields, I did submit a code update yesterday for updating temperature and HFR in focus logging. I don't have a focuser temp sensor, but many of us do have Pegasus PPB, V2, or other weather temperature sensors that can now be properly captured in focus logging (all focus algs). Also added is a separate CSV friendly autofocus log. A header line + comma delimited data fields (one line per successful autofocus) are provided. An example autofocus log is below:

date, time, position, temperature, filter, HFR
2020-06-01, 15:06:53, 42578, 15.0, Red, 1.119
2020-06-01, 15:07:53, 42443, 15.0, Red, 1.19

If approved, these changes will broaden supported temperature sensors for focus logging, and provide better support for correlating temperature, filter, HFR, and focuser position relationships. The code is awaiting approval/merge. The work is related to this other post:
www.indilib.org/forum/ekos/6901-how-does....html?start=24#54331

Cheers, Doug
RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.
The following user(s) said Thank You: Ferrante Enriques
2 years 6 months ago #54978

Please Log in or Create an account to join the conversation.

  • Posts: 124
  • Thank you received: 28
Hi Doug,
a good idea, too. Ideally I would store all context information about and image in the image file and nowhere else, because this data is linked 1:1 togehter.
Michel
2 years 6 months ago #55055

Please Log in or Create an account to join the conversation.

  • Posts: 384
  • Thank you received: 115
Hi Michel, I (almost/pretty much) agree. From one perspective, having all context in the FITS header is really convenient. For example, the archive AstroDom already supports FITS header keywords and this would make focus performance correlation/evaluation easier (a pet peeve for me lately). Ferrante (AD developer) wouldn't need to think about how to import and correlate a separate, focus specific CSV file to capture that info in the image archive DB. On the other hand, it does seem just a bit awkward to include focuser position (for example) in an image header; the info relation doesn't seem quite as compelling as for other fields (HFR, ambient temperature). So, I can see it both ways. Given how much cruft is in the typical FITS header of most professional observatories, having one or two slightly less compelling entries shouldn't really cause any problem... I do think having a separate focuser log is good because that log can be directly graphed to create temperature, HFR, and position correlation information that is independent of any specific image. It wouldn't be very convenient to have to pull this out of headers separately. So I see both ideas (header and separate log) as complementary.
Cheers, Doug
RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.
Last edit: 2 years 6 months ago by Doug S.
2 years 6 months ago #55061

Please Log in or Create an account to join the conversation.

  • Posts: 1944
  • Thank you received: 419
Adding to that, the FITS standard does allow for adding custom keywords but one should be cautious with that. If Ekos adds keywords A and B and another imaging system adds similar keywords but calls them C and D then it would become very hard for applications that process the FITS headers to support all keyword names and formats. I do not necessarily mean to imply to not add additional info to the FITS header of an image but merely that if such an addition would add valuable info, that the discussion about it should be held on a much wider scale that only this forum.

Clear skies, Wouter
Wouter van Reeven

ASI6200MM and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R
2 years 6 months ago #55069

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 128
FOCUSPOS is an official FITS header entry, see here . And I do think it should be in the header of all image frames, IMO it's a hardware setting just like GAIN, EXPTIME etc.....
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
2 years 6 months ago #55152

Please Log in or Create an account to join the conversation.

  • Posts: 376
  • Thank you received: 55
This may be exactly what you implied...
Given the values in the link you provided ( fits parameters )perhaps writing all 3 values in the the fits file (if they are available) would extend the posibilities of integration with other code.
FOCUSPOS – Focuser position in steps, if focuser is connected.
FOCUSSSZ – Focuser step size in microns, if available.
FOCUSTEM – Focuser temperature readout in degrees C, if available.
120 MM Skywatcher Esprit + Celestron CGX, ZWO ASI 224MC guiding, Pegasus FocusCube+PPBA
Nikon Z7 8256 x 5504 4.34 um. Triad Ultra Quad NB Filter
1) MeLE Quieter3C 8G Ubuntu-mate 22.04.1 2) Odroid-N2. 3) StellarMate RPI4 8G
The good, the bad, the ugly at sciencedowneast.no-ip.ca/zenphoto/
2 years 6 months ago #55157

Please Log in or Create an account to join the conversation.

  • Posts: 206
  • Thank you received: 31
This is a very good idea to integrate the focuser parameters into the FITS header
FOCUSPOS – Focuser position in steps, if focuser is connected.
FOCUSSSZ – Focuser step size in microns, if available.
FOCUSTEM – Focuser temperature readout in degrees C, if available.

However in the last KStars version (3.4.2) the FOCUSPOS line doesn't report the current focuser position and stays = 0

Regards,
Celestron EdgeHD 11 on Celestron CGE Pro
Celestron OAG and MicroTouch Autofocuser
ASI2600MC Pro + ASI174MM
HyperStar
MaxDome II
2 years 6 months ago #55191

Please Log in or Create an account to join the conversation.

  • Posts: 18
  • Thank you received: 1
Hi,

do you know if this feature was finally added to Ekos? I bought the ZWP EAF and I have doubts about how to get the focuser position for each set of subframes to reproduce in flats frames (my idea is to refocus on each filter change).

Thanks and regards.
3 months 1 week ago #85829

Please Log in or Create an account to join the conversation.

  • Posts: 435
  • Thank you received: 157
Yes, or INDI actually, just configure the correct focuser as snoop target of your camera and you get:

FOCUSPOS= 1861 / Focus position in steps
FOCUSTEM= -6.950E+00 / Focuser temperature in degrees C
Remote observatory running Ubuntu 21.10 x64 with ScopeDome 2M, Skywatcher EQ8, TS 8" RC, Atik 383L+, ASI178MC, ASI120MM-S, SX Lodestar X2, SX USB wheel with OAG, ZWO EAF, Gemini SnapCap, USB_DewPoint, KomaHub
The following user(s) said Thank You: Juan Daniel
3 months 6 days ago #85910

Please Log in or Create an account to join the conversation.

Time to create page: 2.405 seconds