I found that when setting the intensity parameter on lights, anari-ospray would set the intensityQuantity to OSP_INTENSITY_QUANTITY_IRRADIANCE, which would correspond to units of W/m^2. According to the specs, intensity is however supposed to be in W/sr, which would correspond to OSP_INTENSITY_QUANTITY_INTENSITY. Not sure if this is deliberate, or a bug? (With irradiance being used, the light intensity oddly depends on model size, though.)

These are a couple of fixes to make the superbuild run more smoothly for me. As I'm on ARM Mac, I need to build TBB and Embree from source, so I added cmake options for that.

I had some issues with adding the (meta) project itself as an external dependency, as is done by the superbuild script. In particular, it would try to build the device library in-source, which is however deactivated by the project. I fixed that by specifying a BINARY_DIR inside the current build dir, but I'm not sure if this is desirable. That way, the project builds successfully for me, but solving the issue this way might be a bit controversial, so just let me know if you want this solved differently / want me to use different paths / naming conventions etc.

In regards to the latter, the docs say that if SOURCEDIR is specified cmake will deduce the other variables from that (cf. https://cmake.org/cmake/help/latest/module/ExternalProject.html, "If any of the above ..._DIR options are not specified, their defaults are computed as follows. [..]"), but I found that (seemingly) this is not the case, at least with my cmake version (which is 3.20.3).

Looks like the status has changed on what is implemented in v0.2.

• Samplers appear to be implemented
• (un)mapping of Arrays appears to be implemented
• Anything else that was reported as not implemented yet ?

Currently in the process of installing the latest anari-ospray and will test the above.

Hello, I am having problems running the anari-ospray back end. I get the following error when I try to run.

login4.frontera(1070)$ anariTutorialCpp 
initialize ANARI......loaded debug library!
#ospray: INVALID device --> could not open module lib ospray_module_cpu: /work2/01197/semeraro/frontera/OpenVKL/buildgcc/install/lib64/libospray_module_cpu.so: cannot open shared object file: No such file or directory
#ospray: INVALID device --> Could not find device of type: cpu.  Make sure you have the correct OSPRay libraries linked and initialized.
TERMINATING DUE TO UNCAUGHT ANARI EXCEPTION
terminate called after throwing an instance of 'std::runtime_error'
  what():  OSPRay not initialized correctly!
Aborted

I have set ANARI_LIBRARY=ospray. The framework seems to be looking for ospray_module_cpu.so in OpenVKL/buildgcc/install/lib64. This is the wrong directory. I have included the correct location in the LD_LIBRARY_PATH environment variable (OSPRay/buildgcc/install/lib64). I have no idea why it is looking in the OpenVKL directory instead of OSPRay. I must have set up the environment incorrectly. Can you shed some light on the problem.

I found that apps using anari-ospray crash when the environment variable OSPRAY_LOG_LEVEL was set. That's because anari-ospray installs a custom (user-settable) status function which is however NULL when the user did not set it as a device parameter. The proposed commit will default-initialize that status function to simply print the status messages to stderr, or to the device's default status function set by the user via anariLoadLibrary (if the latter is not NULL).

On macOS, with add_library(MODULE ...), cmake creates an .so file instead of using the ending .dylib. ANARI-SDK does not parse that correctly on dlopening the device library, but instead expects a .dylib on macOS.

For some context, also see this issue here: https://gitlab.kitware.com/cmake/cmake/-/issues/21189

Changing the output target type to SHARED was the easiest fix (also what the ANARI example_device does) . Alternatively, one could also use CMAKE_SHARED_MODULE_SUFFIX.

As another alternative, I could probably also push for ANARI parsing this correctly in the first place. Just let me know which option you prefer.