Problems uploading data file from ISIS -SOLVED-

Affiliation
Madrid Astronomical Association M1 (Spain) (AAM)
Sun, 01/05/2020 - 14:06

Hi,

I'm attempting to upload a data file of an 'alf Ari' spectrum to AVSpec to validate myself.

FITS file is rejected because of Equipment name data. File is generated by ISIS software. It writes only one field for instrumentation.

How could I fix this in an easy way?

Regards

 

FILENAME: alf Ari_20200104_958_RMU.fit
ATTEMPTING TO OPEN FILE
* FILE OPENED
* FILE LENGTH: 1 

********** FILE 0 **********

ATTEMPTING TO READ HEADER
* HEADER READ 
PARSING HEADER FOR KEYWORDS

LOOKING FOR Fits standard
* FOUND Fits standard FROM SIMPLE
Fits standard : True

LOOKING FOR Bits per pixel
* FOUND Bits per pixel FROM BITPIX
Bits per pixel : -32

LOOKING FOR Number of data axes 
* FOUND Number of data axes  FROM NAXIS
Number of data axes  : 1

LOOKING FOR Length of data axis 1
* FOUND Length of data axis 1 FROM NAXIS1
Length of data axis 1 : 4887

LOOKING FOR Coordinate at ref pixel
* FOUND Coordinate at ref pixel FROM CRVAL1
Coordinate at ref pixel : 3602.872933

LOOKING FOR Coordinate increment
* FOUND Coordinate increment FROM CDELT1
Coordinate increment : 0.77493525

LOOKING FOR Object name
* FOUND Object name FROM OBJNAME
Object name : alf Ari

COMPARING STANDARD STAR
STARS MATCH

LOOKING FOR Date of observation start
* FOUND Date of observation start FROM DATE-OBS
Date of observation start : 2020-01-04T22:59:34

LOOKING FOR Date of observation end
X NOTHING FOUND FROM DATE-END
X COULD NOT FIND Date of observation end
OK - Date of observation end OPTIONAL

LOOKING FOR Total exposure time
* FOUND Total exposure time FROM EXPTIME
Total exposure time : 298

LOOKING FOR Exposure decomposition
* FOUND Exposure decomposition FROM EXPTIME2
Exposure decomposition : 7 x 40 s

LOOKING FOR Wavelength unit
* FOUND Wavelength unit FROM CUNIT1
Wavelength unit : Angstrom

LOOKING FOR Axis type
* FOUND Axis type FROM CTYPE1
Axis type : Wavelength

LOOKING FOR Reference pixel
* FOUND Reference pixel FROM CRPIX1
Reference pixel : 1

LOOKING FOR Julian date mid exposure
X NOTHING FOUND FROM JD
* FOUND Julian date mid exposure FROM JD-MID
STANDARDIZING KEYWORD JD-MID TO JD
Julian date mid exposure : 2458853.4598

LOOKING FOR Obscode
* FOUND Obscode FROM OBSERVER
Obscode : RMU

LOOKING FOR Instrument
X NOTHING FOUND FROM AAV_INST
* FOUND Instrument FROM BSS_INST
STANDARDIZING KEYWORD BSS_INST TO AAV_INST
Instrument : RC200+Alpy_600+Atik314L
X EQUIP DISCREPANCY

LOOKING FOR Site
X NOTHING FOUND FROM AAV_SITE
* FOUND Site FROM BSS_SITE
STANDARDIZING KEYWORD BSS_SITE TO AAV_SITE
Site : MDRDVENTILLA

LOOKING FOR Resolving power
X NOTHING FOUND FROM AAV_ITRP
* FOUND Resolving power FROM BSS_ITRP
STANDARDIZING KEYWORD BSS_ITRP TO AAV_ITRP
Resolving power : 496

LOOKING FOR Software
* FOUND Software FROM VERSION
Software : ISIS V5.9.7

CHECKING TIME INFO
  DATE-OBS FOUND
  DATE-END NOT FOUND
  EXPTIME FOUND
  2/3 TIME INFO SATISFIED
  APPENDED DATE-END AS 2020-01-04T23:04:32.000

CHECKING AIRMASS
X COULD NOT CHECK OBSERVATION SANITY

X HEADER BAD
X ABANDONING STAR INFO

ATTEMPTING TO OPEN DATA
* DATA OPENED

** UPLOAD REPORT **
HEADER + DATA BAD
1 ERRORS
  Equipment name from FITS does not match record
 

 

 

 

 

Affiliation
British Astronomical Association, Variable Star Section (BAA-VSS)
BeSS standard

ISIS is correct re the BeSS standard. You only need to supply BSS_INST.  This has to exactly match the information you have already supplied to BeSS/AAVSO about this setup however. I suggest checking that this is the case.

 

"LOOKING FOR Instrument
X NOTHING FOUND FROM AAV_INST
* FOUND Instrument FROM BSS_INST
STANDARDIZING KEYWORD BSS_INST TO AAV_INST
Instrument : RC200+Alpy_600+Atik314L
X EQUIP DISCREPANCY"

Cheers

Robin

Affiliation
Madrid Astronomical Association M1 (Spain) (AAM)
¿How could I modofy FITS header?

Hi.

How could I modofy FITS header?

What software does produce the right header format?

This is a big problem for me in order to submit spectra to AVSpec.

Regards

Miguel

Affiliation
British Astronomical Association, Variable Star Section (BAA-VSS)
Header

There is nothing wrong with ISIS. ISIS produces the correct header. The problem is with AAVSO. You need to tell AAVSO first what your BSS_IST are. One of these must then match exactly what you have in your header. Have you told AAVSO that your BSS_INST is "RC200+Alpy_600+Atik314L" ?

Robin

Affiliation
British Astronomical Association, Variable Star Section (BAA-VSS)
BSS_INST

There is a file list_instru.txt in your ISIS installation. You enter your alternative  BSS_INST in there. They then appear in a drop down list in ISIS and you select which one to appear in your header. Here is mine

You can also modify the header manually in ISIS by displaying the profile and pressing "HEADER" but it is better to use the txt file of BSS_INST as what is in the Header must exactly match what you have alrready told AAVSO or BeSS

 

File upload
Affiliation
British Astronomical Association, Variable Star Section (BAA-VSS)
Equipment description in AAVSO

I have entered hundreds of spectra into BeSS and the BAA spectroscopy databases so I know ISIS works correctly provided the database conforms to the BeSS standard as AAVSO claim theirs does.

As far as I can tell, you enter the description of your setup in AAVSO here

https://www.aavso.org/apps/site_equip/equipment

I expect AAVSO uses "My Equipment Name" as BSS_INST so this must exactly match what you put in the header for BSS_INST

Affiliation
Madrid Astronomical Association M1 (Spain) (AAM)
Thanks Robin, I'll see that issues

Thanks very much, I`ll check those things.

Regards

Affiliation
Madrid Astronomical Association M1 (Spain) (AAM)
It's solved. Thank you

I've found what was wrong. It was my equipment description title in my account. Now, the alf Ari is uploaded. I hope to begin to submit spectra soon.

Regards

MIguel