> 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/trace-path-length.md).

# Trace Path Length

### Description

**Trace 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:** 

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

**Failing Message:** 

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

### Physics Justification

Minimizing the trace length is important because: 

* **Reduced Parasitic Inductance**: 

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

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

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

#### Helpful Definitions 

* **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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.