📄️ Understanding the architecture
To understand the software mechanics throughout these docs, we will start by outlining the chosen software architecture and the rationale behind it. This will make it easier to understand the several software components later on.
🗃️ Arranging communication between services
3 items
📄️ Resolving dependencies
When discussing the output-only software design approach, we already created a notion of dependencies. Recall how such dependencies arise by considering or running example pipeline again:
📄️ Debugging your pipeline
At this point, you have been introduced to all the essential building blocks of the modular software stack provided by the ASE framework. Specifically:
📄️ Tuning
After you have written your software, you will most likely want to tune it. Tuning is the process of modifying parameters that your code uses to optimize for your given challenge. Consider our Camera module from the running example: we would like to tune the brightness and contrast so that the module optimally detects the track edges.
📄️ Testing yourself
This section concludes the introduction. It is good practice to test your knowledge by answering the following questions individually. If you struggle doing so, it might be wise to review parts of the introduction docs again. Naturally, you can ask your daily supervisors to clarify.