Repository navigation
ducksmiles: bump to 0.5.0 - #2055
Conversation
New since 0.4.0 (all RDKit-faithful): - Bit-fingerprint similarity family: dice, cosine, kulczynski, sokal, mcconnaughey, asymmetric, braun_blanquet, russel, and tversky_bit (joins the existing tanimoto_bit), ported from DataStructs/BitOps.cpp. - Descriptors: mol_mr (Wildman-Crippen molar refractivity), qed (drug-likeness, port of Chem.QED), and the RDKit ring-count family (num_saturated_rings, num_aliphatic_rings, and the aromatic/saturated/aliphatic x hetero/carbocycle splits). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…nchmark harness (ref -> merged docking branch)
|
Updated the 0.5.0
Still pure Rust core (no RDKit), MIT. 546 Rust unit tests pass; full pipeline verified end-to-end against the bundled DuckDB. |
|
Closing and reopening to re-trigger CI on |
|
Hi @nkwork9999, can you take a look at the build error in the CI? It seems recurring across CI job reruns. |
|
Updated the source ref to nkwork9999/duckSMILES@3b5940d to address the reported build failure. The ListVector include now supports both the stable DuckDB header layout and newer layouts. The source repository CI targets DuckDB v1.5.5 with v1.5-variegata tools, and this descriptor now explicitly requests the Rust toolchain. Rust cross-target selection and formatting fixes are also included. The new community CI runs are in progress; I am checking the remaining build and SQL-test results. The 21 structural-profile descriptors have a pinned RDKit reference suite, but this update does not claim universal RDKit parser/sanitizer equivalence. |
|
Thanks! |
CI verified (2026-09-05)
Verified source commit:
ff7c681ca14698d7ed6ec4a5d7a15fc40cefe834. Community PR head:42d25c854f8720d561ace44082c7642e09e0c46d(tested merge commit65f5631b4c72dbf66b1eb49c5eb62c191c1dbca3).Existing disabled/documentation/deployment jobs remain skipped according to the workflows; they are not counted as passed. No platform exclusions or test-disabling changes were added. These results verify builds and the executed tests, not publication or universal RDKit compatibility. Wasm checks establish side-module link integrity, not DuckDB-Wasm runtime SQL coverage.
Build and runtime compatibility fixes
Updates
ducksmilesto 0.5.0 (source refff7c681ca14698d7ed6ec4a5d7a15fc40cefe834).Features carried forward since 0.4.0, with SQL regression tests in the source repository:
DataStructs/BitOps.cpp):dice_bit,cosine_bit,kulczynski_bit,sokal_bit,mcconnaughey_bit,asymmetric_bit,braun_blanquet_bit,russel_bit, and asymmetrictversky_bit(a, b, α, β)— joining the existingtanimoto_bit.mol_mr— Wildman-Crippen molar refractivity (shares the LogP atom-contribution table).qed— QED drug-likeness, a port of RDKitChem.QED; reproduces theQED.pyreference values closely.num_saturated_rings,num_aliphatic_rings, and the aromatic/saturated/aliphatic × heterocycle/carbocycle splits (RDKitrdMolDescriptors).Additional changes in the current revision:
extension.requires_toolchains: rustand correct Rust target selection for community cross-platform builds. Source CI now uses DuckDB v1.5.5 and v1.5-variegata tools.Validation: current-ref source, community stable and community development CI all passed; exact runs, test counts and intentional skips are recorded above.
Source PR: nkwork9999/duckSMILES#14
Definitions and limits: https://github.com/nkwork9999/duckSMILES/blob/ff7c681ca14698d7ed6ec4a5d7a15fc40cefe834/PROFILE_PARITY.md