Tags give the ability to mark specific points in history as being important
-
v1.2.4
protected4e0a1aa3 · ·- added Zenodo upload - fix problem with creating user config - add format placeholders for GroupStations.create_ts for file_names parameter - translate Parameter name for Precipitation for create_roger_ts back to german names to work with actual RoGeR version - fix problem when create_ts is invoked with a zip file. Previously the precipitation timeseries did not get expanded to the last complete date and stopped at 00:00 o'clock
-
v1.2.1
protected4cfb0b16 · ·- fix: filllup linear regression did not take configuration value and therefor did never work - config: change LINEAR_INTERPOLATION_LIMIT to be a category - cli: add version parameter - multiprocessing: make process count configurable through user configuration - broker: prevent broker inactivation by other broker - broker: add force deactivate all method to forcefully change the database flag of active brokers
-
v1.1.2
protecteda38c9351 · ·- add method to download DEM data from OpenTopography-API - update StationBase._expand_timeserie_to_period to remove entries that are older than the min_date config to remove unnessecary database entries - fix GroupStation.create_ts: don't throw period changed warning if the change was only due to the expand_to_timestamp output
-
v1.0.5
protected93812ee9 · ·- fix problem with horizon calculation with holes - fix _check_min_date for non existing stations - fix major error in getting multi annual raster values - add reason for dropping in log message - rename droped to dropped in models - add min_date as configuration value - check before each update_raw, if the min_date of the configuration is the same as in the database. If not expand or reduce teh timeserie - add get_date and get_datetime as methods to config - rename config's getlist methode to get_list to be addecuate to the rest - set min_date to 1999-01-01 I did some analysis and if you start earlier, you will only have one to two possible reference station in the radius of 100km from which to fill up data. - set max_fillup_distance for p to 110 km, so at least 4 reference stations are available in the range of 1999-today - add compression to rotaed log files - rename "station_ma_timeseries_quotient_view" to "station_ma_timeseries_raster_quotient_view" - fixed StationMATimeserieRasterQuotientView to not throw error on NULL values in StationMARaster - add update_ma_timeseries method to StationsBase and Broker
-
v1.0.2
protected2a595487 · ·- make Broker not block itself if multiple `with self.is_any_active` are concatenated - fix check_df_raw: - conversion before 2000 was wrong UTC+1 -> UTC was UTC-1 -> UTC - when the DWD timeserie has duplicate entries, there was an error, even though the causing columns are not used here - derive version from git tags - cli: set_db_version asks for confirmation - create_db_schema gets option to define the database owner of the tables and schemas - change amount of charachters for settings values to work with longer versions - get meta explanations from orm models not from database comments - create user config has now an option to define what to do on existing configuration files - alembic database connection is now possible through alembic section in the user configuration file. - add broker method and cli option to upgrade the database schema - add function to query the quotients between the timeseries kinds or between the timeseries mean and the multi annual raster value
-
-