Exporting Data
Clavis supports standard scene screenshots, structured analysis exports, path-traced publication renders, and trajectory videos.Unified Export Center
Open the RENDER tab to use the Export Center. It presents only the actions that apply to the loaded scene and locks the remaining actions while an export is active.
Single-frame scenes omit frame-sequence and movie actions instead of showing a permanent “Requires multiple frames” error. When a trajectory exists but a specific export path is unavailable, the action explains the actual requirement.
Image Export (PNG)
Press Ctrl/Cmd + E or click the export button to save a PNG of the current 3D view.- Captures visible atoms, cages, rings, guests, H-bonds, axes, and PBC box
- Uses the current camera pose and, when Preview Mode is active, the configured render-frame crop and output dimensions
- Honors layer visibility and opacity settings
- Excludes preview-only guide artifacts such as yellow frame guides, focus markers, light-position indicators, and drag handles
Render Frame Export
The RENDER tab includes configurable output width/height and common aspect presets. Preview Mode displays a centered render frame overlay so you can compose a figure before exporting. Drag Frame mode uses the exact drawn crop, and output dimensions follow that crop aspect without increasing the current pixel area. Standard PNG export and path-traced still export now share this render-frame contract, so a 4:5 preset or user crop produces a matching output image instead of the raw browser viewport.Data Export
After running analysis, export results as CSV or JSON.CSV Export
CSV files include one row per detected cage with fields such as:JSON Export
JSON export preserves structured cage, ring, occupancy, and trajectory data for programmatic use. Trajectory rows include their algorithm and both zero-basedframeIndex and one-based display frame, preventing results from different algorithms or frame conventions from being merged silently.
Batch and Video Export
For trajectories, Pro workflows can export frame ranges and MP4 videos. Choose start/end frame, step, FPS, quality, loop count, and WebGL or path-traced render mode. The CPU still-image fallback is for still PNG export only; video export remains WebGL or GPU path-traced. FFmpeg runs in the browser through WebAssembly for MP4 encoding. Frame-sequence and movie exports capture frames sequentially. If Clavis cannot load a frame, capture its image, or prepare an active TRACE/H-bond overlay, it stops and reports the failing stage instead of producing a silently incomplete archive or movie. On exit—success, cancellation, or failure—the exporter restores the original frame and the cage, ring, H-bond, and occupied-guest visibility state that was active before export.Blender Bundle Export
Pro users can choose Blender bundle in the Export Center to download a versioned.claviscage.zip. Import the archive as one bundle; the JSON files inside it are consumed by the ClavisCage Blender extension.
Import the bundle in Blender
- Keep the downloaded
.claviscage.zipintact. Do not extract the archive or select one of its JSON files. - In Blender, open the 3D Viewport sidebar and select the ClavisCage tab.
- Under Input → ClavisCage Bundle, select the
.claviscage.zipfile itself. - Click Import Web Bundle. The extension validates both JSON members before replacing the ClavisCage scene.
- Adjust the restored molecule, residue, CHILL+, H-bond, cage, PBC, material, lighting, and render controls as needed, then save your own
.blendfile.
.claviscage.zip rather than the extracted folder. The Blender file picker should point to the archive itself.
What the JSON files do
You may inspect these files to audit what was exported, but editing them is not a supported public editing API. The importer deliberately requires an exact, internally consistent schema and rejects missing or extra archive members, unsupported schema versions, invalid indices, malformed coordinates, and inconsistent styles. Make presentation changes after import with the Blender extension controls instead.
The web exporter writes schema v2. Its
cageAnalysis object identifies trace, htr, or grade; records the zero-based source frameIndex; distinguishes total and currently visible cages; stores the relevant cutoff/angle/planarity parameters; and carries only geometry owned by that algorithm and frame. Blender restores it through editable scene and overlay controls; the file is not a pre-rendered image or a generated .blend.
The Blender extension also accepts legacy schema v1 bundles, where the cage field is HTR-specific. Schema v1 cannot express TRACE or GRADE provenance. Both versions are intentionally offline and single-frame: they do not contain a trajectory or provide live browser-to-Blender synchronization. When cached analysis belongs to another frame, Clavis omits it and records a warning rather than exporting stale results.