ModuleNotFoundError: No module named ‘my_subscriber_pkg’
[publish_age_node-1] process has died [pid 15497, exit code 1, cmd /home/user/catkin_ws/src/my_subscriber_pkg/scripts/exercise4.3_message.py __name:=publish_age_node __log:=/home/user/.ros/log/21439c46-6bef-11ed-89e0-0242c0a87007/publish_age_node-1.log].
log file: /home/user/.ros/log/21439c46-6bef-11ed-89e0-0242c0a87007/publish_age_node-1*.log
can you help me? please!
Hi @h.santander ,
if I remember correctly, this unit is about to create your own service or action message, right? So could you please show the code? Or double-check if you have adjust CMakelist.txt and package.xml correctly.
Hi,
the code looks fine. So I guess it it the problem of CMakelist.txt and package.xml. Could you please copy the content of these 2 files again?
By the way, you can use this to contain a piece of code in chat:
import something
and don’t have to take a full screenshot of the compiler.
@MeineLiebeAxt
Thanks for your advise
cmake_minimum_required(VERSION 3.0.2)
project(my_subscriber_pkg)
## Compile as C++11, supported in ROS Kinetic and newer
# add_compile_options(-std=c++11)
## Find catkin macros and libraries
## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
## is used, also find other catkin packages
find_package(catkin REQUIRED COMPONENTS
rospy
std_msgs
message_generation
)
## System dependencies are found with CMake's conventions
# find_package(Boost REQUIRED COMPONENTS system)
## Uncomment this if the package has a setup.py. This macro ensures
## modules and global scripts declared therein get installed
## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html
# catkin_python_setup()
################################################
## Declare ROS messages, services and actions ##
################################################
## To declare and build messages, services or actions from within this
## package, follow these steps:
## * Let MSG_DEP_SET be the set of packages whose message types you use in
## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...).
## * In the file package.xml:
## * add a build_depend tag for "message_generation"
## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET
## * If MSG_DEP_SET isn't empty the following dependency has been pulled in
## but can be declared for certainty nonetheless:
## * add a exec_depend tag for "message_runtime"
## * In this file (CMakeLists.txt):
## * add "message_generation" and every package in MSG_DEP_SET to
## find_package(catkin REQUIRED COMPONENTS ...)
## * add "message_runtime" and every package in MSG_DEP_SET to
## catkin_package(CATKIN_DEPENDS ...)
## * uncomment the add_*_files sections below as needed
## and list every .msg/.srv/.action file to be processed
## * uncomment the generate_messages entry below
## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...)
## Generate messages in the 'msg' folder
add_message_files(
FILES
Age.msg
#Message1.msg
#Message2.msg
)
## Generate services in the 'srv' folder
# add_service_files(
# FILES
# Service1.srv
# Service2.srv
# )
## Generate actions in the 'action' folder
# add_action_files(
# FILES
# Action1.action
# Action2.action
# )
## Generate added messages and services with any dependencies listed here
generate_messages(
DEPENDENCIES
std_msgs
)
################################################
## Declare ROS dynamic reconfigure parameters ##
################################################
## To declare and build dynamic reconfigure parameters within this
## package, follow these steps:
## * In the file package.xml:
## * add a build_depend and a exec_depend tag for "dynamic_reconfigure"
## * In this file (CMakeLists.txt):
## * add "dynamic_reconfigure" to
## find_package(catkin REQUIRED COMPONENTS ...)
## * uncomment the "generate_dynamic_reconfigure_options" section below
## and list every .cfg file to be processed
## Generate dynamic reconfigure parameters in the 'cfg' folder
# generate_dynamic_reconfigure_options(
# cfg/DynReconf1.cfg
# cfg/DynReconf2.cfg
# )
###################################
## catkin specific configuration ##
###################################
## The catkin_package macro generates cmake config files for your package
## Declare things to be passed to dependent projects
## INCLUDE_DIRS: uncomment this if your package contains header files
## LIBRARIES: libraries you create in this project that dependent projects also need
## CATKIN_DEPENDS: catkin_packages dependent projects also need
## DEPENDS: system dependencies of this project that dependent projects also need
catkin_package(
# INCLUDE_DIRS include
# LIBRARIES my_subscriber_pkg
CATKIN_DEPENDS rospy message_runtime
# DEPENDS system_lib
)
###########
## Build ##
###########
## Specify additional locations of header files
## Your package locations should be listed before other locations
include_directories(
# include
${catkin_INCLUDE_DIRS}
)
## Declare a C++ library
# add_library(${PROJECT_NAME}
# src/${PROJECT_NAME}/my_subscriber_pkg.cpp
# )
## Add cmake target dependencies of the library
## as an example, code may need to be generated before libraries
## either from message generation or dynamic reconfigure
# add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
## Declare a C++ executable
## With catkin_make all packages are built within a single CMake context
## The recommended prefix ensures that target names across packages don't collide
# add_executable(${PROJECT_NAME}_node src/my_subscriber_pkg_node.cpp)
## Rename C++ executable without prefix
## The above recommended prefix causes long target names, the following renames the
## target back to the shorter version for ease of user use
## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node"
# set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "")
## Add cmake target dependencies of the executable
## same as for the library above
# add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
## Specify libraries to link a library or executable target against
# target_link_libraries(${PROJECT_NAME}_node
# ${catkin_LIBRARIES}
# )
#############
## Install ##
#############
# all install targets should use catkin DESTINATION variables
# See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html
## Mark executable scripts (Python etc.) for installation
## in contrast to setup.py, you can choose the destination
# catkin_install_python(PROGRAMS
# scripts/my_python_script
# DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
# )
## Mark executables for installation
## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_executables.html
# install(TARGETS ${PROJECT_NAME}_node
# RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
# )
## Mark libraries for installation
## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_libraries.html
# install(TARGETS ${PROJECT_NAME}
# ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
# LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
# RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION}
# )
## Mark cpp header files for installation
# install(DIRECTORY include/${PROJECT_NAME}/
# DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
# FILES_MATCHING PATTERN "*.h"
# PATTERN ".svn" EXCLUDE
# )
## Mark other files for installation (e.g. launch and bag files, etc.)
# install(FILES
# # myfile1
# # myfile2
# DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
# )
#############
## Testing ##
#############
## Add gtest based cpp test target and link libraries
# catkin_add_gtest(${PROJECT_NAME}-test test/test_my_subscriber_pkg.cpp)
# if(TARGET ${PROJECT_NAME}-test)
# target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
# endif()
## Add folders to be run by python nosetests
# catkin_add_nosetests(test)
<?xml version="1.0"?>
<package format="2">
<name>my_subscriber_pkg</name>
<version>0.0.0</version>
<description>The my_subscriber_pkg package</description>
<!-- One maintainer tag required, multiple allowed, one person per tag -->
<!-- Example: -->
<!-- <maintainer email="jane.doe@example.com">Jane Doe</maintainer> -->
<maintainer email="user@todo.todo">user</maintainer>
<!-- One license tag required, multiple allowed, one license per tag -->
<!-- Commonly used license strings: -->
<!-- BSD, MIT, Boost Software License, GPLv2, GPLv3, LGPLv2.1, LGPLv3 -->
<license>TODO</license>
<!-- <doc_depend>doxygen</doc_depend> -->
<buildtool_depend>catkin</buildtool_depend>
<build_depend>rospy</build_depend>
<build_depend>std_msgs</build_depend>
<build_depend>message_generation</build_depend>
<build_export_depend>rospy</build_export_depend>
<exec_depend>rospy</exec_depend>
<build_export_depend>std_msgs</build_export_depend>
<exec_depend>std_msgs</exec_depend>
<build_export_depend>message_runtime</build_export_depend>
<exec_depend>message_runtime</exec_depend>
<!-- The export tag contains other, unspecified, tags -->
<export>
<!-- Other tools can request additional information be placed here -->
</export>
</package>
Hi,
unfortunately I didn’t find anything strange, I don’t know why it doesn’t work…
maybe you can check if you package ‘my_subscriber_pkg’ is located correctly, a.k.a check it is really located in /home/user/catkin_ws/src, sometimes someone will wrongly create package outside /src.
And I am not sure if this is important, but I’ve never seen a filename like this:
exercise4.3_message.py
with a point within filename. Maybe you can try:
exercise43_message.py
instead.
thank you very much @MeineLiebeAxt for your help
I have checked if the file was created in the correct place, and I think it is correct.
user:~/catkin_ws$ source devel/setup.bash
user:~/catkin_ws$ roscd my_subscriber_pkg
user:~/catkin_ws/src/my_subscriber_pkg$
Now I’m going to try changing the filename.
I can rename the file or I must to create new and start again.
Hi @h.santander ,
Welcome to this Community!
I just read through this entire post. DO NOT CHANGE THE PACKAGE NAME ! You do not have to.
From my inspection of your files and code, they seem to be correct and just fine.
The problem here, what I suspect, is the command line that you are using to compile.
catkin_make usually gives problems like what you have at the moment. Sometimes it is unreliable, this is from my experience. You can notice this in your very first image: catkin_make actually did nothing!
The best way to avoid this is to compile with the following command modifications
cd ~/catkin_ws
catkin_make --only-pkg-with-deps my_subscriber_pkg
source devel/setup.bash
What the above code does is, it force compiles the specified package.
So if you want to compile more than one specific package, use the general line
catkin_make --only-pkg-with-deps <pkg1_name> <pkg2_name> <pkgN_name>
source devel/setup.bash
Let me know if this worked out for you!
Regards,
Girish
Thank you very much @girishkumar.kannan, yes, the problem was that catkin_make.
Could you tell me the link where I can read more about this problem?
I would like to know why this happens.
Harrison Smith.
Hi @h.santander ,
Glad to know that your problem is fixed!
I have no references to this problem. I accidentally found this out myself. Since then, I never wanted to know why this happens, and honestly did not put effort into knowing this.
Performing a quick Google search, I found this: catkin_make does not compile all packages in the workspace [closed] - ROS Answers: Open Source Q&A Forum
Basically, if your delete build and devel directories and do catkin_make the builds succeed. But if you already have prebuilt packages and try doing catkin_make then the general command fails to build all packages. So that is the reason I use the catkin_make --only-pkg-with-deps <pkg_name> usually.
Regards,
Girish