search

glos / myglos

Repository for MyGLOS (GLOS Data Portal)
GNU General Public License v3.0
2 stars 2 forks source link

MIssing .nc files? #134

Open tslawecki opened 7 years ago

tslawecki commented 7 years ago

See 45176 in THREDDS and 45176 in legacy GreatLakeBuoys.org - why aren't there .nc files for 0610 and 0611? Perhaps related to ssh problems, is this easy to correct? There are some other stations with this issue as well.

Guessing this is @cheryldmorse?

cheryldmorse commented 7 years ago

@tslawecki I'm not seeing any data in the obs database for buoy 45176 on the 10th or 11th

tslawecki commented 7 years ago

Adding @gcutrell (and by e-mail) Ed since this is one of "our" buoys. Greg or Ed ... how can we check if our buoy data server had issues at that time pushing to GLOS? It seems pretty clear that UGLOS was receiving, so we need to figure out where the breakdown was in the 45176 -> LimnoTech -> GLOS -> obs/nc flow was.

From: cheryldmorse notifications@github.com Sent: Tuesday, June 13, 2017 4:35 PM To: glos/myglos Cc: Tad Slawecki; Mention Subject: Re: [glos/myglos] MIssing .nc files? (#134)

@tslaweckihttps://github.com/tslawecki I'm not seeing any data in the obs database for buoy 45176 on the 10th or 11th

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/134#issuecomment-308240570, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PvYXvCh8TCcqfZZQpQy1FJDQ5fBKks5sDvKWgaJpZM4N4_3h.

gcutrell commented 7 years ago

@tslawecki @cheryldmorse I have noticed that gwangs app is not removing old xml files from the 45176 directory so when checking the xml files from the 9th and 10th there are many files with 0 bytes size. I also just checked the buoy and it is currently not successfully sending data to glos. We are sending the same xml file to glos, mtri, and ndbc so I am not sure why there would be a file size of 0 bytes. All of these issues may be tied together.

kkoch commented 6 years ago

@gcutrell Was this resolved? Can this ticket be closed?

gcutrell commented 6 years ago

The larger issue of obs_parser not reading in buoy data was solved. Unfortunately as a result two days for 45176 is not in glos_obs.

gcutrell commented 6 years ago

I don't think the amount of effort needed to fill two days is worth while. It would be worth while at some point to create a script that will pull from csv files and insert into the database. But that is a future topic to bring up.