Happy to help. There isn’t currently a way for you to access the run number directly, but here are a few workarounds:
You can use wandb.log and manually log run numbers if you’d like them to be numbered 1-8 (or if you’d like to save them as artifacts, that is an option too)
Alternatively, you can access the run ID for a particular run using wandb.run.id if you’d like to access the unique run ID’s for a particular run.
Hi chris-pedersen, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!