-
# Abstract
In the month of May, 2011, we began writing a significant amount of code which must interact with the OpenQuake database. This introduces some challenges with respect to development/testin…
-
The main reason we did _not_ make risk calculations available in the June-demo-GUI was the lack of performance in the risk engine. We need to anayse/profile the latter and enhance it by removing the p…
-
When running db_tests, I get the floowing error:
ProgrammingError: (ProgrammingError) permission denied for sequence surface_id_seq
'INSERT INTO eqcat.surface (semi_minor, semi_major, strike) VALUES…
-
# Problem
The following branch has some test files which produce a fairly large loss map (about 31k assets): https://github.com/larsbutler/openquake/tree/loss-map-serializer-speed
In all, it takes a…
-
Somehow we missed a bunch of these:
`$ grep "OpenGEM" -Rn .`
./bin/openquake:54:flags.DEFINE_string('config_file', 'openquake-config.gem', 'OpenGEM configuration file')
./build.xml:32:
./celery…
-
#
## ERROR: \* Serializes the csv into the database
Traceback (most recent call last):
File "/home/mattia/devel/gem/openquake/db_tests/db_loader_unittest.py", line 183, in test_csv_to_db_loader_en…
-
Allow the web GUI user to search and reuse existing/previously stored source models and calculation parameters and to start seismic calculations from these.
-
Presently the user is forced to start the work-flow in the web GUI by always uploading a source model because there is no way to select/reuse a source model that was uploaded in the past.
This may ap…
-
When a user starts a potentially lengthy OpenQuake calculation it should be possible to specify a feedback mechanism (e.g. email/instant messaging account) and/or a notification granularity (job progr…
-
This is a detailed spec for:
https://www.pivotaltracker.com/story/show/10016217
# Abstract
The OpenQuake engine is currently generating hazard maps which can be serialized to NRML. the focus of this …