Skip to content

Could not map results, the relaxation-induced distortion looks OK #335

@sjtuzhanglei

Description

@sjtuzhanglei

Dear CASM developers,

Should I modify the casm update conditions or any python wrappers?

Even the simplest 111 supercell cannot be mapped. I checked the CONTCAR and POSCAR, they are not much different. No severe distortions, no lattice site swapped, etc.

casm update
-- Read: Settings -- 
{
  "force" : false,
  "mapping" : {
    "cost_tol" : 0.000010000000,
    "fix_lattice" : false,
    "fix_volume" : false,
    "ideal" : false,
    "k_best" : 1,
    "lattice_weight" : 0.500000000000,
    "max_va_frac" : 0.500000000000,
    "max_vol_change" : 0.300000000000,
    "min_va_frac" : 0.000000000000,
    "primitive_only" : false,
    "robust" : false,
    "strict" : false
  }
}

Updating data records for SCEL1_1_1_1_0_0_0/0
WARNING: Could not map 1 results.
  See detailed report: "/pscratch/sd/v/voz5005/RuO2/casm/211/srun64/casm-2/reports/update_report.4/update_config_fail"

cat reports/update_report.4/update_config_fail
[
  {
    "atomic_deformation_cost" : null,
    "best_score" : null,
    "energy" : null,
    "has_all_required_properties" : false,
    "has_any_required_properties" : false,
    "is_new_best" : false,
    "lattice_deformation_cost" : null,
    "properties_origin" : "",
    "score" : null,
    "selected" : false,
    "to_configname" : ""
  }

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions