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

Ulam bug 417 #418

Merged
merged 4 commits into from
Jul 2, 2024
Merged

Ulam bug 417 #418

merged 4 commits into from
Jul 2, 2024

Conversation

osorensen
Copy link
Collaborator

No description provided.

@osorensen
Copy link
Collaborator Author

Details are in #417.

@osorensen osorensen mentioned this pull request Jul 2, 2024
@osorensen osorensen merged commit 4c793da into develop Jul 2, 2024
8 checks passed
@osorensen osorensen deleted the ulam-bug-417 branch July 2, 2024 09:07
@osorensen osorensen restored the ulam-bug-417 branch July 2, 2024 09:31
osorensen added a commit that referenced this pull request Jul 8, 2024
* dev version

* Ulam bug 417 (#418)

* hotfix

* updating news

* fixing Ulam issue

* incrementing version before running CRAN tests

* updating news.md to say that no bug in Ulam distance has been fixed

* fixing error in likelihood calculation

* added unit test for log likelihood with clusters

* fixed namespace thing

* switching to vapply for safety

* fixing some more wrong test expectations
osorensen added a commit that referenced this pull request Aug 15, 2024
* dev version

* Ulam bug 417 (#418)

* hotfix

* updating news

* fixing Ulam issue

* incrementing version before running CRAN tests

* updating news.md to say that no bug in Ulam distance has been fixed

* fixing error in likelihood calculation

* added unit test for log likelihood with clusters

* fixed namespace thing

* switching to vapply for safety

* fixing some more wrong test expectations

* ready for cran
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.

2 participants