** 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.
@@ -14,3 +14,7 @@ The service would need to provide at least the following:
...
@@ -14,3 +14,7 @@ The service would need to provide at least the following:
* Access to overlay or additional data associated with feeds
* Access to overlay or additional data associated with feeds
* Automatic camera control options
* Automatic camera control options
* Sharing of cameras and scene configurations by users with other groups of users
* Sharing of cameras and scene configurations by users with other groups of users
More advanced functionality to add eventually: Composite / mix multiple scenes together. To achieve this it has to be possible to perform filtering/clipping as well as merge operations on the different sources. This requires a sophisticated interface and configuration system that is comprehensible to users, meaning that a great deal of automation is required. Exactly what is exposed via the web-service for this functionality is unclear currently. Dependency / data-flow / graph-based approaches are common in top end video processing and modelling tools, we would need something similar.
Another advanced feature is the ability to add virtual content. Similar to above, this has to be mixed into a scene but it must also be simple to create such content via the web interface.
