![]() It must be noted that headless support is a rapidly evolving area and changes are expected in coming months. When it comes to headless operation, there are alternative APIs that an application can use to create the OpenGL context that avoid this dependency on the window system (or X server for the sake of this discussion).Ĭurrently, ParaView supports two distinct APIs that are available for headless operation: EGL and OSMesa (also called Offscreen Mesa). Thus, they are designed for non-headless operation. Traditionally, OpenGL implementations are coupled with the window system to provide an OpenGL context. ![]() Nonetheless we use this naming scheme as it has been prevalent. Despite the names, H/W doesn't necessarily imply use of GPUs, nor does S/W imply exclusion of GPUs. S/W currently includes Mesa3D – a software implementation of the OpenGL standard. The runtime libraries needed for these are available on the system. H/W includes OpenGL implementations provided by NVIDIA, ATI, Intel, Apple and others which typically use the system hardware infrastructure for rendering. Many vendors provide implementations of this API, including those that build GPUs.įor sake of simplicity, let's classify OpenGL implementations as hardware (H/W) and software (S/W). OpenGL is an API specification for 2D/3D rendering. Both version are available as a binary from our downloads page. Headless support requires special builds of ParaView which are not compatible with standard build options. Thus ParaView binaries available from support these modes. Onscreen and offscreen support is built by default. In addition, on Linux, it implies that the rendering does not require an accessible X server nor will it make any X calls. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |