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
As promised, here is a list of the actionable items we raised in the workshop. Please feel free to edit/reword and create new issues around it. I'm just dumping the list here so anyone can input more information or details.
ADCP Ensemble averaging - code is written - missing test/merge - how to join with upstream
BUG: Impossible Depth PP not handling Bec case - instrument varying depth widely in the water column.
Set new defaults: IMOS Salinity PT should be after the manualQC
ADCP Temperature should be flag as bad automatically?
Change the ADCP internal temperature metadata: name: INSTRUMENT_TEMP, and associated longname/variable descriptions (Majority vote)
Change the ADCP depth metadata: name: INSTRUMENT_PRESSURE_REL, and associcated longname/variable descriptions. (Majority Vote).
Store individual quality control results so we can track what test marked what.
Updates Documentation: how to process RDI single/ensemble ping data - RDI tools to fix binary files with time drifts/pressure offsets/temperature record/sound velocity recalculations. [Simon/Bec].
Tidal analysis - investigate the branch for tidal analysis and compare with what OceanCurrents is doing - also direct the results to detect timedrifts.
Update documentation about PercentGood: Only applies to internally processed average data.
The text was updated successfully, but these errors were encountered:
A couple of changes to the ADCP netCDF format would be good,
Put the depth of each current observation into the netCDF file, so depth will have the same dimensions as the current variables (TIME, HEIGHT_ABOVE_SENSOR). At the moment the user has to calculate the depth of each observation by combining the height_above_sensor and (instrument) depth.
The ADCP files could also be flattened, to a observation of time, depth, current, all with the single dimensions of OBS. The file is simply a bunch of current observations at a time and depth.
@hugo-sardi thank you for the summary of actionnable items, would you please be able to point to existing issues/PRs in the repo or create a relevant one if not existing? I only managed to map one I was sure of.
Hi all,
As promised, here is a list of the actionable items we raised in the workshop. Please feel free to edit/reword and create new issues around it. I'm just dumping the list here so anyone can input more information or details.
Top priorities
1. Fix Bug in Error Velocity QC and update the wiki. (done)
2. Fix interactivity zoom when QC a new variable. ("easy")
3. Fix the window pop-up if user didn't click on qc stats after applying qc. "easy"
4. Finish RDI - BinMapping Downward data. ("medium")
5. Improve OceanContourParser to support more processing and different export cases (probably easy as long as we list our cases!?). Current issues/PR related to the OceanContour parser: #775 , #774 , #778
6. make Bec Plots for Thresholds available (histograms, pcolors, etc.) (done).
7. Reapply PP - Back and Forth Support. ("medium - possible side effects?)
The text was updated successfully, but these errors were encountered: