Sweep goes way beyond the suggested time for a single run

[BertrandDecoster]

When executing a sweep with max_suggestion_cost set to 300, the 9th run was running for 5 hours already with Remaining time estimated to be 11 hours

Unable to reproduce, it just happened, and it takes quite some time to see it happen

[BertrandDecoster]

After investigation, I wonder if this is the cause in default.ini:

# TODO: Elim from base
[sweep.train.total_timesteps]
distribution = log_normal
min = 3e7
max = 1e10
scale = time

It can be closed if it's the case, but the doc could include some info about this

[kywch]

Your hunch is right. Sweep's max suggestion cost is merely a noisy suggestion, especially during early runs when its estimations are not good.

You should adjust [sweep.train.total_timesteps] min and max depending on your sim's speed. These values are set for PufferLib ocean envs, where 1M+ sps is the norm, and 20M steps would take 20 sec.