scope of timestep keyword in input script

I need just a small clarification:

If I declare timestep keyword once in input file and run multiple runs, time step will remain same for all runs right?

i.e if input file is like:

units real

timestep 0.1

thermo 1

run 1000

run 1000

run 1000

then all runs are 100 ps of physical time (1000 * 0.1 ps)

I need just a small clarification:

If I declare timestep keyword once in input file and run multiple runs,
time step will remain same for all runs right?

depends. it will remain the same only if you do not use fix dt/reset or
clear anywhere in between.

​axel.​

More generally, all settings in an input script persist from

the point they are defined until you change them.

The clear and dt/reset commands Axel mentioned

can change the timestep.

Steve

Ok. Thanks for the clarification.

P.S. jsut one last thing. I just wanted to know general lammps mailing list etiquettes, I mean are mails like “thanks” are discouraged? they add more of a spam, and when browsing old mails its an unnecessary distraction on the other hand it marks completion of a conversation. So what is preferred policy here?

Ok. Thanks for the clarification.

P.S. jsut one last thing. I just wanted to know general lammps mailing
list etiquettes, I mean are mails like "thanks" are discouraged? they add
more of a spam, and when browsing old mails its an unnecessary distraction
on the other hand it marks completion of a conversation. So what is
preferred policy here?

​there is no policy for that. other things are much more distracting, e.g.
people providing too vague descriptions of their problems or posting (often
irrelevant) minimal snippets of their input when asking about problems or
huge and convoluted input decks.​ or people not stating version of LAMMPS
and platform they run or and so on. or people replying to and quoting an
entire digest e-mail to ask a one-line question. :wink:

axel.

i should add, that it is usually helpful to people searching the mailing is archives, if somebody confirms that a problem or question is (completely?) resolved and - if applicable - to briefly describe which solution was used.

when just asking for a clarification or confirmation, there is probably less value to that.