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

GNILC dust model d9 configuration #83

Closed
zonca opened this issue Sep 16, 2021 · 8 comments
Closed

GNILC dust model d9 configuration #83

zonca opened this issue Sep 16, 2021 · 8 comments
Assignees

Comments

@zonca
Copy link
Member

zonca commented Sep 16, 2021

I propose to continue the PySM 2 numbering, the first model should be d9.

Templates

The new GNILC dust IQU templates are being implemented in #82
What should we use for spectral index and dust temperature?

Resolution

The model will be natively at 8192, so we want to also have a version of it at 512, so it keeps being usable on laptops.
My proposal is to generate all templates both at 8192 and 512 from the same alms. Then if the user requests a NSIDE=512 or lower, the 512 map is loaded, otherwise the 8192 map.

Model implementation

Use ModifiedBlackBody as other standard dust components:

[d3]
class = "ModifiedBlackBody"
map_I = "pysm_2/dust_t_new.fits"
map_Q = "pysm_2/dust_q_new.fits"
map_U = "pysm_2/dust_u_new.fits"
unit_I = "uK_RJ"
unit_Q = "uK_RJ"
unit_U = "uK_RJ"
map_mbb_index = "pysm_2/beta_mean1p59_std0p3.fits"
map_mbb_temperature = "pysm_2/dust_temp.fits"
unit_mbb_temperature = "K"
freq_ref_I = "545 GHz"
freq_ref_P = "353 GHz"

@giuspugl @seclark @bthorne93 @brandonshensley any feedback?

@zonca zonca self-assigned this Sep 16, 2021
@zonca zonca changed the title GNILC dust models d9 configuration GNILC dust model d9 configuration Sep 16, 2021
@brandonshensley
Copy link
Contributor

We should follow Planck 2018 XI: beta = 1.48 for I and 1.53 for Q and U. If both need to be the same, then probably 1.48. For temperature, T_d = 19.6 K.

@zonca
Copy link
Member Author

zonca commented Sep 17, 2021

so you confirm you don't want to use a map but prefer constant over the sky? I can have 2 coefficients for I and pol.
do we also need other model with variable beta and T_d?

@giuspugl
Copy link
Contributor

giuspugl commented Sep 17, 2021

Having variable spectral parameters are of course one of the challenges for many foreground cleaning methodologies. personally, I am in favor of having another model with spatially variable beta and T_d , e.g. the ones from GNILC maps (see Planck 2016 ).

@zonca
Copy link
Member Author

zonca commented Sep 20, 2021

@giuspugl @brandonshensley instead of having a low-resolution dataset at 512, I think it would be better to have it at 1024. I think with current hardware 1024 is quite manageable even on laptops. Suggestions?

@zonca
Copy link
Member Author

zonca commented Feb 1, 2022

ok, a first implementation of d9 is ready, I was comparing it with d0 and differences are substantial, we probably should address this in paper if not there already. @giuspugl @brandonshensley

image

see notebook (needs branch of #108): https://gist.github.com/ec542934da2da38109d35ce288c0d3c2

@brandonshensley
Copy link
Contributor

I was expecting differences in I at the ~10% level from the color correction and maybe the 50% level at high latitudes where the CIB amplitude is comparable to the dust amplitude. The variations here are much larger, so we'll need to understand what's driving them. Q and U look better behaved?

@zonca
Copy link
Member Author

zonca commented Feb 2, 2022

I wanted to give Colab a try...please let me know if it doesn't work.

so, this is a notebook which installs the right branch of pysm3 and runs on Google Compute Engine, so no setup required - runs in browser, it should be editable (or you can make a copy), so you can add more interesting plots and inspect the maps:

https://colab.research.google.com/drive/1YSsQaEOoAkd5f3Iodx88LOb_7zHMmvuw?usp=sharing

@brandonshensley @seclark @delabru

@zonca
Copy link
Member Author

zonca commented Feb 27, 2022

implemented in #108

@zonca zonca closed this as completed Feb 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants