** Notice: all internal pipelines have been restricted to 30 minute timeouts, if your CI/CD runs take longer, either use your own runners or read below **
We would remind everyone that the CI/CD services provided by the university Gitlab servers are intended for CI/CD use only (ie. delivering new versions of your software to your production servers, etc).They are not intended for data analysis or -production use, or creating, building and running servers to do heavy data calculation or visualization.
As a general guideline; if your jobs take more than 15 minutes, you might be running something that is better suited for a dedicated system or a virtual server - in this case, please contact the helpdesk for a solution to your needs.
Data is synchronised and organised into discrete frames that are represented by a `Frame` class. This page outlines the requirements and chosen design for this class since it is central to the entire system
Data is synchronised and organised into discrete frames that are represented by a `Frame` class. A `Frame` has a unique identification and ownership within a `Feed`, along with a timestamp. Frames can be generated for a given ID by either the owner or a non-owner wishing to change the state relating to that `Frame`. A specific protocol must existing for the generation, transmission and receipt of frames. This page outlines the requirements and chosen design for this class since it is central to the entire system.
