Opened 18 years ago

Closed 18 years ago

#45 closed enhancement (fixed)

Requirement 6.2-5 Multibeam MX mode

Reported by: Chris Phillips Owned by: Malte Marquarding
Priority: normal Milestone: ASAP 2.1
Component: General Version: 2.0
Severity: normal Keywords:
Cc: James.Caswell@…

Description (last modified by Chris Phillips)

Support for MX observing with multibeam is needed. MX mode is observing a point source, cycling through each beam. There are a numbr of ways this could be implemented, consult with Jim Caswell on possible solutions. One possible solution is a multistep process which should work for general MX observations:

  • Form a reference spectra by averaging the data. This could either be done as a meadian average for each beam for all data OR making a mean average of each beam for each making sure to not include spectra including the source (see below for discussion on reference beam).
  • Use this average spectra as a reference in a quotient spectra with original data
  • Optionally data the quotient data and discard beams that were not on source
  • Optionally average the onsource beam data together (ie average data from each beam together)

For this to work the onsource beam need top be known. This is called (in TCS or livedata) the reference beam. Apparently livedata knows which beam this is. Consultation with Mark C. is probably needed to find out how to know this

Change History (3)

comment:1 Changed 18 years ago by Chris Phillips

Description: modified (diff)
Milestone: ASAP2 releaseASAP 2.1

comment:2 Changed 18 years ago by Chris Phillips

Owner: changed from malte.maquarding to Malte Marquarding

comment:3 Changed 18 years ago by Malte Marquarding

Resolution: fixed
Status: newclosed

All features mentioned have been added as

  • scantable.mx_quotient()
  • scantable.average_beam()

where the usual weighting schemes can be used.

Median averaging has also been added

  • average_time(weight='median')
Note: See TracTickets for help on using tickets.