Emission lines from post-AGB UV radiation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by running the supplied Python script and inspect the get_spectrum call together with the pAGB, nebemlineinspec, and add_neb_emission parameters. Compare the resulting spectra for the three pAGB values; the issue is complete when the cause of the zero emission-line fluxes is identified and the expected behavior or required configuration is documented.
Written by the indexing model from the issue text.
Description
Hi,
I am running some models to test the UV contribution from the post-AGB stars to the emission lines of a galaxy. To test this, I use SSPs at the age of 3Gyrs (also tried for 0.1Gyrs and 5Gyrs). Models have no attenuation. The SSPs have solar metallicity. I test 3 separate instances which all have the same parameter values, except that each time I change the pAGB fraction to be 0, 0.5 and 1. I can see that I get ionizing radiation by turning on post-AGB stars.
The problem is that I get emission line fluxes that are all 0. Shouldn't this UV give emission lines for pAGB = 0.5 and pAGB = 1 ? Am I missing something obvious here?
From this tests I get the following plot:
The srcipt I run is the following:
import fsps
import matplotlib.pyplot as plt
import numpy as np
sp = fsps.StellarPopulation(zcontinuous=1)
sp.params['sfh'] = 0
sp.params['dust1'] = 0.0
sp.params['dust2'] = 0.0
sp.params['add_neb_emission'] = True
sp.params['add_dust_emission'] = True
sp.params['nebemlineinspec'] = True
sp.params['logzsol'] = 0.0
sp.params['gas_logz'] = sp.params['logzsol']
t = 3.0
for p in [0.0,0.5,1.0]:
sp.params['pagb'] = p
wave, flux = sp.get_spectrum(tage=t,peraa = True)
plt.loglog(wave, flux,label='pAGB = ' + str(p))
plt.xlabel('Wavelength (Angstroms)')
plt.ylim([1e-7, 1e-2])
plt.xlim([1e2, 1e5])
plt.ylabel('Flux')
plt.title('tage = ' + str(t)+'Gyr')
plt.legend(fontsize=14)
plt.show()
Best,
Babis
- Dominant language
- Python
- Stars
- 76
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
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.
More from dfm/python-fsps
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dfm/python-fsps#121 ·
-
Performance question Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
dfm/python-fsps#350 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dfm/python-fsps#229 · 8 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
dfm/python-fsps#199 · 4 comments ·
-
dfm/python-fsps#197 · 2 comments · 1 assignee ·
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·