Closed uvchik closed 4 years ago
There are still some tests missing with a wrong dataset.
At the moment the test will log suspicious data sets but will not remove them. If the check leads to an error the data set will not be stored. This could be changed in the future, so that only broken datasets are remove but the rest will be stored.
It is possible to add additional checks.
@birgits, @SabineHaas Please check whether you agree with the basic approach.
This pull request introduces 1 alert when merging d32aca5a23a9c9bab3c7b8d8d9ecb3c7e4899013 into 1273dea0fcbd4722bc96bbce4921a5c517879d01 - view on LGTM.com
new alerts:
Thank you @uvchik! I only had a quick look so far and made some minor comments. As far as I can see without running the code myself, it looks good. If you want a more thorough feedback it unfortunately has to wait until after my holidays.
A new thought about this issue. We could store the update of the turbine data at a new place. This will have some advantages:
UPDATE:
get_turbine_types()
will not silently import new database from oedb. In the past the local data has been overwritten by this function.