Open peterdesmet opened 2 years ago
@peterdesmet fyi the 'underwater acoustic monitoring' contains several different hydrophones, with completely different purposes, but one combining factor is that they measure some part of the underwater sound. So I know it needs to be kept short, but I would suggest 'acoustic'.
Unfortunately we already use acoustic
for acoustic telemetry functions: https://inbo.github.io/etn/reference/index.html#section-explore-acoustic-telemetry-data
Would underwater
make sense?
@jreubens @PieterjanVerhelst or is there a better name than acoustic
for acoustic telemetry functions like get_acoustic_detections()
?
To my opinion, it makes more sense to use 'acoustic' for the hydrophone measurements, and change for the acoustic telemetry to 'telemetry' ? 'underwater' doesn't make sense, but 'sound' would be fine if 'acoustic' is claimed by @PieterjanVerhelst @jreubens
acoustics can't be changed... as it is linked to acoustic telemetry. Telemetry also has a lot of different functionalities. thus that's not a good alternative. thus I suggest @DebusschereE goes for 'sound' :-)
ok for me. @peterdesmet 'sound' it is.
@debusscheree we need a good short name for underwater acoustic monitoring, one that can be used in ETN functions/parameters. I used
cpod
but as you mentioned, that is a specific technology/manufacturer, which we want to avoid.Alternatives:
underwater
?hydrophone
?Example of function name:
get_hydrophone_deployments()