Skip to content
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

Adding Gibbs sampling code to ENTERPRISE EXTENSIONS #230

Closed
wants to merge 8 commits into from

Conversation

NimaLaal
Copy link
Contributor

The updated Gibbs sampling code is added alongside its test. This method performs the Gibbs sampling of single-pulsar analyses.

NimaLaal and others added 7 commits November 1, 2022 16:11
The Gibbs Method (Bayes Power) code for single pulsar analyses.
Testing the Gibbs Method code
The gibbs sampling code is added alongside its test. This method performs the Gibbs sampling of single-pulsar analyses.
@NimaLaal
Copy link
Contributor Author

Do I need to use "black" for the linting issues?

@vhaasteren
Copy link
Member

Do I need to use "black" for the linting issues?

Yes, black should fix the linting

@vhaasteren
Copy link
Member

Looking at the code, it seems you've included more than just the Gibbs sampler. As fas as I can see, this PR should only included gibbs.py and test_gibbs.py, is that right?

 enterprise_extensions/altpol/altmodel.py               | 137 ++++++++++++++++++++++++++++++
 enterprise_extensions/altpol/altorfs.py                |  45 ++++++++++
 enterprise_extensions/altpol/altutils.py               | 232 +++++++++++++++++++++++++++++++++++++++++++++++++++
 enterprise_extensions/blocks.py                        |   5 +-
 enterprise_extensions/frequentist/optimal_statistic.py |  30 ++++---
 enterprise_extensions/gibbs_sampling/gibbs.py          | 468 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/test_gibbs.py                                    |  55 ++++++++++++

Could you split off the alternative polarization utilities and blocks updates in a different branch? If you work on multiple features, it's often more maintainable to develop them in separate git branches, and then file a PR from one of those into the main repo. Then you can keep stuff that isn't ready out of the PR

Linting problems removed by "black".
Altpol utils removed (they were included by accident!)
@NimaLaal NimaLaal closed this Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants