1672
Comment:
|
1659
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
[[TableOfContents]] | |
Line 4: | Line 5: |
== Heterodyne: == | == Heterodyne == |
Line 20: | Line 21: |
== Bolometer: == | == Bolometer == |
Line 22: | Line 23: |
For the bolometer observations, indicate the old commands in your {{{ObsForm}}}, we will adapt them accordingly. | For the bolometer observations, indicate the commands in your {{{ObsForm}}}. |
Line 25: | Line 26: |
* For the mapping indicate with the old syntax, we will adapt it. | * For a complete description, check in CookbookPako |
Line 32: | Line 33: |
Pako (@wbolo macro) | '''Pako''' (@wbolo macro) |
Line 36: | Line 37: |
Monitor (mopsic): On-Off | '''Monitor''' (mopsic): On-Off |
Heterodyne/Bolometer observing procedures with the New Control System (NCS) at the IRAM-30m. The .pako extension is understood by the paKo software which produces the xml files to run the observations.
Heterodyne
- To setup the SIS project (PI, ProjID, Receiver, Catalogues) : attachment:setup-xxx_xx.pako
- To setup the backends: attachment:backends-xxx_xx.pako
- To setup a wobbler-switching procedure: attachment:target-wsw-xxx_xx.pako
- To setup a position-switching procedure: attachment:target-psw-xxx_xx.pako
- To setup a frequency-switching procedure: attachment:target-fsw-xxx_xx.pako
- Here is a model of the line catalog, use a specific name for your project: attachment:model.lin
VESPA: Note that by default the receivers are in wide mode, except the 3mm receivers. The sky frequency that you specify appears at 598MHz in the IF which is close to the upper limit of VESPA. The receivers should be configured in narrow mode for VESPA for normal observations.
Bolometer
For the bolometer observations, indicate the commands in your ObsForm.
The onf.pako macro allows an onOff integration, typically you can use it as: pako> @onf 20 35 (it performs a 20x60sec integration with a wobbler throw of 35")
For a complete description, check in CookbookPako
Don't forget to fill up your ObsForm in the DB, it will ensure that your project is correctly observed.
Snapshots:
Pako (@wbolo macro)
attachment:pakosnapshot1.jpg
Monitor (mopsic): On-Off
attachment:monitor-1.jpg