Feature-level composition parser#934
Conversation
|
Thanks for breaking up #926, this makes the current new functionality you're adding here much easier to digest |
| check_entry(const std::string &name) const; | ||
|
|
||
| struct composition_property | ||
| { |
There was a problem hiding this comment.
Moved up since the struct must be declared before get_vector()
| "name":"TestPlate", | ||
| "max depth":300e3, | ||
| "coordinates":[[0,0],[100e3,0],[100e3,100e3],[0,100e3]], | ||
| "coordinates":[[0,0],[100e3,0],[100e3,50e3],[0,50e3]], |
There was a problem hiding this comment.
Add a test case for different plate models
Coverage Report for CI Build 24134920095Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage decreased (-0.2%) to 98.245%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
|
|
Can you split out the fix typos into a seperate pull request (make a new branch from main, and you can use |
b7ae84f to
a12a8c6
Compare
|
I squashed my own typos into Extend the parser to all features. The typo in the installation_methods.md is left as is. Maybe I should drop the Git GUI completely :). |
|
On my machine with Windows Subsystem for Linux it compiles just fine, can't figure out why it fails some tests here. I am afraid to keep pushing commits just to test. |
Don't be afraid, push as much as you need to find and fix the issue. The testers automatically stop and restart if you push new commits. I think the problem is that you need to include world.h (or where ever |
|
You might be able to reproduce the issue if you turn off the unity build. You can do that with |
Following #909, #926 (obsolete), and #932, users now can assign compositions using an array of names (string) or indices (unsigned int) that they define in the composition_properties map. Name-based entries are parsed and resolved to their corresponding composition indices (and associated default properties)
Although the schema and tests are currently valid, I have not yet identified edge cases where parsing may fail for random composition profiles. In addition, the output naming function has not been updated yet, so visualization still shows Composition_[n] labels.