AB1 VIEWER

AB1 viewer and Sanger validation for Mac

Open Sanger .ab1 and .abi traces, inspect chromatogram evidence, review FASTQ-backed calls, and keep QC notes attached to the construct instead of a detached screenshot or email thread.

Sanger mismatch review with coding impact in RayCrest MDS

OUTCOMES

What teams need from an AB1 file viewer

Open AB1 and ABI traces in context

Start from the expected construct so mismatch review has a real reference point.

Jump from mismatch to chromatogram evidence

Inspect the actual trace before deciding whether a change is real or noise.

Use FASTQ support when Sanger is not enough

Review read support and depth without leaving the same validation workflow.

Keep the decision with the construct

Store notes, pass/fail calls, and follow-up context where teammates can reuse them.

FEATURE WALKTHROUGH

How RayCrest handles Sanger and FASTQ validation

AB1 mismatch review with coding impact

Open and review AB1 traces against the expected construct

RayCrest acts as Sanger sequence analysis software, not just as a passive viewer, because the trace is attached to the construct you are actually validating.

  • Import verified .ab1 and .abi files.
  • Detect mismatches against the expected sequence automatically.
  • Keep coding-impact context nearby while reviewing the call.
Chromatogram viewer with read, reference, and quality context

Jump from mismatch to chromatogram evidence

The fastest way to trust a call is to look at the evidence that produced it while the construct context is still on screen.

  • Use the chromatogram viewer to inspect the exact base under review.
  • Compare reference, observed read, and quality score side by side.
  • Record notes while the evidence is visible.
FASTQ evidence with depth and allele-fraction tracks

FASTQ support and QC context in the same place

When one trace is not enough, RayCrest lets you inspect FASTQ-supported calls in the same validation workflow.

  • See how many reads support a flagged base.
  • Distinguish low-support noise from convincing support.
  • Keep the FASTQ viewer tied to the same construct and decision history.
Construct-linked QC history across multiple runs

Construct-linked decision history

The point of a good validation workflow is not just to inspect evidence once. It is to keep the decision, rationale, and follow-up attached to the construct.

  • Store pass, fail, or flagged outcomes with the construct.
  • Review conflict and coverage context across runs.
  • Hand the result to a teammate without rebuilding the story.

TECHNICAL DETAILS

Verified validation inputs and workflow notes

Supported validation inputs
  • Verified Sanger inputs: .ab1 and .abi.
  • Verified FASTQ inputs: .fastq, .fq, and .fastq.gz.
  • One modality is imported per batch so the review flow stays predictable.
What makes this more than a viewer

RayCrest is built to help teams decide, document, and hand off the result, not just inspect a trace image once.

  • Mismatches are reviewed against the expected construct.
  • Chromatogram and FASTQ evidence stay attached to the same construct record.
  • QC notes and outcomes remain available for later review.

WORKFLOW + OUTPUTS

From imported trace to saved decision

Typical workflow

  1. Import

    Add Sanger .ab1/.abi traces or FASTQ runs and attach them to the expected construct.

  2. Inspect

    Jump through mismatch calls with chromatogram or FASTQ evidence at the base under review.

  3. Decide

    Record pass, fail, or flagged outcomes with notes so the evidence trail is preserved.

Outputs

  • Evidence-linked Sanger and FASTQ review records
  • Construct-linked QC notes and outcomes
  • Clear handoff context for teammates or writeups
  • Direct path into repeatable protein MSA when needed

RELATED PAGES

Connect validation to the rest of the workflow

Use RayCrest as your AB1 viewer and validation workflow

Request beta access if you need chromatogram-backed decisions, FASTQ support, and construct-linked QC history in one Mac app.