benchmark

It would be helpful to see the elapsed time on the initial time measurement.

Right now, I have a very long running benchmark subject sitting at "Initial time measurement" and "ETA 00:00:00"; I'd love to see the elapsed time ticking at least in this case, e.g. as " AT 00:10:23", indicating that hyperfine is 10 minutes 23 seconds into the initial run.

Various characters (e.g. |) if used in a Params will end up invalidating the generated markdown, causing it to render incorrectly. It'd be helpful if benchmarkdotnet could escape the markdown output, e.g. output \| instead of |.

Is your feature request related to a problem? Please describe.
The benchmark library recoginzes a command line option --v to set verbosity.

A benchmark program might want to set its own verbosity based on that flag.

Describe the solution you'd like
Have a declaration in the public interface that lets the calling program know the verbosity value.

**Describe alternatives you've

• I have marked all applicable categories:
  • exception-raising bug
  • RL algorithm bug
  • documentation request (i.e. "X is missing from the documentation.")
  • new feature request
• I have visited the [source website], and in particular read the [known issues]
• I have searched through the [issue tracker] and [issue categories] for duplicates
• [ ]

We keep this issue open to collect feature requests from users and hear your voice. Our monthly release plan is also available here.

You can either:

1. Suggest a new feature by leaving a comment.
2. Vote for a feature request with 👍 or be against with 👎. (Remember that developers are busy and cannot respond to all feature requests, so vote for your most favorable one!)
3. Tell us that you wo

Motivation:

We plan to improve our documentation and tutorials! Users may encounter various problems during the use of MMPose, and we plan to collect all these feedback and provide a more detailed documentation or guidance.

Please feel free to leave a message and create a PR if you are willing to contribute.

Related issues #917, #902, #922

TODO:

• Move some useful discussi