You can use task rules to change the way that Fusion processes files. As soon as you implement a task rule, it applies to all the tasks that Fusion performs. In other words, you can't apply task rules to individual assets or projects.
You can add one or more of these task rules to your asset root’s .config directory:
- ImageryPacketLevel makes it faster to build imagery projects by assigning two CPUs to process a pack file instead of one.
- TerrainPacketLevel makes it faster to build terrain projects by assigning up to six CPUs to process a pack file.
- KRP lets you manage disk space by writing large imagery files to a volume you specify, instead of to the default raster.kip directory in asset root.
- KRMP lets you manage disk space by writing mask files to a volume you specify, instead of the default
mask.kmpdirectory in asset root.
Implementing task rules
To implement a task rule:
- Create the task rule using the XML sample code shown below for each rule.
- Depending on the rule you want to use, name the task rule ImageryPacketLevel.taskrule, TerrainPacketLevel.taskrule, KRP.taskrule, or KRMP.taskrule. Fusion uses these names when the tasks run, so don't change them.
- For the KRP and KRMP task rules, define the volumes you want Fusion to write files to. See Defining volumes.
- Place the task rule files in the asset root's
.configdirectory. - Restart the system manager using the
/etc/init.d/gefusionstopandstartcommands.
ImageryPacketLevel task rule
By default, Fusion assigns one CPU to work on each pack file. You can use this task rule to assign two CPUs instead. Fusion creates pack files during project builds, so this rule makes it faster to build a project. However, placing more than two CPUs on a pack file doesn't necessarily speed up processing, so you should keep the maxNumCPU value at 2.
<TaskRule>
<taskname>ImageryPacketLevel</taskname>
<inputConstraints/>
<outputConstraints/>
<cpuConstraint>
<minNumCPU>2</minNumCPU>
<maxNumCPU>2</maxNumCPU>
</cpuConstraint>
</TaskRule>TerrainPacketLevel task rule
By default, Fusion assigns one CPU to work on each terrain pack file. You can use this task rule to assign up to six CPUs instead. Fusion creates pack files during project builds, so this rule makes it faster to build a project. Set the minimum CPU value to a number from 1 to 6, and set the maximum to a number between 2 and 6.
Sample: TerrainPacketLevel.taskrule<TaskRule>
<taskname>TerrainPacketLevel</taskname>
<inputConstraints/>
<outputConstraints/>
<cpuConstraint>
<minNumCPU>1</minNumCPU>
<maxNumCPU>6</maxNumCPU>
</cpuConstraint>
</TaskRule>KRP task rule
When Fusion creates an asset, it writes large imagery files to the raster.kip directory in asset root by default. You can manage your disk space by using the KRP task rule to write these files to a different volume. See Example of File Locations.
In the sample below, the volume you’ve created is products. To learn how to create a new volume, see Defining volumes.
<TaskRule>
<taskname>KRP</taskname>
<inputConstraints/>
<outputConstraints>
<outputConstraint>
<num>0</num>
<requiredVolume>products</requiredVolume>
<pathPattern>${assetref:dirname:sansext}-${vernum}${defaultpath:ext}</pathPattern>
</outputConstraint>
</outputConstraints>
<cpuConstraint>
<minNumCPU>1</minNumCPU>
<maxNumCPU>1</maxNumCPU>
</cpuConstraint>
</TaskRule>You can also enter a second requiredvolume tag in your task rule to specify the next available volume in case the first volume fills up. However, you'll need to restart the system manager to trigger Fusion to write files to the next volume.
KRMP task rule
When Fusion creates an asset, it writes the mask files to the mask.kmp directory in asset root by default. You can manage your disk space by using the KRMP task rule to write these files to a different volume. See Example of File Locations. In the sample below, the volume you’ve created is products. To learn how to create a new volume, see Defining volumes.
<TaskRule>
<taskname>KRMP</taskname>
<inputConstraints/>
<outputConstraints>
<outputConstraint>
<num>0</num>
<requiredVolume>products</requiredVolume>
<pathPattern>${assetref:dirname:sansext}-${vernum}${defaultpath:ext}</pathPattern>
</outputConstraint>
</outputConstraints>
<cpuConstraint>
<minNumCPU>1</minNumCPU>
<maxNumCPU>1</maxNumCPU>
</cpuConstraint>
</TaskRule>You can also enter a second requiredvolume tag in your task rule to specify the next available volume in case the first volume fills up. However, you'll need to restart the system manager to trigger Fusion to write files to the next volume.
Defining volumes
The KRP and KRMP task rules include a requiredvolume tag that indicates where to write files. You need to make sure that this volume is defined and has enough space to hold the files. To define the volume, use the geconfigureassetroot -- editvolumes command, then edit the XML as shown in the sample below. In this sample, the volume you’re creating is called products.
<products>
<netpath>/gevol/products</netpath>
<host>linux</host>
<localpath>/gevol/products</localpath>
<reserveSpace>100000</reserveSpace>
<isTmp>0</isTmp>
</products>Example of File Locations
The table below shows an example of the default file locations and the locations after applying the KMP and KRMP task rules. In this example, the asset root is /gevol/assets, the volume you’ve created is products, and you’ve built an asset called TestImage in the imagery subdirectory.
| Task rule | File type | Default location | Location with task rule |
|---|---|---|---|
| KMP | large imagery files |
/gevol/assets/imagery/TestImage.kiasset/ products.kia/ver001/raster.kip |
/gevol/products/imagery/ TestImage-001.kip |
| KRMP | smaller mask files |
/gevol/assets/imagery/ TestImage.kiasset/ maskproducts.kia/ver001/mask.kmp |
/gevol/products/imagery/TestImage-001.kmp |