Public bug reported:
Currently, hazard calculations are parallelized over sources (i.e. for
each source in a source model a task is created).
It can happen that a source model is defined over a large geographical
region (say US) but the region of interest is only a portion of it (say
California). However, in the current set up, we create tasks for all
sources in a source model, even for those sources that are evidently too
far (say sources that are on the east coast). For each of these tasks
distance calculations are also performed (to remove sites that are too
far from the source)
To avoid the creation of unneeded tasks, the locations where hazard
results need to be computed for can be saved into the DB, and tasks can
be created only for sources for which the 'rupture enclosing polygon'
(already saved into the DB) and dilated by maximum_distance intersect
the bounding box of the locations of interest.
** Affects: openquake
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to
OpenQuake.
Matching subscriptions: openquake-bugs
https://bugs.launchpad.net/bugs/1096926
Title:
OQ-Engine: define hazard tasks only for sources that are close to the
region of interest
Status in OpenQuake:
New
Bug description:
Currently, hazard calculations are parallelized over sources (i.e. for
each source in a source model a task is created).
It can happen that a source model is defined over a large geographical
region (say US) but the region of interest is only a portion of it
(say California). However, in the current set up, we create tasks for
all sources in a source model, even for those sources that are
evidently too far (say sources that are on the east coast). For each
of these tasks distance calculations are also performed (to remove
sites that are too far from the source)
To avoid the creation of unneeded tasks, the locations where hazard
results need to be computed for can be saved into the DB, and tasks
can be created only for sources for which the 'rupture enclosing
polygon' (already saved into the DB) and dilated by maximum_distance
intersect the bounding box of the locations of interest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openquake/+bug/1096926/+subscriptions