Standards and practices

CASA version used for reduction: 4.5.3

Reduction conventions Reference antenna(e) for self-cal: Use the same antenna(e) as NRAO

Style conventions Fields and antennae will be referred to by name rather than by number (e.g, Field = "HD_163296" and not Field = 3) to minimize confusion for people looking at the scripts.

Naming conventions Currently, all the reduction scripts are named something like FIELDNAME.py, and contain the reduction for short baseline data (SB = 'short baseline' and LB = 'Long baseline'). However, since the long baseline data may be undergoing independent rounds of imaging, we will copy over the script and start a new script tagged with our initials, like Elias_27_jh.py. When we decide on a final calibration method, it will be copied back over into Elias_27.py.

Git workflow Make sure to pull from the repository every time you start editing the reduction scripts

git pull

Suppose I'm working on the HD 163296 scripts. Once I'm done for the day, I will save the script as HD_163296_jh.py

Type

git status

If I'm adding HD_163296_jh.py for the first time, I will see it listed under untracked files. If I'm modifying it, I will see it listed as a modified file. In either case, I need to type

git add HD_163296_jh.py

(If you've modified or created other files in the repository, you will also see them listed when you type git status. You can add them as well if you'd like).

Then type a useful commit message, e.g.

git commit -m "added calibration steps for HD 163296 long baseline data"

Finally, push it to the remote repository with

git push

Commit early, commit often! Even if you're not done reducing the data.

Colormaps: To be determined when the long baseline data come in. Useful resources to consider in the meantime - http://www.stsci.edu/~dcoe/trilogy/Intro.html http://iopscience.iop.org/article/10.1086/345794/fulltext/