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

Units for theoretical_pitch are in Hz #128

Merged
merged 4 commits into from
Mar 19, 2021

Conversation

pelinski
Copy link
Contributor

Hi! @marinaniet0 and I realized this while working in the Audio and Muisc Processing Lab assignment:

In line 73:

                        theoretical_pitch = Converter.cent_to_hz(
                            note_cent, tonic_hz)

So theoretical_pitch must be in Hz when written to the stable_notesdict.

@pelinski pelinski changed the title corrected cent to Hz Units for theoretical_pitch are in Hz Mar 19, 2021
@codecov
Copy link

codecov bot commented Mar 19, 2021

Codecov Report

Merging #128 (5cc452e) into master (10e94bc) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #128   +/-   ##
======================================
  Coverage    0.40%   0.40%           
======================================
  Files          46      46           
  Lines        5000    5000           
======================================
  Hits           20      20           
  Misses       4980    4980           
Impacted Files Coverage Δ
src/tomato/audio/notemodel.py 0.00% <ø> (ø)
src/tomato/__init__.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 10e94bc...5cc452e. Read the comment docs.

@sertansenturk sertansenturk self-requested a review March 19, 2021 16:35
@sertansenturk
Copy link
Owner

sertansenturk commented Mar 19, 2021

Thank you @pelinski and @marinaniet0 not only for reporting the issue but also for making the fix! 🥳

Before I approve the PR can you also do the following:

  • Increment the version to v0.14.2 in package init.py
  • Add the new version and a brief explanation to the changelog
  • Last and most important. Can you add yourselves to the Contributors? 😄

Thanks in advance!

@pelinski
Copy link
Contributor Author

Done! Thank you for considering the PR and for the toolbox :-)

@sertansenturk sertansenturk changed the base branch from master to dev March 19, 2021 17:40
@sertansenturk
Copy link
Owner

My pleasure. I'm glad that whatever I did years ago is of some help to you people :)

FYI, Before hitting the merge I've realized that the automated tests are failing. It's not because of your change, but something irrelevant. I've changed the PR to merge to the dev branch so I can fix these problems before pushing to master and creating a problematic release 😄

Thanks for the contributions!

sertansenturk
sertansenturk previously approved these changes Mar 19, 2021
Copy link
Owner

@sertansenturk sertansenturk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

linting borken on Python. It's my problem.

Merging to dev so I can fix these on my own before merging to master.

Thanks!

@sertansenturk sertansenturk changed the base branch from dev to master March 19, 2021 17:50
@sertansenturk sertansenturk dismissed their stale review March 19, 2021 17:50

The base branch was changed.

@sertansenturk sertansenturk changed the base branch from master to marter0-master March 19, 2021 17:54
@sertansenturk sertansenturk merged commit 9b95210 into sertansenturk:marter0-master Mar 19, 2021
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