You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I think this is the correct way to bring your attention to something?
In opacity.py, when you are reading opctab.dat using the roptab function, the variable mtpts is hardcoded as 39.
This is the typical value used in opctab.dat but this can actually vary and some older versions of the RADYN version that Joel, Adam, and I used have mtpts = 34.
Would it be possible to have this as a keyword, defaulted to 39, that the user can vary?
The text was updated successfully, but these errors were encountered:
Okay, the original was just based on the version of the IDL code I had. At first glance it would be best to see if we can infer the value from the structure of the file somehow. Does one of the variables let us easily figure this out? Otherwise it should be a kwarg, but I would rather have it as idiot-proof as possible if it's something that can vary.
So, I think this is the correct way to bring your attention to something?
In opacity.py, when you are reading opctab.dat using the roptab function, the variable mtpts is hardcoded as 39.
This is the typical value used in opctab.dat but this can actually vary and some older versions of the RADYN version that Joel, Adam, and I used have mtpts = 34.
Would it be possible to have this as a keyword, defaulted to 39, that the user can vary?
The text was updated successfully, but these errors were encountered: