[Mesa-users] MESA-Nu-Interactions

[Rob Farmer]

Hi,

Interesting work, i echo franks statement that you should try not to modify
the private/ routines. Given your run_star_extras already computes a rate
and an energy for each reaction, you might find it easier to not modify
net_get. But instead after calling net_get (in your other_net) to add your
rates to the results of net_get. You'll want to look at the arrays eps_nuc,
d_eps_nuc_dRho, d_eps_nuc_dT,d_eps_nuc_dx, dxdt, d_dxdt_dRho, d_dxdt_dT,
d_dxdt_dx which describe the energy/composition change due to nuclear
burning, and the derivatives of the changes.

It can take a bit of mental processing to get the right units and the right
indexes into the arrays to insert values, but if you can express your
results in a d(proton)/dt and d(neutron)/dt terms you can add your reaction
results to the values mesa has calculated for the other rates and thus not
have to modify the private/ routines.

Rob


On Wed, 29 Aug 2018 at 08:16, Francis Timmes via Mesa-users <
mesa-users at lists.mesastar.org> wrote:

> hi liam,
>
> i'm impressed.
>
> this is meaty piece of work that adds new capability and was completed on
> a fairly short timescale.
> by modifying ~20 source code files i think you've gone well beyond "the
> basics".
>
> one danger though of modifying /private source code files is that your
> edits will
> probably not function without modification when a new version of mesa is
> released.
>
> i'm curious how much of this new capability could be encapsulated within a
> run_star_extras using only the /public interfaces and a few other_* hooks.
> the advantage for MESA-Nu-Interactions is that such a run_star_extras is
> more likely to continue functioning when a new version of mesa is released.
>
> so my challenge to you is to create a MESA-Nu-Interactions 2.0 using only
> the /public interfaces and other_* hooks. if you run into an issue where
> something doesn't seem possible without modifying a /private routine,
> please let us know by posting a message to mesa-users at lists.mesastar.org .
>
> in the interim, i've added a link to your MESA-Nu-Interactions repo on
> mesastar.org in the add-ons section. and again, congratulations on an
> impressive body of work.
>
> fxt
>
>
>
>
>
>
> > On Aug 28, 2018, at 3:03 PM, Liam Kroll <liam.kroll at gmail.com> wrote:
> >
> > Hello MESA developers,
> > My name is Liam Kroll. I am an undergraduate student at McMaster
> University's Department of Physics and Astronomy. Through a summer
> internship with my department I have learned how to use the basics of MESA.
> Previously I had emailed the MESA-userslist about neutrino interactions and
> received some very helpful information. Since then I have been spending
> some time trying to develop an addition to MESA (r-10398) star which
> simulates the charged current neutrino interactions on free nucleons in
> core collapse supernovae. At this time the addition is functional but
> relies on user supplied best guesses for the neutrino luminosities and
> energies. Below is a link to the GitHub repository where all the files and
> accompanying information can be found. I wanted to make you folks aware of
> the work in case you were interested. As I am quite new to MESA (and
> stellar astrophysics simulations in general) I would very much appreciate
> any feedback or suggestions on how to improve the work I!
>   have don
>  e so far. I think all the necessary information is included in the
> repository, but if I missed anything or you have questions, concerns, etc.,
> I'd be happy to address them. I obtained your emails from the MESA
> marketplace, but if you know of anyone else this addition would interest,
> feel free to forward this message to them.
> > Thank you for all you do,
> > Liam
> >
> > https://github.com/liam-kroll/MESA-Nu-Interactions
>
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20180829/f69fbd92/attachment.html>