nugrid/nupycee

You can find the website of NuPyCEE at

NuPyCEE

Public NuGrid Python Chemical Evolution Environment

This is a code repository containing the simple stellar population code SYGMA (Stellar Yields for Galactic Modeling Applications), the single-zone galaxy code OMEGA (One-zone Model for the Evolution of Galaxies), and the observational data plotting tool STELLAB (Stellar Abundances).

Requirement: The codes are now in Python3 and use the "future" module.

Online usage: These tools can be used directly online via the public WENDI interface.

Userguides: See the Documentation folder.

Acknowledgments:

• SYGMA: Please refer to Ritter et al. (2017).

• OMEGA: Please refer to Côté et al. (2017).

• STELLAB: Please refer to the NuPyCEE code library.

Installation Instructions

• Create the directory where you want to download the codes.
• Go in that directory with a terminal and clone the GitHub repository:
  • git clone https://github.com/NuGrid/NuPyCEE.git
• From the same directory which contains the cloned NuPyCEE directory, you can import the codes in Python mode by typing:
  • from NuPyCEE import omega
  • from NuPyCEE import sygma
  • from NuPyCEE import stellab
• If you want to import the NuPyCEE codes from anywhere else within your work space, you have to update your Python path using a terminal:
  • export PYTHONPATH="your_path_to_before_NuPyCEE:$PYTHONPATH"
  • Example: export PYTHONPATH="benoitcote/gce_code:$PYTHONPATH"
  • Important: Do not forget :$PYTHONPATH at the end, otherwise the python path will be overwritten.
  • Note: All export commands should be put into your bash file. With MAC, it is the .bash_profile file in your home directory. Otherwise, you will need to define the paths each time you open a terminal.

Installation of the Decay Module for Using Radioactive Isotopes

• In the NuPyCEE folder, type the following
  • f2py -c decay_module.f95 -m decay_module
  • Note: Use the f2py version that will be compatible with your Python version.

nupycee's Issues

Changing IMF boundaries - NS merger implementation

Error - part of nsmerger_bdys must be within imf_bdys for imf_bdys=[1,5].
We should consider turning of the neutron star modeling in default mode @becot85

Difference between the same stellar yields in different tables

Hi builders of NuPyCEE,

I am doing some researches using different stellar yields. I find that there is some slight difference between K10 AGB yields from agb_and_massive_stars_nugrid_K10.txt and from other tables using K10 AGB yields. Also, there is some slight difference between NuGrid AGB yields from agb_and_massive_stars_nugrid_MESAonly_fryer12mix.txt and from other tables using NuGrid AGB yields. But they should be the same. You can see it from the figure I made.

It shows the relation between yields fraction scaled by final mass and initial mass. You can see that there are slight difference for AGB yields between the same yields (i.e. K10-1 and K10-2: other tables contain K10 AGB yields and agb_and_massive_stars_nugrid_K10.txt , NuGrid-1 and NuGrid-2: other tables contain NuGrid AGB yields and agb_and_massive_stars_nugrid_MESAonly_fryer12mix.txt )

Could you explain why?

Bugs of ry

When I use the function to read the yields table, it shows that there is no ry. I check the code from NuPyCEE, there is no definition of ry. However, it use it and its function to read the table. Obviously, it cannot work.

travis build failing

travis is suddenly failing, not because of anything we do but because matplotlib in conda is not working properly, I fixed it in NuGridPy by instead installing required python packages with pip

chem_evol.py -> comma missing between two elements in an array

chem_evol.py, line 1563, definition of "self.elem_list_periodic_table". There is a comma missing between elements "Rn" "Fr", thus causing those two elements to combine together into one "RnFr". This cases self.elem_list_periodic_table to incorrectly have corresponding element number after Rn (86th element). Adding a comma solves the issue.

Extra sources flexibility

I think a good modification to our codes would be to add a mass range associated with the extra_source_table. Furthermore, it would be great to convert these parameters into arrays where the index of these array refers to one specific extra source. Here is an example with 2 extra sources:

extra_mass_range = [ [1,8], [8,12] ]
extra_source_table = ['s-process table.txt', 'r-process table.txt']

That would allow to control in which stars the extra table is applied, and it would prevent from adding more and more parameters for additional extra sources. In chem_evol.py, we could simply loop over the length of the extra_mass_range array.

I think we could do the same for delayed sources that need a delay time (e.g., neutron star mergers, black hole neutron star mergers, iRAWDs, and other things we want to try). We would "simply" need to include a delay-time distribution array as well.

Transition mass and input yield grid

When the transitionmass variable is set to one of the input yield grid masses then the initial mass range intervals for the yields are not set properly. Visible with iolevel=1. To solve this need to decide how the initial mass range intervals are split up in such a case.

WENDI interface-This site can’t be reached

https://nugrid.github.ioprojects/wendi
nugrid.github.ioprojects’s server IP address could not be found.

AttributeError: 'sygma' object has no attribute 'stellar_param_attrs'

hi devs,
i try to run NuPyCEE sygma but i get an error when i put stellar_param_on=True.
it is working well when I remove stellar_param_on=True.