Skip to content

merged clock resolution #3

@mxmlnkn

Description

@mxmlnkn

Currently Clock properties of the traces are adjusted with respect to the first trace's clock properties in the list. We are computing the ratio (relative clock factor) of time resolution of respective trace to the time resolution of the first trace. The relative clock factor and global offsets of the first and respective trace are used to adjust the timestamps of the events.

I propose to either use the smaller clock resolution of the two. Or maybe even use an approximated greatest common divisor so that if you have clock period 0.780s and 0.312s, you'll get something like 0.156s.

Metadata

Metadata

Assignees

No one assigned

    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