I am not sure if this would actually be helpful, but for stats such as tris/vertex (maybe less so this one), tris/surf, and surfs/vol, writing an output file that lists the surf or volume ID or entity handle and the number of tris, surfs, etc. This could be an optional output file but might be helpful if the user wants to know the data for a specific surface or volume. I think it would be a little too much to do the tris/vertex, but tris/surf and surfs/vol could be doable.
Another way to get this information would be to make it an argparse option to specify a specific volume or surface ID and then print to screen the # triangles, surfaces, etc.
I am not sure if this would actually be helpful, but for stats such as tris/vertex (maybe less so this one), tris/surf, and surfs/vol, writing an output file that lists the surf or volume ID or entity handle and the number of tris, surfs, etc. This could be an optional output file but might be helpful if the user wants to know the data for a specific surface or volume. I think it would be a little too much to do the tris/vertex, but tris/surf and surfs/vol could be doable.
Example output:
Another way to get this information would be to make it an argparse option to specify a specific volume or surface ID and then print to screen the # triangles, surfaces, etc.