vtk files are out of order in Paraview

Submitted by AJ.Spin on Mon, 01/28/2019 - 17:16

This just started happening to my simulation recently and I cannot figure why. I will run a .vtk file in Paraview and it is clear the time frames are out of order. When I expand, the .vtk file in the menu it is evident that the numbering sequence is wrong (lpp_1). At first I thought I must be getting sloppy and doing one of the following things even though I know better : running additional simulations with the same name in a populated folder or using * too liberally when I use the lpp command, like if I type lpp t* but I have files named two and twelve. I confirmed that these things are not happening.
When I look in the folder via the terminal, it sort of sticks out that the order goes by the first digit so file names such as 29115 would be next to file 291150 (lpp_2). If I sort the dump files via time modified in the desktop GUI, everything looks normal (lpp_3). The files were created in order, and there are file names that just happen to have one digit less. The number sequence does not match for the .vtk and boundary box (lpp_4). The files seem to be created in batches at the exact same second so I cannot actually tell what comes first. I do not know if the milliseconds data is hidden or is just dropped. There are also cases where non-sequential boundary boxes are next to each other. I do not understand what creates the vtk number because it does not seem to correspond with the number or data of the dump files.
I have no clue if this is occurring because of liggghts, lpp, or paraview. As far as I understand, my commands for creating the dump files in liggghts is pretty standard (lpp_5). I do not what it is but my hunch is the issue is not my liggghts code.
There is something I am missing conceptually because this does not make sense.