Ok fine.

Even simpler than a github, this code reproduce the issues I have.

This is a run I made with the changes, As you can see the iteration now go from 0-111 and in each of them I have image with the name train_{001|150}

I'll try to make a code that reproduce this behavior and post it on github is it fine ? that way you could check if I'm the problem (which is really likely) 😛

You need to change a setting in your host machine to make the elasticsearch working.

yes tag is fixed

I call it like that:
logger.clearml_logger.report_image( self.tag, f"{self.tag}_{iteration:0{pad}d}", epoch, image=image ) `` self.tag is train or valid . iteration is an int for the minibatch in the epoch

Oh can't wait to see this feature 👀

Well, I use ignite and trains-server with a logging similar to ignite.contrib.handlers so I will be very happy to test this integration.

Wow, that really nice. I did almost the same code, TrainsLogger , TrainsSaver , and all the OutputHandler . I'll use your version instead and put any comment if I find something.

Is it somewhere in the documentation ?

🙇

Oh it works with an _ .

Thanks a lot I'll check how to do this correctly

SuccessfulKoala55 Also I see that the images name are not ordered naturaly it's display like this image_name_1 , image_name_10 , image_name_2 , and so on, is it possible to have a natural order to see image_name_1 , image_name_2 , etc... ?

Ok thanks

dashboard

If this issue happens again is there any log I can provide for help/debug ?

I tried to removes all the images and content from docker with docker-compose down and docker rmi , also remove all the content in each directory of /opt/trains/ created by the containers, do you have any idea why this happens?

Pretty good job. I'll try to use it as soon as possible.

Thansk for the ouput_uri can I put in the ~/trains.conf file ?

Any reason for / to not work?

Thanks!

It is in lexicographical ordering as you said.

Is this screenshot better?

I'm on linux, and this morning I restart it and everything was fine.

ok I'll go check

To retrieve metrics from an experiment I use this:
` from trains_agent import APIClient

client = APIClient()

client.events.get_scalar_metric_data(task=task_id, metric="name_of_metric") `Thanks to AgitatedDove14 that point this to me.

Yes this will work I think.