-
Notifications
You must be signed in to change notification settings - Fork 3
Building and starting the project
First, follow the instructions to install the IVCT Framework if it is not already done. Make sure the compiled files are present on the local m2 repository as this project is dependent on them. It might be necessary to modify the files from IVCT_Framework in order to properly link the
In the IVCT_Framework folder:
gradlew clean
gradlew build
gradlew install
The same steps then need to be performed for the Models & Encoders project, available at https://github.com/MSG134/Models-Encoders
When these dependencies are taken care of, you must then setup the Pitch dependencies for the EntityIntegrityChecker.
Make sure the IVCT_HLA_BaseEntity/IVCT_HLA_BaseEntity.gradle, EntityAgent/EntityAgent.gradle and TS_EntityIntegrityChecker/TS_EntityIntegrityChecker.gradle "compileOnly files" and "runtime fileTree" values point to your installation of pRTI (or other RTI) by removing the IEEE1516e dependencies:
and replacing them with Pitch dependencies:

You can then build the TestSuite itself, as the necessary dependencies are now installed. In the TestSuite folder: gradlew build gradlew install
- It is important to copy and paste the TS/IVCT_Runtime contents to the IVCT_Framework/RuntimeConfig folder without overwriting.
- TS_EntityIntegrityChecker/build/install/TS_EntityIntegrityChecker/ folder needs to be copied into IVCT_Framework_RuntimeConfig/TestSuites/
- Then set the rtiHostName in IVCT’s RuntimeConfig/EntityAgent/TS_EntityIntegrityChecker/TcParam.json
- If you are using the SiSuT (Agent), then its RuntimeConfig/IVCTsut/EntityAgent/resources/config/config.properties must be set with proper values.
The badge and the SuT information should have been copied from the TestSuite to the IVCT_Framework'S RuntimeConfig. The SuT and the IVCTtest use the same scenario document and are both connected to the same federation. The SuT has the capability to create the entities as requested in the .csv scenario.
The environment variable IVCT_CONF must point to the RuntimeConfig folder.
At this point, everything should now be ready to be started from the UI project communicating with the TC.exec project.