We use machine-learning (ML) to identify H/S/U victims. The ML model is made by Python and Tensorflow library. Tensorflow is universally used and it is NOT dedicated to the cameras we use (UnitV AI camera).
Of course, all images to train the machine ML model are taken by us. We also did NOT use the ML model generation site of M5 Stack (the company that manufactures the UnitV cameras).
I believe what we do is permitted because we’ve created our ML model and written our code by ourselves. Is this actually allowed?
I would like to know the official answer of the committee as soon as possible.
Would using Google’s Teachable Machine (https://teachablemachine.withgoogle.com/) to create and train a custom model be considered rule-compliant, provided we credit the tool and explain the process in our documentation? Or does the committee expect a deeper technical engagement, such as writing our own training scripts or manually fine-tuning models?
I’d see the first aspect of @Matej fulfilled, because you have to upload your own data. But I’m not sure at all whether specifying the final classes counts as coming up with NN architecture (2. aspect). There are also a few other parameters you can change, but I don’t think it would suit the term „coming up“…
The third point on the other hand shouldn’t be a problem, as far as I’m aware, the model is trained locally inside the browser (I might be wrong though), and you should also be able to change parameters.
Tool: The term “tool” is a comprehensive concept that encompasses both hardware and software components essential for the operation of robots. These can include physical components such as sensors, actuators, or controllers, as well as software elements like algorithms or libraries.
Calibration: Calibration refers to the process in which a team intervenes to adjust or fine-tune the settings of a tool.
Development: Development refers to activities aimed at creating new solutions, technologies, or
systems, as well as enhancing existing ones through innovation and creative problem-solving. In this case, for example, calibration is not considered development since it involves fine-tuning or
configuring an existing system without introducing new features, technological advancements, or innovations.
Tools are allowed as long as they are developed by the team or when they cannot independently complete a task, or a part of a task, that enables the robot to earn points by sending a signal to the controller without further development (e.g., color sensors, cameras, or libraries necessary for sensor operation).
Tools which are not developed by the team, which can independently complete a task, or a part of a task, which enables the robot to earn points by sending a signal to the controller without further development (e.g., line-following sensors, AI cameras, OCR libraries) are prohibited.
Based on this, if you are unsure whether you can use the tool or not, please provide me with more information about how you intend to use it, and I will help you.
