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

Cleanup header documentation #76

Open
JoFrhwld opened this issue Oct 3, 2022 · 4 comments
Open

Cleanup header documentation #76

JoFrhwld opened this issue Oct 3, 2022 · 4 comments
Labels
documentation Primarily related to documenting usage or code

Comments

@JoFrhwld
Copy link
Owner

JoFrhwld commented Oct 3, 2022

The top of extractFormants.py has a large comment block that should be preserved somewhere, but is more appropriate in some more visible and (and updatable) documentation.

@JoFrhwld JoFrhwld added the documentation Primarily related to documenting usage or code label Oct 3, 2022
@chrisbrickhouse
Copy link
Collaborator

chrisbrickhouse commented Oct 4, 2022

should be preserved somewhere

It looks like an old change log, but without dates (blame says it was you and Kyle who added them across two commits). We could stash it in a CHANGELOG.md file and/or on a Sphinx page, and this could be updated with future change logs (we should probably have this anyway). I'm not sure how useful preserving this comment block would be given that it's available in the commit history and at least 9 years old, but I don't see much harm.

@JoFrhwld
Copy link
Owner Author

JoFrhwld commented Oct 4, 2022

The comment block was actually written by Ingrid Rosenfelder, and the two commits would have been the original commit to github, Kyle's commit was from running autopep8.

While there's some changelog components, it also contains documentation. Most important, I think, are this description of the default measurement point selection procedure:

    # - FAAV measurement procedure:                                               ##
    # - AY has 50 ms left padding and is measured at maximum F1              ##
    # - Tuw measured at beginning of segment                                 ##
    # - OW, AW measured halfway between beginning of segment and F1 maximum  ##
    # - EY is measured at maximum F1, but without extra padding              ##

And this discussion of tokens excluded from analysis:

    # - excluded from analysis:                                                   ##
    # - uncertain and unclear transcriptions                                 ##
    # - overlaps                                                             ##
    # - last syllables of truncated words                                    ##

Edit:

It might be silly, but I almost want to save # !!! This is NOT the original extractFormants.py file !!! ##, for posterity. The "original extractFormants.py" would have been a script written by Keelan Evanini for his PhD, which laid the methodological foundations for FAVE

@chrisbrickhouse
Copy link
Collaborator

Ah okay, I wasn't sure if those were documentation or just really brief change log entries. Those seem worth adding to the top-level doc string.

It might be silly, but I almost want to save # !!! This is NOT the original extractFormants.py file !!! ##, for posterity.

I'm down for that. We should keep it as an inline comment though. If we add it to the doc string, it will get added to the Sphinx docs which could confuse people.

@chrisbrickhouse
Copy link
Collaborator

Oh, we also have NEWS.md where we can stash most of the changelog stuff, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Primarily related to documenting usage or code
Projects
None yet
Development

No branches or pull requests

2 participants