You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its nice having a progress bar, but the current implementation for our analysis stage only tracks progress through scripts 1 to 14 and it can't really use that progress to estimate time to completion.
So currently, this looks like this:
The bit on the right ("3/14 [02:08<10:34, 57.71s/it]") is basically meaningless except for the 3/14 bit (that is, step 3/14 for analysis). Its referring to its guestimate of about 1 minute (57.71 seconds) per iteration -- but even if it were accurate, its a bit obscure. Its not accurate though, because for large cities network extraction (this particular script) will take a lot longer than that, while other scripts are practically instant (database creation).
Better would be just to have something like "Step 3/14" and hide the other stuff so it doesn't worry people
The text was updated successfully, but these errors were encountered:
Its nice having a progress bar, but the current implementation for our analysis stage only tracks progress through scripts 1 to 14 and it can't really use that progress to estimate time to completion.
So currently, this looks like this:
The bit on the right ("3/14 [02:08<10:34, 57.71s/it]") is basically meaningless except for the 3/14 bit (that is, step 3/14 for analysis). Its referring to its guestimate of about 1 minute (57.71 seconds) per iteration -- but even if it were accurate, its a bit obscure. Its not accurate though, because for large cities network extraction (this particular script) will take a lot longer than that, while other scripts are practically instant (database creation).
Better would be just to have something like "Step 3/14" and hide the other stuff so it doesn't worry people
The text was updated successfully, but these errors were encountered: