From: "Kim, Seongab via lttng-dev" <lttng-dev@lists.lttng.org>
To: Philippe Proulx <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [EXTERNAL] Re: difference of timestamp between babeltrace and python binding
Date: Thu, 23 Jul 2020 05:43:27 +0000 [thread overview]
Message-ID: <ecb0253a30f54c1aa11b59588e89bc00@HIMDWSMB06.ad.harman.com> (raw)
In-Reply-To: <CAB4xu_3=6yYndO-C49FQ=hXF4eC+f6WGgMQCJ9-GhbA4zQ8mCQ@mail.gmail.com>
> -----Original Message-----
> From: Philippe Proulx <eeppeliteloop@gmail.com>
> Sent: Wednesday, July 22, 2020 4:57 PM
> To: Kim, Seongab <Seongab.Kim@harman.com>
> Cc: lttng-dev@lists.lttng.org
> Subject: [EXTERNAL] Re: [lttng-dev] difference of timestamp between
> babeltrace and python binding
>
> `type(1e3)` is `float`.
>
> You get an inaccurate floating point division operation here instead of an
> integral one.
>
> Do:
>
> ns_from_origin % 1000
>
> or
>
> ns_from_origin % int(1e3)
>
> instead.
>
> Hope this helps,
>
> Phil
>
Hi Phil,
Thanks. With the change, it works as expected.
Best regards,
Seongab
WARNING: multiple messages have this Message-ID (diff)
From: "Kim, Seongab via lttng-dev" <lttng-dev@lists.lttng.org>
To: Philippe Proulx <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [EXTERNAL] Re: difference of timestamp between babeltrace and python binding
Date: Thu, 23 Jul 2020 05:43:27 +0000 [thread overview]
Message-ID: <ecb0253a30f54c1aa11b59588e89bc00@HIMDWSMB06.ad.harman.com> (raw)
Message-ID: <20200723054327.3yAt2cDH4GJ89JhBvsq5_eYu-LbjVK_jvFV9pbO5Bug@z> (raw)
In-Reply-To: <CAB4xu_3=6yYndO-C49FQ=hXF4eC+f6WGgMQCJ9-GhbA4zQ8mCQ@mail.gmail.com>
> -----Original Message-----
> From: Philippe Proulx <eeppeliteloop@gmail.com>
> Sent: Wednesday, July 22, 2020 4:57 PM
> To: Kim, Seongab <Seongab.Kim@harman.com>
> Cc: lttng-dev@lists.lttng.org
> Subject: [EXTERNAL] Re: [lttng-dev] difference of timestamp between
> babeltrace and python binding
>
> `type(1e3)` is `float`.
>
> You get an inaccurate floating point division operation here instead of an
> integral one.
>
> Do:
>
> ns_from_origin % 1000
>
> or
>
> ns_from_origin % int(1e3)
>
> instead.
>
> Hope this helps,
>
> Phil
>
Hi Phil,
Thanks. With the change, it works as expected.
Best regards,
Seongab
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-07-23 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 6:30 difference of timestamp between babeltrace and python binding Kim, Seongab via lttng-dev
2020-07-22 6:30 ` [lttng-dev] " Kim, Seongab via lttng-dev
2020-07-22 14:56 ` Philippe Proulx via lttng-dev
2020-07-22 14:56 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-07-23 5:43 ` Kim, Seongab via lttng-dev [this message]
2020-07-23 5:43 ` [lttng-dev] [EXTERNAL] " Kim, Seongab via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ecb0253a30f54c1aa11b59588e89bc00@HIMDWSMB06.ad.harman.com \
--to=lttng-dev@lists.lttng.org \
--cc=Seongab.Kim@harman.com \
--cc=eeppeliteloop@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).