Fix documentation inconsistencies#195
Open
nyooc wants to merge 3 commits into
Open
Conversation
LukasAdamowicz
previously approved these changes
Feb 18, 2026
nyooc
force-pushed
the
fix-feature-docstrings
branch
from
ef177b9 to
0e2e7d7
Compare
Author
|
@LukasAdamowicz thanks for your approve! GitHub told me that you require signed commits so I rebased and force-pushed the same changes with signed commits. Can you please re-approve the GitHub workflow? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes some inconsistencies in docs:
axis=keyword for thecompute()method was probably copied over fromSignalEntropy, and the feature name stuck. Also in the Fortran code.PfizerRDGitHub org migrated its name topfizer-opensource. Despite the old address still works, I think it's useful if it doesn't create any ambiguity.