Log metrics/models etc... to studio directly with Live or DVCLiveCallbacks in training script about dvclive HOT 9 CLOSED

Thx a lot for your answers

from dvclive.

Yes @BaptisteLoquette, you need to include a Studio token locally to see them live in Studio. See https://dvc.org/doc/studio/user-guide/experiments/live-metrics-and-plots#set-up-an-access-token. We can better clarify this in the DVCLive docs.

Can you better describe how you got to this point? Were you already using DVC or started with DVCLive? Where did you go in the docs to try to find this info?

from dvclive.

I already used dvc & cml. But new to the studio. I already added the studio token in the gitlab variables. And at each git trigger (here push) the commit appears on the studio though, except for the data size, nor the metrics, loss or the models are logged/registered. I do think it's because I haven't configured a dvc.yaml file in my current project. Also, I configured an azure blob storage. When I log_artifact the model, it will be stored in the blob storage right ?

Thx for your answer

from dvclive.

I mean it's logical that the data size is logged as I dvc pushed the datas, but I was thinking Using Live() or DVCLiveCallback would automatically log the metrics etc... to the studio. Only from the training script and no git action.

from dvclive.

Huh, no sry didn't see this https://dvc.org/doc/user-guide/project-structure/configuration#studio I need to enable it in the config right ?

from dvclive.

I mean it's logical that the data size is logged as I dvc pushed the datas, but I was thinking Using Live() or DVCLiveCallback would automatically log the metrics etc... to the studio. Only from the training script and no git action.

Yes, that's how it should look. It sounds like something isn't configured right for you.

Huh, no sry didn't see this https://dvc.org/doc/user-guide/project-structure/configuration#studio I need to enable it in the config right ?

I already added the studio token in the gitlab variables.

The token needs to be either in your dvc config under studio.token or in the environment variable DVC_STUDIO_TOKEN.

from dvclive.

Fixed it, by setting with dvc config --global studio.token. But weird because it starts inside a gitlab CI script and DCC STUDIO TOKEN was configured in the variables

from dvclive.

If you want to post your CI script, we can try to debug. If not, I guess we can close the issue?

from dvclive.

It's fixed. yes we can. Thx a lot again

from dvclive.