-
Notifications
You must be signed in to change notification settings - Fork 868
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
Added threshold_ordering parameter to CollinearMagneticStructureAnalyzer in addition to PR #3574 #3577
Added threshold_ordering parameter to CollinearMagneticStructureAnalyzer in addition to PR #3574 #3577
Conversation
…ccount for floating point imprecision, added test for that.
…lose in favor abs(tot_mag) > 1e-8
…linearMagneticStructureAnalyzer.
what would change based on the threshold? setting could you add a test case that passes a custom |
… on threshold_ordering parameter.
Yes - if, for example, a database is scanned for structures with zero magnetization based on |
I would not change the data that is stored on the object. I think this would be unexpected behavior. If someone needs this, they will implement it themself |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @kaueltzen! 👍
Summary
A parameter threshold_ordering was added to CollinearMagneticStructureAnalyzer below which the total magnetization is treated as zero when defining the magnetic ordering.
@JaGeo @janosh
self.total_magmoms = sum(magmoms)
andself.magnetization = sum(magmoms) / structure.volume
are defined before processing the input magmoms. They could also be affected by the error described in PR #3574 - do you think it's a good idea to add a threshold here as well?