Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • 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
  • Merge requests
  • !51

Resolve "Fix the losscalculator to accept more mappings than needed"

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Tara Evaz Zadeh requested to merge feature/46-fix-the-losscalculator-to-accept-more-mappings-than-needed into master Nov 12, 2021
  • Overview 1
  • Commits 1
  • Pipelines 2
  • Changes 1

Closes #46 (closed) Sometimes im_types_dict.get(self.intensity_measure_map[im_ff], None) is equal to none, then we receive an error. But we do not care when it is none (which mean there are more mappings given than needed). In this case, in order to ignore None we put it in a for loop and only proceed for the ones that do not None.

\approve @tara @shinde

Edited Nov 12, 2021 by Tara Evaz Zadeh
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/46-fix-the-losscalculator-to-accept-more-mappings-than-needed