-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement log-probability for CumSum
Op
#72
Conversation
ricardoV94
commented
Oct 14, 2021
•
edited
Loading
edited
Codecov Report
@@ Coverage Diff @@
## main #72 +/- ##
==========================================
+ Coverage 94.78% 94.92% +0.13%
==========================================
Files 8 9 +1
Lines 1227 1260 +33
Branches 163 164 +1
==========================================
+ Hits 1163 1196 +33
Misses 31 31
Partials 33 33
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but I don't think the CumSum
code should be in scan.py
—that module is pretty specific to Scan
.
In general, given the extent to which we're likely to expand Aesara Op
coverage (i.e. a large extent), we should start creating new modules. For example, we could start mirroring the modules in which the Aesara Op
s are defined—at least when we plan on having log-probability implementations for more than one Op
from the same Aesara modules.
Yeah, I was not very happy with it tucked in there either. Aesara puts this is Edit: Otherwise, we can organize by conceptual types of RVs... like the mixtures. In that case there was a slight link between this and the scan rewrites |
An
Exactly |
d5bf8c3
to
eb01b9c
Compare
c9583a6
to
3721964
Compare
3721964
to
ad37be1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!