Hi there — I am testing some simulation code using the interpreted Matlab version of kspaceFirstOrder2D
and then running a higher resolution version of the simulation on a different machine using kspaceFirstOrder2DG
and getting drastically different results. I believe the discrepancy is accounted for by the fact that the GPU-optimized version of the code doesn't support setting sensor.directivity_angle
— as far as I can tell from tinkering around, it ignores this input entirely. Is that correct?
Thanks,
Ian