Skip to content

Add minimal routing constraints for differentiable optimization#215

Draft
ThomasPluck wants to merge 1 commit intomainfrom
feat/routing-constraints
Draft

Add minimal routing constraints for differentiable optimization#215
ThomasPluck wants to merge 1 commit intomainfrom
feat/routing-constraints

Conversation

@ThomasPluck
Copy link
Copy Markdown
Contributor

@ThomasPluck ThomasPluck commented Mar 24, 2026

Summary

  • Adds model/constraints.json with DRC-derived routing rules (width, spacing, radius) for use with playdough's constraint optimization flow
  • Minimal rule set (<=20 rules) covering routing/waveguide/metal layers only

Test plan

  • Schema validated via playdough.constraints.RoutingConstraints.from_json()
  • Integration test with playdough.Router(constraints=..., routing_layer=...)

🤖 Generated with Claude Code

Summary by Sourcery

New Features:

  • Introduce DRC-derived routing constraints JSON covering routing, waveguide, and metal layers for use by the router.

Adds model/constraints.json with DRC-derived routing rules (width,
spacing, radius) for use with playdough's constraint optimization.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Mar 24, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Introduces a new minimal DRC-derived routing constraints JSON model for use by playdough’s differentiable routing/optimization flow, defining a small set of width, spacing, and bend-radius rules for routing, waveguide, and metal layers.

File-Level Changes

Change Details Files
Add initial DRC-derived routing constraints model consumable by playdough
  • Introduce a new constraints.json file under the model directory to define routing constraints
  • Encode width, spacing, and bend-radius rules for routing, waveguide, and metal layers in a format compatible with playdough.constraints.RoutingConstraints.from_json
  • Limit the constraint set to a small number of rules (<=20) to serve as a minimal viable constraint deck for the router
cspdk/model/constraints.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant