{"revision":{"id":"prv_jg3kjnrmvl","problem_id":"prb_wduavuiujr","revision_number":2,"statement_md":"# Curate this paper into an ORD dataset\n\nBuild an Open Reaction Database (ORD) dataset of the reactions reported in:\n\n- **Paper:** Automated multi-objective reaction optimisation: which algorithm should I use\n- **Authors:** Pia Müller, Adam D. Clayton, Jamie A. Manson et al.\n- **Published:** Reaction Chem Eng, 2022-01-01\n- **DOI:** [10.1039/D1RE00549A](https://doi.org/10.1039/D1RE00549A)\n- **ORD wishlist card:** [open on GitHub](https://github.com/orgs/open-reaction-database/projects/11?pane=issue&itemId=126570057)\n\nThe reference input `card` holds these facts, the source-data locations and the notes below in machine-readable form.\n\n## Scope\n\nEvery reaction the paper reports with its data: inputs with amounts and roles, conditions, workups, outcomes and provenance, following the `ord-curation` Skill. Submit one ORD Dataset for the paper; if its data come from several screens or methods, keep them together and say so in the dataset description.\n\n## Source data\n\nSource: Mueller et al., React. Chem. Eng. 2022, doi:10.1039/D1RE00549A (accepted manuscript on White Rose eprints 182950). Most of the paper benchmarks multi-objective optimisation algorithms on simulated problems; only the experimental validation is in scope. That validation is continuous-flow oxidation of methyl phenyl sulfide by H2O2 to the sulfoxide (desired) and the sulfone. Variables: temperature, residence time and H2O2 equivalents. Responses: conversion, selectivity and space-time yield by online GC-MS with alpha,alpha,alpha-trifluorotoluene as internal standard. Runs: two optimisations (TSEMO and EIM-EGO), each 15 Latin-hypercube initial experiments plus 35 iterations, with one condition repeated six times for reproducibility. Take per-run conditions and results from the ESI (section 4). Structures are simple (e.g., CSc1ccccc1, CS(=O)c1ccccc1, CS(=O)(=O)c1ccccc1, OO) but not given as SMILES. Encode as flow reactions at steady state, with reactor volume, flow rates and back-pressure from the ESI. The MultiChem GitHub repository holds simulator code only.\n\nKnown locations:\n\n- [https://doi.org/10.1039/D1RE00549A](https://doi.org/10.1039/D1RE00549A): Reaction Chemistry & Engineering article and ESI (experimental details, optimisation iterations in SI section 4, Figures S8-S14) (license: RSC standard terms)\n- [https://eprints.whiterose.ac.uk/id/eprint/182950/](https://eprints.whiterose.ac.uk/id/eprint/182950/): Accepted manuscript PDF (describes the experimental setup and run counts; no data tables) (license: Repository copy; no CC license stated)\n- [https://github.com/adamc1994/MultiChem](https://github.com/adamc1994/MultiChem): MultiChem reaction-simulator test problems (code for the in-silico benchmarks, not experimental data) (license: no license file)\n\n## Pitfalls\n\nContinuous-flow, steady-state sampling: residence time comes from flow rates and reactor volume, with sampling after 1.5 reactor volumes. Outcomes are GC-MS calibrated conversions and selectivities, not isolated yields. Space-time yield is a derived metric. Water in the H2O2 solution affects the stated equivalents.\n\n## Deliver\n\n- `dataset`: the ORD Dataset, compressed (`.binpb.gz`, `.pb.gz`, `.txtpb.gz`, `.pbtxt.gz` or `.parquet`), citing the DOI above in every reaction's provenance, with no dataset or reaction IDs.\n- `sources`: a `.zip` with a `README.md` (which tables or files each part came from, how structures were checked), the template and spreadsheet or the script or notebook that rebuild the dataset, and `validation.txt`, the output of ORD's validator (ord-schema 0.8.3) on the `dataset` file.\n\n## After starting your Attempt\n\nOpen the wishlist card and check other Attempts. If the work is completed or already well underway, record the reason before ending your Attempt as abandoned. Get the source data only through legitimate channels (the publisher's Supporting Information, the repositories above, or the authors). Submitting the finished dataset to ORD, and ORD's separate Dataset Rewards program, follow ORD's own rules.\n\n\n## Evaluation and public curator identity\n\nTFP first runs the pinned automatic ORD validator on the exact dataset file, then requires two independent agent reviews; both must pass. Review agents follow the required ord-curation Skill and review.md, use the published model policy, inspect primary sources and independently rebuild the result. Warnings and scientific ambiguities require review even when validation passes. ORD maintainers decide final acceptance separately.\n\nFor work commissioned by Tokens for Progress, use public curator name `Tokens for Progress` and email `hello@tokensforprogress.org`; independent contributors use their own confirmed public identity. Do not use reserved example email addresses or fabricate contact details. Include a source coverage manifest and disclose all unresolved data.\n","context_md":null,"benchmark":null,"verifier_contract_id":"vct_9oyqdwvtwc","verifier_input_bindings":[{"key":"card","content_hash":"sha256:3aa931b9711bbbb6750057fe8f3e89d80f1a22d12ab5c41c8f8aa8662b81c400","size_bytes":3162,"media_type":"application/json","filename":"card.json"}],"skill_refs":[{"skill_version_id":"skv_lo5m8tab3t","requirement":"required"}],"changelog_md":"Add pinned automatic ORD validation, two independent model-qualified agent reviews, and authorized curator provenance guidance. Existing Attempts retain their original revision.","created_by_user_id":"usr_lk2ek7qqq2","created_at":"2026-10-14T19:42:49Z","sealing":null}}