Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • prodimopy prodimopy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ProDiMo
  • prodimopyprodimopy
  • Merge requests
  • !33

Merged
Created Jul 14, 2025 by Christian Rab@c.rabMaintainer

Deal with possible malformed number strings in prodimo output files, for some (very few) fields.

  • Overview 0
  • Commits 1
  • Changes 3
  • e.g. it can happen that a number is written as 1.67+101. python cannot deal with that
  • added convenience function _convToFloatCheck, that catches ValueError, prints a warning and fills the number with some value.+
  • this allows that the reading goes on, even if some numbers are malformed
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fixlineestreading