[mesa-users] mesa problems with the newly added OP opacity tables for a05 and a09 -- the old OP gs98 tables are fine

[Bill Paxton]

On Oct 15, 2013, at 10:22 AM, Ehsan Moravveji wrote:

> Maybe there has been a recent silent change in the OP server?

That looks likely.  The new OP tables that are causing problems for us have a logT upper limit of 8.0 -- the same logT limit as the OP monochromatic tables.  However the old OP tables for gs98 have values up to logT = 8.7 just like the standard OPAL data.   So my guess is that the new OP tables are being created using the monochromatic opacity tables while the old OP gs98 tables were created using something different, something that doesn't tickle the bug in the OPAL software that we've hit.  Nothing wrong with the new OP tables of course -- just an unexpected problem when using them with the OPAL software.  So we need to find a way around that.

Thanks to Haili Hu, we now have OP monochromatic opacities in mesa/kap.  I'm now thinking of making a new OP-to-mesa preprocessor that would just call our OP_mono routines to create the mesa OP kap tables directly -- at any resolution we decide to use rather than limiting ourselves to the old OPAL format that we get from the OP website.    

Or perhaps someone knows how to get higher res tables from the OP website?  I'd like to get at least double the OPAL standard in both logT and logR in order to reduce interpolation effects.

Or perhaps by tomorrow I'll have thought of something else that I like even more! ;D

-Bill






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20131015/9dcc7da0/attachment.html>