-
in the current GUI does not see the status of background processes like TC.exec and LogSink. Some kind of a heatbeat protocol should be implemented to report the status of non-user-interface processes…
-
to use the IVCT system, certain components are required. Currently there is no status information available, that could be used within UI to indicate the overall status. It is also not possible to get…
-
I notice the following message in the console output of the TC runner. The message is marked as an error. The volumes actually already exist from a previous run, although I see the same error when st…
-
use the path /root/conf as default for the IVCT_CONF setting
-
running `gradle build` in the IVCT_Framework root folder does not work out of the box because the tests for the Command project require ENV variable IVCT_CONF to be configured.
It would be preferab…
-
The IVCT GUI enforces a non-empty RTI settings designator. This way it is impossible that the system ever falls back on the default. In the case of the IVCT Docker version the default can be set from …
-
The HW SUT image does not support setting the LRC advertised address. The HW container can therefore not be contacted by a remote federate -- i.e. the IVCT. This applies to the HW SUT composition in o…
-
**Compositions used**
- https://github.com/IVCTool/IVCT_Operation/tree/develop/ivct-pitch/host-mode
- https://github.com/IVCTool/IVCT_Operation/tree/develop/sut-helloworld-pitch/host-mode
**Test …
-
I run the following compositions:
- ivct_pitch (https://github.com/IVCTool/IVCT_Compositions/tree/master/ivct-pitch)
- sut-shipsim-pitch (https://github.com/IVCTool/IVCT_Compositions/tree/master/sut…
-
To access the IVCT web UI I need to use a URL like ``http://:8180/nato.ivct.gui.nato.ivct.gui.ui.html``. An empty path should be sufficient: ``http://:8180``.