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
{{ message }}
Repository navigation
Identify and block failing read/write methods in HazardForecast/ImpactForecast #1126
Check whether the I/O methods for which no test dataset exist might create issues. If possible issues are identified, define new test datasets for these data types.
I don't think this is related to test datasets. We have to check if the write methods from the base classes fail in the derived forecast classes. This can be done with the existing unit test data structures (it's mostly about writing all attributes and their respective types)
changed the title [-]Check whether I/O from other data types fail[/-][+]Identify and block failing read/write methods in `HazardForecast`/`ImpactForecast`[/+]on Dec 10, 2025
I don't think this is related to test datasets. We have to check if the write methods from the base classes fail in the derived forecast classes. This can be done with the existing unit test data structures (it's mostly about writing all attributes and their respective types)
Activity
[-]Check whether I/O from hazard base can be problematic[/-][+]Check whether I/O from other data types fail[/+]ValentinGebhart commentedon Dec 1, 2025
tiff
grib
point
(polygon)
peanutfun commentedon Dec 10, 2025
I don't think this is related to test datasets. We have to check if the write methods from the base classes fail in the derived forecast classes. This can be done with the existing unit test data structures (it's mostly about writing all attributes and their respective types)
[-]Check whether I/O from other data types fail[/-][+]Identify and block failing read/write methods in `HazardForecast`/`ImpactForecast`[/+]peanutfun commentedon Jun 10, 2026
@chahank Not sure how to proceed here?
chahank commentedon Jun 11, 2026
Did you have a concrete idea here?