-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
timechanging NcML bug #4
Comments
ETA ? Is there an open ticket about this ? |
Not sure but they seem pretty quick... Sent the original ticket only tuesday. I can ask if they have an idea for the ETA. I guess it depends how complicated a fix it is for them. I have a feeling they might be assuming a gregorian calendar and we end up with offset days over time (my data was 'noleap' only by chance) |
Ticketing is flagged with a number but only in my email. I don't seem to be able to find a 'forum' on their support site Ticket DetailsTicket ID: XYW-188900 |
Good enough. ESGF considers that time units that vary over a simulation should be fixed by the data provider. |
Yep. I honestly have never come across a dataset that has changing time units but I guess we still want to validate this functionality |
J'ai eu ce bug moi aussi hier justement.
…On Thu, Jan 9, 2020 at 10:05 AM Travis Logan ***@***.***> wrote:
Yep. I honestly have never come across a dataset that has changing time
units but I guess we still want to validate this functionality
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#4?email_source=notifications&email_token=AD7CIHGS4HJKDIXOUEV5MMTQ444KHA5CNFSM4KEZFVWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIQTKOI#issuecomment-572601657>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD7CIHGCSSCMEFBIEATLYK3Q444KHANCNFSM4KEZFVWA>
.
--
----------------------
Sébastien Biner
----------------------
|
as noted in initial comment : #1 (comment) using the timeunitsChange="true" flag results in an offset of +5 days
Have been in contact with UNIDATA support and this is indeed a bug on their end. I am supposed to notified when a fix is available.
The text was updated successfully, but these errors were encountered: