Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • L losscalculator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynamic ExposureDynamic Exposure
  • Global Dynamic ExposureGlobal Dynamic Exposure
  • losscalculator
  • Issues
  • #32
Closed
Open
Issue created Feb 08, 2021 by Tara Evaz Zadeh@taraMaintainer

Detect ground-motion types automatically

Ground-motion types are hard-coded into the program. A variable named gmDict includes the column number of the ground-motion types in the GMF as its values and the ground-motion types as its keys.

For example, the ground-motion field for Attica has the format of lon,lat,PGA,SA(0.3),SA(0.6),SA(1)
Thus gmDict = {"PGA": 2, "SA(0.3)": 3, "SA(0.6)": 4, "SA(1)": 5}

But the program should automatically create gmDict, because it will not remain the same for all ground-motion fields in the future.

Assignee
Assign to
Time tracking