Activity for 3DTK - The 3D Toolkit
-
Fabian Arzberger committed [r2402] on Code
ros_listener: replace ofstream with file ptr, added min max dist flags for points
-
Better always_all_points state that will not make ImGui unresponsive. Color manager fix: Do not reset minmax when color_type panel is open.
-
Imshow: Now replicates show behaviour exactly. Bug fixed: Only reduced points were drawn when leaving All Points mode into no checkbox marked state.
-
Imshow fix: State where neither All Pts nor Always Reduce was selected did not display the very last scan index.
-
condense takes first scan as reference, not middle
-
Trajectory length skip size parameter added
-
ros listener looks up frame_id by itself, --skip_points added for faster bagfile re-use
-
ImGui color value input fixed
-
typo. did not compile
-
ImGui Spacemouse support added
-
ImGui Show Feature complete, Github folders removed
-
First imshow GUI finished. Rotate view is stil kinda bugged sometimes. Next TODO: docking
-
ImGui Selection Window implemented.
-
ImGui Selection Window first examples working
-
ImGui support added. Build files and demo.
-
Michael Bleier committed [r2387] on Code
Updated AprilTag to v3.3.0.
-
Sven Jörissen committed [r2386] on Code
Equivs control file for Debian bookworm
-
ros_listener ignore_timestamps flag fix. Pose callback queue is cleared every LiDAR callback
-
ros_listener replaces bag_listener. Added support for matching and interpolating timestamps in msg headers. Orthograhpic projection of a trajectory is now drawn at it's actual location.
-
Added Deadzone for Spacemouse
-
Remove NaN in bag_listener for real this time
-
Remove NaN in bag_listener
-
Better support for 3Dconnexion mouse. Transform around camera frame when using spacemouse. Rotation around origin when using normal mouse.
-
Removed dangerous redefinitions.
-
Dorit Borrmann committed [r2378]
initialize pairing mode
-
Longer paths in baglistener posible now 2+
-
Longer paths in baglistener posible now
-
Makita Daigo posted a comment on discussion Help
Hi. I start using 3dtk to remove dynamic object from scan data. Peopleremover create a folder (pplremover) and some files ,but I didn't understand how to show dynamic-object-removal map and how to use those files. Could you give me advice? Thank you
-
ROS listener write on rest mode
-
Bag Listener can create directory itself
-
fixed autoOct for scanio with data_suffix other than .3d
-
Added option toggle off show display objects
-
Generic Listener added that listens to ROS bagfiles, given names of topics and transformations. Exports directly in .3d and .pose file in UOSR format
-
Bkd Unit Test Mem Violation Fix
-
Condense/Atomize skip empty scans flag
-
cleanup CMakeLists.txt
-
Compute lenght of trajectory based on pose or frames files
-
JoSch committed [r2366]
add .github/workflows/main.yml
-
include/model/graphicsAlg.h: CGAL 5.3 removed deprecated Alpha_shape_euclidean_traits_2.h
-
src/ros/cartographer2scan.cc: resolve ambiguous use of filesystem
-
CMakeLists.txt: log4cxx headers require C++17 or later
-
What the heck is the uint type??
-
KDtreeIndexed fix and trailing whitespaces
-
bkd updates
-
condense/atomize skip on/off bool switch
-
bkd multi insert
-
Small planes update
-
Trailing whitespaces...
-
Small KDtree::CollectPts() fix
-
condense/atomize supports scatter removal now
-
Simon Engel committed [r2353]
add bruteforce search for slam6D and fix associated help text
-
atomize flushes the buffer at the end
-
atomize finished, trailing whitespaces removed
-
This time really, atomize.cc and atomize.h added, unfinished
-
atomize.cc and atomize.h added, unfinished
-
only comments about consistency of rgb / color reduce. FIXME later.
-
Normals Non-Threaded Added. Use when indices have to be preserved
-
BKD debugged
-
e57: fixed link order of libcurl.
-
scanio: Do not include framereader in scanio since framereader depends on scan.
-
BKD tree unit tests added (one of which still fails and i dont know why...)
-
Introducing BKD-Trees.
-
Bugfixes for condense. Now skips empty scanfiles. Last few scans are now flushed.
-
Condense exports path now.
-
Reverting these three files from fbr/panorama.
-
calc_normals --exportRGB added. Is default true.
-
Added default behaviour for -s and -e to scan_red (start at 0 and end at last available scan)
-
Emil Dumic committed [r2336]
-deleted trailing whitespaces in r2335
-
-added miller projection for scan_to_panorama and panorama_to_scan
-
Hi, I'm sure, JoSch could answer most questions better than me, but I'll give it a try anyways: yes, indeed. For that kind of data you should give the voxel size in cm. Regarding the masks, there is one small thing to consider. When reading the data some filters may be apllied. You can specify a minimum range and a maximum range, for example. I think there is also a peopleremover-specific filter applied to reduce the number of misdetections. The peopleremover only considers points which are not filtered...
-
Abe Link modified a comment on discussion Open Discussion
Thanks JoSch and Dorit for replies. Quoting Dorit, The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed So, for data which follows the data format used in Osnabrück present here (#13a) (that follows left hand rule), I should give voxel size in cm right? The other questions I have are the following: I see peopleremover creates a sub-directory named pplremover containing another sub-directory names 'masks'....
-
Thanks JoSch and Dorit for replies. Quoting Dorit, The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed So, for data which follows the data format used in Osnabrück present here (#13a) (that follows left hand rule), I should give voxel size in cm right? The other questions I have are the following: 1. I see peopleremover creates a sub-directory named pplremover containing another sub-directory names 'masks'....
-
Thanks JoSch and Dorit for replies. Quoting Dorit, The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed So, for data which follows the data format used in Osnabrück present here (#13a) (that follows left hand rule), I should give voxel size in cm right? The other questions I have are the following: 1. I see peopleremover creates a sub-directory named pplremover containing another sub-directory names 'masks'....
-
Thanks JoSch and Dorit for replies. Quoting Dorit, The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed So, for data which follows the data format used in Osnabrück present here (#13a) (that follows left hand rule), I should give voxel size in cm right? The other questions I have are the following: 1. I see peopleremover creates a sub-directory named pplremover containing another sub-directory names 'masks'....
-
Thanks JoSch and Dorit for replies. Quoting Dorit, The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed So, for data which follows the data format used in Osnabrück present here (#13a) (that follows left hand rule), I should give voxel size in cm right? The other question I have is the following: I see peopleremover creates a sub-directory named pplremover containing another sub-directory names 'masks'....
-
Thanks JoSch and Dorit for replies. Quoting Dorit, The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed So, for data which follows the data format used in Osnabrück present here (that follows left hand rule), I should give voxel size in cm right? The other question I have is the following: I see peopleremover creates a sub-directory named pplremover containing another sub-directory names 'masks'. scan000.mask...
-
Some more avoiding unnecessary normal calculation for point pair search.
-
Avoid unnecessary normal computation for point pair search.
-
Joschka van der Lucht committed [r2332]
scan2scan_distances: deactivated unused code with errors for building without OpenMP
-
Please note though, that there are a few important exceptions, most importantly the xyz and the rxp (proprietary format for Riegl laser scanners) format. As there are so many default parameters in all the programs in 3DTK some assumptions had to be made for those. The default format (uos) is in a left handed coordinate system and for the default parameters scenarios with mobile robots and data in cm are assumed. If your data is in a right handed coordinate system, you might want to use the xyz format....
-
The unit of the voxel size parameter is the same unit your data is in.
-
Hi, I have a few questions about peopleremover. To start with, I've one question: what are the units of the voxel-size parameter? Thanks AL
-
detectCylinder circleDetetctor: fixed non-constant-expression cannot be narrowed from type 'RBD_COMMON::Real' (aka 'double') to 'float' in initializer list [-Wc++11-narrowing]
-
maybe no more carriage return despite the fact that I couldn't find any before
-
merge gone wrong
-
Bug fix for normal calculation, needed in scan2scan distance
-
Added tool to compute scan2scan distance
-
removed debug output
-
-r parameter now working in show.
-
Sarah Menninger committed [r2324]
Bug fix typ error
-
src/detectCylinder/cylinderDetector.cc: prevent narrowing from double to float in initializer list [-Wc++11-narrowing]
-
Cylinder detection
-
Cylinder detection
-
please run 'make test' before committing
-
Travis macOS: fixed broken brew script
-
fixed naming issue in the variable related to Dorit's commit 27eb4a1bba32c20007b56fbeef9448946f78a6b1
-
Compute distance of points in global coordinates instead of local coordinates.
-
syntax error
-
changed default control files to install no ROS related packages
-
Fixed missing OpenMP::OpenMP_CXX for CMake <3.9