-
Notifications
You must be signed in to change notification settings - Fork 3
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
range data format #86
Comments
ping @alfonsotecnalia I see two options:
The advantage of the first option is that we know from the file name its content. I don't mind adding such format.
I would rather use the |
I'm perfectly ok with the distance format, including the option to include multiple columns! I'll update my data format. |
Ok with including distance format. |
@Enri2077 did you use that format at the end? If yes, please point me to your files, and I will adjust documentation accordingly |
Yes I used it. I still don't have a definitive dataset, but I'll attach a file using this format: |
Perfect, thanks! |
Hi @aremazeilles,
I'm working on beast and need a data format representing a distance through time.
I considered using the
Joint center 3D trajectory
orLandmark 3D trajectory
data formats, reporting a position in meters through time, but having the x, y and z fields is not ideal since I need to represent a distance rather than a position.The data is computed as the minimum range between the trolley and obstacles at any time, measured with a lidar/range finder.
I suggest the following data format:
sec
m
What do you think?
The text was updated successfully, but these errors were encountered: