comm_modify docs tweak
comm_modify cutoff usage clarification, when using restart files
This commit is contained in:
@ -40,11 +40,12 @@ coordinates and other properties are exchanged between neighboring
|
||||
processors and stored as properties of ghost atoms.
|
||||
|
||||
NOTE: These options apply to the currently defined comm style. When
|
||||
you specify a "comm_style"_comm_style.html command, all communication
|
||||
settings are restored to their default values, including those
|
||||
you specify a "comm_style"_comm_style.html or
|
||||
"read_restart"_read_restart.html command, all communication settings
|
||||
are restored to their default or stored values, including those
|
||||
previously reset by a comm_modify command. Thus if your input script
|
||||
specifies a comm_style command, you should use the comm_modify command
|
||||
after it.
|
||||
specifies a comm_style or read_restart command, you should use the
|
||||
comm_modify command after it.
|
||||
|
||||
The {mode} keyword determines whether a single or multiple cutoff
|
||||
distances are used to determine which atoms to communicate.
|
||||
|
||||
Reference in New Issue
Block a user