Bufkit date issue starting on July 1st 00z data and beyond.

[Rejean Boudreau]

I'm running Bufkit and never had issue until some of the models starts to get data starting on July 1st.

EX: if i look at the GFS for Monday June 30th 4:00 pm (21z), the date (bottom right) is showing it correctly. Then if i move to the next period, the date is showing as Monday January 6th 7:00 pm (00z) - as if the month and the day have been reversed.

I started to get that with GFS data, thinking it was a bad run - i didn't mind.. But now that other models are reaching the same period of time, they too are showing the wrong date. I looked at the data itself and the TIME = is formated the same way before or after that period - so it's not the data, but Bufkit itself.

Is anybody getting the same issue ? Any feedback will help .

P.S. if it was my desktop config, i think i would have the same problem all year long - but the issue is only showing with timestamp data starting on July 1st 00z and beyond.

Picture of the issue :
http://www.reggphotos.com/tphoto/dateok1.png

 

[MClarkson]

On this machine I have an older version of Bufkit(circa 2010?), using profiles from Iowa State, and have no issues.

 

[Rejean Boudreau]

ok .. I'm using Version 13.4 from April 2013. I think it is the latest version.

 

[Rejean Boudreau]

I just tried with an older version (10.6) and i don't get the behavior.. Seems the issue is with newer versions - i just sent a note to NOAA WDTB. I'll post the answer (if any).

 

[GPhillips]

I'm not seeing the problem with the latest version of Bufkit on a Win7 PC. Perhaps a locality issue, i.e. the way that Bufkit reads dates from localities other than the U.S.? Of course that doesn't explain why it breaks for you on the crossover from June to July. There was a fix for the "Adjust Local Time" capability in 13.4, but once again, why the June to July problem? Strange.

 

[Rejean Boudreau]

Got the answer from NOAA WDTB - the issue is with the language setting of the PC itself. It's working fine with English (Canada or US), but gives the issue if using another language (my case). For a reason to be determined, it only affects timestamps from july 1st 00z and beyond, and not the ones prior to that timestamp.

Thanks for the feedbacks.

 

[Rejean Boudreau]

Last feedback from NOAA WDTB office.

They now have a documented issue to fix for an upcoming version. Temporary fix or workaround is to set the PC to English (Canadian or US).

Case closed for me.