Skip to content

Added type of frequency clarification#53

Open
KronosTheLate wants to merge 5 commits intoJuliaMath:masterfrom
KronosTheLate:normal_vs_angual_frequency
Open

Added type of frequency clarification#53
KronosTheLate wants to merge 5 commits intoJuliaMath:masterfrom
KronosTheLate:normal_vs_angual_frequency

Conversation

@KronosTheLate
Copy link

@KronosTheLate KronosTheLate commented Feb 22, 2021

In reading the documentation for fftfreqs, I did not find what I came there for - a clarification about if the frequencies were measured in oscillations/second, or radians/second. From my background (engineering student), I am used to talking about angular frequencies in most cases, and so the fact that normal frequency is returned was not obvious to me, an indication that it might not be to everyone. I have therefore appended the following line in the docs for fftfreq and rfftfreq:
The return values are not to be confused with angular frequency.

I considered specifying the unit of oscillation/second, but I felt like specifying this without adding "as opposed to..." was weird, and when adding it, it is longer and more trailing than this solution. Other suggestions are very welcome

In reading the documentation for `fftfreqs`, I did not find what I came there for - a clarification about if the frequencies were measured in oscillations/second, or radians/second. From my background (engineering student), I am used to talking about angular frequencies in most cases, and so the fact that normal frequency is returned was not obvious to me, indication that it might not be to everyone. I have therefore appended the following line in the docs for `fftfreq` and `rfftfreq`:
`The return values are not to be confused with angular frequency.`

I considered specifying the unit of oscillation/second, but I felt like specifying this without adding "as opposed to..." was weird, and when adding it, it is longer and more trailing than this solution. Other suggestions are very welcome
@codecov
Copy link

codecov bot commented Feb 22, 2021

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@KronosTheLate
Copy link
Author

friendly bump

@jishnub
Copy link
Member

jishnub commented Jul 26, 2021

Perhaps you may also add that the angular frequencies may be obtained by multiplying the output by 2pi

@KronosTheLate
Copy link
Author

Perhaps you may also add that the angular frequencies may be obtained by multiplying the output by 2pi

Check. I am on my phone, so I could not find the UTF8 symbol for pi, but feel free to insert it id you can. Otherwise I think that 'pi' ia more reliable to display properly on e.g. phones.

@jishnub
Copy link
Member

jishnub commented Jul 27, 2021

Yeah pi is better, and in any case is a valid identifier in Julia. Could you add back ticks to 2pi so that it displays as 2pi? This makes it clear that this is inline code.

@JamesWrigley
Copy link
Contributor

Bump, I think this can be merged?

@KronosTheLate
Copy link
Author

Haha 5 years later xD

But yhea, I agree this should be good to go.

@JamesWrigley
Copy link
Contributor

😛

image

Co-authored-by: Steven G. Johnson <stevenj@mit.edu>
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.

4 participants