-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Renamed SMC files #6174
Renamed SMC files #6174
Conversation
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.
Thanks for opening the PR. We should keep the internal function names unchanged. Change only file names.
@IMvision12 Why did you close #6173 and open this PR? |
No particular reason; did I do something wrong? |
If you are not happy with a PR that you submitted, or if the tests don't pass, etc., there is no need to create a new PR: the easiest is to push again to the same branch, and the PR will be updated. If you remove or modify some of the commits that are already pushed, you can |
Thanks for Information |
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.
Following up on @ricardoV94's review, I pointed out the places that should not be modified.
@Armavica Thanks for feedback, I have updated the files |
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.
There are still two places in test_smc.py
that have been modified but shouldn't be. There are also a few places in this file that have not been modified but should be, you will see them if you run the tests with pytest pymc/tests/smc
. After that, I think that it should be good.
@Armavica I modified the file, but the tests are still failing. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6174 +/- ##
==========================================
- Coverage 93.77% 85.65% -8.13%
==========================================
Files 101 99 -2
Lines 22232 20962 -1270
==========================================
- Hits 20849 17955 -2894
- Misses 1383 3007 +1624
|
Some of these tests fail because there are still a few places in Some others fail because now Line 71 in a135f53
@ricardoV94 what should we do here? |
I pushed some changes that specify |
@IMvision12 I squashed the commits and force-pushed do solve the conflicts. Be careful to get the upstream changes before you try to do further changes |
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.
One small comment, otherwise this appears to be ready to merge?
from pymc.smc.kernels import IMH, MH | ||
from pymc.smc.sampling import sample_smc | ||
|
||
__all__ = ("sample_smc",) |
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.
@IMvision12 you didn't include IMH
and MH
in __all__
?
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.
They weren't available at the root level before, just via pymc.smc. I think it was fine like that
from pymc.smc.kernels import IMH, MH | ||
from pymc.smc.sampling import sample_smc | ||
|
||
__all__ = ("sample_smc",) |
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.
nit: Isn't __all__
usually a list? In PyMC it is a list in 42 places and a tuple in only 2.
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.
I'm team tuples
What is this PR about?
Renamed SMC Files
Closes : #6171
Major / Breaking Changes