Closed markccchiang closed 1 year ago
@acdo2002 please validate the fix.
Yes, I have confirmed the issue has been solved with this PR. Now the IRAM old data can be opened with this PR
Package | Line Rate | Health |
---|---|---|
src.Cache | 66% | ➖ |
src.DataStream | 52% | ➖ |
src.FileList | 67% | ➖ |
src.Frame | 50% | ➖ |
src.HttpServer | 42% | ➖ |
src.ImageData | 28% | ❌ |
src.ImageFitter | 83% | ✔ |
src.ImageGenerators | 43% | ➖ |
src.ImageStats | 76% | ✔ |
src.Logger | 44% | ➖ |
src.Main | 54% | ➖ |
src.Region | 18% | ❌ |
src.Session | 29% | ❌ |
src.Table | 52% | ➖ |
src.ThreadingManager | 87% | ✔ |
src.Timer | 85% | ✔ |
src.Util | 49% | ➖ |
Summary | 38% (7087 / 18701) | ❌ |
Description
What is implemented or fixed? Mention the linked issue(s), if any. Closes #1312.
How does this PR solve the issue? Give a brief summary. Add a parser for the angle unit string from IRAM FITS images in the
NormalizeUnit
function.Are there any companion PRs (frontend, protobuf)? No.
Is there anything else that testers should know (e.g. exactly how to reproduce the issue)? The IRAM FITS images can be opened now.
Checklist