editconf not updating atom names correctly - Redmine #3107
Archive from user: Dallas Warren
If you select a subset of atoms using editconf, atom names are not correctly propagated into the output coordinate file. It appears that it simply copies directly over from the input file in the same numerical order i.e. source file is C1 C2 C3 C4 …. and the filtered file is expected to be C10 C11 C12 C13 … but it is still labelled as C1 C2 C3 C4…. And it makes no difference what the selected group is, how it is selected, whether from the default groups generated without an index file, or if the groups are from an index file, the atom names are not propagated correctly in any permutation I have tried. All other information such as atom number and coordinates are transferred correctly, it is the atom name that is not updated correctly.
Works correctly with 2016.3
(from redmine: issue id 3107, created on 2019-09-25 by gmxdefault, closed on 2019-09-27)
- Changesets:
- Revision 6c1b268a by Mark Abraham on 2019-09-27T07:08:24Z:
Fix gro file output with index groups
The bug was found with editconf, but the issue was present in writing
of any gro file for which index groups were used (not just index
groups supplied by the user).
Fixes #3107
Change-Id: I3fc586c69066a354b3210d9616125ef666f1ce26
- Revision e91fa76b by Mark Abraham on 2019-09-27T08:50:20Z:
Add tests for editconf file conversion with indexing
The indexed output to gro files illustrates bug #3107
Fixed two memory leaks necessary to let the tests pass
Refs #3107
Change-Id: Ie61430210ac8a804fb86783c8b76c41333b8d3cf
- Revision bc406d20 by Mark Abraham on 2019-09-27T08:51:51Z:
Fix gro file output with index groups
Fixes #3107
Change-Id: I3fc586c69066a354b3210d9616125ef666f1ce26