Preflight Configuration and Export

Tools Hackathon - Preflight Checks 2024
1

I’m thinking of adding Json export and Yaml external configuration to pre-flight checks. Export so the data can be aggregated across projects, e.g. with PowerBI. Also I would like to have the ability to configure the checks with different targets, and I would like this to be something that can be overridden. So a firm could set their defaults and push out with pyRevit, but they could also override, in part or whole, the configuration by project, and finally I would like to be able to call the checks with a specific instance override, for example I might call a selection of checks as part of a model sharing export script.

Obviously to do this there should be some consensus, so expressing my ideas here first.

I’m thinking the settings would look a bit like this:

outputwindow: True
exportjson: False
modelchecker:
  - check: modelGroupCount
    skip: False
    min-critical: -1
    min-target: 0
    max-target: 100
    max-critical: 200
  - check: notParametricFamilies
    skip: False
    min-critical: -1
    min-target: 0
    max-target: familyCount * 0.3
    max-critical: familyCount * 0.5

I have no idea how to override settings per project, I don’t like the idea of pushing project file settings out to every Revit user in the firm, and also don’t like Revit schema. I’ll leave that for now but will allow for loading and parsing a default file and passing a partial config when calling the model check class set-up function.

Michael

3 Likes