May 3rd 2021 – With over 11 man-years of working, and tinkering, long into the night, I am pleased to announce we have hit version 1.0. Following quickly after the release of ClearML 0.17.5, we added the last remaining features we felt 1.0 needed. Namely multi-model support, as well as improved batch operations. With these in place, the choice was clear. The next version released should be the baseline moving forward.
Few things in life are certain, least of all roadmaps. There is a saying I love, apart from the one above, which says “if you want to hear God laugh, tell him/her your plans”. Nowhere is that more true than in software development in a startup. There are grand ideas put forward, people often vie with one another, in short, life happens.
Let’s start with a real-world example from one of my past machine learning (ML) projects: We were building a customer churn model. “We urgently need an additional feature related to sentiment analysis of the customer support calls.” Creating the data pipeline to extract this dataset took about 4 months! Preparing, building, and scaling the Spark MLlib code took about 1.5-2 months!
Although the title might sound like a collaboration of two music bands with really bad names, this blog is all about understanding how computer vision and machine learning can be used to improve safety and security in a harsh and dangerous environment of a construction site. The construction industry is one of the most dangerous industries according to the common stats from OSHA.
Telecom companies monitor their network using a variety of monitoring tools. There are separate fault management and performance management platforms for different areas of the network (core, RAN, etc.), and infrastructure is monitored separately. Although these solutions monitor network functions and logic – something that would seem to make sense — in practice this strategy fails to produce accurate and effective monitoring or reduce time to detection of service experience issues.
