Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

tqdm is one of the very few Python packages that makes it into every script I write. It's a very high ROI for managing and tracking simple loops.

My only complaint is the smoothing parameter; by default it predicts the estimated time remaining based on the most recent updates so it can fluctuate wildly; smoothing=0 predicts based on the total runtime which makes more sense given law of large numbers.



The older I get, and the more i come across these issues, the more sympathy i have for the Windows file copy progress dialog...


Yet the estimate of when you'll become fully sympathetic to the Windows file copy dialog changes wildly by the day, right :)


Yes, assuming i.i.d. samples. If the first batch is "warmup samples", this goes out the window.


Even if it's not i.i.d, a small amount of samples with much higher/lower times will just average out as noise.


well, it seems to me that its quite likely that speed varies across the process, so the more recent updates are probably a more useful default, so if your first part of the process is slower/faster this won't permanently mess up the estimates.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: