> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/physics-rule-checks-prcs/signal-path-length.md).

# Signal Path Length

Summary of the Trace Path Length PRC, validating trace lengths to minimize inductance, enhance noise filtering, and ensure efficient power and signal integrity.

### Description

**Signal Path Length** calculates the trace length between two pins of interest.

**Passing Criteria:** \
This check passes if the calculated trace length falls below a specified tolerance

**Reporting Units:** \
CENTIMETERS (cm)

### **Examples**

**Passing Message:**&#x20;

{% hint style="success" %}
Signal path length of 0.73cm within acceptable range (0cm to 1cm)
{% endhint %}

**Failing Message:**&#x20;

{% hint style="danger" %}
Signal path length of 2.95cm outside acceptable range (0cm to 1cm)
{% endhint %}

### Physics Justification

Minimizing the trace length is important because:&#x20;

* **Reduced Parasitic Inductance**:&#x20;

  Longer traces introduce **parasitic inductance**, degrading the ability to respond to high-frequency noise.&#x20;
* **Improved Noise Filtering**:&#x20;

  A short trace allows a capacitor to quickly supply or absorb current, effectively stabilizing the voltage and filtering noise.&#x20;
* **Lower Impedance Path**:&#x20;

  Shorter traces decrease impedance, ensuring robust and efficient power/signal delivery to the pin.&#x20;

#### Helpful Definitions&#x20;

* **Parasitic Inductance** \
  The unintended inductance present, which arises from the magnetic field created by current flow and opposes changes in current, especially at high frequencies. It can degrade circuit performance by slowing responses and causing noise.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quilter.ai/physics-rule-checks-prcs/signal-path-length.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
