#249 closed defect (fixed)
ASAP 3.0 scantables incompatible with 3.1 ?
| Reported by: | Owned by: | Malte Marquarding | |
|---|---|---|---|
| Priority: | normal | Milestone: | ASAP 3.0 |
| Component: | General | Version: | 1.0 |
| Severity: | critical | Keywords: | |
| Cc: |
Description
When trying to load ASAP scantables previously created using version 3.0.0, I get the error 'SEVERE: Invalid Table data type when accessing column in ROArrayColumn ctor for column RESTFREQUENCY'
Likewise, scantables created in 3.1.0 produce the same error when attempting to load them into 3.0.0. I attach an example scantable created in 3.0. Is there a fix or workaround for this problem?
Attachments (1)
Change History (4)
Changed 13 years ago by
| Attachment: | L1527_scantable.tgz added |
|---|
comment:1 Changed 13 years ago by
| Owner: | changed from Malte Marquarding to Malte Marquarding |
|---|---|
| Severity: | major → critical |
| Status: | new → assigned |
Yikes I feared there would be something coming in through the major changes via the ALMA changes. In short there is no workaround, I have to fix it. I probably have to release asap-4.0 immediately as this is a change to the data format and then need to provide a asap3to4 script.
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This has been resolved in r2321. A new release asap-4.0.0 will follow soon.
comment:3 Changed 13 years ago by
asap-4.0.0 is now out. Don't keep any scantables written with asap-3.1
Scantable folder created using ASAP 3.0.0