and under that there will be three graphs with title as train test and loss
Can my request be made as new feature so that we can tag same type of graphs under one main tag
Sure, open a Git Issue :)
I have 100 experiments and I have to log them and update those experiments every 5 minutes
No. since you are using Pool. there is no need to call task init again. Just call it once before you create the Pool, then when you want to use it, just do task = Task.current_task()
logger.report_scalar("loss-train", "train", iteration=0, value=100)logger.report_scalar("loss=test", "test", iteration=0, value=200)
notice that the title of the graph is its uniue id, so if you send scalars to with the same "title" they will show on the same graph
Just so I understand,
scheduler executes main every 60sec
main spins X sub-processes
Each subprocess needs to report scalars ?
Can my request be made as new feature so that we can tag same type of graphs under one main tag
no i want all of them in the same experiment
my scheduler will be running every 60 seconds and calling main function
@<1523720500038078464:profile|MotionlessSeagull22> you cannot have two graphs with the same title, the left side panel presents graph titles. That means that you cannot have a title=loss series=train & title=loss series=test on two diff graphs, they will always be displayed on the same graph.
That said, when comparing experiments, all graph pairs (i.e. title+series) will be displayed as a single graph, where the diff series are the experiments.
but what is happening is it is creating new task under same project with same task name
I will share my script u can see it what I am doing
In the side bar you get the title of the graphs, then when you click on them you can see the diff series on the graphs themselves
It will not create another 100 tasks, they will all use the main Task. Think of it as they "inherit" it from the main process. If the main process never created a task (i.e. no call to Tasl.init) then they will create their own tasks (i.e. each one will create its own task and you will end up with 100 tasks)
now after 1st iteration is completed then after 5 minutes my script runs automatically and then again it logs into trains server
You can always click on the name of the series and remove it for display.
Why would you need three graphs?
like in the sidebar there should be a title called "loss" and under that two different plots should be there named as "train_loss" and "test_loss"
Just call the Task.init before you create the subprocess, that's it 🙂 they will all automatically log to the same Task. You can also call the Task.init again from within the subprocess task, it will not create a new experiment but use the main process experiment.
then if there are 100 experiments how it will create 100 tasks?
logger.report_scalar("loss", "train", iteration=0, value=100)logger.report_scalar("loss", "test", iteration=0, value=200)
then my combined function create a sub task using Task.create(task_name=exp_name)
so, if I call Task.init() before that line there is no need of calling Task.init() on line number 92
See on line 212 I am calling one function "combined" with some arguments
You can do:task = Task.get_task(task_id='uuid_of_experiment')task.get_logger().report_scalar(...)
Now the only question is who will create the initial Task, so that the others can report to it. Do you have like a "master" process ?
@<1523701205467926528:profile|AgitatedDove14> I want to log directly to trains using logger.report_scalar
like if u see in above image my project name is abcd18 and under that there are experiments Experiment1, Experiment2 etc.
and that function creates Task and log them