Hello, everyone and welcome to another update for mlops uh here gitlab. So today we're gonna talk quickly about the progress on mlflow or on more specifically on experiment tracking uh within gitlab and a little bit about Jupiter as well, because why not so um just a reminder? What we're doing here we've been working for the past few months on enabling experiment tracking for uh for gitlab.

So what experiment tracking means is finding a way or allowing data scientists to keep track of what hyper parameters generated, what model candidates within gitlab and how could this influence or how could this be used across the plot, digit platform or better? How could the gitlab platform help data scientists track these experiments?

So on the past few weeks we did a lot of improvements on the ux and UI. We've been iterating over the internal testing that started in December, um so we have data scientists here gitlab and we added we asked them to test this feature.

They already use ml flow, so the only thing that they did was swap the URI to gitlab and gave us feedback or what needs to be done still so, based on that feedback, we've added a few different things, so we added, for example, search now there's search over here um when you go to the we also added display for the name of of an exp of a running. If there is so, let me just play over here uh this one.

So if there is a name, we display the creation, the user that you created it. When we go over the details of of that of that candidate, we also will be able to see the metadata for that candidate. So, for example, over here, this was created by mflo itself. So we use the referral client, and here you can see all the metadata that was generated during the creation of that uh candidate oral that run. So all of this came from internal testing and we are further integrating on this uh testing out new things.

So a bunch of Mrs emerged for this, and additionally, we took a little bit of time to work on Jupiter book divs. There's a big low hanging fruit, which is there is a size limit for divs, which is 512 gigabytes, any Jupiter, diff kind of goes over that. So what we're trying to do here is enabling uh setting a different size limit for Jupiter diffs. So we did the code already in Italy.

We just need to implement now on on the client side on the gitlab side, so that more users can see diffs over Jupiter notebook divs.

So what's next uh validate with further internal testing, so we did a lot of changes. A lot of uh new features, a lot of that. A new feature request from from our colleagues so validating those we can move on to external testing already either closed or open I'm, not entirely sure how that's going to go. But we are at a point that we fixed all of the major we. We introduced all of the major features and fixed what was needed so as a feature it works already. So as a experiment tracking, it works.

What we need to do now is go beyond is how can we leverage the gitlab platform to both increase the experience, while using uh experiment tracking, but also how can experiment tracking inform the other steps of the devops for data science workflow or for the mlaps workflow, so yeah? This is uh where we are at now, and thanks for watching.