Scientific visualization

Bring the file.
See the physics.

SynapseX is building one path from real scientific files to figures that state their units, their source and what was reduced. The gallery below is not a set of screenshots: every tile is drawn live in your browser.

Illustration of the product
11
kinds of scientific view, drawn live on this page
6
of them live in SynapseX Chat today
16
format families on the reader roadmap
0
screenshots on this page
The real-file pipelineIn development

From the file on your disk
to a figure you can defend.

This is what we are building. It is not running yet, which is why nothing below moves.

  1. 01

    Bring the file

    Simulation output, an instrument file or a trajectory, as it left the code or the detector. No conversion on your side.

  2. 02

    A reader opens it in a sandbox

    A reader for that format runs in an isolated sandbox and lists what is inside: grids, fields, units, time steps.

  3. 03

    One dataset model

    Whatever the format, the content becomes one description: quantities, axes, units, meshes and time.

  4. 04

    The planner proposes a view

    From the shape of the data and your question: a slice, an isosurface, streamlines, an event display. You can overrule it.

  5. 05

    Reduced on the server, drawn in the browser

    The server cuts the data down to what the view needs. The browser draws that and stays interactive.

  6. 06

    A figure with its provenance

    The figure states its units, colour map and range, the source file and its hash, and the reduction applied.

Provenance

A picture
is not yet a result.

Units
The quantity and its units, on the axes and on the colour bar.
Colour map and range
Which map, which limits, linear or logarithmic. A picture can be made to say anything by moving them.
Source and hash
The file the figure came from and its SHA-256, so the same file can be found again.
Reduction applied
The slice, the downsampling or the threshold. What you are not seeing is part of the result.
your_run.h5HDF5 · openPMDNext
Electron densityslice z = 0 · every 4th cell0204060200-20x (µm)y (µm)log10²⁵10²⁴10²³10²²m⁻³
quantity
electron density
units
m⁻³
colour map
sequential, logarithmic
range
10²² to 10²⁵, on the colour bar
source
your_run.h5
sha256
the file's own hash
reader
HDF5 with openPMD
reduction
slice at z = 0, every 4th cell

An illustration: a synthetic field drawn in your browser, with placeholder values. Not a real file. Point at a line of the stamp to see what it governs. The tiles above already carry a short form of it under each picture.

Capability ledger

What renders today.
What we are building.

Two states and nothing else. Live today means it renders now in SynapseX Chat. In development means it is on the build list and not available yet.

Rendering in Chat

  • Surfaces and vector fields
    From a function or a field you describe, with integrated streamlines.
  • Molecules, crystals and proteins
    From structure text: MOL and SDF, CIF, PDB.
  • Point clouds in 3D
    Embeddings projected onto their principal components.
  • Device topologies, code lattices and diagrams
  • Maps
    From GeoJSON.
  • Toolpaths
    From G-code.
  • Charts and typeset mathematics

Real-file pipeline

  • Upload of scientific containers
    Simulation output, instrument files and trajectories, without conversion.
    Next
  • Readers in an isolated sandbox
    One reader per format, listing grids, fields, units and time steps.
    Next
  • One dataset model
    Quantities, axes, units, meshes and time, whatever the format.
    Next
  • A planner that proposes the view
    From the shape of the data and the question asked. You can overrule it.
    Next
  • Reduction on the server
    Slices, downsampling and surface extraction before anything reaches the browser.
    Next

New kinds of view

  • Volume rendering
    Next
  • Time: trajectories and scrubbing through steps
    Next
  • Event display for particle physics
    Next
  • Spectrograms with linked audio
    Next
  • Multi-dimensional image stacks
    Next
  • Medical volumes
    Viewing only. No measurement and no diagnostic use.
    Next

Trust

  • A provenance stamp on every figure
    Units, colour map and range, source file and SHA-256, reduction applied.
    Next
  • Figures you can re-open
    Each figure keeps the record needed to draw it again from the same file.
    Next
  • Export for publication
    Vector output that carries its provenance with it.
    Next
Formats

The order
the readers are built in.

Open formats first, the ones that hold the most science. Real files from design partners can change the order.

