| Home | Trees | Indices | Help | 
 | 
|---|
|  | 
ROS time and duration representations, as well as internal routines for managing wallclock versus a simulated clock. The important data classes are Time and Duration, which represent the ROS 'time' and 'duration' primitives, respectively.
| Classes | |
| Duration Duration represents the ROS 'duration' primitive type, which consists of two integers: seconds and nanoseconds. | |
| Time Time represents the ROS 'time' primitive type, which consists of two integers: seconds since epoch and nanoseconds since seconds. | |
| Functions | |||
| Time | 
 | ||
| float | 
 | ||
| 
 | |||
| bool | 
 | ||
| threading.Cond | 
 | ||
| bool | 
 | ||
| 
 | |||
| 
 | |||
| Variables | |
| __package__ =  | |
| Function Details | 
| 
 Get the current time as a Time object 
 | 
| 
 Get the current time as float secs (time.time() format) 
 | 
| 
 Internal use. Mark rostime as initialized. This flag enables other routines to throw exceptions if rostime is being used before the underlying system is initialized. 
 | 
| 
 Internal use. 
 | 
| 
 internal API for helper routines that need to wait on time updates 
 | 
| 
 Internal use for ROS-time routines. 
 | 
| 
 Internal use. Switch ROS to wallclock time. This is mainly for testing purposes. | 
| 
 Internal use. Windows interrupts time.sleep with an IOError exception when a signal is caught. Even when the signal is handled by a callback, it will then proceed to throw IOError when the handling has completed. Refer to https://code.ros.org/trac/ros/ticket/3421. So we create a platform dependant wrapper to handle this here. | 
| Home | Trees | Indices | Help | 
 | 
|---|
| Generated by Epydoc 3.0.1 on Tue Mar 7 03:45:10 2017 | http://epydoc.sourceforge.net |