Closed pford closed 2 months ago
@pford this looks good to be a formal PR.
Package | Line Rate | Health |
---|---|---|
src.Cache | 72% | ➖ |
src.DataStream | 44% | ➖ |
src.FileList | 67% | ➖ |
src.Frame | 36% | ❌ |
src.HttpServer | 42% | ➖ |
src.ImageData | 28% | ❌ |
src.ImageFitter | 83% | ✔ |
src.ImageGenerators | 43% | ➖ |
src.ImageStats | 75% | ✔ |
src.Logger | 37% | ❌ |
src.Main | 52% | ➖ |
src.Region | 69% | ➖ |
src.Session | 4% | ❌ |
src.Table | 52% | ➖ |
src.ThreadingManager | 67% | ➖ |
src.Timer | 85% | ✔ |
src.Util | 38% | ❌ |
Summary | 46% (8641 / 18973) | ➖ |
Description
What is implemented or fixed? Mention the linked issue(s), if any. Closes #1385
How does this PR solve the issue? Give a brief summary. Set MomentRequest rest frequency in MomentGenerator image coordinate system, then restore image rest freq after moment images created.
Are there any companion PRs (frontend, protobuf)? CARTAvis/carta-frontend#2404 + CARTAvis/carta-protobuf#98
Is there anything else that testers should know (e.g. exactly how to reproduce the issue)? Rest frequency will be added to Moment dialog in frontend.
Checklist