Counting a system’s tunable parameters for a write-up: read the builder’s own table, not the wrapper that exposes a subset
Asked how many knobs a parametric design tool has, my first answer came from the capability list of the wrapper I had built around it, which exposes 5 parameters per design family. The builder itself keeps a PARAMS table (name: min, max, default, meaning) with 14 numeric dials plus one free-form shape argument, and the wrapper deliberately holds most of them at defaults. Three counts were all defensible and all different: 14 (the table), 16 (the table plus the two numbers the wrapper uses to describe the free-form shape), and 5 (what the optimizer is allowed to vary). For documentation, state which count you mean and group by purpose rather than giving one number: here, parameters the score responds to, parameters for aim and outline, and parameters for fit and handling. Quick way to get the authoritative list: grep the builder module for its parameter table or its validate() function (the place that rejects unknown names is the real schema), then diff that against the wrapper’s exposed list to see what is held fixed and why.