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
KITTI to XVIZ conversion error #540
Comments
I have the same problem,Has your problem been solved? thanks lot. |
No, Not solved yet. |
thanks. This shows an issue arround Float64Array(). I'll give this a try ASAP and see if I can pinpoint the cause. |
I am getting the exact same errors when converting the KITTI dataset. Is there any update on this? I know there is a a validation tool supposedly able to validate the generated XVIZ data, however I don't see much documentation on how to use it or what it would provide. This also seems to be related to #534 and #535. I suspect as was stated in #534 the converted data consists of several |
Taking a closer look at the generated JSON file using the
The EDIT: Here is a screenshot of what I'm seeing with no LIDAR, Tracklets, trajectory converted. Notice no velocity/acceleration plots and no visible camera windows: |
So I think I found the issue with the trajectory generation code. In the Change the return statement to use function getPoseTrajectory(_ref) {
var poses = _ref.poses,
startFrame = _ref.startFrame,
endFrame = _ref.endFrame;
var positions = [];
var iterationLimit = Math.min(endFrame, poses.length); for (var i = startFrame; i < iterationLimit; i++) {
positions.push(poses[i].pose);
} var startPose = poses[startFrame].pose;
var worldToStartPoseTransformMatrix = new _math._Pose(startPose).getTransformationMatrix().invert();
return positions.map(function (currPose) {
var offset = getGeospatialVector(startPose, currPose);
var relativeOffset = worldToStartPoseTransformMatrix.transformVector(offset);
return [relativeOffset[0], relativeOffset[1], relativeOffset[2]];
});
} With this fix, the trajectory generation works for the vehicle. Unfortunately, the velocity/acceleration metrics are still missing, as are the camera displays. After digging a bit deeper, the return uiConfig ? (
<div>{uiConfig.children && uiConfig.children.map(this._renderItem)}</div>
) : null; Since this property is undefined, nothing is displayed. I'm not sure at the moment where this property is supposed to be set or why its not currently being set. Has anyone else seen this issue? Here is the props object in {name: "Camera", uiConfig: undefined, log: XVIZFileLoader, style: {…}, components: {…}, …}
componentProps: {}
components: {}
log: XVIZFileLoader {onXVIZMessage: ƒ, onError: ƒ, getCurrentTime: ƒ, getLookAhead: ƒ, getMetadata: ƒ, …}
name: "Camera"
style: {}
uiConfig: undefined
__proto__: Object |
Also found out that in streetscape.gl modules/core/src/utils/transform.js |
I clearly need to jump back on this. I have a Ubuntu setup I will test on tonight. Thanks @speculees @patnolan33 for all your digging. Sorry this has been broken for you. |
@patnolan33 Huge thanks for tracking this down. The problem was rooted in math.gl being updated and no longer returning a class but a plain array. Previously it had accessors for fields like |
- Update math.gl usage and remove deprecated math.gl function from v2 - Fixes aurora-opensource#534, aurora-opensource#535, aurora-opensource#540
KITTI to XVIZ converter generates corrupted files which gives error while parsing on browser. Everything works fine with the already converted KITTI data available in XVIZ-data directory.
https://github.com/uber/xviz-data/tree/master/kitti/2011_09_26_drive_0005_sync
Tried with different data streams from the KITTI website but the issue is the same.
The converter generates the files without any error
XVIZServer also starts without any errors
start-streaming-local also does not give any error
The text was updated successfully, but these errors were encountered: