Browser · your own project

Analyse a copy in your browser and retain its export.

Import processed data, review the available conditions and export the project together with the report. A web account is not Windows copy registration.

Guide reviewed · 7 November 2026 · Calculation times depend on data and hardware.

  1. Sign in and protect earlier work

    Sign in with your laboratory account. Before importing another sample, download the current project or deliberately manage its recoverable draft. Create a copy whose name distinguishes sample, ramp and review.

    Before continuing: A signed-in session, local draft and cloud-saved project are different states. A download is a backup; another tab is not.

  2. Import the complete processed folder

    Select the Bruker folder with its subfolders: 1r with procs and acqus, or 2rr with procs/proc2s, acqus/acqu2s and its lists and evidence. Choose the exact acquisition and pdata in the selector; alternative processings remain separate.

    Before continuing: fid and ser require prior processing; the browser does not transform those raw data. 2rr padding rows are not acquired observations.

  3. Review rows, gradients and encoding

    Read Source, parameters and detection. Under Review rows and gradients check correspondence and documented units. Do not conflate G/cm, T/m, percent and fraction. When the list already includes waveform area, do not apply that correction twice.

    Before continuing: The web does not offer explicit SI b-list import here. Do not paste b values into gradient fields or turn a discrepancy into assumed percentages.

  4. Select signals and their own conditions

    Mark peaks in this sample’s spectrum and review ppm, window and signed curve. Check standard, calibration, temperature and model before a new fit. A standard failing its checks retains the corrected-result blocker.

    Before continuing: Do not attribute every Windows TTMS-transfer or experimental-AI feature to the browser. A no-standard diagnosis, if chosen, must be retained as a separate scenario.

  5. Calculate only reviewed inputs

    Run the available fit after resolving the identified findings. Review excluded points and reasons, prediction and residuals. If a new calculation fails, retain and distinguish the previous result rather than presenting it as newly calculated.

    Before continuing: A fitted D does not itself authorise Rh, Mn, Mw or dispersity: conditions or assumptions are absent when the report says so.

  6. Export, check and reopen

    Download project, report and CSV from the reviewed result. Check sample, ramp, date/review, factors, units, numbering and reasons for missing values. Switch ES/EN for presentation without recalculating the result. Reopen a downloaded copy to verify preservation.

    Before continuing: Mobile tables may require internal scrolling. Browser display and printing are not validation of PDF pagination on every device.

BEFORE CALCULATION · DOSY 2rr

Correct reading is not enough to calculate D.

Input review separates binary format, row correspondence and physical encoding. A matrix can be readable yet still not support a reliable diffusion calculation.

procs · proc2s · 2rr

Dimensions, XDIM blocks, numeric type, byte order and NC_proc scale. An axis displayed by procs does not replace a physical b vector.

acqus · acqu2s

Acquisition status, increment count, timings and GPNAM/GPZ. These arrays use zero-based indices. Pending acqu is not a silent substitute for acquisition-status acqus.

pulseprogram · gpnamN

Actual program instructions identify the active gradient; comments do not configure it. GPNAM supplies the declared shape, while gpnamN retains its samples and area factor when archived. There is no need to type an already-declared shape.

Difframp · difflist · gradient_calib

List, amplitude and shape are compared with the applicable calibration. Standard Bruker difflist includes waveform area; it is neither a percent nor to be shape-corrected twice. A custom list requires its documented convention.

  1. Retain available evidence: program, shapes, lists and audita/auditp. If history links 2rr to another acquisition, resolve provenance before assigning current parameters to it. An optional file’s absence alone does not establish that the experiment is invalid.
  2. If shape, amplitude or list conflict, read the finding’s code, file and reason. Do not automatically set GPZ to 100%, substitute SINE for SMSQ, or copy another sample’s calibration to remove it.
  3. A row confirmation does not resolve a physical contradiction. On Windows an explicit b list needs provenance and review for this exact input. The web laboratory does not offer that route here; do not substitute gradient fields for it.
  4. Changing files, path, processing, list or declaration invalidates the dependent review. Repeat it before calculation or export of a new calculation. Historical results remain historical: opening them does not reauthorise or recalculate them.

If the conflict cannot be resolved from the available data, retain the diagnosis and obtain a coherent export. Do not invent b or interpolate a missing acquisition; padding rows are never fitted.

WHEN COMPLETE

Your result should be reopenable and explainable.

Retain source, project, review, recipe, factors, findings and report. If a criterion fails, retain its reason too. Professional formatting and cross-application agreement do not replace scientific review.

Usage documentation; it neither runs calculations, changes projects nor experimentally validates a method. Historical screenshots in complete help retain their version and provenance.