Ricardo Vieira
Ricardo Vieira
## Description This showed up in #691 and was introduced/not properly handled by #664 We need to explicitly broadcast the new parameters to define the new size! ## Checklist -...
## Description Makes graphs with Assert a bit more readable ## Checklist - [x] Checked that [the pre-commit linting/style checks pass](https://docs.pymc.io/en/latest/contributing/python_style.html) - [x] Included tests that prove the fix is...
### Description #735 shows how the current interface to copy stack traces during rewrites look like. It's verbose and easy to forget. There is/was a special mode/flag to check variables...
### Description https://github.com/pymc-devs/pytensor/actions/runs/8894500236/job/24423790167?pr=735#step:6:40
## Description We should keep the stack trace during our rewrites, so that when the Op fails to perform we can point to the moment where the node was created....
## Description Reverting back to the option first suggested in https://github.com/pymc-devs/pytensor/pull/493 and then overridden in https://github.com/pymc-devs/pytensor/pull/494 The `[ ]` is the only way that allows for the Python slice `:`...
## Description PyTensor uses `DisconnectedType` and `NullType` variables to raise informative errors when users request gradients wrt to inputs that can't be computed. This is a problem for OpFromGraph which...
The gradients of OpFromGraph seem a bit fragile. I saw the following failures: ## Multiple output ```python from pytensor.compile.builders import OpFromGraph import pytensor.tensor as at x, y = at.scalars("x", "y")...
### Description ```python import numpy as np import pytensor.tensor as pt x = pt.tensor("x", shape=(0, 2)) pt.logsumexp(x).eval({x: np.zeros((0, 2))}) # ValueError: Input of CAReduce{maximum} has zero-size on axis %d ```...