[lammps-users] Melting of alloy using eam/alloy

Dear all,

I attached the NPT input file to obtain the lattice constant of fcc-AlCu3 alloy using AlCu.eam.alloy, which is provided in Potential directory of LAMMPS. However, after initialization, the temperature is increased and the alloy is melted (crystal lattice is distroyed), which is viewed in xmovie. It's funny. In the case of pure Ni using Ni_us.eam, such problem is not occured.

Because I think the AlCu.eam.alloy potential is reliable, maybe are there any further command options for alloy simulation?

Best wishes,
Chol-Jun.

units metal
boundary p p p

atom_style atomic
lattice fcc 4.2
region box block 0 10.0 0 10.0 0 10.0
create_box 2 box
create_atoms 1 box basis 1 1 basis 2 2 basis 3 2 basis 4 2

pair_style eam/alloy
pair_coeff * * AlCu.eam.alloy Al Cu

neighbor 0.3 bin
neigh_modify delay 5

velocity all create 500.0 4928459 rot yes dist gaussian
fix 1 all npt 500.0 500.0 10.0 xyz 0.0 0.0 10.0 drag 1.2
thermo 10

thermo_style custom step temp press vol etotal cpu
timestep 0.002

dump 1 all atom 10 dump.eam1500
run 500000

AlCu-temp.png

I would make sure you are getting the crystal structure you
expect with the Al and Cu in the right places. Using lattice
fcc in the way you are w/out knowing where LAMMPS is putting
the basis atoms, might be problematic.

Steve

In my understanding, in fcc crystal lattice (four basis atoms), first basis atom is located at position (0 0 0) -Al and others are located at (0.5 0.5 0.0), (0.5 0.0 0.5) and (0.0 0.5 0.5) -Cu3 in the unit cell.

If my setting way to position the basis atoms is not right, how can I do correctly in LAMMPS?

Best, Chol-Jun

Steve Plimpton wrote:

That looks right - but you'd have to look inside the code to
figure that out. So normally, you'd define those
basis atoms yourself in a lattice custom command rather
than assume an ordering used internally by keyword fcc.

Steve

The problem with your simulation is that the temperature
shoots up so high and then isn't relaxing to 500K. So
you're probably melting the crystal. Your relaxtion
time for temperature is quite long - 10.0 = 10 psec =
5000 timesteps, so I'd try playing with that and not
use the drag keyword initially.

Steve

Another thought - can you run NVT of your initial system and get a stable
temperature? If so, then your NPT run must be changing the box volume
dramatically which indicates a lattice constant that doesn't match what
the potential wants to induce.

Steve

I did so as follows,

lattice custom 4.2 a1 1.0 0.0 0.0 a2 0.0 1.0 0.0 a3 0.0 0.0 1.0&
    basis 0.0 0.0 0.0 basis 0.5 0.5 0.0 basis 0.5 0.0 0.5 basis 0.0 0.5 0.5
region box block 0 5.0 0 5.0 0 5.0
create_box 2 box
create_atoms 1 box basis 1 1 basis 2 2 basis 3 2 basis 4 2

Steve Plimpton wrote:

The system evolves towards 500k. However the system is not crystal but the liquid. That is, the liquid after some initial time step goes to the 500K. Even if I do not use the drag, the system becomes the liquid soon.

Chol-Jun
Steve Plimpton wrote:

Dear Steve,

The effect of NVT is same to NPT. When I tested the smaller lattice constant, then the system was expanded quikly and then became liquid again. Moreover this potential was developed for fcc crystal and its lattice constant is 4.5A.

Chol-Jun

Steve Plimpton wrote:

When I tested the pure metal such as fcc-Ni using the Ni-u3.eam, I did not meet such problem and got the equilibrium lattice constant agreed with the experimental value. Whenever I tried to treat the alloy system such as AlNi and AlCu, I had to meet such trouble.

Chol-Jun
Steve Plimpton wrote:

You r script uses a lattice constant of 4.2, not 4.5. If you're building
the lattice you think you should (spacing, structure) which you probably
need to viz to make sure, and you can't run NVT and keep it stable
at a T well below the melting point, then I'd say the potential is not
formulated for the system you think it is. Are you sure the AlCu
potential is meant for AlCu3 ? Are there other AlCu alloys?

Steve

Dear Steve,

thank you very much for your many comments and hints. After viewing the paper for AlCu3, I found the lattice constant of fcc-AlCu3 is 3.71 A. Then the test of NPT of AlCu3 reached reasonable results, attached.

So it seems that MD simulations would sensitive to the lattice constant. This means, if the bad lattice constant is used to determine the true lattice constant, the simulation could be failed? How much deviation from the true lattice constant can we start?

Best wishes,
Chol-Jun

#The input script
units metal
boundary p p p

atom_style atomic
lattice custom 3.7 a1 1.0 0.0 0.0 a2 0.0 1.0 0.0 a3 0.0 0.0 1.0&
    basis 0.0 0.0 0.0 basis 0.5 0.5 0.0 basis 0.5 0.0 0.5 basis 0.0 0.5 0.5
region box block 0 5.0 0 5.0 0 5.0
create_box 2 box
create_atoms 1 box basis 1 1 basis 2 2 basis 3 2 basis 4 2

pair_style eam/alloy
pair_coeff * * AlCu.eam.alloy Al Cu

neighbor 0.3 bin
neigh_modify delay 5

velocity all create 300.0 4928459 rot yes dist gaussian
fix 1 all npt 300.0 300.0 10.0 xyz 0.0 0.0 10.0 drag 0.5
thermo 10

thermo_style custom step temp press vol etotal cpu
timestep 0.002

dump 1 all atom 50 dump.eam1500
run 70000

Steve Plimpton wrote:

lattice.png

press.png

temp.png

So it seems that MD simulations would sensitive to the lattice constant.
This means, if the bad lattice constant is used to determine the true
lattice constant, the simulation could be failed? How much deviation
from the true lattice constant can we start?

Solids are very sensitive to the lattice constant. A percent or two is
a big effect. Your simulation is off by 15% o rmore, so the potential
is way off. Look at thermal expansion coefficients to see how little
a solid expands across a wide temperature range.

Steve