Thanks Michal.
The config file is mostly just the default values with the only customisation coming in the first 5 lines:

• line 1 to run only the modernize-use-nullptr check
• line 3 to ensure that it warns about things in our header files
• line 5 so that it uses our .clang-format file for reformatting after any auto-applied changes

I have no doubt that the existing code will need cleaning up as we enable more checks. This is why I say "eventually" about having this run automatically, otherwise we'll just be swamped with warnings. A point for subsequent discussion will be what checks we want to use and in what order to start to gradually enable them and fix stuff as we go. I'll create a task where we can have such a discussion.

Thanks John!

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.