Review declared code ownership and complete S-parameter matrices
Choose one CODEOWNERS snapshot, inspect explicit ownership gaps, and export every Touchstone pair with raw tokens and correct matrix coordinates.
Choose the source that answers the receiving task
Use CODEOWNERS routing when a list of changed paths must be grouped by declared owners. Use the Touchstone report when a measured .sNp export must become complete matrix rows for plotting or further inspection. Both tasks retain original source text and hashes; their reports do not verify a remote account or a physical device.
CODEOWNERS: snapshot selection precedes path matching
Choose one intended snapshot explicitly. GitHub searches .github/CODEOWNERS, root CODEOWNERS and docs/CODEOWNERS in that order and uses the pull-request base branch when requesting reviews. An offline file cannot establish which branch or file GitHub will use. This tool never opens the repository or calls GitHub.
The starter retains six supplied paths, including a duplicate. Five have declared owners and apps/github/action.yml is explicitly unowned. A later empty owner list clears the earlier /apps/ match. docs/* owns docs/readme.md but does not cover docs/deep/readme.md; the earlier * rule remains its final match. Every decision retains source line and all owners on that line.
Inspect the skipped-rule count before handing the report to a reviewer. GitHub-invalid !negation, character ranges and escaped leading # lines are omitted from routing with full original lines and reasons. A legal escaped-space pattern is outside this release and rejects the whole batch as Unsupported; it is never silently skipped to produce a different owner. Owner strings are declarations; account existence, write permission and team visibility remain unverified.
Touchstone: coordinates prevent a plausible but wrong matrix
Choose the actual 1–4-port count. Recognized .sNp filename and chosen count must agree. Two-port raw order is S11,S21,S12,S22, whereas 3/4-port points use one physical matrix row per line. The starter has two frequency points and eight complex pairs; its scalar R75 option is valid even though R appears before MHz and RI.
The profile requires one pre-data # option line, finite scalar reference and ASCII LF/CRLF source. Empty # defaults to GHz, S, MA and R50. Per-port reference, repeated or late option lines, noise, Y/Z/G/H, 2.x keywords and other valid wrapping return Unsupported. Missing # or non-increasing frequency is invalid. These profile limits do not redefine Touchstone standards.
JSON and CSV retain raw frequency and pair tokens with original line, column and byte coordinates. Derived real, imaginary, magnitude, normalized phase and dB use float64; they do not replace original measurement precision. dB is 20log10 magnitude, and exact zero has the string -Infinity with phase0. Nonzero underflow or nonfinite derived ranges reject. No RF calibration, reciprocity, performance or circuit correctness is inferred.
Keep the complete handoff separate from the preview
The table shows the first 200 rows and at most 2,000 UTF-16 units per cell. When a report exceeds 20,000 characters, text and copy contain a labelled preview with full row count. Full JSON/CSV downloads still contain every routed path or every Sij pair. Keep the original snapshot, changed paths or measurement file with the handoff.
All input, count, work and output budgets apply together. A valid file can still fail its complete-output budget; the tool publishes no partial artifacts. After cancellation, rerun valid selected sources. Download before closing the tab.
| Task | Input | Structure and complete output |
|---|---|---|
| CODEOWNERS | Selected source2MiB + changed paths2MiB | 10k rules;10k paths;1,024UTF16 path/pattern;100owners;2M combinations;32MiB JSON+CSV |
| Touchstone S | One ASCII source10MiB; explicit1–4ports | 20k frequencies;100k pairs;4,096UTF16 numeric tokens;40MiB JSON+CSV |
- Correct repository-relative paths; preserve duplicate path positions if the receiving task needs them.
- Review invalid source-line diagnostics and distinguish explicitly-unowned from unmatched.
- Re-export an unsupported Touchstone profile deliberately; do not delete reference, noise or version declarations blindly.
- Preserve raw tokens before plotting converted values; no browser-local conversion proves a working RF device.
References
- CODEOWNERS changed-file grouping request
First-person demand read2026-10-07; offline access verification remains outside scope.
- S-parameter CSV plotting question
First-person demand read2026-10-07; matrix extraction supports the stated handoff, without circuit validation.
- GitHub CODEOWNERS syntax
Correctness reference read2026-10-07, not demand evidence.
- IBIS Touchstone2.1 specification
Includes1.0/1.1 compatibility; read2026-10-07. This tool declares a narrower physical-row S profile.
Tools in this category
Expand a tool to see its steps, options and supported formats, then open its workspace.
CODEOWNERS changed-path routingResolve each supplied changed path against one selected CODEOWNERS snapshot, retaining the last valid rule, all declared owners and explicit ownership gaps.
Group changed paths by declared reviewer without accessing GitHub. Choose the intended branch snapshot yourself; inspect skipped source lines and distinguish cleared owners from unmatched paths.
Steps
- Choose the intended CODEOWNERS snapshot, then enter repository-relative changed paths, one per line.
- Run routing; inspect skipped rule count, declared owners, explicitly unowned paths and unmatched paths.
- Download full JSON/CSV with source provenance and all owner groups before using the handoff.
Available options
- Protect CSV formula-like text
- On by default
Capabilities and limits
- One explicitly selected UTF-8 CODEOWNERS file or paste up to 2 MiB, plus a newline-delimited changed-path list up to 2 MiB. Choose the intended snapshot; .github/root/docs priority and pull-request base branch are not inferred.
- Up to 10,000 rule lines, 10,000 paths, 1,024 UTF-16 units per pattern/path and 100 owners per rule. Valid rule count × supplied path count must be at most 2,000,000. Complete JSON and CSV together must fit 32 MiB; combined limits apply.
- Case-sensitive GitHub-style *, ?, whole-component **, root paths and directory patterns. Last matching valid source line wins. Owners on the same line stay together; an empty owner list explicitly clears ownership. Duplicate paths remain in order. User, team and email strings are declarations; account existence, access and review requests remain unverified.
- GitHub-invalid negation, character ranges and escaped leading # lines are skipped with full original lines, reasons and UTF-8 byte offsets. Legal escaped patterns, including escaped spaces, fail the whole batch as Unsupported. Absolute/backslash/dot-dot/control/ambiguous empty path segments reject; source and path text remain inert.
- The complete report includes original sources and hashes, valid/invalid rules, every supplied path and owner grouping. Table previews 200 rows, clipping long cells to 2,000 UTF-16 units. Above 20,000 report characters, copying gives a labelled preview; full downloads retain all rows. Cancellation or an error publishes no partial routing.
Touchstone S-parameter matrix reportRead one declared 1–4-port Touchstone S-parameter file into a complete matrix CSV/JSON, preserving raw numeric tokens, option provenance and source positions.
Export every Sij measurement in the correct port order before plotting. Inspect complex values, magnitude, phase and dB alongside the original RI, MA or DB tokens; no device or circuit is simulated.
Steps
- Select the ASCII .sNp source and explicit port count; confirm the option line and physical matrix rows.
- Inspect frequency, reference, representation and matrix coordinate summaries.
- Download all complex pairs as JSON/CSV, retaining raw measurements before plotting or further analysis.
Available options
- Explicit port count
- 1 port · 2 ports · 3 ports · 4 ports
- Protect CSV formula-like text
- On by default
Capabilities and limits
- One ASCII file or paste up to 10 MiB with explicit 1–4 ports. A recognized .sNp filename must match the selected port count. Up to 20,000 strictly increasing frequency points, 100,000 complex pairs and 4,096 UTF-16 units per numeric token; complete JSON/CSV together up to 40 MiB. Combined limits apply.
- Visible Version1.0/1.1 compatible S-parameter profile: exactly one pre-data # option line. An empty # means GHz, S, MA, R50. A positive finite scalar R may occur in any supported option order. Missing # is invalid; second/late options, per-port R, Y/Z/G/H, noise records and 2.x keywords are Unsupported profile.
- Physical rows: 1/2-port points keep frequency and every complex pair on one line; 3/4-port points use one matrix row per physical line, frequency only in the first row. Other valid wrapping is Unsupported rather than labelled a standard error. LF/CRLF, inline ! comments and original ASCII source are preserved; standalone CR and non-ASCII input are unsupported.
- Two-port source order is S11,S21,S12,S22; 3/4-port order is matrix-row order. Full raw token strings and line/column/byte coordinates accompany derived float64 real, imaginary, magnitude, normalized phase degrees and 20log10 magnitude dB. Exact zero has phase0 and explicit string -Infinity dB. Nonfinite input, float64 overflow/underflow and unsupported ranges reject rather than fabricate values.
- Complete JSON preserves option defaults, reference, source hash, comments and every matrix pair. CSV retains all frequency/pair rows and safe spreadsheet text. Table previews 200 pairs, clipping cells to 2,000 UTF-16 units; above 20,000 report characters, copy is a labelled preview. No RF calibration, circuit performance, reciprocity or device validation.