github-actions[bot]
commented
4 months ago 
| Package | Line Rate | Health |
|---|---|---|
| src.Cache | 72% | ➖ |
| src.DataStream | 44% | ➖ |
| src.FileList | 67% | ➖ |
| src.Frame | 36% | ❌ |
| src.HttpServer | 42% | ➖ |
| src.ImageData | 28% | ❌ |
| src.ImageFitter | 76% | ✔ |
| 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 | 40% | ➖ |
| Summary | 46% (8874 / 19168) | ➖ |
Description
What is implemented or fixed? Mention the linked issue(s), if any. Implement #1236.
How does this PR solve the issue? Give a brief summary. Create a class
Deconvolverwhich converts the fitting results to beam deconvolved images. The convolution method is originally from thecasacode.Are there any companion PRs (frontend, protobuf)? So far no. Question: do we need to create an image for fitting results with beam deconvolution? If so, we may need to modify the frontend and protobuf. We can choose to show both fitting PDF images w and w/o beam deconvolution or there is an option to show only one of them.
Is there anything else that testers should know (e.g. exactly how to reproduce the issue)? When fitting with the image that has beam information, the fitting results with beam deconvolution will also shown like the following snapshot:
Checklist