BUG: When reading a legacy NeighborList, the incorrect group was passed to the reader #1464
Conversation
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
imikejackson
force-pushed
the
topic/legacy_neighbor_list_reader_bug
branch
from
f28e572 to
092a8c8
Compare
imikejackson
force-pushed
the
topic/legacy_neighbor_list_reader_bug
branch
from
092a8c8 to
088c2c4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reading a 6.5.171 .dream3d file with neighbor lists would give warnings to the console about not being able to read the data sets with the number of neighbors. This will fix that. But I am wondering how reading the neighborlist actually has been working.