Hello,
I want to participate for the alpha Drac. observing campaign. These data must be submitted to the STAROS database. I use SpcAudace software for datareduction. By uploading the spectra, i get errormessage that several fits-keywords are not present. several keywords, which were not present I was able to solve myself.
But 2 of them: BSS_ITRP and JD_OBS are not in the FITS header.
Simular keyword BSS_ESRP is present for the resolution. I don't know what the difference is between BSS_ESRP and BSS_ITRP ?
How can BSS_ITRP and JD_OBS be added tot the fits header in SpcAudace ?
thanking n advance,
Erik
fits-keywords for STAROS database and SpcAudace
-
- Posts: 49
- Joined: Sun Jun 15, 2014 1:31 am
- Location: Kruibeke
- Contact:
-
- Posts: 1952
- Joined: Mon Sep 26, 2011 4:41 pm
- Contact:
Re: fits-keywords for STAROS database and SpcAudace
Hi Erik,
STAROS should not be asking for BSS_ITRP if BSS_ESRP is present
BSS_ESRP is the resolution measured in the actual spectrum
BSS_ITRP is the resolution given in the instrument description (which is added by BeSS if BSS_ESRP is not present)
From the definitions in the BeSS fits standard document
The FITS header should contain the real spectral resolution (in BSS_ESRP), and the wavelength
used for calculation (in BSS_SRPW). This value should be close to the typical resolution of
instrument (defined in the Instrument record). If the spectral resolution is significantly different
from the typical instrument resolution (e.g. if the spectrum has been binned), the reason /
method for binning should be given (in BSS_BINN).
If the real resolution is not given in the
header, BeSS will add in the spectrum header a separate keyword (BSS_ITRP) containing the
typical resolution of the instrument used to obtain the spectrum (as an indication).
STAROS should not be asking for BSS_ITRP if BSS_ESRP is present
BSS_ESRP is the resolution measured in the actual spectrum
BSS_ITRP is the resolution given in the instrument description (which is added by BeSS if BSS_ESRP is not present)
From the definitions in the BeSS fits standard document
The FITS header should contain the real spectral resolution (in BSS_ESRP), and the wavelength
used for calculation (in BSS_SRPW). This value should be close to the typical resolution of
instrument (defined in the Instrument record). If the spectral resolution is significantly different
from the typical instrument resolution (e.g. if the spectrum has been binned), the reason /
method for binning should be given (in BSS_BINN).
If the real resolution is not given in the
header, BeSS will add in the spectrum header a separate keyword (BSS_ITRP) containing the
typical resolution of the instrument used to obtain the spectrum (as an indication).
LHIRES III #29 ATIK314 ALPY 600/200 ATIK428 Star Analyser 100/200 C11 EQ6
http://www.threehillsobservatory.co.uk
http://www.threehillsobservatory.co.uk
-
- Posts: 1952
- Joined: Mon Sep 26, 2011 4:41 pm
- Contact:
Re: fits-keywords for STAROS database and SpcAudace
JD_OBS is also not part of the BeSS standard and so is not defined. Only DATE_OBS is required in the BeSS standard so STAROS should be generating it from that if it is required.
I recommend contacting the STAROS team and asking them what standard they are using and why they are not using the BeSS standard
Robin
I recommend contacting the STAROS team and asking them what standard they are using and why they are not using the BeSS standard
Robin
LHIRES III #29 ATIK314 ALPY 600/200 ATIK428 Star Analyser 100/200 C11 EQ6
http://www.threehillsobservatory.co.uk
http://www.threehillsobservatory.co.uk
-
- Posts: 1432
- Joined: Mon Sep 26, 2011 6:59 pm
- Contact:
Re: fits-keywords for STAROS database and SpcAudace
The next update will offer greater flexibility. For example, BESS_ESPR will be optional. Please note, however, that it is primarily up to the software designers to ensure that the data produced is as compatible as possible with the analysis applications (BESS, STAROS, ...), and not the other way round.
Christian B
Christian B
-
- Posts: 24
- Joined: Mon Apr 15, 2019 4:33 pm
Re: fits-keywords for STAROS database and SpcAudace
Hi all,
Yes, I've listed (and update) the necessary keys on this page : https://alphadra.staros-projects.org/kn ... /start/how
I have update the application
The JD-OBS key was an error related to an old display on the title of a plot, i delete it.
As said Christian, for the resolution keys, I've changed the logic in relation to this standard and made them optional to avoid any blocking.
Thank you very much for these feedback, it helps to improve the platform.
Matthieu
Yes, I've listed (and update) the necessary keys on this page : https://alphadra.staros-projects.org/kn ... /start/how
I have update the application
The JD-OBS key was an error related to an old display on the title of a plot, i delete it.
As said Christian, for the resolution keys, I've changed the logic in relation to this standard and made them optional to avoid any blocking.
Thank you very much for these feedback, it helps to improve the platform.
Matthieu
-
- Posts: 1952
- Joined: Mon Sep 26, 2011 4:41 pm
- Contact:
Re: fits-keywords for STAROS database and SpcAudace
I strongly disagree. The database designers should makes sure that as far as possible it is compatible with existing standards. For example I can upload the same spectrum to AAVSO, ARAS,BeSS I do not want to have to change the header format for different databases. There is other software besides SpecIntiChristian Buil wrote:The next update will offer greater flexibility. For example, BESS_ESPR will be optional. Please note, however, that it is primarily up to the software designers to ensure that the data produced is as compatible as possible with the analysis applications (BESS, STAROS, ...), and not the other way round.
Christian B

Cheers
Robin
LHIRES III #29 ATIK314 ALPY 600/200 ATIK428 Star Analyser 100/200 C11 EQ6
http://www.threehillsobservatory.co.uk
http://www.threehillsobservatory.co.uk
-
- Posts: 1952
- Joined: Mon Sep 26, 2011 4:41 pm
- Contact:
Re: fits-keywords for STAROS database and SpcAudace
This is a start but it is not sufficient to define the header precisely. See the BeSS standard document for an example of how the header should be specifiedMatthieu Le Lain wrote:Hi all,
Yes, I've listed (and update) the necessary keys on this page : https://alphadra.staros-projects.org/kn ... /start/how
The BeSS standard is not ideal and could be improved but changes should be done transparently and in agreement with other database operators and software suppliers, not unilaterally. (I already faced this problem with AAVSO who wanted to introduce a completely incompatible system)
Cheers
Robin
LHIRES III #29 ATIK314 ALPY 600/200 ATIK428 Star Analyser 100/200 C11 EQ6
http://www.threehillsobservatory.co.uk
http://www.threehillsobservatory.co.uk
-
- Posts: 49
- Joined: Sun Jun 15, 2014 1:31 am
- Location: Kruibeke
- Contact:
Re: fits-keywords for STAROS database and SpcAudace
[quote="Matthieu Le Lain"]Hi all,
Yes, I've listed (and update) the necessary keys on this page : https://alphadra.staros-projects.org/kn ... /start/how
I uploaded again a spectrum and now with succes.
thank you for thinking with me and solving the problem !
best regards,
Erik
Yes, I've listed (and update) the necessary keys on this page : https://alphadra.staros-projects.org/kn ... /start/how
I uploaded again a spectrum and now with succes.
thank you for thinking with me and solving the problem !
best regards,
Erik
-
- Posts: 24
- Joined: Mon Apr 15, 2019 4:33 pm
Re: fits-keywords for STAROS database and SpcAudace
Thanks Erik, I'm glad it's resolved.
Thanks also Robin, I'll work on it!
Matthieu
Thanks also Robin, I'll work on it!
Matthieu