Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properties are not always mapped with --include-equivalents #311

Open
xivh opened this issue Aug 18, 2023 · 0 comments
Open

Properties are not always mapped with --include-equivalents #311

xivh opened this issue Aug 18, 2023 · 0 comments

Comments

@xivh
Copy link
Contributor

xivh commented Aug 18, 2023

After setting calculated configs on with casm select -c CALCULATED --set selected, the following commands produce different outputs:

  1. casm query -k energy --include-equivalents -o one.json does not map energy, i.e. the energy field is null for every config with equivalent_index != 0
  2. casm query -c CALCULATED -k energy --include-equivalents -o two.json maps the energy to the equivalent configs.

The same happens in csv output, except energy is 'unknown' instead of 'null'.

A similar thing happened with relaxation strain. When I queried relaxation strain, the strain did not map unless I used -c CALCULATED, and then the mapped strains were all identical for equivalent configs. However, when I initialized a new project with dof_strain and imported properties.calc.json, the strain mapped to equivalent structures as expected (not unknown/null, and equivalent structures have symmetrically equivalent strain instead of identical strain).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant