Hi QuaintJellyfish58 , it already is! Just upgrade your server to 1.9 to have the feature 🙂

Disabling the VCS cache will no longer cache the cloned git folder You can filter by 'Running' Experiments in ClearML and search for one that hasn't reported for a while and start investigating those

Hi AdventurousButterfly15 ,

When running code locally, how are the installed packages detected? Does it detect your entire venv or does it detect only the packages that were used?

You can set CLEARML_AGENT_DEAMON_OPTIONS and these will be added to the clearml-agent command in the docker. Default is ---services-mode --create-queue

Simply point it to the relevant address

If you fetch the Task object you can find it in task.data.script.version_num

Hi OutrageousSheep60 ,

I'm not sure I've seen such an example. But you can definately wrap torch dataset in clearml datasets. I am over simplifying but in the end think of the clearml dataset is like a large zip of all your files.

GiganticTurtle0 , which ClearML version are you using? From what I can see in the documentation to add the new parameters, you'll have to task.connect() again to add the new args

Do you see any errors in the ES container?

What happens during the run is that plotly plots are shown during run on your computer but they don't show in UI and ONLY after the run is finished the plots show up?

Are your runs long?

Hi @<1534344465790013440:profile|UnsightlyAnt34> , I'm afraid there is no easy way to do it. You would need to edit the links in mongodb/elastic to properly migrate it

Did you run the code locally first? I don't see the agent installing the packages themselves, did you remove it from the log or how are the packages being installed?

@Alex Finkelshtein, if the parameters you're using are like this:

parameters = { 'float': 2.2, 'string': 'my string', }
Then you can update the parameters as mentioned before:
parameters = { 'float': 2.2, 'string': 'my string', } parameters = task.connect(parameters) parameters['new_param'] = 'this is new' parameters['float'] = '9.9'
Please note that parameters['float'] = '9.9' will update the parameter specifically. I don't think you can update the parameter en masse...

SucculentBeetle7 please give an example of the path that is given to you by the web interface :)

Hi @<1594863230964994048:profile|DangerousBee35> , do you have some stand-alone code snippet that reproduces this behaviour?

Hi @<1572395190897872896:profile|ShortWhale75> , this capability exists as part of the HyperDatasets feature which is present in the Scale/Enterprise licenses.

did you setup agent.git_pass & agent.git_user in clearml.conf ?

Hi JitteryCoyote63 , I think this is what you're looking for:
https://clear.ml/docs/latest/docs/references/sdk/task#move_to_project

ThankfulHedgehong21 , server 1.6.0 is available. Can you try with it as well?

I see the issue. SuccessfulKoala55 , what do you think?

WittyOwl57 , when creating credentials, the credentials are associated with your user. So even if you give others those credentials, the experiments in the system will show up under the user who's credentials were being used when running the experiment 🙂

Hope this helps

Hi TimelyCrab1 , directing all your outputs to s3 is actually pretty easy. You simply need to configure api.files_server: <S3_BUCKET/SOME_DIR> in clearml.conf of all machines working on it.

Migrating existing data is more difficult since everywhere in the system everything is saved as links. I guess you could change the links in mongodb but I would advise against it.

Hi @<1535069219354316800:profile|PerplexedRaccoon19> , why not just run it as python script.y ?

During a run, correct?

Is it a self hosted server?

Hi @<1523701842515595264:profile|PleasantOwl46> , I'm not sure. Do you see any errors in the API server on such a startup?

Everything in None

Hi @<1570220844972511232:profile|ObnoxiousBluewhale25> , you can click on the model in the artifacts tab and that should take you to the model repository. What is logged in the url of the model?

So you migrated your server and since then this issue appeared?

You shouldn't lose credentials. How exactly are you deploying your server? All of the related data to the server should be saved in one of the /opt/ folders as explained in the installation steps