This document explains how to use the implementation of hazard_search.py. Note that it currently works for CyberShake17p9 (v17p9) version only.

• ssh your_login@dev01-quakecore.canterbury.ac.nz (if you don't have a login contact Melody or Daniel)
• cd /var/www/seisfinder2/CLI
• You will find lots of scripts, enter values in hazard_search_config.ini. A sample config for v17p9 is shown below:

  • [HAZARD_SEARCH]
    CYBERSHAKE_VERSION = Cybershake17p9
    TMPLOCATION_TO_CREATE_HAZARD_FILES = /rcc/home/projects/quakecore/cybershake/v17p9/Hazard/
    EMPIRICAL_FILES_LOCATION = /rcc/home/projects/quakecore/cybershake/v17p9/Empiricals
    SQLITE_DB_PATH = /rcc/home/projects/quakecore/cybershake/v17p9/seisfinderdb.db
    FAULT_LIST_CSV_FILE_LOCATION = /rcc/home/projects/quakecore/cybershake/v17p9/cyber_shake_file_v17p9.csv
    IMDB_DB_LOCATION = /rcc/home/projects/quakecore/cybershake/v17p9/IMDB/database.sqlite

• The one that you need to run is hazard_search.py.
  
  • python hazard_search.py -h will show the help for the script.
  • python hazard_search.py -l returns all the simulation groups we currently have (disabled and we only have v17p9).
  • python hazard_search.py -s latitude longitude IM (or --single cshake_ver latitude longitude IM) will create a temporary directory for you and will copy (if they exist) the empirical file for the closest station that we have for the given latitude and longitude. It will print some instructions on how to calculate hazard and deaggregation.
  • python hazard_search.py -m csv_file IM (or --multi cshake_ver csv_file IM) takes as input a CSV file containing latitude,longitude lines for several locations of interest. As previously, it will copy all the relevant empirical files to a temporary folder. The instructions printed will  be shorter, but you will be provided some bash scripts to automate the execution.