-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implementing Config Files #91
Conversation
…e, added example for reading INI files and ZVertexCut
Latest commit changed the config file format to YAML using the yaml-cpp library. This allows for type invariant config files and we can now have arrays of maps which allows us to define run & pid dependent cuts. Changes in latest commit: |
This reverts commit 06b597d.
This is also why we build a newer At least macOS tests 00 and 01 are working. |
I pushed a lot of commits here. I'm gonna reset your branch to where you left off, and put all my changes on a separate branch and file a PR against your fork, so you can see the difference and review. Then we can merge the two together into |
…t downstream place
Purpose of pull request is to implement config files in iguana eg for configuring different algorithms. The desired file format must be able to contain all data types used in iguana (int, double, string, and arrays of), library for this file format must be able to parse and serialise to the file format. We also want the file format to be type independent or at least easily pluggable into the algorithm type variant.
Current pull request investigated using INI with the GLib library. This might not be suitable due to a requirement for the file format to be able to hold arrays of dictionaries. Current PR made following changes:
Added functionality to read from INI file
Added ZVertexCut as example
Added example for reading INI files (will get rid of this eventually but has example code for serialising)
Added an example forZVertexCut
NB: This is currently a draft PR as we investigate different file formats.