Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » For Developers » timing_measurement
for_developers:timing_measurement

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
for_developers:timing_measurement [2016/08/17 11:10] – [How the timer works] gehrigfor_developers:timing_measurement [2016/10/24 07:57] – [Using built in timer for measuring real time performance] graf
Line 1: Line 1:
-====== Using built in timer for measuring real time performance ======+====== Using Periodic Counter to measure Realtime Performance ======
  
 ===== How the timer works ===== ===== How the timer works =====
Line 7: Line 7:
   * jitter: |actual period - set period|   * jitter: |actual period - set period|
 Of these three measurements the minimal value, maximal value, mean value and the variance are calculated. Of these three measurements the minimal value, maximal value, mean value and the variance are calculated.
 +
 +Implementation in //Execurot.cpp//:
 +<code cpp>
 +...
 +loop {
 +    counter.tick();
 +    //code under test (list.run();)
 +    counter.tock();
 +}
 +...
 +</code>
  
 ===== Influence of the measurement on the real time performance of the system ===== ===== Influence of the measurement on the real time performance of the system =====
Line 18: Line 29:
  
 ===== Implementation ===== ===== Implementation =====
-To integrate the measurement, following code has to be integrated after a task is created and before the task is added to the //Executor//. Following example shows the integration of the measurement including creation and assignment to the executor of a control system:+To integrate the measurement, following code has to be integrated after a task is created and before the task is added to the //Executor//. The following example shows the integration of the measurement including creation and assignment to the executor of a control system:
 <code cpp> <code cpp>
 using namespace eeros::logger; using namespace eeros::logger;
Line 24: Line 35:
  
  
-eeros::task::Periodic td("control system",dt, timedomain);+eeros::task::Periodic per("control system",dt, timedomain);
  
-td.monitors.push_back([&](eeros::PeriodicCounter &c, Logger<LogWriter> &log) {+per.monitors.push_back([&](PeriodicCounter &c, Logger<LogWriter> &log) {
  static int ticks = 0; // mseconds   static int ticks = 0; // mseconds
   
Line 33: Line 44:
   
  // timing measurement (tictoc)  // timing measurement (tictoc)
- eeros::PeriodicCounter counter = c;+ PeriodicCounter counter = c;
  c.reset();  c.reset();
  std::cout << "CS: period max: " << setw(7)  << counter.period.max*1000  std::cout << "CS: period max: " << setw(7)  << counter.period.max*1000
Line 40: Line 51:
 }); });
  
-eeros::Executor::instance().add(td);+eeros::Executor::instance().add(per);
 </code> </code>
  
  
-==== Explanation of the implementation ==== +If the executor has a small cycle time (less than 1 second) it is not advisable to update the log output each time. In the example the output is only updated after 1000 cycles. Depending on the cycle time, this number can be adjusted.\\ 
-If the executor has a small cycle time (less than 1 second) it is not advisable to update the log output each time. In the implementation of the code example the output is only updated after 1000 cycles. Depending on the cycle time, this number can be adjusted in line 3.+
  
 Line 7 defines which date should be written to the terminal output. Following options are available for //run// time and //period// time: Line 7 defines which date should be written to the terminal output. Following options are available for //run// time and //period// time: