Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report] Using time.time() instead of time.per_counter() #1

Open
Mayankm96 opened this issue Mar 13, 2023 · 0 comments
Open

[Bug Report] Using time.time() instead of time.per_counter() #1

Mayankm96 opened this issue Mar 13, 2023 · 0 comments

Comments

@Mayankm96
Copy link
Member

Thanks a lot for this! I was comparing it to my own Timer class in Orbit

https://github.com/NVIDIA-Omniverse/Orbit/blob/main/source/extensions/omni.isaac.orbit/omni/isaac/orbit/utils/timer.py

I was wondering if using time.time() is correct compared to time.perf_coutner(). From a read here, the perf counter measures time at the most precision using CPU clock. On the other hand, time() is synced with UTC time and can be adjusted based on the OS being used.

More info here: https://www.webucator.com/article/python-clocks-explained/

@Mayankm96 Mayankm96 changed the title Using time.time() instead of time.perf_counter() [Bug Report] Using time.time() instead of time.() Mar 13, 2023
@Mayankm96 Mayankm96 changed the title [Bug Report] Using time.time() instead of time.() [Bug Report] Using time.time() instead of time.per_counter() Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant