vsTASKER 7 User Manual
×
Menu
Index
Search
 
   
   
   
 
Copyright VirtualSim 2004-2020 - All rights reserved

Properties

 
Properties
1

Federation Name

1. Federation Name
Use this field to change the name of the Federation.
It is normally extracted from the loaded Federation File.
vsTASKER will try to join/create the Federation named according to this string.
 
2

Federation File

2. Federation File
Use to import a Federation file located by default in /data/Fom directory. The file might be .xml (1516) or .fed (for 1.3)
Use to refresh all OMT and FedItems objects with the content of the current file. This can be useful inside an update cycle:
1 - Add/Remove/Update an Object and the OMT level (Object, Interaction, Data definition, ...)
2- Export the OMT definition as an FDD file.
3- Refresh the SOM part (FedItems) with the new data from the file.
 
3

Reload

3. Reload
Reload the FDD and rebuild all OMT counterpart data structures.
This does not change any FedItem definitions.
In case of Federation change (or update), manual changes must be done by user on the SOM part.
 
4

Discard Path

4. Discard Path
When this option is selected, the FDD filename only will be given to the rtiAmbbasador to create the federation execution.
This can be useful when the FDD will be available on the same directory as the executable (standalone exe or not).
 
5

Clear All

5. Clear All
Use this button to remove all vsTASKER HLA definitions, including all OMT data and FedItems.
This action does not remove Data Models generated by the OMT converter.
Also, Federation files are not removed from the disk.
 
6

Federate Name

6. Federate Name
By default, when no name is provided, vsTASKER will use the label vsTasker + a uniq ID.
If something is specified in this field, vsTASKER will use this string and will append an ID to make it uniq on the Federation.
 
7

Force Generation

7. Force Generation
 
By default, vsTASKER does not generate any HLA code when no FedItem is defined (or when all have been disabled).
When this checkbox is ticked, HLA code will be generated.
An RTI must be specified, even if no FDD is loaded.
 
8

Disabled

8. Disabled
 
When this checkbox is ticked, the HLA code is not generated whatever the FedItem definitions are.
Also, RTI will not be joined in any way.
 
9

Import / Export

9. Import / Export
 
Export or Import to a file all FedItems definitions (SOM).
This can be useful to exchange between databases, users (or versions) the full HLA environment.
When an HLA environment has been setup for a specific Federation, saving it for reuse with another database.