[Q] How to avoid data averaging when logging to metric across multiple runs?

Hello, I’m trying to log data points for the same metric across multiple runs (wandb.init is called repeatedly in between each data point) and I’m unsure how to avoid the behavior seen in the attached screenshot…

Instead of getting a line chart with multiple points, I’m getting a single data point with associated statistics. In the attached e.g., the 1st data point was generated at step 1,470 and the 2nd at step 2,940…rather than seeing two points, I’m instead getting a single point that’s the average and appears at step 2,205.

My hunch is that using the resume run feature may address my problem, but even testing out this hunch is proving to be cumbersome given the constraints of the system I’m working with…

Before I invest more time in my hypothesized solution, could someone confirm that the behavior I’m seeing is, indeed, the result of logging data to the same metric across separate runs without using the resume feature?

If this is the case, can you confirm or deny my conception of how to use resume?

Initial run:

1. run = wandb.init()
2. wandb_id = run.id
3. cache wandb_id for successive runs

Successive run:

1. retrieve wandb_id from cache
2. wandb.init(id=wandb_id, resume="must")

Is it also acceptable / preferable to replace 1. and 2. of the initial run with:

1. wandb_id = wandb.util.generate_id()
2. wandb.init(id=wandb_id)

[lukas]

Hi! Using id and resume definitely works for your use case.

The reason you are seeing a single datapoint is the line chart averages points over runs by default when they are grouped. If you want to turn this off you can do so in the UI in the upper right.

[thanos-wandb]

Hi @a-rich thank you for confirming this. I will close the ticket for now, but feel free to re-open it by posting here if you have any further questions and we will be happy to keep investigating!