Opened 13 years ago

Last modified 12 years ago

#222 new question

ERROR: SDFITS file contains invalid beam number.

Reported by: kuiper@… Owned by: Malte Marquarding
Priority: normal Milestone: Unified development
Component: General Version: 2.0
Severity: normal Keywords:
Cc:

Description

What does this error mean? From my data:

In [6]: for i in range(32): print tbdata[i]BEAM?,

...:

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

From the header:

TTYPE16 = 'BEAM ' TFORM16 = 'I '

Attachments (1)

1989_148.fits​ (123.8 KB) - added by anonymous 13 years ago.

Download all attachments as: .zip

Change History (4)

Changed 13 years ago by anonymous

Attachment: 1989_148.fits​ added

comment:1 Changed 13 years ago by kuiper@…

I checked the source code in SDFITSreader.cc and saw that the beam number is 1-relative. Changing the beam number to 1 made the error go away.

comment:2 Changed 12 years ago by anonymous

Is this really the way it suppose to work? By the what could mean error fatal error access to undeclared static property ?

comment:3 Changed 12 years ago by Malte Marquarding

I think 1-based is the convention in SDFITS. ASAP certainly does 0<->1 changes during IO. This is caused by the underlying IO library (from livedata) ASAP is built upon. I would have to change this upstream.

Note: See TracTickets for help on using tickets.