Notes
Story / Deliverable
I want to use SeisFinder site-search after "scenariotest" branch is merged and bugfixes are made.
When I compute hazard maps, it will only need a single command to compute CS/Emp hazard map and ratio hazard map and histogram of ratio for each IM
When I compute hazard for single/multiple locations, I'd like a simple CLI command that also does plotting hazard curves
When I compute deagg for single/multiple locations, I'd like a simple CLI command
Summaries
Reading from CSVs took 6.5sec for each set of (loc, IM type)
Reading from IMDB also takes 6.5sec for each set of (loc, IM type) for adding the data to the column. BUT if user varies IM level, it only takes 1 sec.
Calculation of Hazard and Deagg is streamlined, and it submits the auto-generated slurm scripts.
Story / Deliverable
When calculating deagg with IM type, location and cs_ver, varying IM_level or exceedance should not force the program to re-read raw IM agg data and process them.
When calculating GM selection, user should be able to use the same set of parameters as deagg calculation
Streamline hazard/deagg calculation steps
<Design/Plan> When I run SeisFinder site-based search, it will allow me to access the data depending on my access levelTasks/Progress
| Who | Status | Deliverables | |||||||
|---|---|---|---|---|---|---|---|---|---|
| (1) | Complete "scenariotest" branch merge and fix bugs | 2 days | Done | Precompute SQLite db for all IM_agg data | 1 day | Viktor | Done | https://github.com/ucgmsim/seisfinder2/pull/46 | |
| (2) | Write histogram plotting code that displays the ratio between CS and Emp hazard map for a given IM | 3 days | Develop an API that outputs all IMs in a numpy array for given IM type, station name | 1 day | Viktor | Done | |||
| (3) | Write two execution methods 1. via SLURM 2. via CLI to compute hazard for single/multiple locations and plotting hazard curves | 2 days | Done | https://github.com/ucgmsim/seisfinder2/pull/50/commits/7c22a29755275916bb4f0f5065dd4218dff88e47 | |||||
| (4) | Write two execution methods 1. via SLURM 2. via CLI to compute deagg for single/multiple locations | 2 days | Done | https://github.com/ucgmsim/seisfinder2/commit/33960f5875c8ac53d9251699ebc9ce0b8beb9490 | |||||
| (5) | Plan Access control/Edition/Release | 2 days | Done | SeisFinder versions, releases and access control | |||||
| (6) | Create a diagram that shows the architectural overview and interaction of components | 3 days | Done | https://www.lucidchart.com/invitations/accept/90eda8c1-1b56-47d4-84b5-cd2b0cbdbb38 |
Known Issues / To Dos
| Update setup process to do step (1) automatically. | 1 day | Sung | Done | ||
| (4) | Fix hazard to use the API from (2) | 1 day | Sung | Done | |
| (5) | Fix deagg to use the API from (2) | 1 day | Sung | Done | |
| (6) | Write site_search_gm_sel.py that mimics the interface of site_search_deagg.py | 1 day | Viktor | Done(to be revisited) | |
| (7) | Automatically generate sl scripts and submit for hazard/deagg calc | 2 days | Sung | Done |
Known Issues / To Dos
- Fault screening based on user specified loc vs. simulation domain is no longer necessary as the API from (2) does all the filtering already
- site_search's ArgParse needs revamp. Very counter-intuitive at the moment.
- site_search and site_search_deagg should generate .sl scrupt and run if executed from Mahuika.