Tasks #524

Which timestamps should be set based on recorded information?

Added by J. Moringen over 12 years ago. Updated over 6 years ago.

Status:In ProgressStart date:08/26/2011
Priority:NormalDue date:
Assignee:J. Moringen% Done:

30%

Category:-
Target version:Robotics Service Bus - rsb-0.18

Description

Out of create, send, receive and deliver, which timestamps should be recorded and later restored when replaying events?

One use-case reported by Johannes:

If one channel in a tide file is assumed to be the absolute reference for all other activities, all timestamps should be relative to the first event of that special stream. The first event there should have timestamp 0.


Related issues

Related to RSBag - Feature #709: Allow replacing stored timestamps with current wall-clock... Resolved 11/10/2011

Associated revisions

Revision bc853efe
Added by J. Moringen about 12 years ago

Added file src/rsb/replay/timestamp-adjustment-mixin.lisp
refs #524
  • src/rsb/replay/timestamp-adjustment-mixin.lisp: new file;
    contains mixin class `timestamp-adjustment-mixin'
  • src/rsb/replay/recorded-timing.lisp (recorded-timing): added
    superclass `timestamp-adjustment-mixin'
  • src/rsb/replay/fixed-rate.lisp (fixed-rate): likewise
  • src/rsb/replay/as-fast-as-possible.lisp (as-fast-as-possible):
    likewise
  • src/rsb/replay/package.lisp (header): updated copyright
    (package rsbag.rsb.replay): added exported symbols
    timestamp-adjustment-mixin and strategy-adjustments
  • cl-rsbag.asd (system cl-rsbag): added file
    src/rsb/replay/timestamp-adjustment-mixin.lisp; added dependency of
    src/rsb/replay/{recorded-timing,fixed-rate,as-fast-as-possible}.lisp
    on src/rsb/replay/timestamp-adjustment-mixin.lisp

Revision efba7eb6
Added by J. Moringen almost 12 years ago

Implemented more patterns in src/rsb/replay/timestamp-adjustment-mixin.lisp
refs #524
  • src/rsb/replay/types.lisp (header): added one-line summary
    (timestamp-adjustment-value/now): new type; replace with current time
    (timestamp-adjustment-value/copy): new type; replace with copy of
    some other timestamp
    (timestamp-adjustment-value/delta): new type; replace with some
    delta
    (timestamp-adjustment-value): new type; timestamp replacement
    value specification
    (timestamp-adjustment-spec): new type; timestamp replacement
    specification
  • src/rsb/replay/timestamp-adjustment-mixin.lisp
    (timestamp-adjustment-mixin::adjustments): removed initarg
    (shared-initialize :after timestamp-adjustment-mixin t): set
    adjustments via writer
    (setf strategy-adjustments :before t timestamp-adjustment-mixin):
    new method; check type of new value
    (process-event :before replay-bag-connection timestamp-adjustment-mixin t):
    support now, copy, delta and literal timestamp specifications
    (print-object timestamp-adjustment-mixin t): new method; print object
  • test/rsb/timestamp-adjustment-mixin.lisp: new file; contains
    test for `timestamp-adjustment-mixin' class
  • test/rsb/package.lisp (header): updated copyright
    (package rsbag.rsb.test): added used package rsbag.rsb.replay
  • cl-rsbag.asd (system cl-rsbag-test): added file
    test/rsb/timestamp-adjustment-mixin.lisp

Revision 702772d0
Added by J. Moringen almost 12 years ago

Added missing dependency in cl-rsbag.asd
refs #524
  • cl-rsbag.asd (system cl-rsbag): added missing dependency of
    src/rsb/replay/timestamp-adjustment-mixin.lisp on
    src/rsb/replay/types.lisp

Revision 92e62545
Added by J. Moringen almost 12 years ago

Process delta adjustment in src/rsb/replay/timestamp-adjustment-mixin.lisp
refs #524
  • src/rsb/replay/types.lisp (timestamp-adjustment-value/delta): allow
    negative offsets
  • src/rsb/replay/timestamp-adjustment-mixin.lisp
    (process-event replay-bag-connection timestamp-adjustment-mixin t t event t):
    actually process :delta adjustment

History

#1 Updated by J. Moringen about 12 years ago

  • Target version set to rsb-0.7

#2 Updated by J. Moringen about 12 years ago

  • Status changed from Feedback to In Progress
  • Assignee set to J. Moringen
  • % Done changed from 0 to 30

The associated change allows overwriting specified timestamps in simple ways. E.g. "replace original create timestamp with the current time".

The general issue still needs feedback. What do you think?

#3 Updated by J. Moringen almost 12 years ago

  • Description updated (diff)

#4 Updated by J. Moringen almost 12 years ago

  • Target version changed from rsb-0.7 to rsb-0.9

#5 Updated by J. Moringen about 11 years ago

  • Target version changed from rsb-0.9 to rsb-0.10

#6 Updated by J. Moringen over 10 years ago

  • Target version changed from rsb-0.10 to rsb-0.11

#7 Updated by J. Moringen over 9 years ago

  • Target version changed from rsb-0.11 to rsb-0.12

#8 Updated by J. Moringen about 9 years ago

  • Target version changed from rsb-0.12 to rsb-0.13

#9 Updated by J. Moringen about 8 years ago

  • Target version changed from rsb-0.13 to rsb-0.14

#10 Updated by J. Moringen almost 8 years ago

  • Target version changed from rsb-0.14 to rsb-0.15

#11 Updated by J. Moringen over 7 years ago

  • Target version changed from rsb-0.15 to rsb-0.16

#12 Updated by J. Moringen about 7 years ago

  • Target version changed from rsb-0.16 to rsb-0.17

#13 Updated by J. Moringen over 6 years ago

  • Target version changed from rsb-0.17 to rsb-0.18

Also available in: Atom PDF