How to set correctly the timeunit and the offset when importing traces ?

[generoso]

From @stanisic on March 31, 2015 13:58

I see that this part have been changed so users can choose the time unity. However, the way it is implemented at the moment is not intuitive. I understand that the most logical solution (where user would just choose the time unit of the whole trace) would mean that the trace import is much longer. Still, I am ready to pay that price as it is much more convenient approach.

Copied from original issue: soctrace-inria/framesoc#149

[generoso]

From @dosimont on March 31, 2015 14:21

Hi Luka. The time unit field is only a way to specify the unit for trace formats whose this information is not explicited, such as Pajé. It does not influence the import time.

[dosimont]

Should this issue be closed?

[generoso]

The problem is still there: the way currently used to specify the time unit and the time offset is not intuitive. Currently the unit specify refers to the time unit after the offset has been applied (destination time unit). The user does not necessary know the offset to apply. This offset could be therefore computed and the user may be asked to provide only the source time unit. Knowing the offset we can compute the destination time unit.

E.g.

timestamps: 54.34; 55.556; 57.21
source time unit: s

offset: 3 (computed)
destination timeunit (computed): ms
timestamp stored (longs): 54340; 55556; 57210