You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dpo_hydrophoneDataDiversionMode sometimes required, sometimes prohibited #4
Some hydrophone acoustic data requires dpo_hydrophoneDataDiversionMode, some prohibit it. It's impossible to tell from the API when it's required. This necessitates the workaround of sending the request once within a try, catching the exception, and then sending the slightly modified request in an except block.
Expected behavior
Hydrophones for which "dpo_hydrophoneDataDiversionMode" does not apply should accept "OD" or "All". Any other values ("HPF", "LPF"), should give the "no data" response (HTTP 400 w/error code: 33)
Actual behavior
fromonc.oncimportONConc=ONC(<yourtoken>)
Some hydrophones need the dpo_hydrophoneDataDiversionMode option, e.g.:
Thank you for raising the issue. Just want to give you an update. I bring this topic up in the internal meeting and it is decided that the API call should be more forgiving on the user side. Our developer is working on changing the backend. Hopefully the new feature will be released in the near future.
Activity
ENH: Workaround bugs in ONC server
kan-fu commentedon Nov 22, 2023
Thank you for raising the issue. Just want to give you an update. I bring this topic up in the internal meeting and it is decided that the API call should be more forgiving on the user side. Our developer is working on changing the backend. Hopefully the new feature will be released in the near future.