-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add ElectronicEigenvalues and ElectronicBandStructure properties #63
Add ElectronicEigenvalues and ElectronicBandStructure properties #63
Conversation
0f4b8a5
to
51f4b49
Compare
Pull Request Test Coverage Report for Build 9347862591Details
💛 - Coveralls |
73f47af
to
f6c74aa
Compare
9e4ce18
to
16171c5
Compare
Added KLinePath and KMesh variables with refs to the NumericalSettings sections
…completely crazy....... I had to squash all the shit into one single commit. It was that, or just killing myself.
16171c5
to
90edd52
Compare
Deleted unused comment-warning in variables.py
… from conftest Fix bulk type in resolve_reciprocal_lattice_vectors
…32 (it needs int types)
Looks all fine to me except for some minor improvements. Do I check also the tests? |
Thanks! I think the tests are just there to help understand the code, so up to you. Coverage is 99% (whatever that means 😅), so I guess I did a good job. |
Fixed test_band_structure Fixed methods in ElectronicEigenvalues Added .vscode/settings.json to gitignore
f8fdb29
to
976adf5
Compare
…e_homo_lumo_eigenvalues
Ok, this pr is ready. I added also a validator for comparing a quantity with respect to Thanks for the review @ladinesa @ndaelman-hu ! 🥳 |
This pr contains the definition for the former
ElectronicBandStructure
with the new schema (PhysicalProperties
andVariables
), as well as the new propertyElectronicEigenvalues
. During development, I also wanted to defineFermiSurface
, but this makes more sense in a separate pr (#78).Some important changes with respect to the old schema and normalization:
value_contributions
whose objective is to group all the former stuff that was inBandEnergies
asvalue_<name-of-the-contribution>
KLinePath(Variables).points
as a flat list of pointsadd_band_gap
normalization. Now, we haveextract_band_gap
and, mainly,resolve_homo_lumo_eigenvalues
to handle this.get_special_points
function is re-defined undernumerical_settings.py:KMesh
. This was a very buggy function, specially when the path is not defined for points related by symmetry (e.g.,'X'
is both[0.5, 0, 0]
and[-0.5, 0, 0]
. Now we aim people to define the strings related with the high symmetry points OR manually define the path.One question is whether
reciprocal_cell
will be still here in this schema or we can resolve it in another way. This quantity is only interesting for the front end.