moveit octomap for different namespaces

edit

I have a setup for husky platform with ur3 arm attached to it, i configured the launch file for spawning two husky's under the namespace husky1 and husky2, i am able to move both the arm using moveit. But the problem arises in the perception pipeline, how do i get an octomap for husky1 and husky2 seperately?

platfrom used: ROS melodic, ubuntu 18.04, moveit

error that i am getting

[ERROR] [1621331524.096919906, 7.459000000]: Transform error: "base_link" passed to lookupTransform argument source_frame does not exist. 
[ERROR] [1621331524.096995823, 7.459000000]: Transform cache was not updated. Self-filtering may fail.

below are the different launch files i am using:

ur3_planning_execution.launch

<?xml version="1.0"?>
<launch>
<group ns="husky1">
  <arg name="allow_trajectory_execution" default="true"/>
  <rosparam command="load" file="$(find velo_moveit)/config/joint_names.yaml"/>
  <include file="$(find velo_moveit)/launch/planning_context.launch">
    <arg name="load_robot_description" value="true"/>
  </include>

  <include ns="move_group" file="$(find velo_moveit)/launch/sensor_manager1.launch.xml" if="$(arg allow_trajectory_execution)">
    <arg name="moveit_sensor_manager" value="husky" />
  </include>

  <node name="joint_state_publisher" pkg="joint_state_publisher" type="joint_state_publisher">
    <param name="/use_gui" value="false"/>
    <rosparam param="source_list">[/joint_states]</rosparam>
  </node>

  <include file="$(find velo_moveit)/launch/move_group.launch">
    <arg name="publish_monitored_planning_scene" value="true"/>
  </include>

  <include file="$(find velo_moveit)/launch/moveit_rviz.launch">
    <arg name="rviz_config" value="$(find velo_moveit)/launch/robot1.rviz"/>

  </include>

</group>

<group ns="husky2">
  <arg name="allow_trajectory_execution" default="true"/>
  <rosparam command="load" file="$(find velo_moveit)/config/joint_names.yaml"/>
  <include file="$(find velo_moveit)/launch/planning_context.launch">
    <arg name="load_robot_description" value="true"/>
  </include>

  <include ns="move_group" file="$(find velo_moveit)/launch/sensor_manager2.launch.xml" if="$(arg allow_trajectory_execution)">
    <arg name="moveit_sensor_manager" value="husky" />
  </include>

  <node name="joint_state_publisher" pkg="joint_state_publisher" type="joint_state_publisher">
    <param name="/use_gui" value="false"/>
    <rosparam param="source_list">[/joint_states]</rosparam>
  </node>

  <include file="$(find velo_moveit)/launch/move_group.launch">
    <arg name="publish_monitored_planning_scene" value="true"/>
  </include>

  <include file="$(find velo_moveit)/launch/moveit_rviz.launch">
    <arg name="rviz_config" value="$(find velo_moveit)/launch/robot2.rviz"/>
  </include>

</group>

</launch>

sensor_manager1.launch.xml

<launch>

  <!-- This file makes it easy to include the settings for sensor managers -->

  <!-- Params for 3D sensors config -->
  <rosparam command="load" file="$(find velo_moveit)/config/sensors_3d1.yaml" />

  <!-- Params for the octomap monitor -->
  <param name="octomap_frame" type="string" value="husky1/base_link" />
  <param name="octomap_resolution" type="double" value="0.05" />
  <param name="max_range" type="double" value="5.0" />

  <!-- Load the robot specific sensor manager; this sets the moveit_sensor_manager ROS parameter -->
  <arg name="moveit_sensor_manager" default="husky" />
  <include file="$(find velo_moveit)/launch/$(arg moveit_sensor_manager)_moveit_sensor_manager.launch.xml" />

</launch>

sensor3d1.yaml

sensors:
  - filtered_cloud_topic: filtered_cloud
    max_range: 5.0
    max_update_rate: 1.0
    padding_offset: 0.1
    padding_scale: 1.0
    point_cloud_topic: /husky1/camera/depth/points
    point_subsample: 1
    shape_padding: 0.01
    shape_scale: 1.0  
    sensor_plugin: occupancy_map_monitor/PointCloudOctomapUpdater

main launch file

<?xml version="1 ...