Skip to content
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

nominal time versus start time #134

Open
adokter opened this issue Oct 23, 2019 · 2 comments
Open

nominal time versus start time #134

adokter opened this issue Oct 23, 2019 · 2 comments
Milestone

Comments

@adokter
Copy link
Owner

adokter commented Oct 23, 2019

Certain baltrad polar volumes have nominal time in 15 minute blocks, even when polar volumes are available every 5 minutes. This leads to profiles that have duplicate nominal times (under what/date and what/time). The starting time of the scan, as stored under /how/startdate attribute, is different for these polar volumes.

Two possible solutions:

  1. switch to using /how/startdate or - more in line with bioRad convention so far - (/how/startdate + /how/enddate)/2as the profile nominal time instead. This requires a change in vol2bird.
  2. make sure nonimal times are different for the polar scans on baltrad, which requires a change in baltrad polar volume generation.
@adokter
Copy link
Owner Author

adokter commented Oct 23, 2019

Need to inquire with Gunther Haase whether this should be considered baltrad issue, this might happen in merging scripts generating polar volumes that do not store the adequate nominal time.

@adokter
Copy link
Owner Author

adokter commented Oct 23, 2019

From ODIM hdf5 data model:

Note that all date and time information is for the nominal time of the data, ie. the time for which the data are valid. (The nominal time is not the exact acquisition time which is found elsewhere in the file.)

Note that all scans belonging to the same volume must have the same nominal date and time.

Some ambiguity here in what time for which the data are valid means exactly

@adokter adokter added this to the 0.6 milestone Nov 6, 2019
@adokter adokter modified the milestones: 0.6, 0.7 Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant