birth cloud dust attenuation applied beyond dust_tesc
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
I ran into the following issue regarding the birth cloud dust attenuation:
I'm running StellarPopulation with dust_tesc=7.0, which I think means that only stellar populations with age < 1e7 should be affected by birth cloud dust attenuation. However, I find that when birth cloud dust attenuation is applied to stellar populations with age 1.1e7.
Below is an illustration. I generate spectra for a stellar population with tage=1.1e7. In one of the spectra, I set dust1 = 0.9; in the other I set dust1=0. Since tage > dust_tesc, I didn't expect there to be a difference between the two spectra but the figure below shows a significant difference.
I find that for dust_tesc=7.0, birth cloud dust attenuation is applied up to tage=1.12e7yr
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the StellarPopulation handling of dust_tesc and dust1, then reproduce the reported case with tage=1.1e7 and dust_tesc=7.0 while comparing dust1=0.9 against dust1=0. Done means birth cloud attenuation no longer changes spectra for ages beyond the configured threshold, with coverage for the reported boundary behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran, python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100