question related to generation of streams with non-regular intervals

[JRV77]

Hi,

Ref to

Streamserver use the files in the "dataset" directory to produce infinite stream data. The timetstamps must be orderedchronogically from older to newer. Streamserver use the timestamps only to simulate the intervals between two different tuples of the stream. The streamserver replaces the timestamps with current timestamps.

The event csv doesn't have a regular time interval for events. I'm struggling to get data out of this stream. Could that be the reason?

[csvingos]

Yes the event csv have events that produced with huge time intervals. That is the reason why you didn't get the output immediately.

[JRV77]

Ok but I abviously got timeout, is that something to be tuned in Exareme?

On Fri, Oct 21, 2016 at 8:34 AM +0200, "csvingos" <notifications@github.commailto:notifications@github.com> wrote:

Yes the event csv have events that produced with huge time intervals. That is the reason why you didn't get the output immediately.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/9#issuecomment-255305108, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AO7UwlUr4X4UtTJWCrwliJR6xIysekrvks5q2Fz4gaJpZM4KbOwO.

[csvingos]

Hello Jean,

The event dataset has timestamps that are

Ok but I abviously got timeout, is that something to be tuned in Exareme?

Hi Jean,

I delete some tuples that produced the problem with the huge time intervals.

Update your repository and try again.

On Fri, Oct 21, 2016 at 8:34 AM +0200, "csvingos"
<notifications@github.commailto:notifications@github.com> wrote:

Yes the event csv have events that produced with huge time intervals. That
is the reason why you didn't get the output immediately.

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/9#issuecomment-255305108,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AO7UwlUr4X4UtTJWCrwliJR6xIysekrvks5q2Fz4gaJpZM4KbOwO.

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#9 (comment)

[JRV77]

Hi,

Thanks I'll try that.
Also on my local install, I've sorted the measurement csv by timestamp and I am now able to see both S001 and S002 values. S002 were at the bottom and never generated. I can upload it later if you want.

Best regards,
Jean-Raphael

---

From: csvingos <notifications@github.commailto:notifications@github.com>
Sent: Thursday, October 27, 2016 5:40 PM
Subject: Re: [madgik/Docker-StreamServer] question related to generation of streams with non-regular intervals (#9)
To: madgik/Docker-StreamServer <docker-streamserver@noreply.github.commailto:docker-streamserver@noreply.github.com>
Cc: Author <author@noreply.github.commailto:author@noreply.github.com>, JRV77 <jean-raphael_vieille@hotmail.frmailto:jean-raphael_vieille@hotmail.fr>

Hello Jean,

The event dataset has timestamps that are

Ok but I abviously got timeout, is that something to be tuned in Exareme?

Hi Jean,

I delete some tuples that produced the problem with the huge time intervals.

Update your repository and try again.

On Fri, Oct 21, 2016 at 8:34 AM +0200, "csvingos"
<notifications@github.commailto:notifications@github.commailto:notifications@github.com> wrote:

Yes the event csv have events that produced with huge time intervals. That
is the reason why you didn't get the output immediately.

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/9#issuecomment-255305108,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AO7UwlUr4X4UtTJWCrwliJR6xIysekrvks5q2Fz4gaJpZM4KbOwO.

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#9 (comment)

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/9#issuecomment-256680500, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AO7UwhaIVu2AfbeIUo-gSxMr3tMv3pazks5q4MX-gaJpZM4KbOwO.

[csvingos]

Hi Jean,

It will very helpful to upload your changes.

kind regards,
Christoforos

Hi,

Thanks I'll try that.
Also on my local install, I've sorted the measurement csv by timestamp and
I am now able to see both S001 and S002 values. S002 were at the bottom
and never generated. I can upload it later if you want.

Best regards,
Jean-Raphael

---

From: csvingos <notifications@github.commailto:notifications@github.com>
Sent: Thursday, October 27, 2016 5:40 PM
Subject: Re: [madgik/Docker-StreamServer] question related to generation
of streams with non-regular intervals (#9)
To: madgik/Docker-StreamServer
<docker-streamserver@noreply.github.commailto:docker-streamserver@noreply.github.com>
Cc: Author <author@noreply.github.commailto:author@noreply.github.com>,
JRV77
<jean-raphael_vieille@hotmail.frmailto:jean-raphael_vieille@hotmail.fr>

Hello Jean,

The event dataset has timestamps that are

Ok but I abviously got timeout, is that something to be tuned in
Exareme?

Hi Jean,

I delete some tuples that produced the problem with the huge time
intervals.

Update your repository and try again.

On Fri, Oct 21, 2016 at 8:34 AM +0200, "csvingos"
<notifications@github.commailto:notifications@github.commailto:notifications@github.com>
wrote:

Yes the event csv have events that produced with huge time intervals.
That
is the reason why you didn't get the output immediately.

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/9#issuecomment-255305108,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AO7UwlUr4X4UtTJWCrwliJR6xIysekrvks5q2Fz4gaJpZM4KbOwO.

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#9 (comment)

You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHubhttps://github.com//issues/9#issuecomment-256680500,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/AO7UwhaIVu2AfbeIUo-gSxMr3tMv3pazks5q4MX-gaJpZM4KbOwO.

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#9 (comment)