DRCY is Allspice’s AI assistant for exploring and analyzing electronic designs. With DRCY Review, it can operate as an extra reviewer on your team during design reviews, systematically checking your electronic designs for potential component and connectivity issues. It surfaces findings as comments and design snippets within the Allspice Design Review workflow, giving your team a shared set of concerns to examine, discuss, and track.
When to use DRCY Review
Use DRCY Review when you want broad, systematic coverage of a design, particularly to surface issues you might not have thought to look for. It complements the focused investigation capability of DRCY Chat for assisting you during the design process..
Run DRCY Review to uncover potential issues and blind spots across the full design
Use the findings as a starting point for team discussion and issue tracking
Bring specific findings into DRCY Chat for deeper investigation when needed
Running a review
Navigate to your repository and open the Design Review you want to run DRCY on.
Add DRCY to the list of Reviewers.
Open the Request DRCY menu, choose your preferred settings, then click Start DRCY.
.png)
Wait for DRCY to complete its analysis.
Review the findings posted as comments in the design review conversation.
Understanding DRCY findings
DRCY Connections Checker Review
The first comment DRCY posts after completing its analysis is a top-level summary of the components it examined and any issues with missing or unresolved datasheets. It’s recommended to look through this section first before reviewing any detailed findings from DRCY in the comments that follow.
.png)
Component Details
DRCY analyzes every component using its listed attributes, pins, nets, and connectivity to the rest of the design. It also references available (fetched or uploaded) datasheets, repository files, and additional context you provide to build a complete picture. The analysis of every component is documented in this section.
To make it easier to understand and triage DRCY’s findings, you can:
Search for specific components, pages, or findings
Filter by schematic page or Severity Tag (see the Severity Tags section below for more details)
Sort by component designator, part, schematic page, etc.
Download in CSV format
Missing Datasheets
DRCY uses component part numbers to fetch datasheets automatically, but sometimes there might be unresolved components. This could be due to a few reasons:
An internal part number was used instead of manufacturer part number in the component attribute
The datasheet isn’t in a publicly-available database (i.e. the part is internal, in pre-release, or under NDA)
There was a mistake or typo in the part number entry
If the issue isn’t easily correctable in your component attributes, you can manually upload a datasheet instead.
Click on Upload a datasheet for each component you want to update.
Allspice will automatically create a commit with your uploaded files. Add a commit message and click Commit Changes, then rerun DRCY to incorporate the uploaded schematics. During all subsequent DRCY runs, your manually uploaded datasheets will now be used for analysis.
Comments
A comment posted by DRCY summarizes everything you need to address issues with your design, as well as the evidence and logic DRCY used to reach its determination.
.png)
There are several parts of a comment that provide information:
Severity tag and claim: Indicates the finding’s priority and summarizes the potential issue DRCY identified.
Observed: Describes the condition DRCY identified in your design.
Requirement: States the datasheet specification or design constraint against which that condition is evaluated.
Consequence: Explains the potential impact of the condition on circuit behavior or reliability.
Evidence: Provides the design details and source references supporting the finding.
Suggested repair: Recommends a change to address the identified concern.
Datasheets: Links to the specific datasheets DRCY used for its analysis and determination
You can also click on the schematic snippet that DRCY posted and jump directly into the design review interface. From there, you can see the actual component, any recent changes that caused the issue, and all the evidence from the rest of the design.
Addressing DRCY findings
There are multiple options at the bottom of a DRCY comment for addressing findings, either by adding feedback, investigating deeper, or just changing the visibility during future DRCY runs. In cases where DRCY is wrong about a finding (i.e. a false positive), there are ways to manage that as well.
Response | Use when | What DRCY does next time |
|---|---|---|
Thumbs up 👍 | The finding is correct | Keeps reporting the finding until you fix it |
Thumbs down 👎 | The finding is wrong about the design | Suppresses the finding now and on future runs of this design |
Chat | The finding is correct and you need to investigate deeper or add supporting documents | Incorporates any feedback from the Chat session |
Resolve conversation | The finding is correct but not relevant for this board | Clears the finding from this review |
Reply | The finding is wrong and the reason needs to be documented | Nothing different, but the record stays on the review |
Reply with @DRCY | The finding is wrong and DRCY needs to know | Feedback will be incorporated |
When a DRCY Review finding warrants follow-up beyond a quick reply, it can easily be turned into a tracked issue directly from the comment itself. Just open the More Options (…) menu, then click Reference in New Issue. Creating an issue from the finding keeps it visible and actionable for the team outside of the review conversation, allowing it to be assigned, prioritized, and tracked through resolution.
Severity Tags
DRCY tags each finding with a severity level to help you prioritize. There are three levels, from lowest to highest:
Recommendation: a departure from best practice that does not necessarily indicate a functional problem.
Warning: a concern that may affect behavior or reliability under certain conditions.
Error: a higher-impact issue that warrants close attention.
Select which tags you want to be visible as comments from DRCY severity in the Comment filter. Toggling severity levels only affects comment visibility. It does not change the underlying analysis or remove findings from the summary.
Troubleshooting
DRCY doesn’t start or the analysis stalls
Confirm that DRCY is added as a reviewer and that you started it from the Request DRCY menu. If the analysis stalls or fails, request DRCY again. If the problem persists, contact Allspice Support and include the design review link and any error details.
DRCY reviewed zero components or fewer pages than expected
Check the review summary for a page-selection notice. When page selection is active, DRCY reviews only the selected pages. To review all changed pages, clear the page-selection settings for the design review and run DRCY again.
Some components could not be analyzed
Expand Component Details and check Analysis Failures. These failures are usually temporary, so try requesting another review. If the same components continue to fail, contact Allspice Support and include the affected component names and review link.
Findings aren’t visible in the review conversation
Check the severity filter. It controls which posted comments are visible, not the underlying analysis. Review the summary for findings that aren’t shown as standalone comments.
Components are listed as missing datasheets
DRCY may not have the reference material needed to analyze those components. Check the component part numbers and datasheet mappings, then upload any missing datasheets, commit the changes, and rerun DRCY. See Missing Datasheets above for details.