bGeigie import: "number of lines" vs. "number of measurments"

[thinrope]

Number of lines should include all lines in the file (including comments, corrupted lines, etc.), more or less $(wc -l) ...

Number of measurements, probably means "number of valid (=parsed fine) lines", so may be renamed to "number of valid measurements:" or simply "number of datapoints:" or even "valid data lines:" ...

Additionally, "errors:" and "comment lines:" is useful.

[nokton]

The databot app has most of the logic for this parsing AFAIK. Is it reuseable?

On Jan 19, 2013, at 12:16 AM, Kalin KOZHUHAROV notifications@github.com wrote:

Number of lines should include all lines in the file (including comments, corrupted lines, etc.), more or less $(wc -l) ...

Number of measurements, probably means "number of valid (=parsed fine) lines", so may be renamed to "number of valid measurements:" or simply "number of datapoints:" or even "valid data lines:" ...

Additionally, "errors:" and "comment lines:" is useful.

— Reply to this email directly or view it on GitHub.

[seanbonner]

Databot is on Lionel's server so we don't have access to anything about how it works. We asked to move it to Safecast but haven't gotten a reply.

If we're going to be using it more going forward it should be on safecast's servers with some documentation so it can be used in other areas. -s

On Mon, Jan 21, 2013 at 7:20 PM, Pieter Franken notifications@github.comwrote:

The databot app has most of the logic for this parsing AFAIK. Is it reuseable?

On Jan 19, 2013, at 12:16 AM, Kalin KOZHUHAROV notifications@github.com wrote:

Number of lines should include all lines in the file (including comments, corrupted lines, etc.), more or less $(wc -l) ...

Number of measurements, probably means "number of valid (=parsed fine) lines", so may be renamed to "number of valid measurements:" or simply "number of datapoints:" or even "valid data lines:" ...

Additionally, "errors:" and "comment lines:" is useful.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/safecastapi/issues/81#issuecomment-12491723.

Sean Bonner homebase http://seanbonner.com | twitter http://twitter.com/seanbonner | G+ https://plus.google.com/101629211371073711149/posts | SAFECASThttp://safecast.org

• I'm no longer on Facebook, here's whyhttp://blog.seanbonner.com/2012/04/15/on-leaving-facebook/ .

[nokton]

I see - let me see what I can do.

Pieter

On Jan 21, 2013, at 7:38 PM, seanbonner notifications@github.com wrote:

Databot is on Lionel's server so we don't have access to anything about how it works. We asked to move it to Safecast but haven't gotten a reply.

If we're going to be using it more going forward it should be on safecast's servers with some documentation so it can be used in other areas. -s

On Mon, Jan 21, 2013 at 7:20 PM, Pieter Franken notifications@github.comwrote:

The databot app has most of the logic for this parsing AFAIK. Is it reuseable?

On Jan 19, 2013, at 12:16 AM, Kalin KOZHUHAROV notifications@github.com wrote:

Number of lines should include all lines in the file (including comments, corrupted lines, etc.), more or less $(wc -l) ...

Number of measurements, probably means "number of valid (=parsed fine) lines", so may be renamed to "number of valid measurements:" or simply "number of datapoints:" or even "valid data lines:" ...

Additionally, "errors:" and "comment lines:" is useful.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/safecastapi/issues/81#issuecomment-12491723.

Sean Bonner homebase http://seanbonner.com | twitter http://twitter.com/seanbonner | G+ https://plus.google.com/101629211371073711149/posts | SAFECASThttp://safecast.org

• I'm no longer on Facebook, here's whyhttp://blog.seanbonner.com/2012/04/15/on-leaving-facebook/ . — Reply to this email directly or view it on GitHub.

[jamoross]

Getting the databot stuff brought over should be possible now that Lionel is back. I've sent him a request.

[jamoross]

Oops! Clicked the wrong button. Please bear with me as I come up-to-speed with this GitHub thingy.