Improving readability of progress bar

[erikvansebille]

Description

This PR improves the readability of the tqdm progress bar by

• cleaning up the datetime formatting (removing subsecond information)
• removing the redundant counter information

Before

After

Note: I'm not sure how to write unit tests for this; and whether that is even necessary

Checklist

• This PR targets the correct branch (main for normal development, v3-support for v3 support)

AI Disclosure

• This PR contains AI-generated content.
  • I have tested any AI-generated content in my PR.
  • I take responsibility for any AI-generated content in my PR.
  • Describe how you used it (e.g., by pasting your prompt): I asked Claude how to implement the format changes that I wanted

[erikvansebille]

Perhaps we should change "Integration time" to "Simulation time" or simply "Time" or "Progress"?

[michaeldenes]

I quite liked the 554400.0 / 2678400.0 like information. If my simulation crashed, I could tell immediately from the log at what timestep to investigate. Could this be a toggle-able run-time option (like the rcParams in matplotlib)?

[erikvansebille]

I quite liked the 554400.0 / 2678400.0 like information. If my simulation crashed, I could tell immediately from the log at what timestep to investigate. Could this be a toggle-able run-time option (like the rcParams in matplotlib)?

But can't you use the datetime itself for that? That is in front of the progress bar and is also updated. What does the time counter have that the datetime doesn't?