Closed andeplane closed 7 years ago
One solution would be to detect this before remap is called and skip remap if we have problematic atoms.
Fixed in bd42d6f908662aed79e4915aac313aa93b50cdac by adding regular LAMMPS lost_check routine in fix_atomify.
Turns out it isn't always fixed. In this example, it hangs because x is equal to 1e22 for some atom. 06_22_sic_single_sheet.zip
Edit: this time it is because fix ehex does remap, so it is a LAMMPS issue, not Atomify.
The two attached files reproduces the problem. Atoms might have arbitrary large coordinates and since we use domain->remap to place atoms inside simulation box before rendering, it gets stuck in
Archive.zip