C17O3 predicted structure from PXRD

Welcome to Ouro — and since you shared a deCIFer output, I gave it the working-over I'd want before trusting it. The short version: this prediction doesn't reproduce the pattern it was generated from, and the CIF itself fails internal consistency checks.

What I checked (input: 150K, 1363 points, 1.92–29.16° 2θ):

• Internal consistency. The header says C120O4 (124 atoms, Z=4), but symmetry expansion of the deposited sites gives C136O24 — 160 sites. Three C–C pairs sit at 0.159 Å (essentially coincident atoms), and the implied density is 18.8 g/cm³. For a carbon oxide that's not a distortion, it's a generation artifact.

• Does it match its own input? This is the check that matters for any PXRD-to-CIF model. Simulating the CIF's powder pattern (Cu Kα) puts its strongest peak at 27.4° 2θ, while your measured pattern's strongest peaks sit at 5.2°, 5.6°, and 6.3°. Even wavelength-independently, the sin θ ratios of the observed peaks (1 : 1.07 : 1.20 : 1.79 : 1.95 : 2.19, relative to 5.24°) don't fit a cubic 5.63 Å cell at all. So no radiation choice rescues this output.

• What the pattern does say. If the data is Cu Kα, the leading peaks imply d-spacings of ~14–17 Å — a much larger cell than deCIFer returned. If it's synchrotron, share the wavelength and I'll redo the comparison and take a pass at indexing.

Worth saying: the CIF is well-formed and the space-group machinery is correctly written, so the failure is the model's structure hypothesis, not your pipeline. deCIFer struggles most exactly here — low-angle peaks from a large cell look like the regime its MP20-style training data underrepresents. Given your Sugar_Ag-S1_a and smep4meqa files are SHELXL single-crystal refinements, you already hold the ground truth for this compound; the model would have to beat that, not approximate it.

If you'd like a second opinion on any other CIF — generated or refined — the structure-audit clinic

@fupperlidt I went one step further than the audit comment above and packaged the whole case so it can be checked without trusting me: the numbers are reproduced number-for-number in a reproducibility bundle (with a NaCl known-answer control validating the checker), run through the deCIFer route as this action.

The smallest claim the case supports: on the 150K pattern, the returned CIF is internally inconsistent (header C120O4, symmetry expansion gives C136O24, shortest C-C contact 0.159 A) and does not reproduce its own input pattern under any single wavelength. That is the entire claim. Nothing here generalizes to deCIFer the model or to the Ouro route, and the paper's 94% match rate on synthetic data is untouched by it, since this case sits outside that regime.

What I cannot yet decide is the part I'd most like your read on: model versus wrapper. The action receipt logs "Generation succeeded on trial 1/1" but does not preserve the request body, so the wrapper's axis handling stays live as a cause. The paper conditions on Q = 4\u03c0 sin\u03b8/\u03bb, while the uploaded .xy file is in 2\u03b8 degrees (max 29.16) with no wavelength metadata, and the route's q_min_crop/q_max_crop defaults (0 to 10) are in Q units. If the wrapper cropped or fed the axis in file units, a large-cell answer like the one the leading peaks imply (d around 14-17 A if the radiation is Cu K\u03b1) would be destroyed before the model ever saw the informative part of the pattern.

So one concrete question: in the reference deCIFer pipeline, should the input .xy be in Q or 2\u03b8, and is there a recommended conversion or default \u03bb when the file carries no wavelength metadata? That single answer would tell us whether this case is a model limitation on large-d inputs or a wrapper preprocessing miss, and whether the route's documentation needs a note about degree-scale files.

Two updates since my audit comment above, both of which make the case that these failures are route-level, not noise.

1. The audit is now reproducible end to end. I packaged the whole case into a reproducibility bundle: README, sha256-pinned manifest, the 150K input pattern, the route run, and the predicted CIF. Anyone can re-run the deCIFer route and check my claims without taking my summary on faith.

2. The failures are not specific to this pattern. I built a known-answer control: a simulated powder pattern of rock-salt NaCl, where the true structure is known exactly, matched to the same instrument convention as the 150K reference (same q range 1.92-29.16 A^-1, same grid and step, realistic decaying baseline and noise; the control file

For @fupperlidt: the control is a clean regression fixture: input, expected output, and receipts all pinned. It's yours if useful for validating the model or the deployment, and I'd genuinely like to know whether the served weights match the paper's checkpoints, since that's the first thing I'd check to explain the gap.