Opened 13 years ago
Closed 13 years ago
#268 closed defect (fixed)
new_average fails for Mopra broadband data
Reported by: | Malte Marquarding | Owned by: | Kana Sugimoto |
---|---|---|---|
Priority: | normal | Milestone: | Unified development |
Component: | General | Version: | |
Severity: | normal | Keywords: | |
Cc: | takeshi.nakazato@… |
Description
Hi Kana, has there been development of a method in ASAP to merge adjacent IFs into a single IF in your group? I had a user request here and wasn't sure if you have been working on this? Cheers, Malte
Attachments (4)
Change History (9)
by , 13 years ago
Attachment: | broadband.asap.tar.bz2 added |
---|
comment:3 by , 13 years ago
Status: | new → assigned |
---|
I found that new_average does not run properly in case spectra has negative increment in FREQUENCIES table. I started fixing the bugs. It may take a few more days to fix them.
Malte, is the time scale fine for your release?
comment:5 by , 13 years ago
Cc: | added |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
I believe I've fixed Scantable::regridChannel, Scantable::regridSpecChannel and STMath::new_average so that asapmath.new_average works for data which contains IFs both with positive and negative spectral increments. Please find the attached figures of plots of spectra before and after new_average(compel=T).
I've tested new_average by checking numerical values of an averaged spectrum using a simple artifical input spectrum. The result had a good agreement with the analitical solution.
However, there is still a known issue of asapmath.new_average. The method raises array comformance error when the input scantable has multi-channel Tsys columns. Takeshi agreed with taking care of it.
Summary of commits:
Commit dates: 2012/04/12, 13, 16
Revisions: r2462-2463,and r2466-2467
Modified Codes: Scantable.cpp, STMath.cpp
Broadband 4 IF data