Report fixes
A couple of fixes to reporting jobs I caught while running them in idq-batch
:
- The report generated from
idq-batch
was only targetting a single segment, so I changed those times to begps_start
,gps_end
. - In
reports.Report
, if you weren't plotting timeseries or if you don't have thefrequency
column in your features, these jobs will fail since it assumes the existence offrequency
intimeseries data discovery
and the corresponding frequency bound, which I'm finding a bit restrictive in some cases when running batch jobs.