Dear CP2K Developers,
I am writing to ask for your advice regarding some small but systematic discrepancies I observed in density matrices and Mulliken population analysis obtained from a single‐point calculation performed using CP2K.
In my test for CO, I compared the following files generated from the same single-point SCF calculation:
The MOLDEN file (CO_molopt_smearing-mos.molden-1_0.molden)
The Mulliken file (CO_molopt_smearing-mulliken-1.mulliken)
The largest iteration AO log file (e.g., CO_molopt_smearing-ao-1_0_12.Log)
The 1_0 AO log file (CO_molopt_smearing-ao-1_0.Log)
I found that:
The density matrices read from the last AO log file and from the 1_0 AO file differ by approximately 1×10⁻⁷, even though they originate from the same single-point calculation.
Constructing Mulliken populations by element-wise multiplication of the density matrix and the overlap matrix (i.e., computing for each pair of atomic orbitals) leads to slightly different values compared to the MULLIKEN NET ATOMIC ORBITAL AND OVERLAP POPULATION MATRIX reported in CP2K’s Mulliken output file.
Additionally, when processing the MOLDEN file using Multiwfn, the computed Mulliken bond orders are again slightly different from those obtained directly from CP2K.
Before I proceed further, I would like to confirm:
Are these ~1e−7 differences expected due to formatting, truncation, numerical precision, or different internal representations used when writing the log files, MOLDEN file, and Mulliken file?
Is there a recommended “most reliable” source of the density matrix for reproducing CP2K Mulliken results (Mulliken file vs. AO log file vs. MOLDEN file)?
Are the Mulliken matrices produced by CP2K post‐processed in any additional way (e.g., symmetrization, thresholding) that could explain these differences?
Are there known limitations or differences in the basis function ordering between MOLDEN export and the AO log files?
For reference, I attach (or can provide) the following files:
Any guidance on how to interpret these discrepancies would be greatly kind of you. Thank you very much for your time and for your continuous development of CP2K.
Best regards