Brandon T. Willard

Results 203 issues of Brandon T. Willard

In Numba, [`assert`s](https://numba.readthedocs.io/en/stable/developer/architecture.html#stage-5b-perform-automatic-parallelization) can be used to specify relationships between NumPy array shapes and potentially reduce runtime checks. We might be able to add such `assert`s based on our static...

enhancement
help wanted
Numba
performance concern

One thing we could also explore (separately) is converting constant negative indexes to positive indexes when the shape of the tensor is fixed. We know this at the Aesara level,...

help wanted
graph rewriting
shape inference
performance concern

This PR (potentially) addresses some `Scan` issues that appear when rewrites use nominal variables too liberally. **At the moment, this is just a draft for testing purposes.**

bug
important
graph rewriting
Scan

The name `Generic` is, well, too generic; it should be something like `GenericCType`.

enhancement
good first issue
help wanted
refactor
C-backend

One thing we could also explore (separately) is converting constant negative indexes to positive indexes when the shape of the tensor is fixed. We know this at the Aesara level,...

enhancement
help wanted
graph rewriting
performance concern

We should consider changing the dtypes of `Alloc`, `ARange`, and similar allocation `Op`s that are used as indices—at least when they have no other clients. _Originally posted by @brandonwillard in...

enhancement
help wanted
graph rewriting
performance concern

As a follow-up to the conversation in #1081, we should consider turning on bounds checking by default. One requirement is that [`NUMBA_BOUNDSCHECK`](https://numba.readthedocs.io/en/stable/reference/pysemantics.html?highlight=boundscheck#bounds-checking) be honored.

enhancement
help wanted
question
backend compatibility
Numba

The `DimShuffle` in the following should not be produced: ```python import aesara import aesara.tensor as at x = at.scalar("x") z = x.dimshuffle() aesara.dprint(z) # InplaceDimShuffle{} [id A] # |x [id...

bug
good first issue
help wanted

Our tests should not allow un-caught/checked warnings. The addition to `setup.cfg` mentioned [here](https://docs.pytest.org/en/7.1.x/how-to/capture-warnings.html) should be sufficient. We'll need to update our tests to prevent them from failing, though.

bug
testing
important

The config setting `optimizer_excluding` (and related settings) cannot be changed after `aesara` is imported, making it significantly less useful than it could be. Let's see if we can change this.

enhancement
help wanted
tooling