The usage of maximum_distance_factor in LocalGeometryFinder.compute_structure_environments #2569
Replies: 3 comments
-
I am suspecting that this is related to stored reference polyhedra in ChemEnv. ChemEnv does not have any reference parameters for polyhedra with more than 13 neighbors. Starting from a max_distance_cutoff of 1.2, you get 14 however. I will further look into your case and hope to have a better answer soon. |
Beta Was this translation helpful? Give feedback.
-
To circumvent this, you can focus on cation-anion bonds or cation-cation bonds only. For example by providing valences:
With regard to choosing the parameter, I would use the default value but with valences. |
Beta Was this translation helpful? Give feedback.
-
It's on my list somewhere to update the tutorial in this regard but might take time. We should probably also add a clearer error-message. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Something strange happens when I use LocalGeometryFinder.compute_structure_environments. The maximum_distance_factor is explained as "param maximum_distance_factor: If not set to None, neighbors beyond maximum_distance_factor*closest_neighbor_distance are not considered". It appears to be the maximum bond length when evaluating the bonding environment. Usually, I will think a larger enough number would at least give some results. However, for some structures, this will raise up error message due to the failure of calculating valid ce_dict. The following code can reproduce some frequently seen error messages. Could anyone let me know why this happens? Also, how do we choose maximum_distance_factor normally?
Beta Was this translation helpful? Give feedback.
All reactions