Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S shakyground2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Shakemap
  • shakyground2
  • Merge requests
  • !32

Merged
Created Dec 17, 2021 by Graeme Weatherill@gweatherOwner

Bug/oq change dec2021

  • Overview 0
  • Commits 5
  • Pipelines 4
  • Changes 5

More upstream changes to the openquake.hazardlib.contexts.ContextMaker class broke the Shakemap calculator (yet again!). Fundamentally now one cannot work with the three separate contexts (RuptureContext, SitesContext, DistancesContext) but with the single context object. Trying to keep changes to a minimum I am still calling the GMPEs themselves with three inputs (now just the context object repeated), which is still supported by OpenQuake specifically for this backward compatibility, even if it is inelegant.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: bug/oq_change_dec2021