...
Advanced users may also configure other presentation Listeners through the use of an INI configuration file.
Live Statistics Configuration
...
| Note |
|---|
Configuration options are limited for live stats as this is a prototype feature. As the system evolves, so too will the ability to interactively create custom configurations of live stats. |
...
| Anchor | ||||
|---|---|---|---|---|
|
Advanced Configuration: INI File
The stats configuration file (default name: "stats.ini") holds the basic default settings for the stats session. It can also be utilized for advanced configuration to build a list of listeners to attach, and per-listener rules for metric data to be observed by each listener.
Below is an example of a simple configuration file that enables an end-of-render JSON report, including checkpoints:
...
RfB uses the prman command-line mechanism as described above, including the use of the RMAN_STATS_CONFIG_PATH override environment variable. Interactive configuration of live stats is available in the Blender preferences.
Houdini
If the RMAN_STATS_CONFIG_PATH environment variable is set RfH will use that search path to look for a file named stats.ini.
If no file is found, or if that environment variable is not set then the default configuration will be used.
Interactive configuration of live stats is available in the Live Stats window UI.
Katana
If the RMAN_STATS_CONFIG_PATH environment variable is set RfK will use that search path to look for a file named stats.ini.
...
prmanGlobalStatements.stats.configPath (default: ".:${RMANTREE}/etc")
prmanGlobalStatements.stats.configFile (default: "stats.ini")
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<katana release="4.0v2" version="4.0.2.000001">
<node name="__SAVE_exportedNodes" type="Group">
<node baseType="OpScript" edited="true" name="AdvancedStatsConfiguration" ns_colorb="0.050000" ns_colorg="0.260000" ns_colorr="0.090000" ns_errorGlow="0.000000" ns_fromContext="legacy" selected="true" type="OpScript" x="287.350171" y="-212.346316">
<port name="i0" source="GafferThree.out" type="in"/>
<port name="out" type="out"/>
<group_parameter name="AdvancedStatsConfiguration">
<string_parameter name="CEL" value="((/root))"/>
<string_parameter name="location" value="/root/world/location"/>
<group_parameter name="script">
<string_parameter name="lua" value="
-- Default: 'stats.ini'
local configFile = Interface.GetOpArg('user.configFile'):getValue()

-- Default: '.:${RMANTREE}/etc'
-- Can be overriden with RMAN_STATS_CONFIG_PATH
local configPath = Interface.GetOpArg('user.configPath'):getValue()

Interface.SetAttr(
 'prmanGlobalStatements.stats.configFile', 
 StringAttribute(configFile))

Interface.SetAttr(
 'prmanGlobalStatements.stats.configPath', 
 StringAttribute(configPath))

"/>
</group_parameter>
<string_parameter name="executionMode" value="immediate"/>
<string_parameter name="applyWhere" value="at locations matching CEL"/>
<string_parameter name="applyWhen" value="during op resolve"/>
<string_parameter name="modifierNameMode" value="node name"/>
<string_parameter name="modifierName" value="modifier"/>
<string_parameter name="resolveIds" value=""/>
<number_parameter name="recursiveEnable" value="0"/>
<string_parameter name="disableAt" value=""/>
<string_parameter name="inputBehavior" value="by index"/>
<number_parameter name="multisampleUserOpArgs" value="0"/>
<group_parameter hints="{}" name="user">
<string_parameter hints="{'widget': 'fileInput'}" name="configFile" value="stats.ini"/>
<string_parameter expression="'.:'+getenv("RMANTREE", ".")+'/etc'" hints="{}" name="configPath"/>
</group_parameter>
</group_parameter>
</node>
</node>
</katana> |
| Note |
|---|
RfK no longer allows interactive configuration of stats through the PrmanLiveStats Tab. Configuration will soon be allowed through exposed attributes, in the meantime all configuration must come from an INI configuration file as described above. |
Maya
If the RMAN_STATS_CONFIG_PATH environment variable is set RfM will use that search path to look for a file named stats.ini.
If no file is found, or if that environment variable is not set then the default configuration will be used.
Interactive configuration of live stats is available in the Live Stats window UI.
Solaris
The new stats are not yet supported in Solaris.
...