...
- The RenderMan option:
jsonFilename - Configuring a JSON Report listener in the stats.ini configuration file
- Both an option and a configuration file, which will provide either two reports or override a configured JSON Report output file name
If no filename is provided, and no JSON Report listeners are found in the configuration file, the final report is disabled.
...
Add for 26.0:
The viewing of the diagnostic report is best done through the new RenderMan Stats Portal application, stportal
...
which can be used for both live data presentation and offline report introspection.
...
Its content is limited but useful for viewing the JSON metric hierarchy and comparing two or more reports.
Configuration
Easy Setup: Render option
...
When setting up a report using the configuration file it is possible to override the outputFilename parameter for the configured report by specifying a qualified file name for the RenderMan jsonFilename option. It is not sufficient to simply specify a new JSON filename since it is technically possible to configure multiple JSON reports in a single configuration file. In order for For the option override to take effect the option value must contain the override file name and the name of the listener to which the override should be applied.
...
Without this qualification, a separate report will be generated for the file name specified by the option.
...
Add for 26.0:
Viewing Report Data
The JSON document produced by the JSON Report listener is hierarchical, matching the hierarchy of the metrics it contains.
Below is the display of an example file in stportal where you can see the "raytracing" subsystem highlighted with the tree of its metrics below:
The metric name tree is on the left and in the second column is the raw payload data. The data displayed in stportal is a direct translation of the data from the file, with minimal formatting for clarity.
...
.