FAQ / ROUTE PLANNING AND AUDITING
Frequently asked questions
The short answers researchers usually need before deciding whether to start with a target, a route file, or a comparison protocol.
What does RENKIN take as input?
Planning begins with a target molecule. Auditing begins with a route file in a supported format. Optional stock and policy inputs define the boundary for the checks that use them.
What does a local audit return?
The audit writes a JSON report with route status, structural checks, stock validation when configured, forward validation, findings, and an audit manifest.
Does local mean no upload?
The documented CLI and browser workflows process route data on the machine or browser running them. Keep sensitive data out of unrelated hosted services.
Does an audit validate a synthesis experimentally?
No. The report records computational checks and the evidence available to those checks; it does not establish yield, safety, scale-up behavior, or laboratory feasibility.
FAQ
Questions before you start
What is the difference between planning and auditing?
Planning searches from a target toward building blocks. Auditing inspects a supplied route and records what the route and its declared context support.
Which route sources can be audited?
RENKIN supports matching formats for RENKIN, AiZynthFinder, Syntheseus, SynPlanner, and documented interchange workflows.
How should route planners be compared?
Freeze the targets, stock boundary, route criteria, versions, and runtime conditions, then retain all outcome categories.