|
Size: 1370
Comment:
|
Size: 1233
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| /!\ Note that messages in aloop are not anymore useful since the START command create an .xml file, send it to the queue and pass to the next loop directly. | |
| Line 20: | Line 19: |
| * The onf.pako macro allows an onfoff integration, typically you can use it as: @onf 20 35 (perform a 20x60sec integration with a throw of 35'') | * 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'') |
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
Bolometer:
For the bolometer observations, indicate the old commands in your ObsForm, we will adapt them accordingly.
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 the mapping indicate with the old syntax, we will adapt it.
Don't forget to fill up your ObsForm in the DB, it will ensure that your project is correctly observed.