Where the formula declares things as float4 this will usually cause problems because the compiler doesn't like to automatically cast double4 to float4. And in fact Ready currently crashes because we don't catch exceptions from changing the data type.
To maintain the flexibility of being able to change the data type we would need to either:
Rewrite the formula to convert float4 to double4 - risky, may break. But maybe this is OK 99.9% of the time.
Ask the user to use a keyword like val instead of float4. Would cover some use-cases but probably not all. Is possibly clearer, since they may not need to know about the 4x1x1 blocks at all.
Related: Do we want to be able to change the block size too? Would be useful to change it to 1x1x1. Nvidia is moving to a scalar architecture, I've read. Is good to keep this flexibility in mind.
e.g. GrayScott1984/parameter-map.vti
Where the formula declares things as float4 this will usually cause problems because the compiler doesn't like to automatically cast double4 to float4. And in fact Ready currently crashes because we don't catch exceptions from changing the data type.
To maintain the flexibility of being able to change the data type we would need to either:
valinstead of float4. Would cover some use-cases but probably not all. Is possibly clearer, since they may not need to know about the 4x1x1 blocks at all.Related: Do we want to be able to change the block size too? Would be useful to change it to 1x1x1. Nvidia is moving to a scalar architecture, I've read. Is good to keep this flexibility in mind.