Commit f49d437
committed
fix(nupdown): only set two_fermi when nupdown is non-zero
When nupdown=0.0 is explicitly set in INPUT, it should behave the same
as not setting nupdown at all. Previously, reading any nupdown value
would unconditionally set two_fermi=true, causing different code paths
even when nupdown=0.0.
Now two_fermi is only set to true when nupdown != 0.0, making nupdown=0
equivalent to not specifying the parameter.1 parent b5ff54c commit f49d437
1 file changed
Lines changed: 1 addition & 1 deletion
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
297 | 297 | | |
298 | 298 | | |
299 | 299 | | |
300 | | - | |
| 300 | + | |
301 | 301 | | |
302 | 302 | | |
303 | 303 | | |
| |||
0 commit comments