Open whw-create opened 2 years ago
Unfortunately not - we just have the per-scan timestamps.
There may de a few of the datasets that have the velodyne packets (which has that information), but they are not uploaded yet.
Thank you for your reply
------------------ 原始邮件 ------------------ 发件人: "NeBula-Autonomy/nebula-odometry-dataset" @.>; 发送时间: 2022年9月27日(星期二) 凌晨4:06 @.>; @.**@.>; 主题: Re: [NeBula-Autonomy/nebula-odometry-dataset] about timestamp (Issue #13)
Unfortunately not - we just have the per-scan timestamps.
There may de a few of the datasets that have the velodyne packets (which has that information), but they are not uploaded yet.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
hi, did you projected all lidars' point to one lidar already? cause i can't find extrinsic between lidars in your yaml of H, thanks for reply
in additional config files there are all the transformations that are needed
in additional config files there are all the transformations that are needed
i'm sorry but i really didn't find the extrinsic between lidars of dataset H in that extra files link
in the file there are relative transformations between different modules (cameras/lidars/base_link ,etc), so you just need to use a chain rule since there are relative transformations (x,y,z,r,p,y (Euler)) .
Frankly speaking the best idea and the easiest way is to just read this to urdf, see how we're doing this in locus over here
in the file there are relative transformations between different modules (cameras/lidars/base_link ,etc), so you just need to use a chain rule since there are relative transformations (x,y,z,r,p,y (Euler)) .
Frankly speaking the best idea and the easiest way is to just read this to urdf, see how we're doing this in locus over here
thanks
Didn't you record the timestamp of each point in the bag ?