Opened 13 years ago
Closed 13 years ago
#231 closed defect (fixed)
Spurious results from scans.opacity()
| Reported by: | Owned by: | Malte Marquarding | |
|---|---|---|---|
| Priority: | normal | Milestone: | ASAP 3.0 |
| Component: | General | Version: | |
| Severity: | major | Keywords: | opacity correction |
| Cc: |
Description
I've been performing opacity corrections on my spectra using scans.opacity(tau), with tau=0.07, but the output scantable has incorrect T values. An example scantable is attached, recorded at an elevation of about 25 degrees. The opacity correction factor should be about 1.19, but when I use scans.opacity(tau), IF1 gets multiplied by about a factor of about 16!
Note however, the scans.opacity() command appears to work correctly when operating on a single IF (using selector.set_ifs()).
Attachments (1)
Change History (6)
Changed 13 years ago by
| Attachment: | test_scantable.tgz added |
|---|
comment:1 Changed 13 years ago by
| Owner: | changed from Malte Marquarding to Malte Marquarding |
|---|---|
| Status: | new → assigned |
comment:2 Changed 13 years ago by
A quick question. Did you build asap from source or know how to do it? I think I know what is wrong and you could patch it.
comment:3 Changed 13 years ago by
Hi,
Thanks for your reply. My ASAP installation was performed by sys admin here, who I believe built it from source. I have been able to work around the problem by calculating my own opacity corrections and using the scale() command, so I probably won't need to do any further opacity corrections with my current Mopra data.
Cheers,
Martin
comment:5 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Mopra scantable