Revision as of 20:15, 22 March 2007 by 22.214.171.124
- 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 to assess the likelyhood for any problems before we start. If you have miriad installed, I suggest a few sanity tests. We will also distribute miriad binary releases, though nobody should shy from an installation from source using your own native compiler.
- brief and basic introduction on miriad on how it really works, the unix way; in addition some wise words about shells: miriad shell vs. c-shell vs. (i)python.
- some technical background on datasets, and what visibility data really are, so we understand hacking tools like "uvio", the difference between puthd and uvputhd (header variables vs. UV Variables), itemize, etc.etc.
- 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.
- Data summary and inspection - listobs, uvindex, uvplt, uvimage/ds9, etc.
- Calibration techniques - selfcal, tranfer of phases from wide to narrow bands. Maybe some gmake/gfiddle as well. Phase, Amplitude and Passband calibration.
- 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)