OutWit.Controller.Visualization.ParaView.Model 0.5.0

.NET 10.0

dotnet add package OutWit.Controller.Visualization.ParaView.Model --version 0.5.0

NuGet\Install-Package OutWit.Controller.Visualization.ParaView.Model -Version 0.5.0

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="OutWit.Controller.Visualization.ParaView.Model" Version="0.5.0" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="OutWit.Controller.Visualization.ParaView.Model" Version="0.5.0" />
                    

                            Directory.Packages.props

<PackageReference Include="OutWit.Controller.Visualization.ParaView.Model" />
                    

                            Project file

For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.

paket add OutWit.Controller.Visualization.ParaView.Model --version 0.5.0

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: OutWit.Controller.Visualization.ParaView.Model, 0.5.0"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

#:package OutWit.Controller.Visualization.ParaView.Model@0.5.0

#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.

#addin nuget:?package=OutWit.Controller.Visualization.ParaView.Model&version=0.5.0
                    

                            Install as a Cake Addin

#tool nuget:?package=OutWit.Controller.Visualization.ParaView.Model&version=0.5.0
                    

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

OutWit.Controller.Visualization.ParaView.Model

Shared data types for the OutWit.Controller.Visualization.ParaView controller — the OmnibusCloud headless ParaView renderer.

Type	Script type	Purpose
`ParaViewSceneRefData`	`ParaViewSceneRef`	The visualization package: state blob (+ digest, size), content-addressed attachments with logical paths, roles, file-series group and per-timestep association, runtime requirements, the producer's timeline, and the opaque package manifest.
`ParaViewAttachmentRefData`	—	One package file: blob, normalized logical path, SHA-256, size, role, series group, timestep indices, ordinal.
`ParaViewRuntimeRequirementData` / `ParaViewPluginRequirementData`	—	Producing ParaView version (+ provenance) and the non-built-in plugins the state requires.
`ParaViewOutputOptionsData`	`ParaViewOutputOptions`	View, size, format, transparency, and the frame selection.
`ParaViewFrameSelectionData`	—	Single / Range / All / Explicit timestep selection.
`ParaViewRenderTaskData`	`ParaViewRenderTask` (+ `Collection`)	One unit of distributed work: state, view, timestep, options and the task's minimal attachment subset. Internal to the controller.
`ParaViewRenderResultData`	`ParaViewRenderResult` (+ `Collection`)	One rendered output: task identity, image blob, validated dimensions, backend versions, duration.
`ParaViewValidationReportData`	`ParaViewValidationReport`	Outcome of `ParaView.Validate`: errors, warnings, subsetting fallbacks, package digest, resolved view / timeline / indices / size.

All types derive from OutWit.Common.Abstract.ModelBase, are [MemoryPackable(GenerateType.VersionTolerant)] with an explicit [MemoryPackOrder] on every member (append-only evolution), and implement Is/Clone.

Job document vocabulary (`paraview.*@1`)

The request and result types are published as [JobDocumentContract] types so non-.NET initiators — first of all the OmnibusCloud ParaView plugin — submit jobs through the native SDK's job request documents and read results back as value documents:

Type id	Type
`paraview.sceneRef@1`	`ParaViewSceneRefData`
`paraview.attachmentRef@1`	`ParaViewAttachmentRefData`
`paraview.runtimeRequirement@1`	`ParaViewRuntimeRequirementData`
`paraview.pluginRequirement@1`	`ParaViewPluginRequirementData`
`paraview.outputOptions@1`	`ParaViewOutputOptionsData`
`paraview.frameSelection@1`	`ParaViewFrameSelectionData`
`paraview.turntable@1`	`ParaViewTurntableData` (Model 0.2.0: optional camera orbit inside the output options)
`paraview.renderResult@1`	`ParaViewRenderResultData`
`paraview.validationReport@1`	`ParaViewValidationReportData`
`paraview.dataScene@1`	`ParaViewDataSceneData` (Model 0.3.0: bare data + presentation choices, composed on the fleet by `ParaView.Compose` into a `paraview.sceneRef@1`)

Documents/ holds the generated artifacts (paraview.schema.json, paraview_documents.hpp, paraview_documents.py), regenerated on every build by OutWit.Cloud.Documents.Generator and verified in CI; they ship in this package under documents/. A C++ host (the ParaView plugin) vendors paraview_documents.hpp and composes, for example, RenderParaViewFrames(ParaViewSceneRef, ParaViewOutputOptions) from typed bindings; see the controller author guide.

Package invariants the controller enforces

Logical paths are relative, /-separated, without .., drive letters, URI schemes or absolute roots.
Every attachment declares size and SHA-256; the node verifies both while materializing.
The state refers only to logical package paths; the runner maps them under the task's package root.
The timeline comes from the state's TimeKeeper; TimestepValues on the scene reference is the producer's view of it.
TimestepIndices on an attachment are the indices at which the file is displayed; an empty list means "every timestep". A series member with an empty list makes its whole group ship to every task (a recorded fallback).

Product	Compatible and additional computed target framework versions.
.NET	net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed.

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

net10.0
- OutWit.Common (>= 1.3.2)
- OutWit.Common.MemoryPack (>= 1.1.4)

NuGet packages (1)

Showing the top 1 NuGet packages that depend on OutWit.Controller.Visualization.ParaView.Model:

Package	Downloads
OutWit.Controller.Visualization.ParaView Headless scientific visualization: safely executes OmnibusCloud ParaView packages (a saved .pvsm state plus content-addressed data attachments) and distributes independent rendering tasks across worker nodes. ParaView.Validate treats the state as untrusted input (hardened XML parsing, proxy allowlist, programmable-pipeline rejection, logical-path and plugin-requirement checks, size and resolution limits); ParaView.Split produces deterministic tasks per timestep, each carrying only the attachments its timestep needs (per-task attachment subsetting); ParaView.RenderFrame materializes a task's subset into an isolated package root and renders one output through the controller-owned pvpython runner on the software-rendering baseline; ParaView.SplitBatched + ParaView.RenderFrameBatch (0.5.0, FrameBatch) group consecutive outputs into chunks rendered by ONE pvpython process each — the state loads once, every output selects its timestep and camera move — so process startup, the dominant cost of a single frame, is paid once per chunk (the bundled animation scripts use it; the node benchmark measures the same shape); ParaView.Collect returns the ordered frame set. ParaView.Compose (0.3.0) composes a scene from bare data — one blob-referenced CalculiX .frd result plus colouring, colour map, representation and camera choices — on one node into a real saved state, so a result already in the cloud renders with no client-side packaging (RenderParaViewDataStill/Frames/Video). The ParaView runtime ships as per-platform Tier-2 assets, never inside the package.	1.4K

Package

Downloads

OutWit.Controller.Visualization.ParaView

Headless scientific visualization: safely executes OmnibusCloud ParaView packages (a saved .pvsm state plus content-addressed data attachments) and distributes independent rendering tasks across worker nodes. ParaView.Validate treats the state as untrusted input (hardened XML parsing, proxy allowlist, programmable-pipeline rejection, logical-path and plugin-requirement checks, size and resolution limits); ParaView.Split produces deterministic tasks per timestep, each carrying only the attachments its timestep needs (per-task attachment subsetting); ParaView.RenderFrame materializes a task's subset into an isolated package root and renders one output through the controller-owned pvpython runner on the software-rendering baseline; ParaView.SplitBatched + ParaView.RenderFrameBatch (0.5.0, FrameBatch) group consecutive outputs into chunks rendered by ONE pvpython process each — the state loads once, every output selects its timestep and camera move — so process startup, the dominant cost of a single frame, is paid once per chunk (the bundled animation scripts use it; the node benchmark measures the same shape); ParaView.Collect returns the ordered frame set. ParaView.Compose (0.3.0) composes a scene from bare data — one blob-referenced CalculiX .frd result plus colouring, colour map, representation and camera choices — on one node into a real saved state, so a result already in the cloud renders with no client-side packaging (RenderParaViewDataStill/Frames/Video). The ParaView runtime ships as per-platform Tier-2 assets, never inside the package.

1.4K

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last Updated
0.5.0	105	8/26/2026
0.4.0	329	8/25/2026
0.3.0	113	8/25/2026
0.2.0	127	8/22/2026
0.1.0	302	8/19/2026