![]() The enum type OSPDataType describes the differentĮlement types that can be represented in OSPRay valid constants are However, if the stride should be calculated, then an ordering inĭimensions is assumed to disambiguate, i.e., Than byteStride1, which is equivalent to a transpose. Stridesĭo not need to be ordered, i.e., byteStride2 can be smaller If byteStride is zero it will beĭetermined automatically (e.g., as sizeof(type)). (per dimension) is given in bytes with byteStride and canĪlso be negative. The distance between consecutive elements The data is arranged in threeĭimensions, with specializations to two or one dimension (if some The number of elements numItems must be positive (thereĬannot be an empty data object). Will remain valid for the duration that this data array is being used. The calling program guarantees that the sharedData pointer The call returns an OSPData handle to the created array. OSPData ospNewSharedData ( const void *sharedData, OSPDataType, uint64_t numItems1, int64_t byteStride1 = 0, uint64_t numItems2 = 1, int64_t byteStride2 = 0, uint64_t numItems3 = 1, int64_t byteStride3 = 0 ) Or are recorded to be later queried by the application via These error codes are either directly return by some API functions, ![]() There is not enough memory to execute the The following errors are currently used by OSPRay: Possible error codes, i.e., valid named constants of type Specified through ospInit or manually set device Note that these environment variables take precedence over values osp:load-modules, can be a comma separated list of “ OSPRAY_”): Environment variables interpreted by OSPRay. Variables for easy changes to OSPRay’s behavior without needing toĬhange the application (variables are prefixed by convention with OSPRay’s generic device parameters can be overridden via environment OSP_DEVICE_VERSION OSP_DEVICE_VERSION_MAJOR OSP_DEVICE_VERSION_MINOR OSP_DEVICE_VERSION_PATCH OSP_DEVICE_SO_VERSION Environment Variables Properties (attributes about the device, not parameter values) The following function can be used to get these device-specific Order to do enhanced validation of what device was loaded at runtime. OSPRay allows applications to query runtime properties of a device in Number of explicit calls to ospDeviceRetain. OspNewDevice, ospGetCurrentDevice, and the Only decrement the reference counts that come from Reference held by the current set device should be handled by Only be used with reference counts that the application tracks: removing OspDeviceRetain and ospDeviceRelease should Internally has its reference count incremented. When a device is set as the current device, it When a device is created, its reference count is initiallyġ. If there is no current device set, this will return an invalid Handle, so applications must use ospDeviceRelease whenįinished using the handle to avoid leaking the underlying device object. Note this API call will increment the ref count of the returned device Set as the current device, it does not need to be set as current again. If changes are made to the device that is already Respond to OSPRay API calls, where users can set/change parameters and This function returns the handle to the device currently used to Once parameters are set on the created device, the device must be If set to 1 0 disables binding omitting the parameter will let OSPRay Severity) are OSP_LOG_NONE, OSP_LOG_ERROR,īind software threads to hardware threads Parameters can be set on all devices: Parameters shared by all devices. Is exactly the same as ospSetParam, which is documentedīelow in the parameters section. Void ospDeviceSetParam (OSPObject, const char *id, OSPDataType type, const void *mem ) To how other objects are created and used by The second method of initialization is to explicitly create theĭevice and possibly set parameters. ![]() To hardware threads 0 disables binding default isĮquivalent to calling ospDeviceSet*(param, value) You the default cpu device Note if the device to be used Messages go valid values for dst are cerr andĭevice for OSPRay to create e.g., -osp:device=cpu gives osp:log-level=debug and enable debug output on osp:log-level=info and enable debug output on Warning messages through the message callback must have Set logging level valid values (in orderĮrror messages through the error callback, otherwise send “ -osp:”) are understood: Command line parameters accepted by OSPRay’sĭefault using all detected hardware threads The following parameters (which are prefixed by convention with Passed to ospInit are processed in order they are listed. It is important to note that the arguments For possible error codesĪnd Status Messages. OSPRay parses (and removes) its known command line parameters from OSPError ospInit ( int *argc, const char **argv )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |