-
Notifications
You must be signed in to change notification settings - Fork 16
Modify ion.n_levels #426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Modify ion.n_levels #426
Conversation
…evels are described in the database than are populated in the model
|
I find this logic a bit confusing. Is it not sufficient to just take the min between |
|
Two additional requests:
|
|
I took the max between n_levels_scups and n_levels_wgfa assuming that if at least one file refered to an energy level, it should be included in the model. This only really matters for Ar 18, where if you took the minimum, level 25 would be excluded. Maybe it should be ... I find two cases (updated from original post) where n_levels_elvlc is > n_levels_scups and n_levels_wgfa: N 4 Ar 6 I find one case where n_levels_scups > n_levels_wgfa: And a few cases where there is now scups or wgfa file: Cr 24 Zn 30 |
|
The cases where there are no scups or wgfa files are fine. In those cases, there is effectively no model and so you can't compute a contribution function anyway. |
Adding logic to ion.n_levels to account for cases where more energy levels are described in the ion.elvlc than than are referred to in ion.wgfa or ion.scups. As of now, this only occurs for N 4.