Question about GMPEs in openquake

[s_hasan...@yahoo.com]

Dec 10

Dear all
My questions are about openquake user's manual and openquake Book:
1- are 1.1 and 0.1 the latest version of two above manuscript?
2- which of two list of GMPEs, implicit in user's manual (21 case in Appendix A) or Book(11 case in Table 3.2), are usable in openquake?
3- In Appendix A of user's manual (pp 100-102) the rake range (-150=<rake<=150) was referred to strike slip. I think it's wrong and its correct range is
(150=<rake and rake<=-150) for right-lateral strike slip

Hasan

[Damiano Monelli]

Dear Hasan,

1- Yes the documents that you can find here (http://beta.globalquakemodel.org/openquake/support/documentation/) are the latest available.

2- For a list of available GMPEs it's better if you look at the Appendix A of the User Manual, those described in the book are just a portion of the ones available.

3- Yes, you are right, thanks for pointing out the error. I think the correction condition is rake >= 150 OR rake <=-150.

Best,

Damiano

[s_hasan...@yahoo.com]

Dear Damiano
Thanks a lot.
I read disaggregation output (h5files) by HDFview and see all matrixes but i can't plot them. could you please introduce me software to plot outputs of disaggregation (3 dimentional histogrom as show above).

Regards

Hasan

[Damiano Monelli]

Dear Hasan,

you can download a script for plotting disaggregation matrices here: https://github.com/GEMScienceTools/oq-tools/blob/master/output/plotDisaggregation.py.

It's a Python script which requires a number of dependencies  (as documented in the script) and uses GMT (http://gmt.soest.hawaii.edu/) for the actual plotting.

The usage is documented in the script: it's a command line script, and you simply have to give the path of the configuration file used for the hazard calculation,

and the path of the hdf5 file containing the disaggregation results you want to plot.

Hope it helps,

Damiano

[s_hasan...@yahoo.com]

Dear Damiano
Thanks for your grateful answer
I have one question about background seismicity.
How can it be considered in openquake for PSHA?
I considered it by definition of 5 large area sources in my study region (Alongside other sources). This area sources overlap with other sources. for an example of those large area sources:
    <areaSource gml:id="src_243">
      <gml:name>Square Area Source</gml:name>
      <tectonicRegion>Active Shallow Crust</tectonicRegion>
      <areaBoundary>
        <gml:Polygon>
          <gml:exterior>
            <gml:LinearRing>
              <gml:posList> 42.0 38.15 43.40 38.10 45.20 36.71 46.55 35.36 47.21 34.89 47.75 34.80 49.456 33.454 52.49 31.08 54.11 30.21 54.25 29.445 56.46 28.29 56.75 28.6 57.65 28.5 56.448 26.896 55.20 26.17 54.0 26.39 51.368 27.796 49.8 30.51 45.80 33.0 44.0 34.95 42.0 36.20 42.0 38.15 </gml:posList>
            </gml:LinearRing>
          </gml:exterior>
        </gml:Polygon>
      </areaBoundary>
      <ruptureRateModel>
        <evenlyDiscretizedIncrementalMFD binSize="3" minVal="4.5">
          182.8549087732
        </evenlyDiscretizedIncrementalMFD>
        <strike>0.0</strike>
        <dip>90.0</dip>
        <rake>0.0</rake>
      </ruptureRateModel>
      <ruptureDepthDistribution>
        <magnitude>6.5</magnitude>
        <depth>0.0</depth>
      </ruptureDepthDistribution>
      <hypocentralDepth>15</hypocentralDepth>
    </areaSource>
The program does not run and i got some error as below:

[2013-01-21 00:53:36,397: ERROR/MainProcess] Task openquake.calculators.hazard.classical.core.compute_hazard_curve[eeb7afd2-7833-433b-b9b4-4d126e358f24] raised exception: JobCompletedError(134L,)
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/celery/execute/trace.py", line 47, in trace
    return cls(states.SUCCESS, retval=fun(*args, **kwargs))
  File "/usr/lib/python2.7/dist-packages/celery/app/task/__init__.py", line 247, in __call__
    return self.run(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line 175, in run
    return fun(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in unwrap_exception
    return func(*targs, **tkwargs)
  File "/usr/lib/pymodules/python2.7/openquake/utils/stats.py", line 313, in wrapper
    result = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/classical/core.py", line 75, in compute_hazard_curve
    calculator = utils_tasks.calculator_for_task(job_id, 'hazard')
  File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 161, in calculator_for_task
    job_ctxt = get_running_job(job_id)
  File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 127, in get_running_job
    raise JobCompletedError(job_id)
JobCompletedError: 134

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/celery/execute/trace.py", line 47, in trace
    return cls(states.SUCCESS, retval=fun(*args, **kwargs))
  File "/usr/lib/python2.7/dist-packages/celery/app/task/__init__.py", line 247, in __call__
    return self.run(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line 175, in run
    return fun(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in unwrap_exception
    return func(*targs, **tkwargs)
  File "/usr/lib/pymodules/python2.7/openquake/utils/stats.py", line 313, in wrapper
    result = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/classical/core.py", line 75, in compute_hazard_curve
    calculator = utils_tasks.calculator_for_task(job_id, 'hazard')
  File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 161, in calculator_for_task
    job_ctxt = get_running_job(job_id)
  File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 127, in get_running_job
    raise JobCompletedError(job_id)
JobCompletedError: 134

I want to know the reason for this error and how I consider background seismicity

The Best Regards
Hasan

[Damiano Monelli]

Hi Hasan,

about background seismicity, yes you can use area sources or also a collection of point sources (for instance if you want to model background seismicity that varies 'smoothly' over a region).

From the log you report is not clear the cause of the error. You may try to rerun it with  the option --log-level=debug and see if you get more informations. Can you also send the log messages as

produced by celery? I suppose that before running OpenQuake, you run the command 'celeryd'. This usually outputs some log messages in the console. If you report them we can have some more

informations about the problem.

Best,

Damiano

[s_hasan...@yahoo.com]

Hi Damiano
Thanks a lot
1- The bug about background seismicity was solved.
2- when i run the script plotdisagregation.py, i got some error as below:
$ python plotdiss.py --config_file=~/Desktop/plot-dissagregation/config.gem --results_file=/var/lib/openquake/disagg-results/job-35/disagg-results-sample:1-gmv:0.1382365-lat:35.7000000-lon:51.4500000.h5
  File "plotdiss.py", line 32
    """
      ^
IndentationError: expected an indented block
3- According to openquake book for the area source consideration of focal mechanism (strike-dip-rake) is optional but openquake dose not run without it.
4- About the incremental evenly-discretized magnitude frequency distribution: if we set for example binsize=1, it means that occurrence rate is constant from the beginning to the end of the bin or not? in the config.gem we set the WIDTH_OF_MFD_BIN = 0.1. Dos'nt it have problem?
Best regards
Hasan

[Damiano Monelli]

Hi Hasan,

2 - The error is due to the fact that the code is not correctly indented (for some reason this happens when saving the script directly from the web browser).

If you download the entire project using the 'zip' button in https://github.com/GEMScienceTools/oq-tools you should be

able to get the code correctly indented.

3 - Yes, this is an inconsistency we did not yet resolved. For the moment OpenQuake requires the focal mechanism to be always specified. It' clear however

that if you use the point rupture approximation, the focal mechanism does not really have an influence (so you can put whatever values you want).

4 - Yes, the occurrence rates is constant over the bin. In the configuration file you can specify also a width of MFD bin, but this applies only to the Gutenberg RIchter MFDs.

If you define a source with an EvenlyDiscretizedMFD, the bin size that you specify in the element is used in the calculation and not the one in the configuration file.

Best Regards,

Damiano

[s_hasan...@yahoo.com]

Hi Damiano
I really thank you for your valuable advice. I am grateful for your patience and complete answers
With the Best Regards
Hasan

[s_hasan...@yahoo.com]

Dear Damiano
A problem about Background seismicity
I got two type Area source with different rupture rate model as:
(1)
<areaSource gml:id="src_240">

<gml:name>Square Area Source</gml:name>
<tectonicRegion>Active Shallow Crust</tectonicRegion>
<areaBoundary>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing>

<gml:posList> 45.422 38.190 46.425 37.937 48.017 36.55
49.40 35.58 50.90 35.52 53.15 34.59 55.461 35.436 55.10 36.0 56.62
36.47 59.7 35.4 61.0 34.70 60.95 29.95 63.50 27.0 60.28 27.10 58.196
27.244 58.0 28.0 57.65 28.50 56.75 28.60 56.46 28.29 54.25 29.445
54.11 30.21 52.49 31.08 49.456 33.454 47.75 34.80 47.21 34.89 46.55
35.36 45.20 36.71 44.18 37.5 45.422 38.190</gml:posList>

</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</areaBoundary>
<ruptureRateModel>

<evenlyDiscretizedIncrementalMFD binSize="2.5" minVal="4.25">
36.3902199627

</evenlyDiscretizedIncrementalMFD>
<strike>0.0</strike>
<dip>90.0</dip>
<rake>0.0</rake>
</ruptureRateModel>
<ruptureDepthDistribution>

<magnitude>5</magnitude>
<depth>0.0</depth>
</ruptureDepthDistribution>
<hypocentralDepth>5</hypocentralDepth>
</areaSource>
and (2)
<areaSource gml:id="src_1">
<gml:name>Source 8.CH.2</gml:name>

<tectonicRegion>Active Shallow Crust</tectonicRegion>
<areaBoundary>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing>

<gml:posList> 45.422 38.190 46.425 37.937 48.017 36.55
49.40 35.58 50.90 35.52 53.15 34.59 55.461 35.436 55.10 36.0 56.62
36.47 59.7 35.4 61.0 34.70 60.95 29.95 63.50 27.0 60.28 27.10 58.196
27.244 58.0 28.0 57.65 28.50 56.75 28.60 56.46 28.29 54.25 29.445
54.11 30.21 52.49 31.08 49.456 33.454 47.75 34.80 47.21 34.89 46.55
35.36 45.20 36.71 44.18 37.5 45.422 38.190</gml:posList>

</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</areaBoundary>
<ruptureRateModel>

<truncatedGutenbergRichter>
<aValueCumulative>36.3902199627</aValueCumulative>
<bValue>1.91</bValue>
<minMagnitude>3.0</minMagnitude>
<maxMagnitude>5.5</maxMagnitude>
</truncatedGutenbergRichter>

<strike>0.0</strike>
<dip>90.0</dip>
<rake>0.0</rake>
</ruptureRateModel>
<ruptureDepthDistribution>

<magnitude>5.0</magnitude>
<depth>0</depth>
</ruptureDepthDistribution>
<hypocentralDepth>5</hypocentralDepth>
</areaSource>

openquake runs from early area source but it gives the following error
using secondary area source:

$ celeryd &
[1] 4114
hasan@hasan-Vostro-1400:/usr/openquake$ [2013-01-24 05:58:30,232:
WARNING/MainProcess]

-------------- celery@hasan-Vostro-1400 v2.4.6
---- **** -----
--- * *** * -- [Configuration]
-- * - **** --- . broker: amqp://guest@localhost:5672//
- ** ---------- . loader: celery.loaders.default.Loader
- ** ---------- . logfile: [stderr]@WARNING
- ** ---------- . concurrency: 2
- ** ---------- . events: OFF
- *** --- * --- . beat: OFF
-- ******* ----
--- ***** ----- [Queues]
-------------- . celery: exchange:celery (direct)
binding:celery


[2013-01-24 05:58:30,241: WARNING/MainProcess] celery@hasan-
Vostro-1400 has started.

hasan@hasan-Vostro-1400:/usr/openquake$ openquake --config-
file=iranhaz2/config.gem --output-type xml --log-level=debug
Ignoring GMF_RANDOM_SEED in classical, it's meaningful only in
scenario_damage, scenario, event_based
[2013-01-24 06:02:07,485 #47 - INFO MainProcess/4257 supervisor]
Entering supervisor for job 47
[2013-01-24 06:02:07,494 #47 - DEBUG MainProcess/4257 amqplib] Start
from server, version: 8.0, properties: {u'information': u'Licensed
under the MPL. See http://www.rabbitmq.com/', u'product':
u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2011 VMware, Inc.',
u'capabilities': {}, u'platform': u'Erlang/OTP', u'version':
u'2.7.1'}, mechanisms: [u'PLAIN', u'AMQPLAIN'], locales: [u'en_US']
[2013-01-24 06:02:07,495 #47 - DEBUG MainProcess/4257 amqplib] Open
OK! known_hosts []
[2013-01-24 06:02:07,495 #47 - DEBUG MainProcess/4257 amqplib] using
channel_id: 1
[2013-01-24 06:02:07,495 #47 - DEBUG MainProcess/4257 amqplib] Channel
open
[2013-01-24 06:02:07,563 #47 hasan-Vostro-1400 PROGRESS MainProcess/
4256 root] ** initializing (hazard)
[2013-01-24 06:02:07,630 #47 hasan-Vostro-1400 PROGRESS MainProcess/
4256 root] ** pre_executing (hazard)
[2013-01-24 06:02:07,885 #47 hasan-Vostro-1400 PROGRESS MainProcess/
4256 root] ** executing (hazard)
Jan 24, 2013 6:02:09 AM org.jredis.ri.alphazero.support.Log log
INFO: WARNING: heartbeat is disabled.
[2013-01-24 06:02:09,036 #47 hasan-Vostro-1400 INFO MainProcess/4256
root] Going to run classical PSHA hazard for 1 realizations and 1
sites
[2013-01-24 06:02:09,042 #47 hasan-Vostro-1400 DEBUG MainProcess/4256
root] > curves!
[2013-01-24 06:02:09,045 #47 hasan-Vostro-1400 INFO MainProcess/4256
root] Calculating hazard curves for realization 0
[2013-01-24 06:02:09,046 #47 hasan-Vostro-1400 INFO MainProcess/4256
root] Storing source model from job config
[2013-01-24 06:02:09,451 #47 hasan-Vostro-1400 INFO MainProcess/4256
root] Storing GMPE map from job config
[2013-01-24 06:02:09,452 #47 hasan-Vostro-1400 DEBUG MainProcess/4256
hazard] -data_length: 1
[2013-01-24 06:02:09,453 #47 hasan-Vostro-1400 DEBUG MainProcess/4256
hazard] -#subtasks: 1
Jan 24, 2013 6:02:09 AM org.jredis.ri.alphazero.support.Log log
INFO: WARNING: heartbeat is disabled.
[2013-01-24 06:02:10,437: ERROR/MainProcess] Task
openquake.calculators.hazard.classical.core.compute_hazard_curve[b3735420-
ec0a-4b6f-8bc0-e2afc5dc4b94] raised exception: JavaException('None',)

Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/celery/execute/trace.py",
line 47, in trace
return cls(states.SUCCESS, retval=fun(*args, **kwargs))
File "/usr/lib/python2.7/dist-packages/celery/app/task/__init__.py",
line 247, in __call__
return self.run(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line
175, in run
return fun(*args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in
unwrap_exception
return func(*targs, **tkwargs)
File "/usr/lib/pymodules/python2.7/openquake/utils/stats.py", line
313, in wrapper
result = func(*args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/

classical/core.py", line 76, in compute_hazard_curve
keys = calculator.compute_hazard_curve(sites, realization)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
general.py", line 84, in decorated
return fn(self, *args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 408, in compute_hazard_curve
unwrap_validation_error(jpype, ex)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 66, in unwrap_validation_error
raise runtime_exception
JavaException: Java traceback (most recent call last):
File "HazardCalculator.java", line 125, in
org.gem.calc.HazardCalculator.getHazardCurvesAsJson
File "HazardCalculator.java", line 92, in
org.gem.calc.HazardCalculator.getHazardCurves
File "HazardCurveCalculator.java", line 435, in
org.opensha.sha.calc.HazardCurveCalculator.getHazardCurve
java.lang.RuntimeException: Error: The probability for this
ProbEqkRupture (1.0) is too high for a Possion source (~infinite
number of events)

Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/celery/execute/trace.py",
line 47, in trace
return cls(states.SUCCESS, retval=fun(*args, **kwargs))
File "/usr/lib/python2.7/dist-packages/celery/app/task/__init__.py",
line 247, in __call__
return self.run(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line
175, in run
return fun(*args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in
unwrap_exception
return func(*targs, **tkwargs)
File "/usr/lib/pymodules/python2.7/openquake/utils/stats.py", line
313, in wrapper
result = func(*args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/

classical/core.py", line 76, in compute_hazard_curve
keys = calculator.compute_hazard_curve(sites, realization)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
general.py", line 84, in decorated
return fn(self, *args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 408, in compute_hazard_curve
unwrap_validation_error(jpype, ex)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 66, in unwrap_validation_error
raise runtime_exception
JavaException: Java traceback (most recent call last):
File "HazardCalculator.java", line 125, in
org.gem.calc.HazardCalculator.getHazardCurvesAsJson
File "HazardCalculator.java", line 92, in
org.gem.calc.HazardCalculator.getHazardCurves
File "HazardCurveCalculator.java", line 435, in
org.opensha.sha.calc.HazardCurveCalculator.getHazardCurve
java.lang.RuntimeException: Error: The probability for this
ProbEqkRupture (1.0) is too high for a Possion source (~infinite
number of events)
[2013-01-24 06:02:10,974 #47 hasan-Vostro-1400 CRITICAL MainProcess/
4256 root] Calculation failed with exception: 'hazard failures ([('oqs/
47/h/nhzrd:failed/i', 1)]), aborting'

Traceback (most recent call last):

File "/usr/bin/openquake", line 9, in <module>
load_entry_point('openquake==0.8.3', 'console_scripts',
'openquake')()
File "/usr/lib/pymodules/python2.7/openquake/bin/oqscript.py", line
197, in main
log_file=args.log_file)
File "/usr/lib/pymodules/python2.7/openquake/engine.py", line 854,
in run_job
_launch_job(job_ctxt, sections)
File "/usr/lib/pymodules/python2.7/openquake/engine.py", line 956,
in _launch_job
calculator.execute()

File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in
unwrap_exception
return func(*targs, **tkwargs)

File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
general.py", line 84, in decorated
return fn(self, *args, **kwargs)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 375, in execute
self.do_curves(data, realizations, serializer=self.ath)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 221, in do_curves
ath=serializer, ath_args=ath_args)
File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line
76, in distribute
return ath(**ath_args)
File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/
classical/core.py", line 505, in ath
raise RuntimeError("hazard failures (%s), aborting" % failures)
RuntimeError: hazard failures ([('oqs/47/h/nhzrd:failed/i', 1)]),
aborting
[2013-01-24 06:02:12,026 #47 - INFO MainProcess/4257 root] Recording
stop time for job 47 to job_stats
[2013-01-24 06:02:12,075 #47 - INFO MainProcess/4257 root] Cleaning up
after job 47
[2013-01-24 06:02:12,080 #47 - INFO MainProcess/4257 root] KVS garbage
collection removed 5 keys for job 47
[2013-01-24 06:02:12,128 #47 - DEBUG MainProcess/4257 amqplib] Closed
channel #1
[2013-01-24 06:02:12,137 #47 - INFO MainProcess/4257 supervisor] Job
47 finished in 0:00:04.619801
[2013-01-24 06:02:12,137 #47 - INFO MainProcess/4257 supervisor]
Exiting supervisor for job 47

I don't know about this bug.
I will grateful if you help me
Best Regards,
Hasan

On Jan 22, 11:46 am, Damiano Monelli <dami...@openquake.org> wrote:
> Hi Hasan,
>
> 2 - The error is due to the fact that the code is not correctly indented (for some reason this happens when saving the script directly from the web browser).

> If you download the entire project using the 'zip' button inhttps://github.com/GEMScienceTools/oq-toolsyou should be

> able to get the code correctly indented.
> 3 - Yes, this is an inconsistency we did not yet resolved. For the moment OpenQuake requires the focal mechanism to be always specified. It' clear however
> that if you use the point rupture approximation, the focal mechanism does not really have an influence (so you can put whatever values you want).
> 4 - Yes, the occurrence rates is constant over the bin. In the configuration file you can specify also a width of MFD bin, but this applies only to the Gutenberg RIchter MFDs.
> If you define a source with an EvenlyDiscretizedMFD, the bin size that you specify in the element is used in the calculation and not the one in the configuration file.
>
> Best Regards,
>
> Damiano

> On Jan 22, 2013, at 7:16 AM, s_hasan_moos...@yahoo.com wrote:
>
>
>
> > Hi Damiano
> > Thanks a lot
> > 1- The bug about background seismicity was solved.
> > 2- when i run the script plotdisagregation.py, i got some error as below:

> > $ python plotdiss.py --config_file=~/Desktop/plot-dissagregation/config.gem --results_file=/var/lib/openquake/disagg-results/job-35/disagg-results-samp­le:1-gmv:0.1382365-lat:35.7000000-lon:51.4500000.h5

> >> [2013-01-21 00:53:36,397: ERROR/MainProcess] Task openquake.calculators.hazard.classical.core.compute_hazard_curve[eeb7afd2-7­833-433b-b9b4-4d126e358f24] raised exception: JobCompletedError(134L,)

> >> Traceback (most recent call last):
> >>   File "/usr/lib/python2.7/dist-packages/celery/execute/trace.py", line 47, in trace
> >>     return cls(states.SUCCESS, retval=fun(*args, **kwargs))
> >>   File "/usr/lib/python2.7/dist-packages/celery/app/task/__init__.py", line 247, in __call__
> >>     return self.run(*args, **kwargs)
> >>   File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line 175, in run
> >>     return fun(*args, **kwargs)
> >>   File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in unwrap_exception
> >>     return func(*targs, **tkwargs)
> >>   File "/usr/lib/pymodules/python2.7/openquake/utils/stats.py", line 313, in wrapper
> >>     result = func(*args, **kwargs)

> >>   File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/classical/core.p­y", line 75, in compute_hazard_curve

> >>     calculator = utils_tasks.calculator_for_task(job_id, 'hazard')
> >>   File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 161, in calculator_for_task
> >>     job_ctxt = get_running_job(job_id)
> >>   File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 127, in get_running_job
> >>     raise JobCompletedError(job_id)
> >> JobCompletedError: 134
>
> >> Traceback (most recent call last):
> >>   File "/usr/lib/python2.7/dist-packages/celery/execute/trace.py", line 47, in trace
> >>     return cls(states.SUCCESS, retval=fun(*args, **kwargs))
> >>   File "/usr/lib/python2.7/dist-packages/celery/app/task/__init__.py", line 247, in __call__
> >>     return self.run(*args, **kwargs)
> >>   File "/usr/lib/python2.7/dist-packages/celery/app/__init__.py", line 175, in run
> >>     return fun(*args, **kwargs)
> >>   File "/usr/lib/pymodules/python2.7/openquake/java.py", line 332, in unwrap_exception
> >>     return func(*targs, **tkwargs)
> >>   File "/usr/lib/pymodules/python2.7/openquake/utils/stats.py", line 313, in wrapper
> >>     result = func(*args, **kwargs)

> >>   File "/usr/lib/pymodules/python2.7/openquake/calculators/hazard/classical/core.p­y", line 75, in compute_hazard_curve

> >>     calculator = utils_tasks.calculator_for_task(job_id, 'hazard')
> >>   File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 161, in calculator_for_task
> >>     job_ctxt = get_running_job(job_id)
> >>   File "/usr/lib/pymodules/python2.7/openquake/utils/tasks.py", line 127, in get_running_job
> >>     raise JobCompletedError(job_id)
> >> JobCompletedError: 134
>
> >> I want to know the reason for this error and how I consider background seismicity
>
> >> The Best Regards
> >> Hasan
>
> >> On Wednesday, January 16, 2013 12:22:21 PM UTC+3:30, Damiano Monelli wrote:
> >> Dear Hasan,
>

> >> you can download a script for plotting disaggregation matrices here:https://github.com/GEMScienceTools/oq-tools/blob/master/output/plotDi....

> >> It's a Python script which requires a number of dependencies  (as documented in the script) and uses GMT (http://gmt.soest.hawaii.edu/) for the actual plotting.
> >> The usage is documented in the script: it's a command line script, and you simply have to give the path of the configuration file used for the hazard calculation,
> >> and the path of the hdf5 file containing the disaggregation results you want to plot.
>
> >> Hope it helps,
>
> >> Damiano
> >> On Jan 16, 2013, at 6:10 AM, s_hasan...@yahoo.com wrote:
>
> >>> Dear Damiano
> >>> Thanks a lot.
> >>> I read disaggregation output (h5files) by HDFview and see all matrixes but i can't plot them. could you please introduce me software to plot outputs of disaggregation (3 dimentional histogrom as show above).
>
> >>> Regards
> >>> Hasan
>
> >>> On Thursday, January 10, 2013 2:36:35 PM UTC+3:30, Damiano Monelli wrote:
> >>> Dear Hasan,
>
> >>> 1- Yes the documents that you can find here (http://beta.globalquakemodel.org/openquake/support/documentation/) are the latest available.
> >>> 2- For a list of available GMPEs it's better if you look at the Appendix A of the User Manual, those described in the book are just a portion of the ones available.
> >>> 3- Yes, you are right, thanks for pointing out the error. I think the correction condition is rake >= 150 OR rake <=-150.
>
> >>> Best,
>
> >>> Damiano
> >>> On Dec 31, 2012, at 8:43 AM, s_hasan...@yahoo.com wrote:
>

> >>>> Post reply

>
> >>>> Dec 10
>
> >>>> Dear all
> >>>> My questions are about openquake user's manual and openquake Book:
> >>>> 1- are 1.1 and 0.1 the latest version of two above manuscript?
> >>>> 2- which of two list of GMPEs, implicit in user's manual (21 case in Appendix A) or Book(11 case in Table 3.2), are usable in openquake?
> >>>> 3- In Appendix A of user's manual (pp 100-102) the rake range (-150=<rake<=150) was referred to strike slip. I think it's wrong and its correct range is
> >>>> (150=<rake and rake<=-150) for right-lateral strike slip
>

> >>>> Hasan- Hide quoted text -
>
> - Show quoted text -

[Damiano Monelli]

Dear Hasan,

the error you are seeing is due to the fact that the rates that you specified for the second source are too high, and therefore the probability of exceeding
whatever ground motion level is equal to 1.

In the second source you specify a cumulative a value equal to 36.3902199627 and a b value equal to 1.91. Minimum magnitude is 3.0 and maximum is 5.5.
This means that the number of events (per year) that the source generates in this magnitude band is 10 ** (36.3902199627 - 1.91 * 3) - 10 ** (36.3902199627 - 1.91 * 5.5) = 4.573120780712653e+30
which is clearly too high.

Maybe 36.3902199627 is not the cumulative a value, but instead the annual rate of events with magnitude greater than 3.0. You can then derive
the cumulative a value using the following formula:
a_cum = b * Mmin + log10(36.3902199627) = 1.91 * 3.0 + log10(36.3902199627) = 7.290984680711218. Which sounds a much more reasonable a value (for a large region).

Hope it helps,

Damiano

[s_hasan...@yahoo.com]

Dear Damiano

At first, I apologize because I discuss some issues that May not be appropriate here

1- In openquake, coulde we identify the contributions to hazard coming from several different sources (no disaggregation in terms of latitude and longitude)?

2- How can I read the disaggregation results for a set of grided sites, as hdf files? I like drawing these results on a map as the attached file (Harmsen and Frankel, 1999). Please introduce if a tool exists.

Beast Regards

Hasan

[Damiano Monelli]

Dear Hasan,

OpenQuake provides a 'Disaggregation Calculator', and you should be able to find an example in the demos/ folder (called 'disaggregation').

In the configuration file you can specify what type of disaggregation results you want to compute (in the demo you can find the complete list).

You can also have geographical disaggregation (so in terms of latitude and longitude, it is called 'LatLonPMF') - in this way you can find contributions to hazard

coming from the different sources.

We have a python script that we use to plot disaggregation results, you can find it here: https://github.com/GEMScienceTools/oq-tools/blob/master/output/plotDisaggregation.py

To use the script you need to pass the configuration file used to compute the disaggregation results and the hdf5 file containing the actual results.

The script uses GMT for the actual plotting (so you need to have it installed and in your PATH).

Hope it helps,

Damiano

--
You received this message because you are subscribed to the Google Groups "OpenQuake Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openquake-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
<geographical disagreggation.JPG>