-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error raised when no data exists in specified time range #8
Comments
At first glance this means that no data was found inside the specified interval. I do agree that it should return an empty data frame instead of throwing an error. Will fix it soon. |
Thanks for your quick reply @glopesdev
|
Yes, sorry what I meant when I said "no data" is that maybe no pellets were delivered during that time, so in that case there would be no events to report. |
At other times there are no pellets delivered but I did not get an error. |
This turned out to be a more general issue around querying time ranges where no data has been recorded (e.g. in case of a crash). I'm pushing a fix now on the |
Fix row skipping when replacing header names
There is a problem in the function
aeon.query.pelletdata
for longer start times, but not for shorter ones.The code bellow runs well with a shorter
star_time=600
but raises an error for a largerstart_time=14000
The text was updated successfully, but these errors were encountered: