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

About the output results of linemap #25

Closed
ccy-ustb opened this issue May 26, 2023 · 3 comments
Closed

About the output results of linemap #25

ccy-ustb opened this issue May 26, 2023 · 3 comments

Comments

@ccy-ustb
Copy link

Excellent job, I am very interested in your work!

Now, I can use your program to rebuild the line map of my own dataset, but I have some questions about the output line map result file.

Can you explain the information of each output file?

I would like to know how to read the 3D line segment coordinates and their corresponding camera ID, 2D line segment ID, and 2D line segment coordinates in the output line map?

Looking forward to your reply very much!

@B1ueber2y
Copy link
Member

Hi, thanks for the interest!

You can directly read all the information in Python. The output is a list of LineTrack. And the attributes can be accessed directly with, for example, track.image_id_list. Full members are listed here: https://github.com/cvg/limap/blob/main/limap/base/bindings.cc#L231-L259, and documentation will be online soon.

Thanks!

@ccy-ustb
Copy link
Author

The output results are in the alltracks.txt file.The content inside may be as follows:

5617
0 188 82
0.5200465577 1.4732014223 5.4052263127
0.4932090298 2.6219705810 5.3912869506
0 1 13 14 15 48 50 150 0 3 6 7 10 13 14 15 16 17 19 49 0 1 14 47 5 6 4 8 5 11 52 3 3 9 16 49 67 8 150 50 47 64 66 50 71 71 35 41 24 27 39 25 38 47 39 47 69 36 50 67 65 65 65 119 119 150 65 66 120 66 64 122 111 119 120 111 121 70 66 121 122 70 67 124 154 156 121 154 155 111 138 120 170 170 121 138 171 170 122 133 143 149 135 143 148 294 138 279 153 138 161 162 160 162 139 153 159 259 152 160 249 162 160 170 153 155 171 179 156 159 161 171 172 179 179 160 172 174 174 176 176 161 171 175 175 259 174 175 175 177 180 180 184 259 173 177 184 259 176 177 184 172 185 172 174 180 180 185 179 181 249 183 183 247 247 181 184 181 187 177 247 185 246 249 35 51 38 39
0 10 357 164 3 817 3 2 275 11 10 1044 935 329 63 325 151 105 1236 62 277 291 382 485 29 65 30 442 178 750 131 31 56 64 192 498 40 175 22 624 56 79 10 693 21 24 737 765 995 256 269 724 1612 123 1 529 52 2 380 47 46 587 267 246 10 33 125 92 80 476 479 18 45 9 23 234 98 29 27 9 74 455 5 0 4 7 4 11 4 111 29 14 74 86 201 273 221 18 202 261 281 109 5 43 407 13 5 2 119 180 207 4 122 145 23 88 178 215 2 145 268 110 13 90 217 1 119 130 106 94 374 71 261 13 229 11 176 253 131 84 182 5 81 57 138 234 147 61 124 465 377 796 804 253 215 284 1005 145 183 391 770 94 557 129 254 622 1170 643 16 1342 269 132 636 314 461 773 480 330 1286 83 372 1099 752 237 1120 486 907 225

The first line is the number of 3D line segments in the line map.
The second line is the 3D segment ID, which corresponds to the number of 2D segments and 2D images.
The third line is the starting point coordinates of the 3D line segment (X1, Y1, Z1).
The endpoint coordinates of the 3D line segment in the fourth row (X2, Y2, Z2).
The fifth line is the image ID corresponding to these 188 2D line segments.
The sixth line is the 2D segment ID in the image ID corresponding to the previous line one by one.

Is my explanation correct?

@B1ueber2y
Copy link
Member

Yes your explanation is very correct. Thanks a lot!

zhangshaos pushed a commit to zhangshaos/limap that referenced this issue Jul 12, 2023
* add hawpv3.

* add hawpv3 folder.

* Ignore dirty changes from hawp third party

Co-authored-by: Rémi Pautrat <remi.pautrat@polytechnique.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants