- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
In this paper, the authors (1) introduce a utility tool to extract atomic descriptor information from ORCA calculations into LMDBs, (2) demonstrate its capabilities by processing specific properties from the wavefunctions of the Omol 4M dataset, which was released as 'omol electronic structures', and (3) create evaluation splits from it.
Critical strengths
This is a workflow paper, and it presents a reasonably difficult engineering effort.
Critical weaknesses
The abstract advertises the wavefunctions, but it seems like the wavefunctions are not actually included in this database. I would increase my score if the authors include full electronic data into this database, eg the Density matrices, Hamiltonian matrices, and electron densities/wavefunction information. That would directly reflect the true utility of the released omol electronic structures data and would save the materials modelling community significant time and effort to do this themselves. As it is, I think it's a useful utility to have, but it seems like the kind of thing individual researchers can set up with agent workflows on a compute cluster. I've done something similar when dealing with this data, and it worked just fine (just needed some minor filtering/cleanup at the end). Eg, I'm not currently convinced this is a level of contribution that can justify an ICLR submission. However, I'm open to being shown wrong, or that there is something I overlooked, and am happy to engage with the authors during the rebuttal stage.
Questions for authors
See 'weaknesses'
Thank you for engaging and for stating what would change your assessment. We address the wavefunction point first:
"The wavefunctions are advertised but not included."
Our wording was misleading, and we have corrected the abstract and introduction. The raw files already exist publicly:
Re-hosting about 500 TB would duplicate public data and add no information, so we instead:
orca_2mklor Multiwfn installation."This could be done with agent workflows on a cluster."
The pipeline itself is not the hard part; producing descriptors that are correct is. Several failure modes exit cleanly and parse without error, so an unsupervised workflow would ship wrong values silently. Examples we found and fixed:
The pipeline is also engineered as a reusable tool, not a one-off script:
"Is this level of contribution enough for ICLR?"
The new experiments aim to push this. A descriptor layer that most ML groups could not compute themselves (500 TB of input, per-structure Multiwfn runs, the integrity issues above) turns out to carry information that energy/force training does not recover on its own:
The general response has the table, and Appendix N has the full experiment. The descriptors also come in a form an ML group can use directly: compact, portable LMDBs instead of hundreds of terabytes of raw files. We think this moves the release from infrastructure to a resource with measured downstream value. We would welcome your view on it.