-
Notifications
You must be signed in to change notification settings - Fork 26
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
Multipole order mismatch in get_coupling_matrix() routine #44
Comments
Hi @Sylk1-9, can you please post a code snippet or a script that reproduces this? |
Hi @Sylk1-9 See the attached script (modified from yours), which shows how to interpret the MCM returned by NaMaster. As you can see from the plot below, there are definitely differences between purified and unpurified!
|
Let me know if that solved the issue! |
Yes indeed, thank you for your response. Mll_yp_rc = np.zeros_like(Mll_yp)
for tag1 in [0, 1, 2, 3]:
for tag2 in [0, 1, 2, 3]:
for l1 in np.arange(3*nside_large):
for l2 in np.arange(3*nside_large):
Mll_yp_rc[tag1*(3*nside_large-1)+l1, tag2*(3*nside_large-1)+l2] = Mll_yp[4*l1 + tag1, 4*l2 + tag2]
matshow(log10(abs(Mll_yp_rc))) I get So the four block-rows/column entries are EE, EB, BE, and BB ? As defined in your paper. |
Yes, that's correct. It follows the same way in which power spectra are stored in NaMaster (for each ell, all the different power spectrum combinations together). I'll close this then, but feel free to reopen if you have more questions. |
Hello,
When calling the new routine get_coupling_matrix(), on the B-modes purification test scrip for example, I get a mixing matrix with rows and column order that are mismatched.
I couldn't recover the initial EE-EE, EE-BB, etc.. blocks of the coupling matrix.
In addition, I compared a matrix from a workspace whose the polarisation purification option is on, with a matrix for which the purification option is off (purifyE/B = True/False). Both arrays are the same. I am surprised since I would have expected that the mixing kernel block EE-BB would be different.
Thanks,
Sylvain
The text was updated successfully, but these errors were encountered: