I’m having trouble with the lammps dump reader. I am reading in the LAMMPS data file first to bring in topology information, and then using the
load trajectory modifier to bring in the trajectory frames. From this simulation I have two dump files written by the same simulation. One is in dump_style atom. The other is with dump_style custom. The dump_style atom trajectory loads in fine. The dump_style custom trajectory keeps throwing errors. I’m using Ovito Pro v3.7.5. It seems to be an issue with persistence of data within Ovito.
Originally, the custom dump file had a few extra columns. I had removed two columns from the custom dump between simulation runs. Whenever I tried to read it with the “load trajectory” modifier, it would throw an error about the number of columns.
To test if it was a problem with the custom dump, I modified the custom dump file to print out the same columns as the atom style. Vimdiff showed that the files were identical. However, Ovito still had trouble loading the custom file. I then simply changed the name of the custom dump file, and then it loaded fine. If I changed the name back to the original filename, it threw the same error. This error persisted even if I closed and reopened Ovito or deleted the pipeline and started from scratch. Is this an issue others have ran into?