Differences between revisions 26 and 38 (spanning 12 versions)
Revision 26 as of 2006-05-11 08:42:33
Size: 1616
Editor: visitor9
Comment:
Revision 38 as of 2009-04-16 08:26:39
Size: 916
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
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. Bolometer/Heterodyne 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.

Back to Pool page: PoolObserving

== Bolometer ==

For the bolometer observations, put instructions and 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.

== Heterodyne ==
Line 4: Line 17:
== Heterodyne: == == Snapshots ==
Line 6: Line 19:
 * 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
'''Pako''' (@wbolo macro)
Line 13: Line 21:

<!> '''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.
{{attachment:pakosnapshot1.jpg}}
Line 20: Line 25:
== Bolometer: ==
Line 22: Line 26:
For the bolometer observations, indicate the old commands in your {{{ObsForm}}}, we will adapt them accordingly. '''Monitor''' (mopsic): example of On-Off on a secondary calibrator
Line 24: Line 28:
 * 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.

 
== Snapshots: ==

Pako (@wbolo macro)

attachment:pakosnapshot1.jpg
{{attachment:monitor-1.jpg}}

Bolometer/Heterodyne 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.

Back to Pool page: PoolObserving

Bolometer

For the bolometer observations, put instructions and 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.

Heterodyne

Snapshots

Pako (@wbolo macro)

pakosnapshot1.jpg

Monitor (mopsic): example of On-Off on a secondary calibrator

monitor-1.jpg

PoolSetup (last edited 2009-04-16 08:26:39 by localhost)