X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=wellesley.edu; s=gmail;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=1eVvy+iHSeMey79lKdOC1PYh2eCVt9A9p+D69Ji4Npc=;
        b=jVvRsCw6xe7nkC9JEjXrJ9ca8zOknIHw8OfFCeIiGED0rIBNY240+lHFoAIxieZIEM
         wf7H5ilhc0ekVzckKocJu9QI3OvUqgpIKTxp8Qdvr+mXd9EtHgoyivO3C0obOjfhzwVi
         3WcjEpW1TuQY4gHN5E5RjhMie4DjO6/oSWXjur2GuKHDStx4WiXY0zCMh8g4doWiHfAi
         nmPkAijpn5n0WaWxMJtjXyVOUp5OVKOlMR8bE9dKQL0uotmunPMZg4IRCSi1q932T0Bk
         hFqtYLCAsrwq8GNfGfXwWokEDza544eAlhTJdbMnEjfCsP5NaQxD4MyMHhlA4jYQVfqz
         pxPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=1eVvy+iHSeMey79lKdOC1PYh2eCVt9A9p+D69Ji4Npc=;
        b=HVligwIxjRYqHAp6ErUni3ZAQkPmjzlacis3Qdjm85u6JcNAgWot1tWMHAdiGlD+s4
         67aZyHfiWRFnQhgT5pKPG76jnE5RcJblLoBjb+SSJckI7KhjOGT5W8Clz4EpKy7rAFhD
         tl0nqXCEymhyc5Vf7bPMItJ6CnkF6ZW/oYtlT7oRkVSfIRS9AC+usxtL75rVMlvhYNvp
         pO7zvX1ArF8u/r/i7Al2+fTe1iFw8lZNN4mInTrerB9mNPKr3s4U2VPLl/g+b+g+31z1
         L7JmhkdglBFz6B4x6uohBidLhaP6kXAzcPZJ5LBDJH4JE+78MDGYi3DpqqTR+pfBYdKX
         sFEQ==
X-Gm-Message-State: AOUpUlFwAFPx5Uded9pu0MGXERBqNfKDRup/kd3yu5pn62zk0hdm5tI0
	6+aizxMHvV0cCWvrehEpq6wQVYXnaR7rFKX9vC35Ow==
X-Google-Smtp-Source: AAOMgpfTTKkpn+h10xlcQCM/MIcXd4am1SVJ/39nh6ZOGlcX/zF0x+oKS4JXOrdCFeQuEYLFPqSLJuMpLHx8sIGfb98=
X-Received: by 2002:a5e:8b4c:: with SMTP id z12-v6mr7360318iom.230.1531393435422;
 Thu, 12 Jul 2018 04:03:55 -0700 (PDT)
MIME-Version: 1.0
References: <1528856167 DOT 572732 DOT 1406110656 DOT 65EF7A52 AT webmail DOT messagingengine DOT com>
 <20180613054634 DOT 9044ff401aa2a0c14fc74f2f AT gmail DOT com> <1531363340 DOT 2194946 DOT 1438008344 DOT 05F00958 AT webmail DOT messagingengine DOT com>
In-Reply-To: <1531363340.2194946.1438008344.05F00958@webmail.messagingengine.com>
From: "James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Thu, 12 Jul 2018 07:03:42 -0400
Message-ID: <CAGDPQk2r0Xg7NomomTnPEra8r2HBM7_U5MgbJEJq2VtD6cCPAA@mail.gmail.com>
Subject: Re: [geda-user] [OT] Open Source Data Logger
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary="000000000000baec000570cb51fe"
Reply-To: geda-user AT delorie DOT com

--000000000000baec000570cb51fe
Content-Type: text/plain; charset="UTF-8"

Many plotting packages (e.g. matplotlib/python) understand the following
standard timestamp string format:
YYYYMMDDTHHMMSS.ssssss
e.g. 20180712T070513.123456

James

On Wed, Jul 11, 2018, 10:58 PM Edward Hennessy (ehennes+oss AT fastmail DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> On Tue, Jun 12, 2018, at 8:46 PM, Nicklas Karlsson (
> nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>
> Usually I dump data into some kind of file and use Octave to plot data.
>
>
> When using Octave, what data would users need to for time, exported in a
> CSV file column? Right now, I'm exporting 64 bit integers in microseconds
> off the epoch date or monolithic clock. What would be better for a plot
> with a user friently time axis?
>
> Ed
>
>

--000000000000baec000570cb51fe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Many plotting packages (e.g. matplotlib/python) understan=
d the following standard timestamp string format:<div dir=3D"auto">YYYYMMDD=
THHMMSS.ssssss</div><div dir=3D"auto">e.g. 20180712T070513.123456</div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">James</div><div dir=3D"auto"><br>=
</div><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr">On Wed, Jul =
11, 2018, 10:58 PM Edward Hennessy (<a href=3D"mailto:ehennes%2Boss AT fastmai=
l.com">ehennes+oss AT fastmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delor=
ie.com">geda-user AT delorie DOT com</a>] &lt;<a href=3D"mailto:geda-user AT delorie.=
com">geda-user AT delorie DOT com</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><u></u>





<div><div>On Tue, Jun 12, 2018, at 8:46 PM, Nicklas Karlsson (<a href=3D"ma=
ilto:nicklas DOT karlsson17 AT gmail DOT com" target=3D"_blank" rel=3D"noreferrer">nic=
klas DOT karlsson17 AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com=
" target=3D"_blank" rel=3D"noreferrer">geda-user AT delorie DOT com</a>] wrote:<br=
></div>
<blockquote type=3D"cite"><div>Usually I dump data into some kind of file a=
nd use Octave to plot data.<br></div>
</blockquote><div><br></div>
<div>When using Octave, what data would users need to for time, exported in=
 a CSV file column? Right now, I&#39;m exporting 64 bit integers in microse=
conds off the epoch date or monolithic clock. What would be better for a pl=
ot with a user friently time axis?<br></div>
<div><br></div>
<div>Ed<br></div>
<div><br></div>
</div>

</blockquote></div></div>

--000000000000baec000570cb51fe--