Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

csv-time-join - Unexpected behavior at border time stamps #60

Open
vendall opened this issue Oct 12, 2015 · 3 comments
Open

csv-time-join - Unexpected behavior at border time stamps #60

vendall opened this issue Oct 12, 2015 · 3 comments

Comments

@vendall
Copy link
Collaborator

vendall commented Oct 12, 2015

I'm having an unexpected issue with csv-time-join, though this may be a feature and I'm not fully understanding the utility.

Here is what I want to do:

Inputs
sensor_data.bin - standard timestamped sensor bin file (hyperspec in my case but irrelevant to this issue)
timestamps.bin - list of time stamps

Goal
I want to grab from sensor_data.bin any data within n seconds of the timestamps in timestamps.bin.

Current Method
sensor_data.bin | csv-time-join 'timestamps.bin;binary=t;fields=t' - --binary='t,3ui,158112w' --fields=t --nearest --bound=n

Current Outcome
This seems to work for all timestamps in timestamps.bin, except for the first and last. For the first one it only outputs data with timestamps up to n seconds larger (inclusive), and for the last one it only outputs data with timestamps up to n seconds smaller (not inclusive).

Is this behavior expected? If yes, can I achieve what I want with csv-time-join?

Cheers,
Alex.

@vlaskine
Copy link

probably the quickest would be to take a look at your desk and decide what to do (even if it is a bug, i can think of a quick workaround)

when would it be a good time?

@vendall
Copy link
Collaborator Author

vendall commented Oct 12, 2015

Hi Seva, do you want to take a look at 12 tomorrow?

I can probably make it work in combination with cvs-time-delay, but I thought I'd ask first in case I'm missing something (or in case it's a genuine bug).

@vlaskine
Copy link

csv-time-delay is exactly the workaround i kept in mind, however let us have a chat at 12 tomorrow (on tuesday); i will go over to your desk

if it is a bug (as it seems so far), we will come up with a simple way to reproduce it and identify the right behaviour

if, less likely, it is a subtle feature, i will update --help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants