Lammps Dump Parser can't do variable columns

[richardjgowers]

Looks like the Lammps Dump Parser can't do extra columns

See: https://groups.google.com/forum/#!topic/mdnalysis-discussion/nhyQX1TBopo

This needs adaptive columns like the data parser has

[amirhs1]

I am new to both Python and Lammps. I realized that there is a Pizza.Py package that handles lamps dumps well but is outdated. I suggest to use this packages to improve MDAnalysis Lammps Dump Parser functionality.
Please also see this https://groups.google.com/d/msg/mdnalysis-discussion/65dSsFhDbhA/iPdRs3psAQAJ

[orbeckst]

According to a user report #2602 (comment) , this got fixed somewhere in 2.0.

@hmacdope did you work on the LAMMPS code recently and did you fix this issue? If so, it should be added to the CHANGELOG and then we can close this one here.

[hmacdope]

@orbeckst I added variable coordinate columns in #3360 The CHANGELOG entry was

LAMMPSDumpReader can now read coordinates in all the different LAMMPS
    coordinate conventions. Both LAMMPSDumpReader and LAMMPSDumpParser are no
    longer hardcoded to a set column layout (Issue #3358, PR #3360).

While you can read coordinates from a DUMP file with any column layout, you cannot read velocities themselves, which is an easy enhancement.

[orbeckst]

I suppose this means we leave this issue open?

[hmacdope]

I guess that depends how you interpret "Lammps Dump Parser can't do variable columns".
We can now read files with any column layout but the data is not necessarily incorporated into the timestep. IMO these things are seperate but I will defer to you @orbeckst :)

[orbeckst]

Looking at the original mailing list message and given that @RuiApostolo confirmed that 2.0 solved their problem I am going to close the issue. If anyone wants to actually read the velocities then they can open a new issue.