Alexander Stukowski
Alexander Stukowski
I would like to discuss a suggestion for an API extension that could provide some performance benefits and reduce memory requirements of an application. Currently, OSPRay only provides the ``ospNewData``...
The ``QTimer`` and ``QSocketNotifier`` helper objects, created by the ``_notify_stream_qt()`` function as child objects of the global ``QApplication``, need to be discarded after use when leaving the Qt event loop....
I am wondering if there is a way to accomplish pseudo-color mapping for mesh surfaces with OSPRay? I need to visualize scalar quantities that are defined on a mesh's vertices....
**Bug summary** I came across [this code](https://github.com/AdaptiveCpp/AdaptiveCpp/blob/7041cdf31521571d1cc7aad4de6fe7dc27593317/include/hipSYCL/algorithms/numeric.hpp#L67C1-L67C90) in AdaptiveCpp, which makes me think that a wrong default identity value may be used for the ``sycl::maximum`` reduction: ```c++ HIPSYCL_ALGORITHMS_DEFINE_KNOWN_IDENTITY(sycl::minimum, std::numeric_limits::max()) HIPSYCL_ALGORITHMS_DEFINE_KNOWN_IDENTITY(sycl::maximum,...
## Description I would like to propose an extension to the GSD C API, which would allow an application to read data from GSD files stored as blob in memory...
### Required prerequisites - [X] Make sure you've read the [documentation](https://pybind11.readthedocs.io). Your issue may be addressed there. - [X] Search the [issue tracker](https://github.com/pybind/pybind11/issues) and [Discussions](https:/pybind/pybind11/discussions) to verify that this hasn't...
It would be very useful if OSPRay could support back-face culling for mesh faces in the future. What I am asking for is an option similar to [VisRTX's experimental `cullBackfaces`...
We would like to use OSPRay in our sci-vis application [OVITO](https://www.ovito.org) via the ANARI interface. OVITO has been integrating ANARI for final frame rendering since version 3.10 and the soon...
We observe a cylinder rendering issue in OSPRay 3.2.0, which seems to occur whenever the length of the cylinder exceeds a certain threshold. This is an animation showing a cylinder...
It looks like the implementation of `DebugDevice::newObjectHandle` is not thread-safe. So I was wondering: Does the debug layer fully support the `ANARI_KHR_DEVICE_SYNCHRONIZATION` extension (given the wrapped device does support it)?...