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

Add Conroy et al. (2010) attenuation model #28

Open
karllark opened this issue May 26, 2018 · 6 comments
Open

Add Conroy et al. (2010) attenuation model #28

karllark opened this issue May 26, 2018 · 6 comments
Labels
enhancement New feature or request

Comments

@karllark
Copy link
Owner

There's a generalization of the CCM89 dust extinction model in the Appendix of Conroy+10 that varies the bump strength to allow for modeling attenuation in galaxies. A possible addition for this package. Originally proposed for the dust_extinction package, but more appropriate here.

karllark/dust_extinction#53

@dcorre
Copy link
Contributor

dcorre commented May 26, 2018

I don't think it should be in the dust_attenuation package but rather in the dust_extinction package.
Yes, it is used for galaxies but it is based on an extinction law (ccm89)... If people want to use extinction recipes for galaxies, this is their choice they need to justify in their papers. We should clearly make a distinction between extinction and attenuation processes to avoid this usage. If I'm not mistaken that is one of the reason why you decided to create 2 separate packages.
However, I don't know whether this modified ccm89 brings something more than the more flexible FM recipes where you could only let the bump parameters vary and set all other parameters to the averaged MW values?

@karllark
Copy link
Owner Author

You make good points. I have not looked at this work in detail yet. As it was proposed for attenuation in galaxies, I figured it was best for this package. But we should check.

I also have your concern that the FM90 and P92 already provide ways to vary the bump strength. As does G16. So, homework is needed clearly.

@dcorre
Copy link
Contributor

dcorre commented May 26, 2018

From their work:
"We also consider attenuation curves whose functional form is equivalent
to the average extinction curve in the MW (Cardelli et al.
1989). As mentioned in Section 1, attenuation and extinction
are different concepts, but in simple geometries they can be
roughly equivalent (modulo wavelength dependence of the dust
albedo)."

I believe it strengthens the motivations which lead to the creation of this package ;)

Charlie Conroy used the Noll+09 formalism in a more recent paper 2013 with Mariska Kriek. So I don't know whether they are still using the modified ccm89 for galaxies.

@karllark
Copy link
Owner Author

Hum... The clearly argues for adding the Noll model before this one. I can contact Charlie and ask him what he thinks.

@dcorre
Copy link
Contributor

dcorre commented May 27, 2018

Indeed, It will be interesting to have his point of view.
The results in the 2013 paper clearly show that the attenuation law is not universal and thus a simple fixed dust law as the Calzetti law or a functional form equivalent to the average MW introduce biases in the estimation of the physical parameters of the galaxy (their Figure 3). In their conclusion they mention that "The MW and Calzetti law provide poor fits at UV wavelengths for nearly all SED types." and so they used the Noll+09 recipe for their main analysis.

One could use a modified version of the ccm89 recipe to account for this non-universality but as it is based on measurements of individual stars it should be implemented in the dust_extinction package in my opinion.

It makes me think that the section "How to choose a model" in the documentation, should address the non-universality of the attenuation law. For instance, for galaxy SED fitting, whenever the spectral coverage allows it (especially rest-frame UV data), the user should use a model with at least one free parameter allowing different UV slopes.

@karllark
Copy link
Owner Author

Really sounds like Noll is the way to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants