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
{{ message }}
This repository was archived by the owner on Feb 3, 2025. It is now read-only.
A doubt that I have with this enhancement. It's that right now there is a diagnostic utility implemented in Gazebo
Gazebo is currently instrumented with high-resolution diagnostic timers at several parts of the inner loop. The timer resolution depends on the hardware in use and is approximately 100ns on our test machines. To prevent performance degradation during normal usage, the timers are disabled unless the ENABLE_DIAGNOSTICS symbol is defined during compilation. For each simulation step, the elapsed time is measured and used to compute the following statistics incrementally: mean, minimum, maximum, and variance of each diagnostic timer. The statistics are computed using the math::SignalStats class. This will output the diagnostic timing data to the ~/.gazebo/diagnostics folder.
Should I remove this? or both utilities should live together?
I think we can leave the diagnostics stuff there now. The rationale is that all Gazebo versions have already been released and we don't want to change existing behaviour.
Add support for Ignition Common's profiler to report time data from key sections of simulation execution.
We should measure and output profile data for at least:
The text was updated successfully, but these errors were encountered: