-
Notifications
You must be signed in to change notification settings - Fork 1
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
Finnish VRAD data not dealiased #98
Comments
|
Thank you for the update. 1) is okay. 2) Historical data is fine, i.e. the problem concerns just data from 2019/2020, so I think older data does not require any changes, but it may not hurt to check. In any case, dealiasVRAD should be 1 in any kind of data. |
A fix on baltrad would be to run the latest vol2bird version without an options.conf configuration file, in that case the algorithm figures out for itself whether it should dealias or not |
It looks like the dealiased=0 problem was introduced with version 0.3.20: vp <- read_vpfiles("fianj_vp_20190925T044500Z_0xb.h5")
vp$attributes$how$dealiased
vp$attributes$how$task_version
|
These are the differences between 0.3.18 and 0.3.20: There has been one commit that changed a Nyquist velocity threshold for dealiasing (adokter/vol2bird@35a0596), however it can't explain the Finnish change as it made dealising more frequent. Specifically, @nwhpt what are the Nyquist velocities of the Finnish data typically? It might be that when vol2bird was updated to 0.3.20 on Baltrad also the options.conf was changed and that it now specifies |
Nyquist for FIN is 7.61 m/s for LPRF and 48.06 m/s for HPRF measurements, but I don't know if bioRad uses the latter at all, these measurements are not executed as often as LPRF. |
I have uploaded the current options.conf at https://github.com/enram/globam-dmp/blob/master/data/options.conf |
Dealiasing is disabled in the |
So, should that line be remove or be set to TRUE? |
It should be removed - in fact I would remove the entire e.g. also the wavelength of the radar is hard set in this options.conf which is not necessary. |
So advice to Günther to not use an option.conf at all? |
Yes I think that is the preferred way to go as long as we keep working with 'one size fits all' settings. These are the other thresholds involved:
So if a polar volume has only a single scan with a Nyquist velocity between One risk of removing |
vol2bird has been updated on BALTRAD since 25 January 2021 16 UTC. The new files are dealiased:
Closing this issue. |
@nwhpt I'm reopening this issue based on the meeting we had. If I understand this issue, Finnish radar data should be dealiased (
|
The data from 2012-2016 look ok. I currently only have empty data from 2017: library(bioRad)
#> Welcome to bioRad version 0.5.2.9419
#> Warning: Docker daemon is not running
#> Warning: bioRad functionality requiring Docker has been disabled
#>
#> To enable Docker functionality, start Docker and run 'check_docker()'
#> in R
vp_2012 <- read_vpfiles("~/Downloads/finland_vp_20120126/fianj_vp_20120126T1535Z.h5")
vp_2012$attributes$how$task_version
#> [1] "0.5.0"
vp_2012$attributes$how$dealiased
#> [1] 1
vp_2013 <- read_vpfiles("~/Downloads/finland_vp_20130924/fikuo_vp_20130924T1645Z.h5")
vp_2013$attributes$how$task_version
#> [1] "0.5.0"
vp_2013$attributes$how$dealiased
#> [1] 1
vp_2014 <- read_vpfiles("~/Downloads/finland_vp_20140113/fivim_vp_20140113T2215Z.h5")
vp_2014$attributes$how$task_version
#> [1] "0.5.0"
vp_2014$attributes$how$dealiased
#> [1] 1
vp_2015 <- read_vpfiles("~/Downloads/finland_vp_20150317/fiuta_vp_20150317T0145Z.h5")
vp_2015$attributes$how$task_version
#> [1] "0.5.0"
vp_2015$attributes$how$dealiased
#> [1] 1
vp_2016 <- read_vpfiles("~/Downloads/finland_vp_20160806/fipet_vp_20160806T2030Z.h5")
vp_2016$attributes$how$task_version
#> [1] "0.5.0"
vp_2016$attributes$how$dealiased
#> [1] 1 Created on 2022-03-17 by the reprex package (v2.0.1) |
Finnish radar data from the years 2019 and 2020 are not dealiased (i.e. dealiasVRAD=0, but it should be 1), which results in faulty wind (bird) speeds and directions in all Finnish radars. In older data, the dealiasVRAD parameter is 1, as it should be, and winds seem fine. This error concerns only data on the Github repository, not data from the BALTRAD archive which FMI receives back. So the issue does not seem to originate from the Finnish data per se as it is sent to BALTRAD originally, but is probably due to a wrong configuration of the respective parameter when data is processed for Github.
The text was updated successfully, but these errors were encountered: