Edit on GitHub

We have renamed Views to Projects in Iterative Studio.

Accordingly, Views dashboard is now called Projects dashboard; View settings are now called Project settings; and so on.

Troubleshooting

Here we provide help for some of the problems that you may encounter when using Iterative Studio.

Projects and experiments

Model registry

Billing and payment

Support

If you need further help, you can send us a message using Help on the Iterative Studio website. You can also email us, create a support ticket on GitHub or join the discussion in Discord.

Error: No data found to visualize

If you have connected to a non-DVC repository, then you need to specify custom files that contain the metrics and hyperparameters that you want to visualize. Otherwise, you will get this message when you try to add a project: We could not find data to visualize in this repo.

For more details, refer to the section on how to prepare your Git repositories for use with Iterative Studio. Instructions on how to specify custom files can be found here.

Note that if you're connecting to a repository just to fetch models for the model registry, and you are not working with DVC repositories, you can ignore this error.

Error: No DVC repo was found at the root

If you get this message when you try to add a project: No DVC repo was found at the root, then it means that you have connected to a Git repository which contains a DVC repository in some sub-directory but not at the root.

This could be a typical situation when your DVC repository is part of a monorepo.

To solve this, you can either:

  • specify the full path to the sub-directory that contains the DVC repo, or
  • specify custom files that contain the metrics and hyperparameters that you want to visualize.

Instructions on how to specify the sub-directory or custom files can be found here.

Note that if you're connecting to a repository just to fetch models for the model registry, and you are not working with DVC repositories, you can ignore this error.

Error: Non-DVC sub-directory of a monorepo

If you get this message when you try to add a project: Non-DVC sub-directory of a monorepo, then it means that you have connected to a Git repository which contains a DVC repository in some sub-directory, but you have selected the incorrect sub-directory.

This could be a typical situation when your DVC repository is part of a monorepo. Suppose your Git repository contains sub-directories A and B. If A contains the DVC repository which you want to connect from Iterative Studio, but you specify B when creating the project, then you will get the above error.

To solve this, you can either:

  • specify the full path to the correct sub-directory that contains the DVC repo, or
  • specify custom files that contain the metrics and hyperparameters that you want to visualize.

Instructions on how to specify the sub-directory or custom files can be found here.

Error: No commits were found for the sub-directory

If you get this message when you try to add a project: No commits were found for the sub-directory, then it means that you have specified an empty or non-existent sub-directory.

To solve this, you need to change the sub-directory and specify the full path to the correct sub-directory that contains the DVC repo.

If you did not intend to work with a DVC repo, you can also specify custom files that contain the metrics and hyperparameters that you want to visualize.

Instructions on how to specify the sub-directory or custom files can be found here.

Project got created, but does not contain any data

If you initialized a DVC repository, but did make any commit with data, metrics or hyperparameters, then you will be able to connect to this repository. However, the project will appear empty in Iterative Studio. To solve this, either make relevant commits to your DVC repository. Or, specify custom files with the metrics or hyperparameters that you want to visualize.

Refer to the DVC documentation for help on making commits to a DVC repository. Instructions on how to specify custom files can be found here.

Note that if you're connecting to a repository just to fetch models for the model registry, and your repository is not expected to contain experiment data, metrics or hyperparameters, your project will appear empty. This is ok - you will still be able to work with your models in the model registry.

Project does not contain the columns that I want

There are two possible reasons for this:

  1. The required columns were not imported: Iterative Studio will only import columns that you select in the Columns setting.

    What if there are more than 200 columns? Currently Iterative Studio cannot import over 200 columns. If you have a large repository (with more than 200 columns), one solution is to split the metrics/hyperparameters/files that you want to display over multiple subdirectories in your git repository. For each subdirectory, you can create a new project in Iterative Studio and limit it to that subdirectory.

    To create projects for subdirectories, specify the project directory in project settings.

    If this solution does not work for your use case, please create a support ticket in the Iterative Studio support GitHub repository.

  1. The required columns are hidden: In the project's experiment table, you can hide the columns that you do not want to display. If any column that you want is not visible, make sure you have not hidden it. The following video shows how you can show/hide columns. Once you show/hide columns, remember to save the changes.

    Show/hide columns

    Showing and hiding columns

Project does not contain some of my commits or branches

This is likely not an error. Iterative Studio identifies commits that do not change metrics, files or hyperparameters and will auto-hide such commits. It also auto-hides commits that contain the string [skip studio] in the commit message. You can also manually hide commits and branches. So, it is possible that the commits or branches you do not see in your project were manually hidden by you or someone else in your team.

You can unhide commits and branches to display them. For details, refer to Display preferences -> Hide commits. However, if the missing commit/branch is not in the hidden commits list, please raise a support request.

Error: Failed to push experiment to repository

This is a non-specific error with a range of possible causes. To resolve it, check that:

  • Your account is able to push to the Git repository.

    If your Git account does not have write access on the Git repository connected to a project, you cannot push changes (e.g., new experiments) to the repository even if the project belongs to a team where you are an Editor or Admin.

  • The repository is not marked as archived / read only.

  • In case of GitHub/GitLab/BitBucket enterprise organizations: there is no IP whitelisting policy in place which limits access to the organization's resources.

  • Whether GitHub, GitLab, or BitBucket are experiencing service disruptions. In case of an on-premises deployment, do check with your administrator.

If you get this error and none of the above applies, please get in touch with us.

Project does not display live metrics and plots

Confirm that you are correctly following the procedure to send live metrics and plots to Iterative Studio.

Also note that live metrics and plots for an experiment are displayed only if its parent Git commit is present in the project table. So, before you run the experiment, make sure that its parent commit is pushed to Git and shown in the project table.

Project does not display DVC experiments

Iterative Studio automatically checks for updates to your repository using webhooks, but it can not rely on this mechanism for custom git objects, like DVC experiment references. So the experiments you push using dvc exp push may not automatically display in your project table.

To manually check for updates in your repository, use the Reload button 🔄 located above the project table.

I cannot find my desired Git repository in the form to add a model

Only repositories that you have connected to Iterative Studio are available in the Add a model form. To connect your desired repository to Iterative Studio, go to the Projects tab and create a project that connects to this Git repository. Then you can come back to the model registry and add the model.

Model registry does not display the models in my Git repositories

For a model to be displayed in the model registry, it has to be registered using GTO. You can register the model from Iterative Studio or with the gto CLI.

How can I remove models from my model registry

To remove a model from the model registry, use the Deprecate model menu item in the 3-dot menu next to the model name. You can also remove all of a project's models by deleting the project from your projects dashboard.

My models have disappeared even though I did not remove (deprecate) them

Models can also be removed by deleting the associated project from the projects dashboard. So make sure that the project is not deleted.

How can I un-assign stages from model versions

To un-assign any stage from a model, open the corresponding Git repository (in GitHub, GitLab or Bitbucket). Then, remove the Git tag pertaining to the stage that you want to un-assign.

After removing the Git tag, reparse the repository. To do this, open the project in Iterative Studio and then click on Force import as shown below.

Showing and hiding columns

Currently, you cannot un-assign stages from the Iterative Studio user interface.

Questions or problems with billing and payment

Check out the Frequently Asked Questions to see if your questions have already been answered. If you still have problems, please contact us.