Report adjustment durations in hh:mm:ss for durations greater than 60 sec

[jhaasdyk-au]

Brief description
Report adjustment times and iteration times in (hours and) minutes if greater than 60 seconds.

Background
v1.2.8 adjust.exe previously reported iteration duration (and total adjustment duration) in hh:mm:ss
(examples: 00:00:00 (when VERY fast); 00:00:00.440000; 00:00:18, 00:01:08; 01:37:21)

RE: Windows v.1.3.0 MKL Build Mar 5 2026, 03:24:55
v1.3.0 adjust.exe now reports only in seconds (or milliseconds):
(examples: 0.078ms, 12.580s, 139.419s, 26697.777s)

Basic requirements
Adopt v.1.3.0 reporting for adjustment durations,
unless greater than 60 seconds, then report hh:mm:ss

Other executables can remain unchanged e.g. Geoid file interpolation took 0.169s.

Priority
Priority 3 (low)

[nicgowans]

I've also noticed the change from v1.2.9 onwards.

It would be nice if the output was consistently formatted, regardless of duration, which makes parsing results easier (e.g. using PynAdjust). My preference would be for HH:MM:SS.SSSSSS.

[jhaasdyk-au]

I've also noticed the change from v1.2.9 onwards.

It would be nice if the output was consistently formatted, regardless of duration, which makes parsing results easier (e.g. using PynAdjust). My preference would be for HH:MM:SS.SSSSSS.

I'm happy with returning to the HH:MM:SS.SSSSSS format (i.e. with increased precision where it is useful).
A truncated version HH:MM:SS is then still almost as easy to parse in most contexts. Perhaps if >10 seconds?

[daleroberts]

Yes, agree. I will do this.