Execution of physical testing
Summary
Execution of physical testing
S00112
Version: 1.10
- arable farming
- horticulture
- viticulture
- test execution
- physical system (possibly including software); software
- Location: in Italy
- Offered by: POLIMI; UNIMI
Description
With this service, we offer support throughout each step required for the actual execution of physical tests. First, we offer general support concerning activities such as monitoring that test operations comply with the testing protocol (defined, for instance, via Service S00107).
Moreover, we offer technical support at test execution time, ensuring, for example, that all necessary processes on the system under test are correctly configured and running.
We also take care of managing the technical infrastructure during test execution, including verifying the correct data exchange between the system under test and the AgrifoodTEF infrastructure.
If required, we will also make available to customers external agricultural machinery (e.g., tractor and relative implements) and personnel (e.g., tractor driver) as needed to allow the correct and complete execution of all tests according to their protocol (e.g., defined via Service S00109).
Example service: In the context of testing a weeding systems on facilities ready for test execution (thanks to preparatory activities performed via S00111), test runs are set for specific times of the day, under specific lighting conditions (e.g., according to the testing protocol defined via S00107). Before testing, AgrifoodTEF verifies the correct operation of: sensors (including their calibration), data stream logging, communication between the Robot Operating System (ROS) modules running on the system under test and any monitoring and logging systems, etc. Dry runs are conducted ahead of testing time to ensure the success of subsequent testing. Our team remains on site for the whole test duration and monitors the status of the system (e.g., system logs are streamed to a laptop on site via SSH) to promptly intervene should any technical issues arise during testing (e.g., sensors start to malfunction after the system under test visits the first plant row).