Dump command during rerun which was working in LAMMPS29Oct2020 not working in LAMMPS24Mar2022. Pls help

I successfully used dump command in writing the output to a text file in LAMMPS29Oct2020. When running same in LAMMPS24Mar2022, the output at every N step is missing. Only the output of 0 step is written to the text file and there is no error warning in log file on rerun in LAMMPS24Mar2022. Apart from initial settings and data here is the reamaining script. File upload is not feasible here for new users. Thanks in advance!

group ht type 2 3

pair_coeff 2 2 dpd/gpu 23.4 4.5
pair_coeff 2 3 dpd/gpu 31.6 4.5
pair_coeff 3 3 dpd/gpu 24.2 4.5
pair_coeff 2 4 dpd/gpu 8.8 4.5
pair_coeff 3 4 dpd/gpu 44.3 4.5
pair_coeff 4 4 dpd/gpu 25.0 4.5
pair_coeff 1 2 dpd/gpu 18.8 4.5
pair_coeff 1 3 dpd/gpu 74.3 4.5
pair_coeff 1 4 dpd/gpu 25.0 4.5
pair_coeff 1 1 dpd/gpu 25.0 4.5
pair_coeff 1 1 coul/slater/long
pair_coeff 1 2 coul/slater/long
pair_coeff 2 2 coul/slater/long

bond_coeff 1  	49.0 0.69
bond_coeff 2  	49.0 0.69
angle_coeff 1	   	11.0			  180
angle_coeff 2	  	11.0			  180

compute 12 ht aggregate/atom 0.7
dump 13 ht custom 625 file.txt c_12

thermo 625
thermo_style custom step temp pe etotal press

rerun file.dcd first 0 last 625 every 625 dump x y z wrapped no format molfile dcd /usr/local/lib/vmd/plugins/LINUXAMD64/molfile

Thanks for your report. This is indeed a bug. I know what change in LAMMPS broke this feature, but the solution is non-trivial and will thus take some time to figure out.

As a workaround, you could change the last part of your input as follows:

compute 12 ht aggregate/atom 0.7
dump 13 ht custom 1 file.txt c_12

thermo 1
thermo_style custom step temp pe etotal press

rerun file.dcd first 0 last 0 dump x y z wrapped no format molfile dcd /usr/local/lib/vmd/plugins/LINUXAMD64/molfile
rerun file.dcd first 625 last 625 dump x y z wrapped no format molfile dcd /usr/local/lib/vmd/plugins/LINUXAMD64/molfile

Thank you! Axel

We finally figured it out. The change to make it work is surprisingly simple. It will be fixed with the next patch release.