Custom Query (241 matches)
Results (94 - 96 of 241)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #55 | wontfix | auto_quotient not picking the right scans | ||
| Description |
auto_quotient with Tid data seems to be choosing the wrong scans with an East-on-on-West pointing pattern. The East scan seems to be chosen as the reference for both in one case. This is because of a pause in observing between the second 'on' and 'west' which makes the 'east' scan the closest. It would be useful to be able to control which reference scan is used to override the nearest-in-time scheme. Also, if auto_quotient could report which scans are being used it would be helpful. |
|||
| #57 | wontfix | Frequency scale is wrong after merging data from two files. | ||
| Description |
I have two files consisting of two parts of the same observation that were interrupted half way through due to a drive error on Mopra. When working with the individual files, I find that they both appear to hold good data, with a correct frequency axis. When I combine the two files, using the following: s1 = scantable('../../../2006-07-10_1001-M168.rpf') s2 = scantable('../../../2006-07-10_1014-M168.rpf') s = merge(s1,s2) I find that the frequency axis comes out incorrect (shifted by about 273MHz). |
|||
| #58 | fixed | Need to document scantable column names | ||
| Description |
Scantable column names and data types need to be documented so that users can use TAQL usefully in the selector object and such. |
|||
