Format: 1.8 Date: Mon, 04 May 2015 09:05:33 +0000 Source: python-oq-engine Binary: python-oq-engine Architecture: all Version: 1.4.0-0~dev1430730333-48949df~precise01 Distribution: precise Urgency: low Maintainer: Ubuntu Build Daemon Changed-By: Automatic Packager (GEM Foundation) Description: python-oq-engine - computes seismic hazard and physical risk Changes: python-oq-engine (1.4.0-0~dev1430730333-48949df~precise01) precise; urgency=low . [Automatic Script] * Development version from 48949df commit . [Matteo Nastasi, Daniele ViganĂ²] * Add binary package support for both Ubuntu 12.04 (Precise) and Ubuntu 14.04 (Trusty) . [Michele Simionato] * Removed the SiteModel table: now the association between the sites and the site model is done by using hazardlib.geo.geodetic.min_distance . [Daniele ViganĂ²] * added authentication support to the 'engineweb' and the 'engineserver' . [Michele Simionato] * the aggregate loss curves can be exported in CSV format . [Matteo Nastasi] * added 'outtypes' attribute with list of possible output types for each output item in outputs list API command * added '/v1/calc//status' API command * added 'engineweb' django application as local web client for oq-engine . [Michele Simionato] * Renamed the maximum_distance parameter of the risk calculators to asset_hazard_distance, to avoid confusion with the maximum_distance parameter of the hazard calculators, which has a different meaning; is it an error to set the maximum_distance in a job_risk.ini file * Added to the API an URL /v1/calc/:calc_id/remove to hide jobs * A new key is_running is added to the list of dictionaries returned by the URL /v1/calc/list * Replaced the mock tests for the engine server with real functional tests * Added a resource /v1/calc/:calc_id/traceback to get the traceback of a failed calculation * Now the logs are stored also in the database, both for the controller node and the worker nodes * Bypassed Django when deleting calculations from the database: this avoids running out of memory for large calculations * Fixed an issue in the scenario calculator: the GMFs were not filtered according to the distance to the rupture * Now critical errors appear in the log file * Added a --run command to run hazard and risk together * Fixed bug in the event based calculator; in the case number_of_logic_tree_samples > 0 it was generating incorrect hazard curves. Also improved (a lot) the performance in this case. * Fixed a tricky bug happening when some tectonic region type are filtered away. * The event based risk calculator now save only the non-zero losses in the table event_loss_asset. * Added a CSV exporter for the Stochastic Event Sets, for debugging purposes. * The GMF CSV exporter now sorts the output by rupture tag. . [Matteo Nastasi] * Each pull request must be accompanied by an update of the debian changelog now. Checksums-Sha1: 9804c544ca43861dcffdb7868fa43c3f25703710 880406 python-oq-engine_1.4.0-0~dev1430730333-48949df~precise01_all.deb Checksums-Sha256: 99fb8d0e5b8d05a43af360fa232bf7b128b76c231e17b756e967dfcfcad2c468 880406 python-oq-engine_1.4.0-0~dev1430730333-48949df~precise01_all.deb Files: 854b097f6a39a872c11222f9ef9d369d 880406 python extra python-oq-engine_1.4.0-0~dev1430730333-48949df~precise01_all.deb