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

Remove Dashing, Eloquent, Foxy, L500 and SR300 support #2841

Conversation

SamerKhshiboun
Copy link
Collaborator

@SamerKhshiboun SamerKhshiboun commented Aug 10, 2023

Remove EOL models
Remove EOL distros
Remove unused files/code (specially related to fisheye and pose sensors)

@Nir-Az
Copy link
Collaborator

Nir-Az commented Aug 28, 2023

This is draft right?
Please update when it's ready for review.

@Arun-Prasad-V
Copy link
Contributor

Hi @SamerKhshiboun ,

Since POSE stream is getting removed, does it make sense to remove the support for POSE sensor as well?
Reference line:

else if (sensor.is<rs2::pose_sensor>())

@SamerKhshiboun
Copy link
Collaborator Author

sensor.isrs2::pose_sensor()

Fixed. Also deleted PoseProfile usage in other places

@Arun-Prasad-V
Copy link
Contributor

sensor.isrs2::pose_sensor()

Fixed. Also deleted PoseProfile usage in other places

@SamerKhshiboun, It's still present in profile_manager.cpp

void PoseProfilesManager::registerProfileParameters(std::vector<stream_profile> all_profiles, std::function<void()> update_sensor_func)

@SamerKhshiboun
Copy link
Collaborator Author

sensor.isrs2::pose_sensor()

Fixed. Also deleted PoseProfile usage in other places

@SamerKhshiboun, It's still present in profile_manager.cpp

void PoseProfilesManager::registerProfileParameters(std::vector<stream_profile> all_profiles, std::function<void()> update_sensor_func)

Fixed, somehow it was missed in the git add command

# import sensor_msgs.point_cloud2 as pc2
import tf2_ros
from sensor_msgs.msg import PointCloud2 as msg_PointCloud2
from sensor_msgs_py import point_cloud2 as pc2
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This used to be humble only, is it relevant to iron and rolling too?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did not understand the question.. can you elaborate more ? are you talking about pc2 or tf2_ros ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NVM I understand now :)

@Nir-Az
Copy link
Collaborator

Nir-Az commented Sep 10, 2023

@SamerKhshiboun please solve conflicts This branch has conflicts that must be resolved

@Arun-Prasad-V
Copy link
Contributor

Arun-Prasad-V commented Sep 11, 2023

@SamerKhshiboun , Shall we remove the support of 'fisheye' sensor as well?

sensor.is<rs2::fisheye_sensor>())

bool is_video_sensor = (sensor->is<rs2::depth_sensor>() || sensor->is<rs2::color_sensor>() || sensor->is<rs2::fisheye_sensor>());

Also, in rs_launch.py

{'name': 'enable_fisheye1', 'default': 'true', 'description': 'enable fisheye1 stream'},

<xacro:property name="r430_cam_depth_to_fisheye_offset" value="0.042"/>

@SamerKhshiboun
Copy link
Collaborator Author

@SamerKhshiboun , Shall we remove the support of 'fisheye' sensor as well?

sensor.is<rs2::fisheye_sensor>())

bool is_video_sensor = (sensor->is<rs2::depth_sensor>() || sensor->is<rs2::color_sensor>() || sensor->is<rs2::fisheye_sensor>());

Also, in rs_launch.py

{'name': 'enable_fisheye1', 'default': 'true', 'description': 'enable fisheye1 stream'},

<xacro:property name="r430_cam_depth_to_fisheye_offset" value="0.042"/>

Fixed

Copy link
Collaborator

@Nir-Az Nir-Az left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SamerKhshiboun SamerKhshiboun merged commit 9dae8bd into IntelRealSense:ros2-development Sep 26, 2023
6 checks passed
@SamerKhshiboun SamerKhshiboun deleted the remove_l500_sr300 branch October 10, 2023 00:53
@christian-rauch
Copy link
Contributor

Is there a good reason to break the compatibility with foxy? Couldn't this be handled with #ifdefs like the other distributions? Could we alternatively at least introduce branches for distributions that are incompatible with the development branch? E.g. create a foxy branch for that last commit that still compiles on ROS foxy?

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

Successfully merging this pull request may close these issues.

None yet

4 participants