-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyError: 'exponent' #53
Comments
Dear Ivan, thanks for reporting! Can you please double check that you really have the most up to date version of BEAT installed! Hannes |
Done. All right ! Thanks Ivan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi BEAT Team
I am trying to run the example about of section "Getting started with BEAT". I run the line:
beat init LandersEQ 1992-06-28 --datatypes='seismic' --individual_gfs --n_sources=1 --source_type=MTSource --min_mag=7
However I got the following:
Traceback (most recent call last):
File "/home/lab/anaconda3/envs/beat/bin/beat", line 11, in
load_entry_point('beat==1.0', 'console_scripts', 'beat')()
File "/home/lab/anaconda3/envs/beat/lib/python3.6/site-packages/beat-1.0-py3.6-linux-x86_64.egg/beat/apps/beat.py", line 1686, in main
globals()'command_' + command
File "/home/lab/anaconda3/envs/beat/lib/python3.6/site-packages/beat-1.0-py3.6-linux-x86_64.egg/beat/apps/beat.py", line 303, in command_init
individual_gfs=options.individual_gfs)
File "/home/lab/anaconda3/envs/beat/lib/python3.6/site-packages/beat-1.0-py3.6-linux-x86_64.egg/beat/config.py", line 1437, in init_config
c.problem_config.init_vars()
File "/home/lab/anaconda3/envs/beat/lib/python3.6/site-packages/beat-1.0-py3.6-linux-x86_64.egg/beat/config.py", line 725, in init_vars
lower = default_bounds[variable][0]
KeyError: 'exponent'
As a result only the BEAT_log is generated, with one line that states (not much):
2020-05-11 21:25:32,868 - utility - INFO - Getting relevant events from the gCMT catalog for the dates:1992-06-27 00:00:00.000 - 1992-06-29 00:00:00.000
Thanks in advance.
Best,
Ivan C.
The text was updated successfully, but these errors were encountered: