It came to our attention lately that a year or so ago, Simon Shepherd identified a period of bad data from the King Salmon radar in October 2010. The velocity recorded in the files in the attached high_vel_ksr.txt file are way high. It was confirmed (I'm fairly certain) with Jef Spaleta that something was not set correctly during a site visit to repair the radar which resulted in the high velocity values.
The high velocity values can be noticed in the attached RTI plot as well as the map potential plot. The map-level data was how Simon originally found this error. We've removed these files and reprocessed our grid and map files at Virginia Tech. I propose that these rawacf files should also be blacklisted on the data mirror.
I'll be working up a new webpage for this issue but for now, the action items for each institution for this issue should be:
Remove the rawacf and subsequent processed files (fitacf) that match the attached text file.
Reprocess grid and map files to clear the high velocity data out of the map potential plots.
Hello all,
It came to our attention lately that a year or so ago, Simon Shepherd identified a period of bad data from the King Salmon radar in October 2010. The velocity recorded in the files in the attached high_vel_ksr.txt file are way high. It was confirmed (I'm fairly certain) with Jef Spaleta that something was not set correctly during a site visit to repair the radar which resulted in the high velocity values.
The high velocity values can be noticed in the attached RTI plot as well as the map potential plot. The map-level data was how Simon originally found this error. We've removed these files and reprocessed our grid and map files at Virginia Tech. I propose that these rawacf files should also be blacklisted on the data mirror.
I'll be working up a new webpage for this issue but for now, the action items for each institution for this issue should be:
Cheers,
-Kevin S.