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

impulseResponse parameters #65

Open
mlp6 opened this issue Jul 21, 2018 · 2 comments
Open

impulseResponse parameters #65

mlp6 opened this issue Jul 21, 2018 · 2 comments

Comments

@mlp6
Copy link
Owner

mlp6 commented Jul 21, 2018

from @ndanieley

"impulseResponse":
{
        "f0": 4000000.0,
        "phase": 0.0,
        "bw": 55.0,
        "wavetype": "gaussian"
},

I don't use any of those variables in my code, and as far as I can tell, you
don't use them in the matlab code. am I missing something?

@mlp6
Copy link
Owner Author

mlp6 commented Jul 21, 2018

These parameters should be used by https://github.com/mlp6/fem/blob/master/field/defineImpResp.m. The parameters for impulseResponse were generated by the probe-specific Matlab calls in the old version (

eval(sprintf('[Th,impulseResponse] = %s(FIELD_PARAMS);', FIELD_PARAMS.Transducer));
).

That workflow has been changed (improved) in your new workflow, but there may be some redundant parameters in the original JSON probe definition files. When wavetype is gaussian, then an idealized impulse is generated from f0 and bw; if experimental, then there is the expected time/voltage data used from hydrophone measurements to define the impulse response.

@ndanieley
Copy link
Contributor

hmmm. I don't see any place where f0 is used; at least, grep can't find it. I'll just proceed on the assumption that I don't need to read that part of the probe file unless we find an error.

@mlp6 mlp6 self-assigned this Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants