# cee

This is the root of the of the EnvisionWeb client component.

Assuming that the EnvisionWeb client component has been imported into the variable `cee`, members of the global module may be referenced using the `cee` prefix, e.g.:

    var myVec = new cee.Vec3(0,0,1);
    var mySession = new cee.CloudSession();

The global component contains general classes like Viewer, View, Model, Overlay, etc. It also has all the base classes like Color3, Color4, Vec3, Mat4, Ray.

The following sub-modules exist:

- Remote Model (cee.ug): Remote Model supporting a full post processing session with a model on a remote server. The CAE model with its results is kept on the server and only the data needed for displaying the model is progressively streamed to the client. Handles FEA and CFD models, and has features like isovolumes, particle traces, cutting planes (all computed on the server).
- Constant Remote Model (cee.cug): Efficient and scalable streaming of pre-defined CAE model configurations. The server is a stateless REST API based server with very low resource usage and is easy to load balance. The streaming starts immediately when a model is opened, no matter the size of the model. Like the RemoteModel, data is sent to the client using 3D Progressive Object Streaming. The model needs to be converted to the CUG database format (using the included CugComposer command line utility) before it can be streamed.
- Unstruct Surface Grid (cee.usg): Client side (in browser) FEA model for surface elements. Suited for streaming/monitoring as well as transient animations with very fast updates. Supports all result mappings (per node, per element, per element node), all result types (scalars, vectors, displacements and rigid body transformations), all draw styles (surface, surface mesh, outline, lines, points), multiple states, adaptive geometries. Supports any number of nodes per element.
- Stream Model (cee.vs): Client side (in browser) streaming model designed to work in pair with the Visualization Streamer Service (VizService) to which it requires a live connection. It handles fast and efficient streaming of 3D data to web while being specifically tailored towards showing CAE visualizations.
- Geometry (cee.geo): Client side (in browser) geometry model capable of handling a very large number of parts (300k+) with very fast updates when changing part settings.
- Markup (cee.mrk): Markup model with support for rendering labels and more simple geometry. Useful for creating annotations and other markup of the 3d model.
- Utilities (`cee.utils`): Various helper classes for the components above.

Enumerations

- ClippingCriteria
- ColorTable
- EyeLift
- HighlightMode
- ModelType
- MouseWheelZoomAndWalkBehavior
- NavigationCubeItem
- NavigationType
- OperatorEventStatus
- OverlayItemPosition
- ProjectionType
- StandardOperator
- TextureMagFilter
- TextureMinFilter
- TextureWrapMode
- ViewLayoutMode
- WBOITMode

Classes

- `AmbientOcclusion`
- `Background`
- `BoundingBox`
- `Camera`
- `CameraAnimationSpinModel`
- `Clipping`
- `CloudSession`
- `Color3`
- `Color4`
- `ColorTableFactory`
- `KeyboardModifiers`
- `Logger`
- `Mat4`
- `Model`
- `Navigation`
- `NavigationOperator`
- `Operator`
- `OperatorStack`
- `Overlay`
- `OverlayColorLegendContinuousDomain`
- `Plane`
- `Range`
- `Ray`
- `RaySphereIntersector`
- `ScalarMapperContinuous`
- `ScalarMapperContinuousDomain`
- `ScalarMapperContinuousPiecewise`
- `ScalarMapperFilledContours`
- `ScalarMapperFilledContoursUniform`
- `SnapPointPicker`
- `Texture`
- `TextureOptions`
- `Vec2`
- `Vec3`
- `View`
- `Viewer`
- `ViewerOptions`

Interfaces

- `AssertFailedHandler`
- `CameraAnimation`
- `CameraConfig`
- `CameraViewChangeHandler`
- `ClientCoord`
- `ClientCoordList`
- `Color3Like`
- `Color4Like`
- `ColorLegendClickedHandler`
- `ModelBoundingBoxOptions`
- `MouseButtonConfig`
- `MouseNavigationChangedHandler`
- `NavigationConfig`
- `NavigationCubeViewConfiguration`
- `NavigationMouseButtonConfig`
- `OperatorConfig`
- `PickHandler`
- `PickHandlerData`
- `PlaneLike`
- `ProcessableModel`
- `ScalarMapper`
- `Vec2Like`
- `Vec3Like`

Functions

- `setAssertFailedHandler`

Modules

- `cug`
- `geo`
- `mrk`
- `ug`
- `usg`
- `utils`
- `vs`

## Functions

### setAssertFailedHandler

`cee.``setAssertFailedHandler`(handler)

  Arguments: | handler (`AssertFailedHandler`) – None

  Set a custom code assert failed handler.

  If specified, any failing assert conditions internally in the HOOPS Envision Web code will trigger this callback.

  If not specified, the failed assert will be logged and then an exception will be thrown (potentially stopping the app).

  Return type: | void

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

Your Docs generative AI assistant. Ask me anything about HOOPS Envision for Web or choose a sample question below to start a conversation:

What is HOOPS Envision for Web?
What are the latest release notes for HOOPS Envision for Web?
How do I start evaluating HOOPS Envision for Web?
How do I write my first sample application?
How can I get assistance?

HOOPSY may store conversations according to OpenAI's policy. Responses may not always be accurate.

HOOPSY is thinking...