openmedical/registry
← registry

retrosynthesis_bot

imported

therapeutics/retrosynthesis-bot

Twitter retrosynthesis bot

Machine-generated from the listed sources and not yet reviewed by a human.

retrosynthesis_bot project image
GitHub preview card for n-yoshikawa/retrosynthesis_bot. Served by its origin, not stored here, and not covered by this registry’s licence.
record
Category
Therapeutics
Subcategory
unknown
License
MIT(osi)
Status
dormant
Maturity
deployed
Organization
unknown
Country
unknown
Documentation
unknown
Tags
cheminformatics · retrosynthesis · twitter
Regulatory
unknown
similar by tags

Computed from shared tags, weighted so a rare tag counts for more than a common one. These are suggestions, not curated relationships.

  • hedgehogcheminformatics · retrosynthesis

    Stage-based evaluation pipeline for generative molecular design: filters, retrosynthesis checks, docking, pose validation, reports, CLI/TUI.

  • renkincheminformatics · retrosynthesis

    Local and reproducible route auditing for AiZynthFinder, Syntheseus and RENKIN — plus a portable Rust retrosynthesis engine.

  • SynPlannercheminformatics · retrosynthesis

    Computer-aided synthesis planning

  • avaxtartwitter

    Model that predicts the probability of a Twitter user being anti-vaccination.

  • ReAgentAIretrosynthesis

    PydanticAI Agent for chemistry related tasks including the retrosynthesis of chemical compounds.

  • Quantifying lexical semantic change of 'toxic', 'healing', 'burnout' on Twitter via temporal Word2Vec + Procrustes alignment | displacement scores, nearest-neighbor shift, t-SNE visualization

sources
  1. api.github.com/repos/n-yoshikawa/retrosynthesis_bot
    retrieved 2026-08-25 · via github-api

    Machine-imported from GitHub search. Last push 2022-07-10, 13 stars, license reported as MIT. Category and schematic were assigned by keyword heuristics and are unreviewed.

Not yet verified by a human. Correct this record →

machine-readable

/v1/entries/27.json→ .entries["retrosynthesis-bot"]

Entries are sharded 64 ways by a stable hash of the id, so a consumer can find any record without an index.