You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolving Faster Zernike evaluation #720 to make zernike evaluations faster - this issue was actually reverted though...
changing the utility functions used in calculating the transform at multiple surfaces (like in make_boozmn_output) to use jax.numpy, which can allow for more parts of the calculation to be performed on the GPU and potentially allow jitting more parts of the calculation (like the zernike_to_fourier function, for example) Vectorize boozer transform over multiple surfaces #1197
The text was updated successfully, but these errors were encountered:
With @unalmis recent updates to grid tags, I think we could add a requires_meshgrid thing to the boozer qtys and then vmap them over rho, allowing you to do multiple surfaces at once.
While we wait on progress on #369 , there are a few improvements that can be made when using the surface transform in DESC
make_boozmn_output
) to use jax.numpy, which can allow for more parts of the calculation to be performed on the GPU and potentially allow jitting more parts of the calculation (like thezernike_to_fourier
function, for example) Vectorize boozer transform over multiple surfaces #1197The text was updated successfully, but these errors were encountered: