Another option for the data format and parser would be JSON and nlohmann_json as the parser.
While I slightly prefer the look of YAML files, the nlohmann_json parser looks to be more fully featured that either json-cpp or yaml-cpp.
Will look at the various use-cases and see which would work better.

For some reason this didn't get automatically closed when you landed the changes. I tried adding the commit to the list of related commits but that didn't do anything either. Is it possible to close it manually?

As part of this review, should check whether there are adequate protections against invalid settings being passed to these models, e.g. not specifying model number 6 for Bs -> phi mu mu decay modelled with BTOSLLBALL, and implement them if missing.

Thanks @kreps - the solution for what to do with the excess BF sounds sensible and the actual changes to the numbers all appear to be correctly done.

Should also take the opportunity to sort out the naming conventions, particularly for the resonances.

Thanks Mark, looks good, I'll merge it.

Many thanks for putting this together Mark, it's great to have an example that uses the MIPW.
I haven't yet tried running it but will try and do so later on, so these are just from a read through and all quite minor stuff.
(For one I've tried out the new "Suggest edit" feature, so hopefully it will be clear what I mean!)

This is mainly a fix of Doxygen warnings but I have taken the opportunity to streamline very slightly the arguments to LauKMatrixPropagator::calcGamma, hence the request for review.

In D58#1640, @kreps wrote:

I think I have it now all, but I ran to another issue with arcanist, which refused to upload diff on a large file without marking it binary. The file is src/EvtGenModels/EvtVubAC.cpp and we might need to change it back from binary when we finish this.

@kreps , @jback feel free to add yourselves as reviewers too
We should also decide whether to extend this to the rest of the package now or leave to later. I'd probably favour doing it all in one go.

Rebase on master

rEVTGEN6d93ea5c4f5e takes care of the CMake configuration to automate the generation of the documentation.
Now just need to add the Doxygen comments to all the classes!

Thanks @kreps , yes the README needs some text in the introduction but agree we can maybe add that in a separate step.
I've just finished going through the History file and making it looks reasonable in Markdown format, see:
https://evtgen.hepforge.org/doc/doxygen/test/md_History.html
So I think this can indeed be landed now.

• Start to convert various files to Markdown format

Thanks for this @johndan. I'm not (yet) very familiar with RDataFrame, so bear with me while I look at that part.
I'm thinking that we could use YAML for the config file for this, which should make it more obvious what the various fields are, make it easier to deal with missing fields, etc.
I've been looking into YAML a little bit already in the context of T48 and this is actually a nicer case in which to try it out for the first time, so I'll have a bit of a play with it.

Thanks for this @johndan. I'm not (yet) very familiar with RDataFrame, so bear with me while I look at that part.
I'm thinking that we could use YAML for the config file for this, which should make it more obvious what the various fields are, make it easier to deal with missing fields, etc.
I've been looking into YAML a little bit already in the context of T48 and this is actually a nicer case in which to try it out for the first time, so I'll have a bit of a play with it.

Looking into using YAML for the data format and the yaml-cpp package for parsing it.

Great, many thanks indeed!

Thanks @mwhitehe, the numbers look good. Just one small inline comment.