no, I meant to change the way it is reported. I'm still interested in the train_loss graph, naturally 🙂 but obviously it is reporting something that is the inverse of the train_loss, since in the graph it is exploding, and in reality (as reported in the terminal) it is decaying to 9e-2

Thanks for letting me know, I'd be very happy to update.

alright, cracking knuckles and... dive into the deep end

in the meantime, I got this error message, this time regarding Trains:

then this:

so, inbound rules should allow custom TCP for the three ports, 8080, 8001, 8081? what about the outbound rules?

the "Payload" tab contains the project id info, so it shouldn't be the cause for the delete call fail

So it means the old WebApp is still in cache...

meaning the browser or in the server?

but if I just enter the URL with ending :8080 it takes me to the old login

when running the docker ps command the output is empty

I think you have the page cached - can you try reloading using

Ctrl-F5

?

using Ctrl-F5 it redirects to the ClearML new login

SuccessfulKoala55 in step 1. it isn't written

How do I check that? I did nothing in the settings other than the recommended defaults in the docs

Thanks Jake, clearing the Cache did the trick! thank you so much for your assistance!

it will switch to the new one

it isn't an error, but just an observation

Good morning Alon, since you helped me so much getting tensorboard to show results yesterday, I'm hoping you can help me understand why some results I'm getting are strange:

here is the result on the Tboard in Trains:

yes, that solved the errors, however the two lines "could not detect iteration reporting" and "reporting detected" a few moments later, still show up

thank you Jake

it is on the scale of 15K...

I will try and let you know in the next experiment

(and I didn't use the -f switch since it wasn't in the instructions, and I'm not familiar with dockers all that much)

Thank you Martin for your fast response! Will do

This is the valin_loss, which is correct: