Open HernandoR opened 2 months ago
@HernandoR We use "pose_xy" to predefine a certain range, because we do not know where the road is. If mvs/lidar points is provided, the range will be more accurate.
The center point seems to have am impact on the range of construction through offset
Please point out if there anywhere to automatically scaling based on the range of scene (maybe refer to the range of camera poses?)
@HernandoR You can simply set ((max_x + min_x) / 2, (max_y + min_y) / 2) as a center point. In application, we need manually make pose center as bev center before we reconstruct.
That surely appropriate I’m currently using ROME a sequential process after colmap, I’m going to write a small script for generating configuration.
Liu Zhen
From: DRosemei @.> Sent: Thursday, October 10, 2024 5:22:04 PM To: DRosemei/RoMe @.> Cc: Liu Zhen @.>; Mention @.> Subject: Re: [DRosemei/RoMe] Cut-off when exeeding certain range of x, or y (Issue #58)
@HernandoRhttps://github.com/HernandoR You can simply set ((max_x + min_x) / 2, (max_y + min_y) / 2) as a center point. In application, we need manually make pose center as bev center before we reconstruct.
— Reply to this email directly, view it on GitHubhttps://github.com/DRosemei/RoMe/issues/58#issuecomment-2404562595, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK4XSWDVOJ4ZA2LASW5HNH3Z2ZBLZAVCNFSM6AAAAABOVZQTASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUGU3DENJZGU. You are receiving this because you were mentioned.Message ID: @.***>
My test of colmap is great, and smooth, at least to a certain range.
the bev and mesh both been cut off at a limit of x, and there's no mesh beyond that line.
My have migrated the pymeshlab api as follows, not sure if related:
the bev is as follows
hoping someone point out potential configs