You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All lines are correct on their own, but l.178 and l.179 (no cloud base detected at dt=-30) are directly inconsistent with l. 177 (1 cloud base detected at dt=-30). Lines 178 and 179 are also redundant.
Currently, the function check_data_consistency() in src/ampycloud/utils.py does not check for these elements (duplicated hits or inconsistent hits). This was not directly related to the error of #119, but it's not ideal nonetheless.
The solution is to enhance check_data_consistency() to cover these cases, and issue a meaningful error to inform the user.
Screenshot
No response
Steps to reproduce
No response
Relevant log output
No response
Environment
The problem was seen is both ampycloud v1.0.0 and v2.0.0.dev.
Code of Conduct
I agree to follow the ampycloud Code of Conduct.
The text was updated successfully, but these errors were encountered:
fpavogt
changed the title
[Bug]: AmpycloudError: Cloud base calculation got an empty array.Maybe check lookback percentage (is set to 100)
Input data validation could be better
Apr 17, 2024
Is there already an issue for this?
Describe the bug
A code user reported the error in #119.
When looking at it, it was noticed that the DataFrame being fed to ampycloud contained something like:
All lines are correct on their own, but l.178 and l.179 (no cloud base detected at dt=-30) are directly inconsistent with l. 177 (1 cloud base detected at dt=-30). Lines 178 and 179 are also redundant.
Currently, the function
check_data_consistency()
insrc/ampycloud/utils.py
does not check for these elements (duplicated hits or inconsistent hits). This was not directly related to the error of #119, but it's not ideal nonetheless.The solution is to enhance
check_data_consistency()
to cover these cases, and issue a meaningful error to inform the user.Screenshot
No response
Steps to reproduce
No response
Relevant log output
No response
Environment
Code of Conduct
The text was updated successfully, but these errors were encountered: