Add support of YAML configs

[ericstoneking]

Add support of YAML configs

[ericstoneking]

I can't promise I'll adopt what you come up with, but I'll be interested in seeing it. To fit in with 42's style, a scheme for reading input files should:

1. Minimize (ideally avoid) external dependencies. A "yamlkit.c" would be best. Linking to external libraries is sub-optimal.
2. Provide a template in the input file itself. I'll be interested to see how you sort out the Keplerian/RV/file options.
3. Fail in an obvious way if some inputs are not provided. Obnoxiousness is a feature. Chasing what appears to be a dynamics bug when it's actually a bad input is painful enough as it is. I fear that having a robust, typo-tolerant input scheme would only make that worse.

Regards,
-Eric (he/him)

[vladtcvs]

Example for orbit:
https://github.com/vladtcvs/42/blob/master/InOut/Orb_Ellipse.yaml

Example for SC:
https://github.com/vladtcvs/42/blob/master/InOut/SC_Simple.yaml

Example simulation description:
https://github.com/vladtcvs/42/blob/master/InOut/Inp_Sim.yaml

[vladtcvs]

I've used https://github.com/pantoniou/libfyaml for yaml because it provides much more useful interface than libyaml. I never heard about "yamlkit.c", and the only lib with name yamlkit is https://github.com/patrickt/yamlkit, but it's objective-c. Can you please give link to yamlkit.c?

[ericstoneking]

Sorry, "yamlkit.c" is shorthand for: Code up whatever yaml support you need in C, and put it in Kit/Source along with all the other *kit.c files, so we can build it along with the rest of 42, thus avoiding adding an external dependency.

[ericstoneking]

Looking at your examples, I think readability is in the eye of the beholder. I might suggest something that I've seen others do: make a front end that takes your yaml input files, and translates them into the format that 42 expects.