-
Notifications
You must be signed in to change notification settings - Fork 20
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
Naming: "source" vs. "field" #27
Comments
They can also generate a single point. |
@hagenw That's a good point! In the future, time-domain sources may even be able to generate a time signal for a single point. |
These function create acoustical transfer functions either in frequency domain or time domain from the source location (exception plane wave) to one or many receiver locations, right? Typical terms used in acoustics are ATF and AIR, acoustical transfer function, acoustical impulse response. Some of these functions then are even Green's functions. |
@fs446 Yes, but in the future, the time-domain functions might also be able to generate time signals for given locations in space. I don't know if that counts as AIR. Either way, are you suggesting a different module name (or multiple modules)? |
Currently, we have the submodules
sfs.mono.source
andsfs.time.source
.This makes sense for now, but we could generalize it by calling it something with "field", because that's actually what the functions generate.
The text was updated successfully, but these errors were encountered: