Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugging 5p vs 7p density maps #308

Open
detoma opened this issue Dec 11, 2024 · 3 comments
Open

Debugging 5p vs 7p density maps #308

detoma opened this issue Dec 11, 2024 · 3 comments
Assignees
Labels
bug fix of a problem in the existing code
Milestone

Comments

@detoma
Copy link
Contributor

detoma commented Dec 11, 2024

Alin reported that when he computes the density for April 9 2024 doing his own fit to compute the peak intensity of the line profile. He reported that using the level2 5p or 3p he gets similar results but not when he uses the 7p.

Below are two density maps he created using the level 2 5p:

Figure 132

and using the 7p for 1074 and 8p for 1079:

Figure 134

Alin thinks there is a problem with the 7p/8p level2 data. What it seems to me is that the 7p/8p density maps is simply masked more. The question is why?

To debug this we are going to do the following:

  • first we are going to reproduce his results
  • second we will use different ratios to identify if the problem is in the 1074 7p, the 1079 8p, or both.

Details on which pairs of images to use for this are given below.

One possible explanation is that something went wrong when processing the 8p which are not common. However the pipeline should not care about it.

Another possible explanation is that when we select the 3 center points to compute the analytical gaussian fit in the 7p or 8p images, we chose by mistake a wavelength that is not the intended one and go to far into the wings. This would results in masking the data too much. To test this, Mike will save the wavelengths used in the analytical gaussian fit.

@detoma detoma added the bug fix of a problem in the existing code label Dec 11, 2024
@detoma
Copy link
Contributor Author

detoma commented Dec 11, 2024

To reproduce Alin's results we will compute the density using these pairs of images:

  • 20240409.180747.ucomp.1074.l2.fts & 20240409.180009.ucomp.1079.l2.fts
  • 20240409.190537.ucomp.1074.l2.fts & 20240409.191146.ucomp.1079.l2.fts
  • 20240409.191848.ucomp.1074.l2.fts & 20240409.192457.ucomp.1079.l2.fts
  • 20240409.193422.ucomp.1074.l2.fts & 20240409.210322.ucomp.1079.l2.fts

To test which image is the cause of the extra masking we will use these pairs of images:

  • 20240409.180747.ucomp.1074.l2.fts & 20240409.191146.ucomp.1079.l2.fts
  • 20240409.190537.ucomp.1074.l2.fts & 20240409.180009.ucomp.1079.l2.fts
  • 20240409.193422.ucomp.1074.l2.fts & 20240409.191146.ucomp.1079.l2.fts
  • 20240409.193422.ucomp.1074.l2.fts & 20240409.180009.ucomp.1079.l2.fts
  • 20240409.180747.ucomp.1074.l2.fts & 20240409.210322.ucomp.1079.l2.fts

@mgalloy mgalloy added this to the UCoMP 1.1 milestone Dec 11, 2024
@mgalloy
Copy link
Member

mgalloy commented Dec 11, 2024

Results are in /export/data1/Data/UCoMP/density-files on the main data server.

@detoma
Copy link
Contributor Author

detoma commented Dec 12, 2024

We cannot reproduce Alin's problem. The density maps for 7p/8p look just the same as the one made with the 5p. They are just a little fuzzier, probably because of a small misalignment between the 1074 and 1079 images. Other than that all combination of images we tried gave essentially the same results.

Screenshot 2024-12-11 at 5 05 51 PM

We do not think there is a problem in the level2 data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix of a problem in the existing code
Projects
None yet
Development

No branches or pull requests

2 participants