Skip to content

Conversation

@prmukherj
Copy link
Collaborator

Case Reader was not able to parse numerical values like: 2[m/s].

That behavior has been fixed.

Copy link
Collaborator

@tejalprabhu01 tejalprabhu01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested with the problematic case file. works! Thanks!

@prmukherj prmukherj merged commit c2366b5 into main May 3, 2023
@prmukherj prmukherj deleted the fix/case_reader_parse_values_with_unit branch May 3, 2023 15:33
mkundu1 pushed a commit that referenced this pull request May 3, 2023
* Case Reader to parse numerical values with units.

* Updated logic.

* Update value.

* endswith instead of suffixes.

* Update endswith -> Path-match

* Improve error handling.

* Update test with correct error type.

---------

Co-authored-by: Your Name <you@example.com>
mkundu1 added a commit that referenced this pull request May 4, 2023
* Case Reader to parse numerical values with units. (#1570)

* Case Reader to parse numerical values with units.

* Updated logic.

* Update value.

* endswith instead of suffixes.

* Update endswith -> Path-match

* Improve error handling.

* Update test with correct error type.

---------

Co-authored-by: Your Name <you@example.com>

* Bump version 0.13.1

---------

Co-authored-by: Prithwish Mukherjee <109645853+prmukherj@users.noreply.github.com>
Co-authored-by: Your Name <you@example.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CaseReader fails while reading the case file: RuntimeError: Could not read case file CaseReader cannot parse values which are like this '2[m/s]'

5 participants