|
Size: 75
Comment:
|
Size: 1439
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| The users of the pool are invited to share pool-related informations. | #acl PoolUsersGroup: read,write All: read The users of the pool are invited to share pool-related informations here. A special guest wikiname has been created to edit that page: ObsPool (pwd: pele68). If you think you need a special page to add more exhaustive comment you can contact wih leon@iram.es for such purpose. |
| Line 4: | Line 7: |
[[TableOfContents(3)]] ------- == 060316 severe coordinate errors [Bertoldi] == We still get a lot of strong coordinate errors, e.g. 10% in 174 and even 30% earlier. == 060316 on-off overheads are factor 3 [Bertoldi] == For one onoff project (175_05) I reduced the data and found that the obs time accounted in the database is a factor 3 of the integration time on the sky, which seems larger than what we had last year, where it was a factor 2. Why is that? == 060316 revised onf30 macro [Bertoldi] == I have saved the old onf30.pako as onf30_old.pako and modified the standard onf.pako to make the subscan duration 30 sec instead 60 sec, and symmetric=no instead of yes. Note that the standard onf has a 2 minute nodding time, which i think is a bit large. I do not see any acceleration problems in the recent data. In principle, the shorter the nodding time, the better the data, but at some time the overheads increase. == 060316 ObsLog missing entry for subscan time [Bertoldi] == The Pool database obs log does not show the duration of a subscan, only the number of subscans. |
The users of the pool are invited to share pool-related informations here. A special guest wikiname has been created to edit that page: ObsPool (pwd: pele68). If you think you need a special page to add more exhaustive comment you can contact wih leon@iram.es for such purpose.
060316 severe coordinate errors [Bertoldi]
We still get a lot of strong coordinate errors, e.g. 10% in 174 and even 30% earlier.
060316 on-off overheads are factor 3 [Bertoldi]
For one onoff project (175_05) I reduced the data and found that the obs time accounted in the database is a factor 3 of the integration time on the sky, which seems larger than what we had last year, where it was a factor 2. Why is that?
060316 revised onf30 macro [Bertoldi]
I have saved the old onf30.pako as onf30_old.pako and modified the standard onf.pako to make the subscan duration 30 sec instead 60 sec, and symmetric=no instead of yes. Note that the standard onf has a 2 minute nodding time, which i think is a bit large. I do not see any acceleration problems in the recent data. In principle, the shorter the nodding time, the better the data, but at some time the overheads increase.
060316 ObsLog missing entry for subscan time [Bertoldi]
The Pool database obs log does not show the duration of a subscan, only the number of subscans.