Created by [ Abel Joseph] on May 09, 2020
What Went well?
This term the infrastructure group was able to create several tools for other groups, improve the state of our continuous integration pipelines, and implement best practices for the production environment. We created a containerization solution at the request of the telemetry team, for a bot which was to run in the production environment. We also made improvements to RViz at the request of the Path Planning group. In addition, we automated unit testing for Path Planning with CI, and created linting configurations for Perception. Lastly, we had several meetings with pipeline operators to determine how the production environment could be improved, and have begun implementing solutions based on those discussions.
\
What didn't go well?
Some tasks that were planned for this term remain unfinished (linting for path planning & processing, production environment improvements). This was partially due to the effects of COVID-19, as divisional meeting cancellations impeded collaboration, and the shift to online classes/cancelled exams resulted in an unexpected workload for several members.
\
Lessons Learned?
When faced with an unexpected event such as the cancellation of classes, is crucial that a mitigation plan is created as soon as possible. This will ensure that core members remain engaged and accountable to complete their assigned tasks.
\
+————-+————-+————-+————-+————-+ | Task For | Importance/ | Possible | Plan for | What Can Be | | Next Term | Is | Blockers/Ho | tackling | done if | | | it critical | w | this | campus is | | | for | we can | problem | locked | | | competition | solve them | | | +:============+:============+:============+:============+:============+ | Linting for | Non-critica | Collaborati | Schedule | N/A | | Path | l | on | all | | | Planning | for the | with other | meetings | | | | competition | team | online and | | | | | members | follow up | | | | | impeded by | with team | | | | | COVID | members | | | | | | regarding | | | | | | progress | | +————-+————-+————-+————-+————-+ | Linting for | Non-critica | Collaborati | Schedule | N/A | | Processing | l | on | meetings | | | | | with other | online and | | | | | team | follow up | | | | | members | with team | | | | | impeded by | members | | | | | COVID | regarding | | | | | | progress | | +————-+————-+————-+————-+————-+ | Implement | Non-critica | Collaborati | Schedule | N/A | | CI for | l | on | meetings | | | localizatio | | with other | online and | | | n | | team | follow up | | | repo | | members | with team | | | | | impeded by | members | | | | | COVID | regarding | | | | | | progress | | +————-+————-+————-+————-+————-+ | Add various | Non-critica | COVID may | Use SSH for | Use SSH for | | enhancement | l; | impede | accessing | accessing | | s | the | access to | the rugged | the rugged | | to the | production | rugged | | | | production | code has | | Get in | | | environment | recently | Rugged may | touch with | | | | been backed | fall into | Intel | | | | up, but | the boot | mentors | | | | further | cycle | about the | | | | improvement | | boot cycle | | | | s | | | | | | can be | | | | | | added | | | | +————-+————-+————-+————-+————-+ | Setup | Critical; | COVID may | Implement | Use SSH for | | License | need to | impede | license | accessing | | Server | ensure that | access to | server on | and setting | | | all | server | the NUC | up the NUC | | | machines | (NUC) | once given | | | | can access | located in | the | | | | software | the garage | required | | | | paid for by | | licenses | | | | the team | | | | | | | | Go to the | | | | | | garage to | | | | | | complete | | | | | | the | | | | | | installatio | | | | | | n, | | | | | | or access | | | | | | the NUC | | | | | | using SSH | | +————-+————-+————-+————-+————-+
Document generated by Confluence on Dec 10, 2021 04:01