Skip to content

replace custom ProgressMeter with tqdm #928

@jbarnoud

Description

@jbarnoud

EDIT (@orbeckst): Based on the discussion in this issue we decided to replace our lib.util.ProgressMeter with tqdm. Use this issue for discussion to refine this idea.


The progress bar could give an estimate of when the calculation is going to be done. This is reassuring for the end user, and allows to plan other things during long calculation (or to know when to come back from a coffee break).

This is easily achievable by keeping track of the time elapsed between two calls of the update method as we know how many frames remain to be analyzed.

It can be misleading for analyses that need to iterate several time through the trajectory, or that have a very long _conclude method. But the current progress bar is misleading already.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions