We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
valueRange
FLOAT64_BOX1
I have discovered another small problem:
When I set the valueRange parameter of the transferFunction1D volume to a FLOAT64_BOX1 value, helide seems to silently ignore it:
const double valueRange[2] = {primitive.pseudoColorMapping().minValue(), primitive.pseudoColorMapping().maxValue()}; anari::setParameter(deviceHandle(), volume, "valueRange", ANARI_FLOAT64_BOX1, valueRange);
It works as expected if I use ANARI_FLOAT32_BOX1 instead.
ANARI_FLOAT32_BOX1
The ANARI spec allows both FLOAT32_BOX1 and FLOAT64_BOX1.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have discovered another small problem:
When I set the
valueRange
parameter of the transferFunction1D volume to aFLOAT64_BOX1
value, helide seems to silently ignore it:It works as expected if I use
ANARI_FLOAT32_BOX1
instead.The ANARI spec allows both FLOAT32_BOX1 and FLOAT64_BOX1.
The text was updated successfully, but these errors were encountered: