![Profile picture](https://clearml-web-assets.s3.amazonaws.com/scoold/avatars/SarcasticSparrow10.png)
Reputation
Badges 1
58 × Eureka!SuccessfulKoala55 Yes, I am using the --docker flag.
You are right about the Keyring. Once I make sure credentials are stored in a secure way, it works as expected. Thanks :)
Hi AgitatedDove14 , yes, I was able to change the color from the UI. But this may be less than ideal for the following use case.
A model is an ensemble of say 10 models. Each member of the ensemble generates two train-validation curves. So for 1 model, I will have 20 plots. There are two problems with the current setup:
Manually changing colors of all the plots is not feasible The default color scheme is not consistent and changes randomly with every run
It would be nice if I can control t...
fatal: could not read Username for '
': terminal prompts disabled error: Could not fetch origin
Why is trains-agent trying read from terminal prompt instead of trains.conf
?
Hi AgitatedDove14 Thanks, I'll check these out.
What is the exact use case you have in mind?
I want to store some additional data that is not relevant to training a model. For example, store inference results, explanations, etc and then use them in a different process. I currently use separate database for this.
Btw, I had been busy with another project and hadn't logged in here for some time. I see that you guys have made a lot of progress in the last two months! I'm excited to di...
What would be the query ? Are you reporting 100+ diff scalars ?
At the moment I am not reporting any scalars related to inference. I'm only reporting data related to training a model. But I would like to report records that result from an inference process. For example the record would contain key_1, key_2, datetime, pred_1, pred_2 ... pred_n. I would have about 20 scalars if each of these fields is reported as a scalar.
The query can be a simple filtering criteria matching some keys ...
Ok, I will look into artifacts. However, I will probably need high performance query functionality. For example, say I have a model and hundreds of thousands of inference records for that model. I want to be able to efficiently query that. My guess is that wouldn't be possible with artifacts. But that should be possible with Task.get_tasks
.
Also it might be better (although not necessary) to have a separate collection for storing inference results for better organization.
I'm using docker to run the experiment. Could it be that the config in the docker container doesn't have the git credentials?
I cannot execute step 4 because I can't get past step 3. Does that make sense?
I was getting the error in step number 3
I'm getting the same error when I followed the instructions to the letter.
Here is one line from the mongo docker output"This version of MongoDB is too recent to start up on the existing data files. Try MongoDB 4.2 or earlier."
There was some complication during the upgrade so I had to resort to the manual process.
I have now been able to upgrade by dumping the mongodb data and restoring it independently.
The docker container in step 3 does not run because of the incompatibility
Steps 1 and 2 basically copy mongo 3.6 data into a new dir mongo_4
but mongo image of version 4.4 does not accept that data. So I had to perform the following steps:
Launch docker container with mongo=3.6 dump data using mongo dump Launch docker container with mongo=4.4 and empty mongo_4
data dir Restore the dump data using mongo restore
This made sure the data is now compatible with mongo 4.0 or greater
Hi AppetizingMouse58
Yes, I tried to perform steps 3-10, however step 3 raised an error because data files for mongo were incompatible between 3.6 and >4.0
Steps 1 and 2 on this https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_mongo44_migration/ say to backup opt/clearml/data/mongo
and uncompress into /opt/clearml/data/mongo_4
. Isn't it just copying the old data files?
Yes, I tried to run steps 1,2,3,4 in order but got stuck at 3
I had to manually create a dump for the mongo data and import it into 4.4. I was just referring to adding a note to the documentation for other users.
Got it. That makes sense. Thanks!
mongo 4.4 image does not launch a container if the data in mongo dir is for previous versions. We should add that comment in the documentation