Make the engine capable to process HAZARD and HAZARD+RISK jobs

Bug #805365 reported by Andrea Cerisara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenQuake (deprecated)
Fix Released
High
Unassigned

Bug Description

The engine must support the processing of HAZARD (only) and HAZARD + RISK jobs.

Tags: sys-quality
Revision history for this message
Andrea Cerisara (acerisara) wrote :

As agreed with Damiano, to trigger just the hazard computation a user should comment or delete the risk subsection (the section definition itself is enough).

Changed in openquake:
status: New → Confirmed
Changed in openquake:
assignee: nobody → Andrea Cerisara (andreacerisara-b)
Revision history for this message
Andrea Cerisara (acerisara) wrote :

I just found the engine already supports this feature. I was able to run just the hazard subsystem, by:

* setting the --include_defaults flag to false (via command line)
* commenting out the [RISK] subsection in my configuration file

Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

That's good news :)

tags: added: current-cycle
Changed in openquake:
importance: Undecided → High
Changed in openquake:
status: Confirmed → In Progress
Changed in openquake:
status: In Progress → Fix Committed
tags: added: sys-quality
removed: current-cycle
Changed in openquake:
milestone: none → 0.4.1
Revision history for this message
Lars Butler (lars-butler) wrote :

> I just found the engine already supports this feature. I was able to run just the hazard subsystem, by:

> * setting the --include_defaults flag to false (via command line)
> * commenting out the [RISK] subsection in my configuration file

I don't know about you guys, but this is kind an obscure method for running hazard-only calculations. I think this should be much more explicit (command line switch, maybe?).

Revision history for this message
Andrea Cerisara (acerisara) wrote :

Damiano asked to run just hazard computations by commenting out the risk subsection in the configuration file. The --include_defaults is necessary because the engine merges the configuration with a default (risk enabled) configuration file, but IIRC we agreed to remove this unused feature sooner or later.

Changed in openquake:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.