Child pages
  • Real-time Ground Motion Simulation Setup
Skip to end of metadata
Go to start of metadata

This guide is for someone who would like to run a simulation with current library and packaging.

Step-by-step guide

1. How to create a working folder

  1. Get the current working version of gm_sim_pkg by using git clone:

  2. Navigate into gm_sim_pkg directory and download the latest package from the FTP server: https://quakecoresoft.canterbury.ac.nz/seisfinder/private/gmsim/gmsim_pack_latest.tar.gz

  3. Use install.sh to install the package just downloaded in the following format:

     ./install.sh gmsim_pack_latest.tar.gz [event_date] [event_location] [event_magnitude]

     

  4. This starts the installation process.

     

  5. This has created the directory structure for managing the ground motion simulation for 2010 September 4 Darfield earthquake (Mw7.1)

  6. Follow the instruction shown on screen to create required Models and files.


    !!! Before you move on, make sure you do the first line give in the instruction. !!!

2. How to create a Velocity Model

  1. Go to the VM directory that instruction has provided

  2. Execute config_vm.py to generate params_vel.py, a config file used for velocity modelling. The command is in the following format.

    $ config_vm.py magnitude centroid_Depth Latitude Longitude

    Three parameters mag, centroidDepth, lon, lat are mandatory. You can set other options with --option, such as --hh 0.2 or manually set by editing params_vel.py


  3. You can manually edit params_vel.py. But you are strongly advised to run test_vm_params.py to validate your params_vel.py if manually edited. Note that values in Section II will be automatically computed based on the values in Section I, but user can manually edit them. However, any manual changes made to Section III will be ignored. 
    In the example, we execute test_vm_params.py after manually editing the value for "code" from "rt" to "nz". This creates new params_vel.py after making a backup of the original, and shows the difference between two. Notice " | " where a difference is observed (line 30).

  4. Run make_vm.sh to create the Velocity Model

  5. Under the working directory VM, a subdirectory is created Model/20100904_Darfield_m7p1/v1.65_200m which contains the velocity model.

  6. Give the admin (Sung) the path to the VM working directory and request to upload the model. The admin will need to execute sendme.sh in the VM directory.

  7. Files have been successfully uploaded to Fitzroy.

    Bash_code



3. How to create Rupture Model (Source)

  1. Go to the Src directory that instruction has provided

  2. Create the config file that is needed for generating a Rupture Model

    The extra options may differ from type to type. Use: "config_src.py type -h" will show you all the options can be provided for that type of source. 

    example of showing options for type 2:

    And example of creating type 2 Source file:


    If config_src.sh has been run more than once, it will ask you if you want to update/replace a current param or create a new one.

    You can choose to create a new sub-folder with time stamp or replace the old files.

    example of creating new folder:

    If you choose to replace existing params, it will show a comparison between two params(old on the left, new on the right).
    Example of replacing a old param file:

  3. Go to the folder provided by instrutions

  4. Edit the setSrfParams.py
    note: every variables with #!!!PLEASE SPECIFY!!!# must be provided

  5. Create the Model using make_src.sh

  6. Under the working directory Src, a subdirectory is created

  7. Give the admin (Sung) the path to the Src working directory and request to upload the model. The admin will need to execute sendme.sh in the Src directory.

4. How to create observation files

note: you can skip this part if you are running for a future event (not yet happened)

  1. Go to the Obs directory that instruction has provided

  2. Create the config file that is needed
    $ config_obs.py geoNet_ftp_url



  3. Run make_obs.sh to generate all the files

  4. The Vs30 and station files will be under working directory Stat/event_name

  5. Give the admin (Sung) the path to the Obs working directory and request to upload the model. The admin will need to execute sendme.sh in the Obs directory.

5. How to setup the simulation

  1. After admin tells you that all files are uploaded to Fitzroy, Run setup_remote.sh
    $setup_remote.sh username

  2. The location on Fitzroy will be under /nesi/projects/nesi00213/RunFolder/username/event

6. Run the simulation on Low Frequency (LF)

  1. Go to the Simulation Folder, located at /nesi/projects/nesi00213/RunFolder/user/run_name

  2. Run submit_emod3d.sh

    It will ask you to enter a wall_clock_limit and if it should auto submit the job.

    note: if you prefer to change some detail configurations, press 2(no) for auto submit.*

     

    use llsubmit to submit your job if you selected to not to auto submit.

  3. Use llq to check if your job has finished. (job status: R= running, C= Complete, I = idle)
    $ llq -u user

  4. After Emod3d finished, run submit_post_emod3d.sh
    note: if you prefer to change some detail configurations, press 2(no) for auto submit.*
    $ ./submit_post_emod3d.sh

  5. submit the job after you manually edited the post_emod3d_source.ll

  6. Use llq to check if your job has finished. (job status: R= running, C= Complete, I = idle)

7. Run the simulation on High Frequency (HF)

note: this part can run before LF is finished

  1. Run install_bb.sh, to setup the parameters
    Choose from the options according to simulation requirement

  2. Run submit_hf.sh
    note: if you prefer to change some detail configurations, press 2(no) for auto submit.*

  3.  use llsubmit to submit your job if you selected not to auto submit.

  4. Use llq to check if your job has finished. (job status: R= running, C= Complete, I = idle)

8. Run the Simulation on Broadband (BB)

Note: This part MUST wait untill both LF and HF are finished

  1. Run submit_bb.sh
    $ ./submit_bb.sh

  2. Use llq to check if your job has finished. (job status: R= running, C= Complete, I = idle)






Icon