Problematic mapping for text lammps dump files by default with element and type columns simultaneously
There is inconsistency when both type and element columns are present in the lammps data file. OVITO tries hard to map them both to the OVITO atom type (not to mention by failing spectacularly). To prevent this behavior, one needs to activate user-defined mapping and disable mapping for one of the columns. Also, it makes no sense to allow the user to map several columns to the same OVITO property, right?
Expected behavior: OVITO maps lammps type to OVITO type by default if both (element and type) columns are present. One can always choose different mapping if desired.