swiggumj/SchedScrape

Bug following 342 MHz receiver checkout?

Closed this issue · 2 comments

Scraping the schedule Aug 19-23, my scraper is missing the first 1.5 hour session (GBT20B-362) following the receiver checkout. I'm not quite sure why this is happening, but it looks like a bug. Watch out for this in putting together GBNCC schedules.

It looks like this is an issue with FutureInds because using --all seems to fix the problem. Hmmm

Actually I'm an idiot. The observation had already started, so the code is working EXACTLY as intended. facepalm