* familiarize users with Carma specific issues in Miriad, mostly calibration (participants are allowed to "bring" their own data to the table)

+

* feedback on the first version of the Carma cookbook we'll use during the Party

+

* make sure Miriad is installed on their computer, and assist if possible. For those who bring their own laptops and do not have Miriad installed yet, a [[questionnaire]] should be returned to Peter

+

+

== Outline ==

+

+

* brief and basic introduction on miriad on how it really works, the unix way; in addition some wise words about miriad shell vs. c-shell vs. (i)python shell.

+

+

* some technical background on datasets, and what visibility data really are, so we understand hacking tools like "uvio", the difference between puthd and uvputhd, itemize, etc.etc. Header variables vs. UV Variables.

+

+

* Data fixing techniques - these are time highly variable, things like the jyperk trick. how to fix broken uv variables (double vs. float). Some of these problems are fixed when the data is refilled at NCSA, but something not timely enough, so we need to know some tricks.

* Mapping techniques (e.g. the issue of OVRO, HATCREEK and CARMA baselines and what it means for mapping). Continuum vs. Spectral Line

+

+

* Analysis: this might be pretty brief, as this is covered quite well in the standard Miriad Users Guide, but some common guidelines will be useful here to cover. Also: (mir)ds9, wip, karma, matplotlib (stuartt's pet peeve)

+

+

+

We might be able to reuse some ideas from the ATNF "Party" from a few years ago. They have kept a

+

record of their [http://www.atnf.csiro.au/computing/software/miriad/tutorials.html tutorials]

Revision as of 17:00, 7 February 2007

The Miriad Party will take place February 20-23, at OVRO.

Goals

familiarize users with Carma specific issues in Miriad, mostly calibration (participants are allowed to "bring" their own data to the table)

feedback on the first version of the Carma cookbook we'll use during the Party

make sure Miriad is installed on their computer, and assist if possible. For those who bring their own laptops and do not have Miriad installed yet, a questionnaire should be returned to Peter

Outline

brief and basic introduction on miriad on how it really works, the unix way; in addition some wise words about miriad shell vs. c-shell vs. (i)python shell.

some technical background on datasets, and what visibility data really are, so we understand hacking tools like "uvio", the difference between puthd and uvputhd, itemize, etc.etc. Header variables vs. UV Variables.

Data fixing techniques - these are time highly variable, things like the jyperk trick. how to fix broken uv variables (double vs. float). Some of these problems are fixed when the data is refilled at NCSA, but something not timely enough, so we need to know some tricks.

Mapping techniques (e.g. the issue of OVRO, HATCREEK and CARMA baselines and what it means for mapping). Continuum vs. Spectral Line

Analysis: this might be pretty brief, as this is covered quite well in the standard Miriad Users Guide, but some common guidelines will be useful here to cover. Also: (mir)ds9, wip, karma, matplotlib (stuartt's pet peeve)

We might be able to reuse some ideas from the ATNF "Party" from a few years ago. They have kept a
record of their tutorials