I'm using rerun to post process a dump file for generating rdf. But I get "ERROR: Cannot reset timestep with a time-dependent fix defined" but I'm not resetting timestep!
I appreciate any help to resolve this issue. I put required files to regenerate the error and I'm using LAMMPS-ICMS ver. 26Feb2015
I'm using rerun to post process a dump file for generating rdf. But I
get "ERROR: Cannot reset timestep with a time-dependent fix defined" but
I'm not resetting timestep!
you do! implicitly via read_dump which is called through rerun.
the error happens through changes in LAMMPS that were added with the
"chunk" commands.
not sure what a clean solution is here. steve would be the expert for
this. as a workaround, you may try changing the value of time_depend
from 1 to 0 in the fix_ave_time.cpp or similar fixes that expect a
continuous time step progression. or revert to a version before 10 Feb
2015.
Steve,
Sorry Steve I forgot to include the list so I’m resending it again.
But in the test files that I’ve sent the link, I’m using a dump file with snapshots 0 and 100 and I’m using ave/time with nevery=100, nrepeat=1 and nfreq=100 which are consistent with available snapshots, aren’t they?
But I still get the error.
Steve,
Sorry Steve I forgot to include the list so I’m resending it again.
But in the test files that I’ve sent the link, I’m using a dump file with snapshots 0 and 100 and I’m using ave/time with nevery=100, nrepeat=1 and nfreq=100 which are consistent with available snapshots, aren’t they?
But lammps currently doesn’t have a way to tell. So it assumes the worst.
Then, it always will complain about that no matter if the fix ave/time timestep requirement are consistent with dump or not, right? In other words, can fix ave/time be used with rerun command in current version of lammps?
Then, it always will complain about that no matter if the fix ave/time timestep requirement are consistent with dump or not, right? In other words, can
Right.
fix ave/time be used with rerun command in current version of lammps?