|From:||Axel Kohlmeyer <akohlmey@...24...>|
|Date:||Mon, 28 Aug 2017 07:47:05 -0400|
Axel, thanks for your response. The tip does not move with constant velocity, it is connected to a single atom using a spring and the single atom moves with constant speed. What I am trying to do is to reach a lower scanning velocity (velocity of the single atom mentioned above) of the tip by parallelizing the time domain using prd simulation (something similar to this paper: https://journals.aps.org/prl/
As far as I know, similar setups with fix rigid worked fine in prd simulations with the LAMMPS version of 2012-2013 and I wanted to check if someone else faces some issues in using both packages concurrently in the recent version of the LAMMPS.
MohammadOn Sat, Aug 26, 2017 at 8:36 AM, Axel Kohlmeyer <akohlmey@...24...> wrote:On Fri, Aug 25, 2017 at 6:43 PM, Mohammad Rasool Vazirisereshk <mvazirisereshk@...24...> wrote:
I am using the latest stable version of LAMMPS (11 Aug 2017) and have a question about the use of REPLICA and rigid packages, concurrently at a simulation.
The problem I am working on is simplified as follows: I have a tip moving laterally on a substrate. The top part of the tip is rigid (using fix rigid) and coupled to an atom moving laterally with constant speed (using fix move). This setup works perfectly in regular MD. However, when I use prd command the system shows strange behavior (the tip sometimes either penetrates in the substrate or flies over simulation box). Below you can find a part of my input file:i would say this is because you are trying to do something that makes no sense.the purpose of PRD is to advance the time line faster by running decorrelated systems in parallel to increase the probability of a rare event to happen within a limited amount of wall time. however, your tip moving at constant speed is defeating that purpose. you don't know in advance, when the rare event happens, so you don't know how far to offset the position of the tip in each replica and the PRD code has no idea that you would need to keep your tip static while decorrelating the replicas, not to mention the unphysical "kick" to your system, when you would let the tip move again.if you want to get improved statistical sampling, you don't need PRD, but can just run the same type of regular MD input concurrently with the -partition flag while considering two important points:1) each replica should use different random number seeds to (re-initialize) velocities2) each replica should run without the tip moving for a sufficiently long time to make sure they are sufficiently decorrelated. using a langevin thermostat (again with different random seeds for each run)of course, that can be done even simpler by just generating multiple input files and running them independently.axel.# 1 fs time steptimestep 0.001variable t equal 300#thermostatfix 1 lo-mid nvt temp 300.000000 300.000000 1fix 90 hi-mid nvt temp 300.000000 300.000000 1fix 91 free nvefix 2 lo-fixed setforce 0.0 0.0 0.0fix 10 hi-fixed addforce 0.0 0.0 -0.003613#rigid/springfix 3 hi-fixed rigid single torque 1 off off offfix 4 hi-fixed spring couple virtual 4.0 0.0 NULL NULL 0.0#virtual atomfix 7 virtual setforce 0.0 0.0 0.0fix 8 virtual move linear 0.01 0.0 0.0 units boxI guess the problem is due to having fix rigid command in the prd simulation since I ran the prd simulation for a similar setup, which did not have fix rigid, without any problem.I also tried to use fix aveforce (0 0 0) instead of fix rigid in my prd simulation but it did not work out.Is there anyone else who faced irregularities with fix rigid in prd simulation? Any idea or comment will be appreciated.Best,Mohammad
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
lammps-users mailing list