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

Slicing functionality #35

Closed
3 of 7 tasks
Georacer opened this issue Apr 4, 2017 · 4 comments
Closed
3 of 7 tasks

Slicing functionality #35

Georacer opened this issue Apr 4, 2017 · 4 comments
Labels

Comments

@Georacer
Copy link
Owner

Georacer commented Apr 4, 2017

It is desirable that functionality is implemented for:

  • Cropping an Ardupilog object to a smaller time window
  • Cropping one or more windows out of the log and keeping the rest

Arguments for cropping could be time or line indexed. For example:

  • getSlice([50 5000], ‘LineNo’)
  • getSlice([0 5.37],’TimeUS’)
  • getSlice([0 105.1],’TimeS’)
  • getSlice([t1 t2],’TimeUTC’)
  • double value = getSlice(5.4,’TimeS’) % For interpolation
  • getSlice(times,’type’,’endpoints’,’format’,’UTC’)
  • double interps = getSlice(times,’type’,’interp’,’format’,’TimeS’)
@hunt0r
Copy link
Collaborator

hunt0r commented Apr 26, 2017

Began addressing in #47

@Georacer
Copy link
Owner Author

Georacer commented Oct 6, 2018

'TimeUS' was dropped, since not all messages have this field and also such fine-grained resolution is not needed.

@hunt0r
Copy link
Collaborator

hunt0r commented Feb 7, 2019

At present, I use slicing often, and it works pretty well. Should we close this Issue?

@Georacer
Copy link
Owner Author

Georacer commented Feb 8, 2019

Yeah, I think it serves its purpose well. Go ahead!

@hunt0r hunt0r closed this as completed Feb 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants