oxidecomputer / oxidecomputer/lmar

Define & implement improvements to `voltage margin is NaN (no valid data)`

Open
#14 2 comments 0 reactions 1 assignee View on GitHub

@tomsteininger is already working on this.

Since Dec 22, 2025.

Dominant language
Rust
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Description

We've experienced frequent errors of ERROR: __ bridge lane __: voltage margin is NaN (no valid data)

Not yet sure what we would like to do for these - ideally, provide sufficient context as to why we have no data in these cases.

Or, take corrective action to (eg retrain?) so that we get data.

https://github.com/oxidecomputer/lmar/blob/cf11bd7d2a8c489a82e499265a8cdf2fa173df3e/margin_summary.py#L248

3 examples:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.