Read in Chat today

As text you paste or attach. No reader to wait for.

  • PDB

  • MOL · SDF

  • CIF

  • OpenQASM

  • G-code

  • GeoJSON

  • CSV · TSV

  • JSON

Readers, in the order they are built

In development
  1. 01

    First

    Between them, these hold most simulation output.

    • VTK

      Meshes and the fields on them.

    • HDF5 with openPMD

      Particles and fields from plasma and accelerator codes.

    • NetCDF and Zarr

      Gridded data, in one file or in chunks.

  2. 02

    Next

    Structures in motion, events, the sky and sound.

    • PDB and mmCIF with XTC and DCD

      Structures and molecular-dynamics trajectories.

    • Cube

      Electron densities and orbitals.

    • ROOT and HepMC

      Detector events.

    • FITS

      Astronomy images and tables.

    • WAV

      Signals with their audio.

  3. 03

    Then

    Weather, microscopy, imaging and scene formats.

    • GRIB

      Weather and forecast fields.

    • GeoTIFF

      Georeferenced rasters.

    • OME-Zarr and TIFF

      Microscopy stacks.

    • MRC

      Cryo-EM maps.

    • DICOM and NIfTI

      Medical volumes, for viewing only.

    • CGNS

      Flow solutions on structured and unstructured grids.

    • OpenVDB

      Sparse volumes.

    • USD

      Scenes and assemblies.

Limits

What we will not
pretend about.

  • Limits

    Big data is reduced on the server.

    A browser cannot hold simulation output that runs to gigabytes. The server reduces it and the figure says how. We quote no file size, point count or frame rate until it has been measured.

  • Limits

    Medical volumes are for viewing.

    In a research context only. No measurement, no diagnosis. SynapseX is not a medical device.

  • Limits

    Synthetic stays labelled.

    A picture that does not come from your data says so in its own provenance line, as every tile on this page does.

Request a scientific data reader

Tell us the file.
We will tell you when it reads.

Each request is counted toward which reader is built next. Tell us the format, how large the files usually are and what the figure has to show. No file is uploaded at this stage.

Metadata only: no file is uploaded. We use your email to reply about this request and nothing else.

FAQ

Visualization,
answered plainly.

No. Every tile is drawn live in your browser from synthetic data generated on the spot. None of it is a result, and each tile says so in the line under the picture.

In SynapseX Chat today: surfaces and vector fields with streamlines, molecules, crystals and proteins from structure text, 3D point clouds, device topologies and code lattices, maps from GeoJSON, toolpaths, diagrams, charts and typeset mathematics. They render on the web and in the desktop app.

Not yet for scientific containers such as VTK, HDF5, NetCDF or FITS. Reading those files is the pipeline in development described on this page. Today Chat reads structure and tabular text: PDB, MOL and SDF, CIF, OpenQASM, G-code, GeoJSON, CSV, TSV and JSON.

A browser cannot hold a simulation output that runs to gigabytes, so the reduction happens on the server: slicing, downsampling, extracting a surface. The browser draws the reduced data, and the figure states what was reduced. We quote no size limits until they are measured.

Units, the colour map and its range, the source file with its SHA-256, and the reduction that was applied. A figure that cannot state these is not shown as a result.

No. Medical volumes are for viewing in a research context only. SynapseX is not a medical device and makes no measurement or diagnostic claim.

VTK, HDF5 with openPMD, and NetCDF or Zarr come first, because they cover most simulation output. Trajectories, detector events, astronomy and audio follow, then weather, microscopy and medical formats. Real files from design partners can change the order.

Request early access and tell us the format, the size of the files and what you need to see. That is what decides which readers are built first.

Show us the file
that is hard to see.

We are choosing the first readers with design partners. Tell us the format, the size of the files and the question you need the figure to answer.

Tiles on this page use synthetic data. The real-file pipeline is in development.

Every picture on this page is drawn from synthetic data generated in your browser and is not a scientific result. Capabilities marked in development are not available yet and carry no delivery date. Format names are used to identify open file formats. Medical volumes are for viewing in a research context only: SynapseX is not a medical device and makes no diagnostic claim.