Hi,
I installed lammps on Windows 10 successfully.
I ran the crack example in parallel, and it ran correctly.
The problem is when I run an example of Reax (AB); I face these warnings!
[…]
WARNING: Ignoring inactive control parameter: simulation_name (src/REAXFF/reaxff_control.cpp:98)
WARNING: Ignoring inactive control parameter: energy_update_freq (src/REAXFF/reaxff_control.cpp:98)
WARNING: Support for writing native trajectories has been removed after LAMMPS version 8 April 2021 (src/REAXFF/reaxff_control.cpp:114)
WARNING: Ignoring inactive control parameter: traj_title (src/REAXFF/reaxff_control.cpp:98)
WARNING: Ignoring inactive control parameter: atom_info (src/REAXFF/reaxff_control.cpp:98)
WARNING: Ignoring inactive control parameter: atom_forces (src/REAXFF/reaxff_control.cpp:98)
WARNING: Ignoring inactive control parameter: atom_velocities (src/REAXFF/reaxff_control.cpp:98)
WARNING: Ignoring inactive control parameter: bond_info (src/REAXFF/reaxff_control.cpp:98)
WARNING: Ignoring inactive control parameter: angle_info (src/REAXFF/reaxff_control.cpp:98)
Reading potential file ffield.reax.AB with DATE: 2011-02-18
WARNING: Changed valency_val to valency_boc for X (src/REAXFF/reaxff_ffield.cpp:296)
These are all harmless. The “AB” input deck uses some functionality that is redundant with what LAMMPS offers (the REAXFF package was originally a standalone MD code written in C) and that functionality has been recently removed. The warnings are to remind people of that, so they are not confused why their settings are not honored anymore. We have not updated old examples for that because this does not impact the correctness of the simulations.
[…]
What am I supposed to do?
Nothing. If you don’t want to see the warnings, you have to remove the corresponding keywords from the control file.
In fact, for most ReaxFF simulations you can stick with the default settings and use no control file at all.
Axel.