softmax.py
make sense? math
seems a bit cluttered. There is also extra_ops.py
?
RandomStream
?import aesara
import aesara.tensor as at
rv, updates = aesara.scan(
fn=lambda : at.random.normal(0, 1),
n_steps=5,
)
print(rv.eval())
# [-1.5294442 -1.5294442 -1.5294442 -1.5294442 -1.5294442]
print(rv.eval())
# [-1.5294442 -1.5294442 -1.5294442 -1.5294442 -1.5294442]
aesara
and numpy
and start working my way through the list. Could do that with scipy
as well.
math
, but this can get unwieldy.
jax.numpy
and jax.scipy
) but it would make a lot of sense
from aesara.tensor.special import softmax
?
from aesara.tensor.math import softmax
from aesara.tensor import softmax
or more typically import aesara.tensor as at; at.softmax
special.py
. Makes comparisons with what’s available in scipy easier
I’m reading the code for linkers and I have 2 questions:
1- Is there any reason why the file structure is different for numba and jax linkers?
2- Is there any way to print the generated code without compiling for debugging ? That was very useful with MCX.
Probably because Jax offers much more flexibility than Numba.
For instance take the case of Scan. Jax has an inbuilt scan like functionality, but in case of Numba we have to create the loops manually.
We can use code generation approach in Jax too, but i think we're yet to run into logic that cannot be implemented in Jax.
Scan