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
Is your feature request related to a problem? Please describe.
Currently the EVS output includes a full timestamp of YYYY-DDD HH:MM:SS.XXXXX which, for most users, is too much information (how likely are you going to run cFS for years?) and creates a lot of noise in the output. Instead, EVS should be configurable (compile-time, load-time, or run-time) to control what output timestamp format it should use.
Describe the solution you'd like
A runtime-reconfigurable timestamp, at minimum the format string to use for strftime, plus "%f" (not part of the C standard, but adopted from the Python strftime API) for the microseconds. Additionally, instead of "clock time", have an option to switch to "seconds since start" and/or "seconds since timer reset" with an associated reset command.
Describe alternatives you've considered
Leaving well enough alone.
Is your feature request related to a problem? Please describe.
Currently the EVS output includes a full timestamp of
YYYY-DDD HH:MM:SS.XXXXX
which, for most users, is too much information (how likely are you going to run cFS for years?) and creates a lot of noise in the output. Instead, EVS should be configurable (compile-time, load-time, or run-time) to control what output timestamp format it should use.Describe the solution you'd like
A runtime-reconfigurable timestamp, at minimum the format string to use for strftime, plus "%f" (not part of the C standard, but adopted from the Python strftime API) for the microseconds. Additionally, instead of "clock time", have an option to switch to "seconds since start" and/or "seconds since timer reset" with an associated reset command.
Describe alternatives you've considered
Leaving well enough alone.
Additional context
See also #2295
Requester Info
Christopher.D.Knight@nasa.gov
The text was updated successfully, but these errors were encountered: