Draft
Conversation
Signed-off-by: Nick Papior <nickpapior@gmail.com>
Contributor
|
I want to push this forward to use it for QM/MM geometries, should I start a new branch and create a separate PR? |
Contributor
|
I haven't been looking much into this (sorry), so from my side you can, of course, proceed as you see fit. I'm still very much interested in this development in sisl! |
Owner
Author
Yes, please do, branch this off would be ideal imho. However, I think it would be very beneficial to discuss here, or reiterate the decisions made in #449. Eg how sparse matrices etc should handle things. |
Owner
Author
|
Or perhaps better, finish the discussions in #449, then let implementation details be discussed in the pr! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@tfrederiksen @pfebrer
this is a first stab at 449. I am starting to grow on the idea.
However, as you can see in this PR, there are many places in the code base where it assumes that there exists some orbitals on atoms.
Whether or not these should be defaulted to be present or not is something that needs to be discussed.
However, it seems that one should be explicit on defining orbitals if one wishes to use them.
Many places the code simply fails because it now requires some kind of explicitness.
But I would agree that this could be useful. If anybody cares to expand/fix/add tests for the remaining details, feel free :)
isort .andblack .[24.2.0] at top-leveldocs/CHANGELOG.md