Publishing details
Changelog
python-oq-engine (1.4.0-0~precise01~dev1430746194-c1dae3a) precise; urgency=low
[Automatic Script]
* Development version from c1dae3a 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/<id>/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.
-- Automatic Packager (GEM Foundation) <email address hidden> Mon, 04 May 2015 13:29:54 +0000
Builds
Built packages
-
python-oq-engine
computes seismic hazard and physical risk
Package files