-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacement Options File Parser #97
base: master
Are you sure you want to change the base?
Conversation
Hello @TomNicholas! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2020-01-07 11:30:47 UTC |
Codecov Report
@@ Coverage Diff @@
## master #97 +/- ##
==========================================
+ Coverage 47.89% 55.83% +7.94%
==========================================
Files 11 12 +1
Lines 1069 1490 +421
Branches 214 354 +140
==========================================
+ Hits 512 832 +320
- Misses 496 568 +72
- Partials 61 90 +29
Continue to review full report at Codecov.
|
|
||
|
||
SECTION_DELIM = ':' | ||
COMMENT_DELIM = ['#', ';'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BOUT++ has dropped support for ;
as a comment character, I doubt you'll come across an input file that uses them
I'm trying to write a replacement BOUT Options File Parser to replace the
boutdata.BoutOptionsFile
class, which solves the issues in #94. The biggest difference is that this version has lots of tests.Due to the bespoke structure of
BOUT.inp
files, I've ended up writing it from scratch, taking a lot of inspiration from the old class. For BOUT v5 I think the options file format should be changed to follow YAML strictly, but this is for until then.Currently a work-in-progress, but feedback is welcome.