Opened 15 years ago

Last modified 15 years ago

#92 new defect

atlod - document correct 'default' options for CABB data

Reported by: VincentMcIntyre Owned by: JamieStevens
Priority: trivial Milestone:
Component: MIRIAD - CABB branch Version:
Keywords: dcoumentation Cc:
Estimated Number of Hours: 1 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0

Description 

From: "Emil.Lenc@csiro.au" <Emil.Lenc@csiro.au>
Date: Fri, 11 Sep 2009 16:14:12 +1000

I had a question from Sarah Maddison with regards to options for CABB data. It
seems that she has been using the options "birdie, reweight, xycorr" in ATLOD
on CABB data (I think these were left in from an old processing script she
had). From what I understand these options should not be used in ATLOD for CABB
data - do you know if they are "silently ignored" by ATLOD if CABB data is
detected? If not, can they have a detrimental effect on the data?

We need to make it clearer in the documentation of ATLOD and in the MIRIAD user's guide what options are sensible.

Change History (2)

comment:1 Changed 15 years ago by VincentMcIntyre

Estimated Number of Hours: 0 → 1

comment:2 Changed 15 years ago by MarkWieringa

Owner: changed from MarkWieringa to JamieStevens

atlod changes to code and docs have been done. miriad manual to do.

Note: See TracTickets for help on using tickets.