Skip to content

TimeSequencer using system clock instead of node clock #175

Open
@ichatzinikolaidis

Description

@ichatzinikolaidis

Hi,

I noticed that TimeSequencer is using the system clock (both here and in the definition of last_time_) instead of the node's clock. Could this be problematic when running a simulation? Shouldn't it use the node's clock, which can be configured to use either sim time or system time by setting the use_sim_time parameter?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions