| Problem definition | Whether the software supports the required elements, composition, stoichiometry, and number of atoms per cell. Check whether fixed-composition and variable-composition searches are available. | Documented element coverage, composition constraints, and tested cell-size range. | A search cannot reliably answer a question outside its supported chemical and structural space. |
| Pressure and temperature conditions | Whether the method models the target conditions. Zero-temperature searches often rank structures by enthalpy, while finite-temperature stability may require free-energy methods. | Supported pressure range and a clear description of whether reported rankings use energy, enthalpy, or free energy. | The most stable structure can depend on pressure and temperature; a ranking at one condition may not apply at another. |
| Search-space exploration | How candidate structures are generated and diversified, including treatment of symmetry, cell shape, and structural constraints. | Search strategy documentation, number of independent runs, and evidence that distinct structure families are explored. | Structure prediction involves a vast search space. Repeatedly finding similar candidates may indicate limited exploration. |
| Energy model and refinement | Which method evaluates and relaxes structures, and whether candidates can be re-evaluated with a more accurate first-principles method. | Reported energy method, relaxation settings, and comparison of search-stage energies with higher-accuracy calculations. | Search rankings are only as reliable as the energy model. Approximate models can help explore candidates but may mis-rank close competitors. |
| Benchmark performance | Whether the software is tested on relevant, independently known crystal structures and chemical systems. | Recovery rate, top-k success rate, structural similarity measures, and a clearly described test set. | Benchmarks provide evidence of performance, but results on unrelated materials may not predict performance for a new chemistry. |
| Ranking and stability analysis | Whether the workflow compares candidate energies consistently and, where relevant, evaluates stability against competing phases. | Energy or enthalpy differences, energy above the convex hull, and documented reference phases and calculation settings. | A low-energy candidate is not necessarily stable against decomposition into other compositions or phases. |
| Robustness and reproducibility | Whether independent runs produce consistent low-energy structures and whether inputs, settings, and random seeds can be recorded. | Results from multiple runs, variation in best-found energies, and reproducible input and output files. | Stochastic searches can produce different results on different runs; reproducibility helps distinguish a robust result from a lucky search. |
| Physical validation | Whether predicted structures can be checked for dynamical or mechanical stability and refined with appropriate calculations. | Phonon calculations, elastic stability checks where applicable, and convergence tests for the final candidates. | Low energy alone does not guarantee a physically viable structure; validation can reveal unstable modes or calculation artifacts. |
| Efficiency and scaling | How runtime and resource use change with system size, number of candidates, and accuracy settings. Check support for parallel calculations. | Runtime and resource reports for systems comparable to the intended study, including the hardware and settings used. | Searches may require many candidate evaluations, so practical cost can determine whether a workflow is feasible. |
| Workflow and data handling | Whether the software supports automated relaxation, error recovery, and export to common structure formats such as CIF. | Documented input and output formats, workflow examples, and retention of calculation settings and structure metadata. | Clear data handling makes results easier to inspect, validate, share, and reproduce with other computational tools. |
| Usability and support | Whether installation, configuration, documentation, and troubleshooting match the team’s technical experience and computing environment. | Installation instructions, example workflows, documentation completeness, and stated support or maintenance arrangements. | A capable method is less useful if it cannot be installed, configured, or operated reliably for the intended project. |