Configuring Multi-fidelity Representations
Configuration of the Windchill system to generate Multi-fidelity representations during the publishing process is driven by a Publish Rules file. The following steps describe how to configure the system quickly to generate Multi-fidelity representations:
1. Enable publish rules for the desired CAD system. See Enabling Publish Rules.
2. Configure a Publish Rules file containing rules dictating the number of fidelities to create and the options for defining different elements of display for each fidelity instance.
An example Publish Rules file is available at the following location. Use it to generate five fidelities during the publish process.
<Windchill>\codebase\com\ptc\wvs\server\xml\PublishRules-Multi-fidelity.xml
* 
This example file configures for Creo Parametric. Change the “authoring-application” tag to reference the appropriate internal name of the Authoring Application for other CAD systems.
See Configuring Publish Rules to upload a Publish Rules file.
3. Publish a CAD document and review the WVS Job Monitor log. If the configuration is correct, the following message appears:
Generating Multi-fidelity representation
Configuring Custom Multi-fidelity Representations
The example Publish Rules file PublishRules-Multi-fidelity.xml is recommended as a starting point to configure the WVS infrastructure to generate Multi-fidelity representations. Tailor Multi-fidelity to the needs of your business. To begin, consider the following two questions:
What is the optimum number of fidelity soft types that are needed in your enterprise?
What elements are included or excluded from each?
Take into consideration the following points:
The greater volume of storage needed.
The number of fidelities to be created during the publishing process is configurable in the Publish Rules file— For example, referring to the provided PublishRules-Multi-fidelity.xml, if you want to use High Fidelity, Medium Fidelity and Low Fidelity, remove the FidelityBBox and FidelityEMPTY options. Then your Multi-fidelity representation is created with three associated fidelity instances. You can also add new fidelity subtypes. See Creating New Fidelity Subtypes to view the procedure of creating a new subtype.
Determine the options for defining the elements—The MCAD Adapter uses the PVS Change utility to post-process the 3D viewable data and metadata that was generated by the initial publishing of the MCAD data. The level of viewable 'fidelity' stored on each fidelity instance is determined by the PVS Change recipe settings defined in the respective publish rules. The correct recipe options and values to utilize in the Publish Rules is determined by using the Creo View Recipe Editor to create the sample PVS Change Recipe files. See Configuring the PVS Change Utility in Creo View MCAD Adapter Installation and Configuration Guide (Creo View Installations- und Konfigurationshandbuch für MCAD-Adapter).
Follow these steps
1. Start a command shell and change directories to the location where the Creo View adapters are installed. Execute the following command:
bin\rcpedit.exe
2. In the rcpedit dialog box, select Creo View PVS Change, and then Create. The Creo View PVS Change Recipe Editor opens.
3. Indicate which options to use to process that data by removing data or tessellation from the viewable for this fidelity. For example, clear Mass Properties, Datum Planes, and Screen Annotations so that data of these entities is not output to the fidelity’s OL files.
4. Select Save As, and specify a name to save the recipe file, for example, SimpleFidelity.rcp.
5. Open the file SimpleFidelity.rcp into a text editor, and copy the options reflecting the changes in the Recipe Editor.

adapter/outputMassProps=0
adapter/outputDatumPlane=0
adapter/outputAnnotScreen=0
6. In Publish Rules, add the options to a specific fidelity definition.
<option name="adapter/outputMassProps" value="0"/>
<option name="adapter/outputDatumPlane" value="0"/>
<option name="adapter/outputAnnotScreen" value="0"/>
In some cases, to generate a “lower” fidelity rendition of the geometry you can reduce the Chord Height (chord deviation). The chordal deviation is a factor of the analytical tolerance, which is defined as a factor of the component bounding box’s longest diagonal. By default, the chordal deviation is a factor of 1 of the analytical tolerance.
<option name="adapter/chordHeight" value="1"/>
To make the tessellation coarser, increase the factor the chordal deviation. The example shown here makes the chordal deviation 5 times larger than the default value.
<option name="adapter/chordHeight" value="5"/>
* 
The Chord Height option is included in the Recipe Editor’s Admin mode. To open the Recipe Editor in Admin mode, use this command:
bin\rcpedit.exe -admin
Configuring the Bounding Box
To generate a bounding box as the only output use the following options.
To generate the bounding box from the OL file contents that would be output without applying the bounding box option. This enables you to remove certain types of data such as model annotations from the output to control, for example, if the bounding box is generated only from the geometry and not including annotations and datum curves.
<option name="adapter/generateBboxOL" value="1"/>
To output only a Creo View point at the center of the bounding box instead of outputting a bounding box:
<option name="adapter/generateBboxCenter" value="1"/>
To output a Creo View point with a label of the CAD system’s name (not the Windchill name) for the component:
<option name="adapter/generateBboxCenter" value="2"/>
To set the color of the bounding box or the point:
<option name="adapter/bBoxColor" value="200,0,255"/>
where the 3 values indicate the red, green, and blue components in the range of 0 to 255. If no color is specified then the data is uncolored and uses the Creo View client’s defaults for uncolored objects.
Publish the configured fidelities, then view and examine the results. Try different sets of Publish Rules until you accomplish the balance of contrast and content required within and between the different fidelities.
War dies hilfreich?