diff --git a/.doctrees/environment.pickle b/.doctrees/environment.pickle index 2a69d2ca..43486870 100644 Binary files a/.doctrees/environment.pickle and b/.doctrees/environment.pickle differ diff --git a/.doctrees/index.doctree b/.doctrees/index.doctree index 88d538ba..28939f52 100644 Binary files a/.doctrees/index.doctree and b/.doctrees/index.doctree differ diff --git a/.doctrees/markdown/archives/previous_tasks.doctree b/.doctrees/markdown/archives/previous_tasks.doctree index 05a9caec..b6cf8441 100644 Binary files a/.doctrees/markdown/archives/previous_tasks.doctree and b/.doctrees/markdown/archives/previous_tasks.doctree differ diff --git a/.doctrees/markdown/archives/sel-task2021/hints.doctree b/.doctrees/markdown/archives/sel-task2021/hints.doctree deleted file mode 100644 index b97682da..00000000 Binary files a/.doctrees/markdown/archives/sel-task2021/hints.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2021/problem-statement.doctree b/.doctrees/markdown/archives/sel-task2021/problem-statement.doctree deleted file mode 100644 index 4f05cbe0..00000000 Binary files a/.doctrees/markdown/archives/sel-task2021/problem-statement.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2021/procedure.doctree b/.doctrees/markdown/archives/sel-task2021/procedure.doctree deleted file mode 100644 index deeefe50..00000000 Binary files a/.doctrees/markdown/archives/sel-task2021/procedure.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2021/selection-task.doctree b/.doctrees/markdown/archives/sel-task2021/selection-task.doctree index b7efbc13..e477b184 100644 Binary files a/.doctrees/markdown/archives/sel-task2021/selection-task.doctree and b/.doctrees/markdown/archives/sel-task2021/selection-task.doctree differ diff --git a/.doctrees/markdown/archives/sel-task2021/submissions.doctree b/.doctrees/markdown/archives/sel-task2021/submissions.doctree deleted file mode 100644 index cb3ff4e3..00000000 Binary files a/.doctrees/markdown/archives/sel-task2021/submissions.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2022/hints.doctree b/.doctrees/markdown/archives/sel-task2022/hints.doctree deleted file mode 100644 index ab84c233..00000000 Binary files a/.doctrees/markdown/archives/sel-task2022/hints.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2022/problem-statement.doctree b/.doctrees/markdown/archives/sel-task2022/problem-statement.doctree deleted file mode 100644 index cfef0042..00000000 Binary files a/.doctrees/markdown/archives/sel-task2022/problem-statement.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2022/procedure.doctree b/.doctrees/markdown/archives/sel-task2022/procedure.doctree deleted file mode 100644 index 8d524073..00000000 Binary files a/.doctrees/markdown/archives/sel-task2022/procedure.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task2022/selection-task.doctree b/.doctrees/markdown/archives/sel-task2022/selection-task.doctree index a3911a05..ad0f270f 100644 Binary files a/.doctrees/markdown/archives/sel-task2022/selection-task.doctree and b/.doctrees/markdown/archives/sel-task2022/selection-task.doctree differ diff --git a/.doctrees/markdown/archives/sel-task2022/submissions.doctree b/.doctrees/markdown/archives/sel-task2022/submissions.doctree deleted file mode 100644 index b170014a..00000000 Binary files a/.doctrees/markdown/archives/sel-task2022/submissions.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task_cad_2022/cad_sel.doctree b/.doctrees/markdown/archives/sel-task_cad_2022/cad_sel.doctree index a530ac37..d43eb57a 100644 Binary files a/.doctrees/markdown/archives/sel-task_cad_2022/cad_sel.doctree and b/.doctrees/markdown/archives/sel-task_cad_2022/cad_sel.doctree differ diff --git a/.doctrees/markdown/archives/sel-task_cad_2022/cad_task1.doctree b/.doctrees/markdown/archives/sel-task_cad_2022/cad_task1.doctree deleted file mode 100644 index 8869ad3e..00000000 Binary files a/.doctrees/markdown/archives/sel-task_cad_2022/cad_task1.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task_cad_2022/cad_task2.doctree b/.doctrees/markdown/archives/sel-task_cad_2022/cad_task2.doctree deleted file mode 100644 index 11d18c9e..00000000 Binary files a/.doctrees/markdown/archives/sel-task_cad_2022/cad_task2.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-task_cad_2022/selection-task.doctree b/.doctrees/markdown/archives/sel-task_cad_2022/selection-task.doctree index d3427594..31c5e450 100644 Binary files a/.doctrees/markdown/archives/sel-task_cad_2022/selection-task.doctree and b/.doctrees/markdown/archives/sel-task_cad_2022/selection-task.doctree differ diff --git a/.doctrees/markdown/archives/sel-task_cad_2022/submissions.doctree b/.doctrees/markdown/archives/sel-task_cad_2022/submissions.doctree deleted file mode 100644 index d2c053ab..00000000 Binary files a/.doctrees/markdown/archives/sel-task_cad_2022/submissions.doctree and /dev/null differ diff --git a/.doctrees/markdown/archives/sel-tasks2023/CAD_Selection_Task.doctree b/.doctrees/markdown/archives/sel-tasks2023/CAD_Selection_Task.doctree index f0707bcb..3a8e0c55 100644 Binary files a/.doctrees/markdown/archives/sel-tasks2023/CAD_Selection_Task.doctree and b/.doctrees/markdown/archives/sel-tasks2023/CAD_Selection_Task.doctree differ diff --git a/.doctrees/markdown/archives/sel-tasks2023/CV_Selection_Task.doctree b/.doctrees/markdown/archives/sel-tasks2023/CV_Selection_Task.doctree index dde204ec..84cef499 100644 Binary files a/.doctrees/markdown/archives/sel-tasks2023/CV_Selection_Task.doctree and b/.doctrees/markdown/archives/sel-tasks2023/CV_Selection_Task.doctree differ diff --git a/.doctrees/markdown/archives/sel-tasks2023/Elec_Selection_Task.doctree b/.doctrees/markdown/archives/sel-tasks2023/Elec_Selection_Task.doctree index f751e66a..76852098 100644 Binary files a/.doctrees/markdown/archives/sel-tasks2023/Elec_Selection_Task.doctree and b/.doctrees/markdown/archives/sel-tasks2023/Elec_Selection_Task.doctree differ diff --git a/.doctrees/markdown/archives/sel-tasks2023/ROS_Selection_Task.doctree b/.doctrees/markdown/archives/sel-tasks2023/ROS_Selection_Task.doctree index 6a224bb4..e0733fc2 100644 Binary files a/.doctrees/markdown/archives/sel-tasks2023/ROS_Selection_Task.doctree and b/.doctrees/markdown/archives/sel-tasks2023/ROS_Selection_Task.doctree differ diff --git a/.doctrees/markdown/archives/sel-tasks2023/Selection_Tasks.doctree b/.doctrees/markdown/archives/sel-tasks2023/Selection_Tasks.doctree index 0e7dd9b0..83febf23 100644 Binary files a/.doctrees/markdown/archives/sel-tasks2023/Selection_Tasks.doctree and b/.doctrees/markdown/archives/sel-tasks2023/Selection_Tasks.doctree differ diff --git a/.doctrees/markdown/archives/sel-tasks2023/Task_Submission.doctree b/.doctrees/markdown/archives/sel-tasks2023/Task_Submission.doctree deleted file mode 100644 index ca18ed9b..00000000 Binary files a/.doctrees/markdown/archives/sel-tasks2023/Task_Submission.doctree and /dev/null differ diff --git a/.doctrees/markdown/general/access-repo.doctree b/.doctrees/markdown/general/access-repo.doctree index 83054d1b..5c19dac7 100644 Binary files a/.doctrees/markdown/general/access-repo.doctree and b/.doctrees/markdown/general/access-repo.doctree differ diff --git a/.doctrees/markdown/general/edit-wiki.doctree b/.doctrees/markdown/general/edit-wiki.doctree deleted file mode 100644 index a39620e4..00000000 Binary files a/.doctrees/markdown/general/edit-wiki.doctree and /dev/null differ diff --git a/.doctrees/markdown/general/main-site.doctree b/.doctrees/markdown/general/main-site.doctree deleted file mode 100644 index 3b3123cb..00000000 Binary files a/.doctrees/markdown/general/main-site.doctree and /dev/null differ diff --git a/.doctrees/markdown/projects/mr-robot/major-code/arduino.doctree b/.doctrees/markdown/projects/mr-robot/major-code/arduino.doctree index a815d4a8..43d39f21 100644 Binary files a/.doctrees/markdown/projects/mr-robot/major-code/arduino.doctree and b/.doctrees/markdown/projects/mr-robot/major-code/arduino.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/major-code/code.doctree b/.doctrees/markdown/projects/mr-robot/major-code/code.doctree index f1e29458..8a38434b 100644 Binary files a/.doctrees/markdown/projects/mr-robot/major-code/code.doctree and b/.doctrees/markdown/projects/mr-robot/major-code/code.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/major-code/esp_diff_tf.doctree b/.doctrees/markdown/projects/mr-robot/major-code/esp_diff_tf.doctree index d8c18840..473f472a 100644 Binary files a/.doctrees/markdown/projects/mr-robot/major-code/esp_diff_tf.doctree and b/.doctrees/markdown/projects/mr-robot/major-code/esp_diff_tf.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/major-code/twist_to_pwm.doctree b/.doctrees/markdown/projects/mr-robot/major-code/twist_to_pwm.doctree index a4ccbf9c..70c99931 100644 Binary files a/.doctrees/markdown/projects/mr-robot/major-code/twist_to_pwm.doctree and b/.doctrees/markdown/projects/mr-robot/major-code/twist_to_pwm.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/miscellaneous/miss.doctree b/.doctrees/markdown/projects/mr-robot/miscellaneous/miss.doctree index dd41a479..e2a7fb1f 100644 Binary files a/.doctrees/markdown/projects/mr-robot/miscellaneous/miss.doctree and b/.doctrees/markdown/projects/mr-robot/miscellaneous/miss.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/mr-index.doctree b/.doctrees/markdown/projects/mr-robot/mr-index.doctree index a0d75fa6..90bb0608 100644 Binary files a/.doctrees/markdown/projects/mr-robot/mr-index.doctree and b/.doctrees/markdown/projects/mr-robot/mr-index.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/script-use/bash.doctree b/.doctrees/markdown/projects/mr-robot/script-use/bash.doctree index 58694684..686d6339 100644 Binary files a/.doctrees/markdown/projects/mr-robot/script-use/bash.doctree and b/.doctrees/markdown/projects/mr-robot/script-use/bash.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/script-use/basic.doctree b/.doctrees/markdown/projects/mr-robot/script-use/basic.doctree index 9b845c92..4e605996 100644 Binary files a/.doctrees/markdown/projects/mr-robot/script-use/basic.doctree and b/.doctrees/markdown/projects/mr-robot/script-use/basic.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/script-use/launch.doctree b/.doctrees/markdown/projects/mr-robot/script-use/launch.doctree index 66d0397f..a81d7a3c 100644 Binary files a/.doctrees/markdown/projects/mr-robot/script-use/launch.doctree and b/.doctrees/markdown/projects/mr-robot/script-use/launch.doctree differ diff --git a/.doctrees/markdown/projects/mr-robot/script-use/working.doctree b/.doctrees/markdown/projects/mr-robot/script-use/working.doctree index 080b12dc..b09786e3 100644 Binary files a/.doctrees/markdown/projects/mr-robot/script-use/working.doctree and b/.doctrees/markdown/projects/mr-robot/script-use/working.doctree differ diff --git a/.doctrees/markdown/projects/projects.doctree b/.doctrees/markdown/projects/projects.doctree index ca9387ac..42fc2244 100644 Binary files a/.doctrees/markdown/projects/projects.doctree and b/.doctrees/markdown/projects/projects.doctree differ diff --git a/.doctrees/markdown/ros/ROS_installation/ROS_index.doctree b/.doctrees/markdown/ros/ROS_installation/ROS_index.doctree index e240d641..316ec3bf 100644 Binary files a/.doctrees/markdown/ros/ROS_installation/ROS_index.doctree and b/.doctrees/markdown/ros/ROS_installation/ROS_index.doctree differ diff --git a/.doctrees/markdown/ros/ROS_installation/installation.doctree b/.doctrees/markdown/ros/ROS_installation/installation.doctree index be599cd8..80d0eccc 100644 Binary files a/.doctrees/markdown/ros/ROS_installation/installation.doctree and b/.doctrees/markdown/ros/ROS_installation/installation.doctree differ diff --git a/.doctrees/markdown/ros/ROS_installation/installation_on_mac.doctree b/.doctrees/markdown/ros/ROS_installation/installation_on_mac.doctree index 1da7b7bb..615cb65c 100644 Binary files a/.doctrees/markdown/ros/ROS_installation/installation_on_mac.doctree and b/.doctrees/markdown/ros/ROS_installation/installation_on_mac.doctree differ diff --git a/.doctrees/markdown/ros/catkin_ws.doctree b/.doctrees/markdown/ros/catkin_ws.doctree index a7c187fe..8083b8bf 100644 Binary files a/.doctrees/markdown/ros/catkin_ws.doctree and b/.doctrees/markdown/ros/catkin_ws.doctree differ diff --git a/.doctrees/markdown/ros/comm/comm.doctree b/.doctrees/markdown/ros/comm/comm.doctree index 79933d46..bb371320 100644 Binary files a/.doctrees/markdown/ros/comm/comm.doctree and b/.doctrees/markdown/ros/comm/comm.doctree differ diff --git a/.doctrees/markdown/ros/comm/topics/rostopic.doctree b/.doctrees/markdown/ros/comm/topics/rostopic.doctree index c593c09f..73113110 100644 Binary files a/.doctrees/markdown/ros/comm/topics/rostopic.doctree and b/.doctrees/markdown/ros/comm/topics/rostopic.doctree differ diff --git a/.doctrees/markdown/ros/comm/topics/topics.doctree b/.doctrees/markdown/ros/comm/topics/topics.doctree index c1162cc9..cc0ce61a 100644 Binary files a/.doctrees/markdown/ros/comm/topics/topics.doctree and b/.doctrees/markdown/ros/comm/topics/topics.doctree differ diff --git a/.doctrees/markdown/ros/examples/eg1.doctree b/.doctrees/markdown/ros/examples/eg1.doctree deleted file mode 100644 index 0664dcc0..00000000 Binary files a/.doctrees/markdown/ros/examples/eg1.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/examples/example.doctree b/.doctrees/markdown/ros/examples/example.doctree index 10617044..2b27ac21 100644 Binary files a/.doctrees/markdown/ros/examples/example.doctree and b/.doctrees/markdown/ros/examples/example.doctree differ diff --git a/.doctrees/markdown/ros/launch/create.doctree b/.doctrees/markdown/ros/launch/create.doctree deleted file mode 100644 index f6d62235..00000000 Binary files a/.doctrees/markdown/ros/launch/create.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/launch/eg1.doctree b/.doctrees/markdown/ros/launch/eg1.doctree deleted file mode 100644 index f80d3a02..00000000 Binary files a/.doctrees/markdown/ros/launch/eg1.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/launch/eg2.doctree b/.doctrees/markdown/ros/launch/eg2.doctree deleted file mode 100644 index e1e7a5e9..00000000 Binary files a/.doctrees/markdown/ros/launch/eg2.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/launch/eg3.doctree b/.doctrees/markdown/ros/launch/eg3.doctree deleted file mode 100644 index cd1dbd7d..00000000 Binary files a/.doctrees/markdown/ros/launch/eg3.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/launch/launch.doctree b/.doctrees/markdown/ros/launch/launch.doctree index a84a3b9d..33207c21 100644 Binary files a/.doctrees/markdown/ros/launch/launch.doctree and b/.doctrees/markdown/ros/launch/launch.doctree differ diff --git a/.doctrees/markdown/ros/master/master.doctree b/.doctrees/markdown/ros/master/master.doctree index f0ea7966..b1d89dd0 100644 Binary files a/.doctrees/markdown/ros/master/master.doctree and b/.doctrees/markdown/ros/master/master.doctree differ diff --git a/.doctrees/markdown/ros/master/param-server.doctree b/.doctrees/markdown/ros/master/param-server.doctree deleted file mode 100644 index 032982c2..00000000 Binary files a/.doctrees/markdown/ros/master/param-server.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/node/create.doctree b/.doctrees/markdown/ros/node/create.doctree deleted file mode 100644 index ec5898ee..00000000 Binary files a/.doctrees/markdown/ros/node/create.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/node/node.doctree b/.doctrees/markdown/ros/node/node.doctree index d81a3960..74f82dc5 100644 Binary files a/.doctrees/markdown/ros/node/node.doctree and b/.doctrees/markdown/ros/node/node.doctree differ diff --git a/.doctrees/markdown/ros/node/rosnode.doctree b/.doctrees/markdown/ros/node/rosnode.doctree deleted file mode 100644 index 279133d1..00000000 Binary files a/.doctrees/markdown/ros/node/rosnode.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/node/rosrun.doctree b/.doctrees/markdown/ros/node/rosrun.doctree deleted file mode 100644 index d3cf3e62..00000000 Binary files a/.doctrees/markdown/ros/node/rosrun.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/package/create.doctree b/.doctrees/markdown/ros/package/create.doctree deleted file mode 100644 index e10c91d4..00000000 Binary files a/.doctrees/markdown/ros/package/create.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/package/package.doctree b/.doctrees/markdown/ros/package/package.doctree index 964bf198..4a2a6522 100644 Binary files a/.doctrees/markdown/ros/package/package.doctree and b/.doctrees/markdown/ros/package/package.doctree differ diff --git a/.doctrees/markdown/ros/ros-package.doctree b/.doctrees/markdown/ros/ros-package.doctree deleted file mode 100644 index 2d3208d7..00000000 Binary files a/.doctrees/markdown/ros/ros-package.doctree and /dev/null differ diff --git a/.doctrees/markdown/ros/ros.doctree b/.doctrees/markdown/ros/ros.doctree index d5a5ee2e..9520d7e8 100644 Binary files a/.doctrees/markdown/ros/ros.doctree and b/.doctrees/markdown/ros/ros.doctree differ diff --git a/.doctrees/markdown/selectiontask24/Electronics_selection.doctree b/.doctrees/markdown/selectiontask24/Electronics_selection.doctree index 20617bb8..2a0c08f3 100644 Binary files a/.doctrees/markdown/selectiontask24/Electronics_selection.doctree and b/.doctrees/markdown/selectiontask24/Electronics_selection.doctree differ diff --git a/.doctrees/markdown/selectiontask24/ROS_selection_task24.doctree b/.doctrees/markdown/selectiontask24/ROS_selection_task24.doctree index 4b00486b..0499a997 100644 Binary files a/.doctrees/markdown/selectiontask24/ROS_selection_task24.doctree and b/.doctrees/markdown/selectiontask24/ROS_selection_task24.doctree differ diff --git a/.doctrees/markdown/selectiontask24/cad_sel.doctree b/.doctrees/markdown/selectiontask24/cad_sel.doctree index 79ef610c..1cb6747a 100644 Binary files a/.doctrees/markdown/selectiontask24/cad_sel.doctree and b/.doctrees/markdown/selectiontask24/cad_sel.doctree differ diff --git a/.doctrees/markdown/selectiontask24/selection_task24.doctree b/.doctrees/markdown/selectiontask24/selection_task24.doctree index e20ecce6..c8d935b5 100644 Binary files a/.doctrees/markdown/selectiontask24/selection_task24.doctree and b/.doctrees/markdown/selectiontask24/selection_task24.doctree differ diff --git a/.doctrees/markdown/selectiontask24/submissions.doctree b/.doctrees/markdown/selectiontask24/submissions.doctree index 445302bc..631e511e 100644 Binary files a/.doctrees/markdown/selectiontask24/submissions.doctree and b/.doctrees/markdown/selectiontask24/submissions.doctree differ diff --git a/.doctrees/markdown/tool_setup/px4.doctree b/.doctrees/markdown/tool_setup/px4.doctree index 7a02256d..bbd066ab 100644 Binary files a/.doctrees/markdown/tool_setup/px4.doctree and b/.doctrees/markdown/tool_setup/px4.doctree differ diff --git a/.doctrees/markdown/tool_setup/ros-pi.doctree b/.doctrees/markdown/tool_setup/ros-pi.doctree index fdf99d22..be0569ea 100644 Binary files a/.doctrees/markdown/tool_setup/ros-pi.doctree and b/.doctrees/markdown/tool_setup/ros-pi.doctree differ diff --git a/.doctrees/markdown/tool_setup/tool_setup.doctree b/.doctrees/markdown/tool_setup/tool_setup.doctree index 3813ed09..1110acd2 100644 Binary files a/.doctrees/markdown/tool_setup/tool_setup.doctree and b/.doctrees/markdown/tool_setup/tool_setup.doctree differ diff --git a/.doctrees/markdown/tool_setup/virtualenv.doctree b/.doctrees/markdown/tool_setup/virtualenv.doctree index 520ed307..a6b82120 100644 Binary files a/.doctrees/markdown/tool_setup/virtualenv.doctree and b/.doctrees/markdown/tool_setup/virtualenv.doctree differ diff --git a/_sources/markdown/archives/sel-task2021/hints.rst.txt b/_sources/markdown/archives/sel-task2021/hints.rst.txt deleted file mode 100644 index 5bee48ab..00000000 --- a/_sources/markdown/archives/sel-task2021/hints.rst.txt +++ /dev/null @@ -1,13 +0,0 @@ -Hints -===== - -- The turtle needs to move in a circular motion with a certain radius. - This radius should be sufficient to fit within the turtlesim window. - But making it rotate in a circular manner, with only velocities to - control is something to think about. - -- Use linear velocity as well as angular velocity with some combination - to get this done. - -- Keep tracking the distance travelled so as to know when to stop. You - can refer to Overview of rospy for more hint diff --git a/_sources/markdown/archives/sel-task2021/problem-statement.rst.txt b/_sources/markdown/archives/sel-task2021/problem-statement.rst.txt deleted file mode 100644 index 685c362b..00000000 --- a/_sources/markdown/archives/sel-task2021/problem-statement.rst.txt +++ /dev/null @@ -1,33 +0,0 @@ -Problem statement -================= - -- The objective of the task is to move the turtle inside the turtlesim - window in a circle and stop at its initial location. - -- To acheive this task you are supposed to create a node named   - /node_turtle_revolve   within a python script, -  node_turtle_revolve.py   - -.. Note:: Dont worry if you are new to ROS or Linux(Ubuntu), the task - is fairly simple and we have provided you with ample resource and - tutorials in this WIKI to the complete this task so only a strong - will and a little bit of brains is required to get the work done. - Also even though this just a weekend task we have provided ample - amount of time as we also have our midterm exams during this time. So - we think a week time is enough so you guys can give your exams freely - and manage your time in order to complete the task - -Once you have read the problem statement please visit the -`Procedure `__ page to get started with the -task. - -Expected Output -=============== - -.. raw:: html - - diff --git a/_sources/markdown/archives/sel-task2021/procedure.rst.txt b/_sources/markdown/archives/sel-task2021/procedure.rst.txt deleted file mode 100644 index 35937617..00000000 --- a/_sources/markdown/archives/sel-task2021/procedure.rst.txt +++ /dev/null @@ -1,39 +0,0 @@ -Procedure -========= - -Follow the instructions given below to get started with the task. - -- First, you will need to create a package named selection_task within - your ROS workspace. Once your package is created, source and build - your workspace. -- Within this package, you should have a ‘scripts’ folder inside which - you’ll create a python script, named node_turtle_revolve.py. -- Fill the script with proper programming ethics. Doing this will help - us understand your code better and quicker than usual. -- After completing the python script. Make it executable, if it isn’t - already. To do that, enter the following code. - -.. code:: shell - - cd ~/catkin_ws - catkin_make - source devel/setup.bash - chmod +x ~/catkin_ws/src/selection_task/scripts/node_turtle_revolve.py - -- Before executing make sure that roscore is running along with - turtlesim_node. You can either run them in separate terminals or - simply create a selection_task.launch file inside the - ``~/catkin_ws/src/selection_task/launch/`` folder. Launch file can - run multiple nodes unlike a python/cpp script. Run the launch file, - enter, This should run three processes in parallel. - -- roscore - -- turtlesim_node - -- node_turtle_revolve.py - -.. seealso:: - Please refer to the tutorials and resouces given in the wiki or visit - the official `ROSWIKI `__ if you - need help with anything regarding ROS. diff --git a/_sources/markdown/archives/sel-task2021/submissions.rst.txt b/_sources/markdown/archives/sel-task2021/submissions.rst.txt deleted file mode 100644 index 294c3885..00000000 --- a/_sources/markdown/archives/sel-task2021/submissions.rst.txt +++ /dev/null @@ -1,36 +0,0 @@ -Submissions -=========== - -For Submissions of your work please refer to the following instructions - -- Video - - - After completing the task, record a video of your work as shown in - the expected output in the problem statement page - - Once the video is recorded, upload the video to Youtube as an - unlisted video - -- Code - - - Once your script is complete, add comments to your code to make it - more readable. - - Create a copy of your script and rename it as task\_.py . Your - example if your name is ‘Alex’, then rename your script as - task_alex.py - -- Submissions - - - Once your have both of the above things ready, submit the YouTube - link of the video and the script in the google form given below - -- Interview - - - Once we review your submission, we will be calling you for a - personal interview based on your work. - -`Google Form for Task -submission `__ - -.. Note:: Even if you are not able to complete entire the task you - are requested to make the submission of the work that you have done - anyway. diff --git a/_sources/markdown/archives/sel-task2022/hints.rst.txt b/_sources/markdown/archives/sel-task2022/hints.rst.txt deleted file mode 100644 index 5d03d238..00000000 --- a/_sources/markdown/archives/sel-task2022/hints.rst.txt +++ /dev/null @@ -1,14 +0,0 @@ -Hints -===== - -- The turtle needs to move in a inward or outward spiral motion with a - certain increasing or decreasing radius. This radius should be - sufficient to fit within the turtlesim window. But making it rotate - in a circular manner, with only velocities to control is something to - think about. - -- Use linear velocity as well as angular velocity with some combination - to get this done. - -- Keep track of the number of circles completed so as to know when to - stop. You can refer to Overview of rospy for more hint diff --git a/_sources/markdown/archives/sel-task2022/problem-statement.rst.txt b/_sources/markdown/archives/sel-task2022/problem-statement.rst.txt deleted file mode 100644 index b6f4d06d..00000000 --- a/_sources/markdown/archives/sel-task2022/problem-statement.rst.txt +++ /dev/null @@ -1,35 +0,0 @@ -Problem Statement -================= - -- The objective of the task is to move the turtle inside the turtlesim - window in a inward or outward spiral motion and to stop it after 4 - turns in order to create a spiral as given in the expected output. - -- To acheive this task you are supposed to create a node named   - /node_turtle_spiral   within a python script,  node_turtle_spiral.py -   - -.. Note:: Dont worry if you are new to ROS or Linux(Ubuntu), the task - is fairly simple and we have provided you with ample resource and - tutorials in this WIKI to the complete this task so only a strong - will and a little bit of brains is required to get the work done. - Also even though this just a weekend task we have provided ample - amount of time as some of you have your end-term exams(onile though). - So we think two weeks time is enough so you guys can study for your - exams freely and manage your time in order to complete the task. - -Once you have read the problem statement please visit the -`Procedure <./procedure.md>`__ page to get started with the task. - -Expected Output -=============== - -`output video `__ - -.. raw:: html - - diff --git a/_sources/markdown/archives/sel-task2022/procedure.rst.txt b/_sources/markdown/archives/sel-task2022/procedure.rst.txt deleted file mode 100644 index 6f3906c3..00000000 --- a/_sources/markdown/archives/sel-task2022/procedure.rst.txt +++ /dev/null @@ -1,38 +0,0 @@ -Procedure -========= - -Follow the instructions given below to get started with the task. - -- First, you will need to create a package named selection_task within - your ROS workspace. Once your package is created, source and build - your workspace. -- Within this package, you should have a scripts folder inside which - you’ll create a python script, named node_turtle_spiral.py. -- Fill the script with proper programming ethics. Doing this will help - us understand your code better and quicker than usual. -- After completing the python script. Make it executable, if it isn’t - already. To do that, enter the following code. - -.. code:: shell - - cd ~/catkin_ws - catkin make - source devel/setup.bash - chmod +x ~/catkin_ws/src/selection_task/scripts/node_turtle_spiral.py - -- Before executing make sure that roscore is running along with - turtlesim_node. You can either run them in separate terminals or - simply create a selection_task.launch file inside the - ``~/catkin_ws/src/selection_task/launch/`` folder. Launch file can - run multiple nodes unlike a python/cpp script. Run the launch file, - enter, This should run three processes in parallel. - -- roscore - -- turtlesim_node - -- node_turtle_spiral.py - -.. seealso:: Please refer to the tutorials and resouces given in the wiki or visit - the official `ROSWIKI `__ if you - need help with anything regarding ROS. diff --git a/_sources/markdown/archives/sel-task2022/submissions.rst.txt b/_sources/markdown/archives/sel-task2022/submissions.rst.txt deleted file mode 100644 index 4333b471..00000000 --- a/_sources/markdown/archives/sel-task2022/submissions.rst.txt +++ /dev/null @@ -1,36 +0,0 @@ -Submission Instruction -====================== - -For Submissions of your work please refer to the following instructions - -- Video - - - After completing the task, record a video of your work as shown in - the expected output in the problem statement page - - Once the video is recorded, upload the video to Youtube as an - unlisted video - -- Code - - - Once your script is complete, add comments to your code to make it - more readable. - - Create a copy of your script and rename it as task\_.py . Your - example if your name is ‘Alex’, then rename your script as - task_alex.py - -- Submissions - - - Once you have both of the above things ready, submit the YouTube - link of the video and the script in the google form given below - -- Interview - - - Once we review your submission, we will be calling you for a - personal interview based on your work. - -`Google Form for Task -submission `__ - -.. Note:: Even if you are not able to complete entire the task you - are requested to make the submission of the work that you have done - anyway. diff --git a/_sources/markdown/archives/sel-task_cad_2022/cad_sel.rst.txt b/_sources/markdown/archives/sel-task_cad_2022/cad_sel.rst.txt index 1e66071d..ddc678df 100644 --- a/_sources/markdown/archives/sel-task_cad_2022/cad_sel.rst.txt +++ b/_sources/markdown/archives/sel-task_cad_2022/cad_sel.rst.txt @@ -164,7 +164,7 @@ Task 2 .. Seealso:: Last date for submission is **27th of August** -.. _google-form-for-task-submission-1: +.. _google-form-for-task-submission: `Google Form for Task submission `__ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/_sources/markdown/archives/sel-task_cad_2022/cad_task1.rst.txt b/_sources/markdown/archives/sel-task_cad_2022/cad_task1.rst.txt deleted file mode 100644 index 84936578..00000000 --- a/_sources/markdown/archives/sel-task_cad_2022/cad_task1.rst.txt +++ /dev/null @@ -1,26 +0,0 @@ -Task 1 -====== - -- The objective of the task is to make a 3D model of a part using the - given engineering drawing. - -- To achieve this task you may use any method but the end result should - be as close as possible to the original drawing. - -- You will be judged on the basis of your way of designing, so keep - that in mind and make sure to follow proper practices(Like using - constraints appropriately). - -.. Note:: You may use any software that you are familiar with but you - are recommended to use **Fusion360**. - -Once you are done with the Task 1 please submit it by heading over to -`Submissions `__ - -.. Note:: Head to `Task 2 `__ once you are done with - task1. - -Expected Output -=============== -.. figure:: https://i.ibb.co/J3Crbpm/cad-task02-v1-v1.gif - :figclass: align-center \ No newline at end of file diff --git a/_sources/markdown/archives/sel-task_cad_2022/cad_task2.rst.txt b/_sources/markdown/archives/sel-task_cad_2022/cad_task2.rst.txt deleted file mode 100644 index 6baff123..00000000 --- a/_sources/markdown/archives/sel-task_cad_2022/cad_task2.rst.txt +++ /dev/null @@ -1,57 +0,0 @@ -Task 2 -====== - -.. raw:: html - -
- -.. raw:: html - -
- -- The objective of the task is to make a 3d design CAD design of a **5 - degree of freedom Robotic Arm** . - -- Details: - - - You are required to create a **5 degree of freedom** Robotic arm - with links and joints as specified in the image above. - - The image is just an example to show the placement of each axis. - You are free to choose the placement of actuators and joints and - use any design you can think of… - - The arm should have a robot workspace in the form of a semi circle - with radius approx 40-60 cm. - - You have to create the arm using **Tower Pro MG946R Metal Gear - Servo** as actuatos. - `Sample `__ - for a metal gear servo. - - The model should have proper mounts and spaces for servos and - other mechanical parts. You free to use any type mechanical - components like screws, bearings etc. - - All components in the arm should be connected with proper joints. - -- You will be judged on the basis of the following criteria: - - - Manufacturability of the links and mounts (Preferebly 3d - Printable) - - Adhering to the giving details and guidelines. - - Reusability and esay to modify in future if required. - - You may use any methods and tools to achieve the task buy make - sure to follow proper 3d modeling practices like constraints, - joints etc. - - - .. Note:: - To achieve the above task, you are free to use any software that - you are familiar with but you are recommended to use **Fusion360** - as you will have to switch over to fusion360 if you join the society. - - .. seealso:: - The last date to submit the task is **28 August, 2022**. **Note**: We - recommend you to manage your time properly and start with the task as - soon as possible as it could get a bit lengthy. Even if you are not - able to complete the whole task, we encourage you to still submit all - the work you are able to complete till the deadline as you sill might - have a chance to get selected based on your submission. - -Once you are done with the Task 2 please submit it by heading over to `Submissions `__ diff --git a/_sources/markdown/archives/sel-task_cad_2022/submissions.rst.txt b/_sources/markdown/archives/sel-task_cad_2022/submissions.rst.txt deleted file mode 100644 index b6cc8393..00000000 --- a/_sources/markdown/archives/sel-task_cad_2022/submissions.rst.txt +++ /dev/null @@ -1,75 +0,0 @@ -Submission Instructions -======================= - -For Submissions of your work please refer to the following instructions - -Task 1 ------- - -- Video - - - Once you are done with the modelling, you have to record a video - of your screen where show the model from different angles in the - software you used. Then you have to upload the video on YouTube - and share a link to the video in the submission form. - -- Model file - - - Once your Model is complete, export it as a stl file and rename it - as .stl. For example if your name is ‘Alex’, then rename your file - as Task1_Alex.stl - -Optional Submissions -^^^^^^^^^^^^^^^^^^^^ - -- Previous Works (Optional) - - - You are welcome to submit any of your previous work related to 3D - modeling. It is optional but, this would help us see your - creativity and skills. You have to add it to drive and share the - drive link in the submission form. **Make sure the link is public - and accessible by anyone.** - - - .. Seealso:: Last date for submission is **26th of August** - -`Google Form for Task submission `__ -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Task 2 ------- - -- Video - - - Once you are done with the modelling, you have to record a video - of your screen where show the model from different angles, move - all the joints and show it’s working in the software you used. - Then you have to upload the video on YouTube as unlisted and share - a link to the video in the submission form. - -- Model file - - - Once your Model is complete, upload the model files in a google - drive folder and share the link in the google form below. Make - sure to give viewing acess while creating the shareable link for - the google drive. - -.. Seealso:: Last date for submission is **27th of August** - -.. _google-form-for-task-submission-1: - -`Google Form for Task submission `__ -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Interview ---------- - -:: - - - Once we review your submission, we will be calling you for a personal interview based on your work. - - We would be asking about some general question related to computers and your thought process & stuff related to the task that you have performed. - - -.. Note:: Make sure you submit both of your task before the 27th of - August. Both the submissions have to be done separately. Even if you - are not able to complete entire the task you are requested to make - the submission of the work that you have done anyway. diff --git a/_sources/markdown/archives/sel-tasks2023/Selection_Tasks.rst.txt b/_sources/markdown/archives/sel-tasks2023/Selection_Tasks.rst.txt index 6ee7f0ff..e7893f6c 100644 --- a/_sources/markdown/archives/sel-tasks2023/Selection_Tasks.rst.txt +++ b/_sources/markdown/archives/sel-tasks2023/Selection_Tasks.rst.txt @@ -38,7 +38,7 @@ There are currently two types of selection tasks which are: CAD Selection Task <./CAD_Selection_Task.rst> `Task submission `__ -++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. Note:: Even if you are not able to complete entire the task you diff --git a/_sources/markdown/archives/sel-tasks2023/Task_Submission.rst.txt b/_sources/markdown/archives/sel-tasks2023/Task_Submission.rst.txt deleted file mode 100644 index 8b109bf2..00000000 --- a/_sources/markdown/archives/sel-tasks2023/Task_Submission.rst.txt +++ /dev/null @@ -1,50 +0,0 @@ -Task Submission -================ - -.. Warning:: - The **Deadline** for all the Tasks is: **11th December, 2022** Head to the - `Problem statement `__ section to begin with the tasks. - - -For Submissions of your work please refer to the following instructions - -- **Video** - - - After completing the task, record a video of your work as shown in - the expected output in the problem statement page - - Once the video is recorded, upload the video to Youtube as an - unlisted video - -- **File** - - - Once your script is complete, add comments to your code to make it - more readable. - - Create a copy of your script and rename it as . - For example if you worked on Computer vision task on a python file - and your name is 'Alex', then rename your script to cvtask_alex.py - -- **Submissions** - - - Once you have both of the above things ready, submit the YouTube - link of the video and the script in the google form given below - - Previous Works (Optional): - You are welcome to submit any of your previous work related to task. - It is optional but, this would help us see your skills. You have to - add it to drive and share the drive link in the submission form. - - .. Warning:: - **Make sure to make the links accessible to everyone before sharing it.** - -- **Interview** - - - Once we review your submission, we will be sending you a confirmation and - will callyou for a personal interview based on your work. - - Questions related to the task that you've performed will be asked. - -`Submit task here `__ -*********************************************************** - -.. Note:: - Even if you are not able to complete entire the task you - are requested to make submission of the work that you have done - anyway. diff --git a/_sources/markdown/general/edit-wiki.rst.txt b/_sources/markdown/general/edit-wiki.rst.txt deleted file mode 100644 index 0bdf3ff5..00000000 --- a/_sources/markdown/general/edit-wiki.rst.txt +++ /dev/null @@ -1,31 +0,0 @@ -Editing this wiki -================= - -Step 1 ------- - -- Fork the github repository by clicking on the fork button on the top - right - -Step 2 ------- - -- Clone your fork of the repository - -Step 3 ------- - -- Make changes, add and commit -- Install and `setup the mdbook - tool `__ -- Build and test if the mdbook is running - -Step 4 ------- - -- Push to your fork - -Step 5 ------- - -- Create a merge request to the main repository diff --git a/_sources/markdown/general/main-site.rst.txt b/_sources/markdown/general/main-site.rst.txt deleted file mode 100644 index 877b96ec..00000000 --- a/_sources/markdown/general/main-site.rst.txt +++ /dev/null @@ -1,23 +0,0 @@ -Editing the ATOM main site -========================== - -Step 1: -------- - -- Fork the repository - -Step 2: -------- - -- Install and `setup - hugo `__ - -Step 3: -------- - -- Make changes to the site - -Step 4: -------- - -- Create a PR to the main repo diff --git a/_sources/markdown/projects/mr-robot/major-code/arduino.rst.txt b/_sources/markdown/projects/mr-robot/major-code/arduino.rst.txt index ec0c5f30..6dd0a614 100644 --- a/_sources/markdown/projects/mr-robot/major-code/arduino.rst.txt +++ b/_sources/markdown/projects/mr-robot/major-code/arduino.rst.txt @@ -73,6 +73,7 @@ This code snippet is used to set up the various settings needed for the robot to - The ``attachInterrupt`` functions attach two interrupt service routines (``updateEncoder_L`` and ``updateEncoder_R``) to the encoder pins for the left and right wheels. These routines are called whenever the state of the encoder signals changes (i.e., when the wheel rotates). They are used to update the encoder counts and calculate the speed of the wheels. .. code:: C + void publish_encoder_data() { encoder_msg_left.data = encoderValue_L; diff --git a/_sources/markdown/ros/comm/topics/rostopic.rst.txt b/_sources/markdown/ros/comm/topics/rostopic.rst.txt index 021dea5d..66cb71c8 100644 --- a/_sources/markdown/ros/comm/topics/rostopic.rst.txt +++ b/_sources/markdown/ros/comm/topics/rostopic.rst.txt @@ -13,8 +13,8 @@ rostopic command for getting the rostopic command help. -- .. rubric:: list - :name: list +- .. rubric:: rostopic-list + :name: rostopic-list - rostopic list returns a list of all topics currently subscribed to and published. @@ -99,8 +99,8 @@ rosmsg - ``geometry_msgs/Vector3 angular`` : While this header describes, angular velocities of all 3 axes. -- .. rubric:: info - :name: info +- .. rubric:: rostopic-info + :name: rostopic-info - This command provides a little more detail about topics then type argument. diff --git a/_sources/markdown/ros/comm/topics/topics.rst.txt b/_sources/markdown/ros/comm/topics/topics.rst.txt index 983bd4fa..d86005a6 100644 --- a/_sources/markdown/ros/comm/topics/topics.rst.txt +++ b/_sources/markdown/ros/comm/topics/topics.rst.txt @@ -17,6 +17,7 @@ ROS Topics data of various data-types. *Consider this analogy* + ---------------------- - Let’s say you are subscribed to a newspaper called The Melodic diff --git a/_sources/markdown/ros/examples/eg1.rst.txt b/_sources/markdown/ros/examples/eg1.rst.txt deleted file mode 100644 index 37231346..00000000 --- a/_sources/markdown/ros/examples/eg1.rst.txt +++ /dev/null @@ -1,51 +0,0 @@ -Example #1: ROS Node to Get and Set Parameters -============================================== - -Aim ---- - -To write a ROS Node to read config_my.yaml file loaded in ROS Parameter -Server (done here), print it on the console and modify the phone number. - -Code ----- - -.. code:: python - - node_param_get_set.py - #!/usr/bin/env python - import rospy - def main(): - #1. Make the script a ROS Node. - rospy.init_node('node_param_get_set', anonymous=True) - # 2. Read from Parameter Server - rospy.loginfo("Reading from Parameter Server.") - param_config_my = rospy.get_param('details') - - # Get all the parameters inside 'details' - # Store the parameters in variables - - first_name = param_config_my['name']['first'] - last_name = param_config_my['name']['last'] - address = param_config_my['contact']['address'] - phone = param_config_my['contact']['phone'] - - # Print the parameters - - rospy.loginfo(">> First Name: {}".format(first_name)) - rospy.loginfo(">> Last Name: {}".format(last_name)) - rospy.loginfo(">> Address: {}".format(address)) - rospy.loginfo(">> Phone: {}".format(phone)) - - # 3. Modify the Phone Number - - rospy.set_param('/details/contact/phone', 55555) - new_phone = rospy.get_param('/details/contact/phone') - rospy.loginfo(">> New Phone: {}".format(new_phone)) - - # Modify only Phone Number in Parame - # Get only Phone Number from Paramet - # Print the new Phone Number - -- The code is self explainatory , please feel free to seek help if you - don’t understand it diff --git a/_sources/markdown/ros/launch/create.rst.txt b/_sources/markdown/ros/launch/create.rst.txt deleted file mode 100644 index 57f8da2f..00000000 --- a/_sources/markdown/ros/launch/create.rst.txt +++ /dev/null @@ -1,94 +0,0 @@ -Create a ROS Launch file -======================== - -roslaunch Command ------------------ - -- roslaunch is a tool for easily launching multiple ROS nodes locally - and remotely via SSH. - -- It includes options to automatically respawn processes that have - already died. roslaunch takes in one or more XML configuration files - (with the .launch extension) that specify the parameters to set and - nodes to launch. - -Usage: - -.. code:: shell - - roslaunch file.launch - -- is nothing but the package name which you have created using - catkin_create_pkg command or used any other package - -Steps to create a launch file ------------------------------ - -- After creating a package, create a folder in the package names as a - launch folder to store all the launch files in that folder. - -.. code:: shell - - cd ~/catkin_ws/src/ - mkdir launch - -- Here we can create launch files by running this command by going into - the launch directory, we can keep any name for the launch file - -.. code:: shell - - cd launch - touch filename.launch - -Now you can edit your launch file by adding different nodes that you have -to run simultaneously. - -Steps to add a ROS node in the launch file ------------------------------------------ - -- - - 1. Launch files always starts with - -```` and end with ```` - -- 2.Now to add any executable file which we have seen in the - rosrun_command section, we have to add this line - -.. code:: xml - - - -- name is the name of the node which is created in that executable -- output means it will print the data given to the roslog command -- type is the name of executable file -- pkg is the package name which you have created. - -Steps to load Config YAML file in ROS Parameter Server ----------------------------------------------------- - -You can use rosparam tag to load the YAML file. - -- type is the name of executable file - -- pkg is the package name which you have created - -- name_of_package is the name of your ROS package. - -- config.yaml is the name of your configuration file. - -Steps to add a shell script in the launch file ----------------------------------------------- - -You can use node tag to run any shell script using launch file - -.. code:: xml - - - - - -- name_of_package is the name of your ROS package. -- shell_script.sh is the name of your configuration file. -- /launch/shell_script.sh is the location of the shell script inside - your ROS Package folder. diff --git a/_sources/markdown/ros/launch/eg1.rst.txt b/_sources/markdown/ros/launch/eg1.rst.txt deleted file mode 100644 index 3cc6daec..00000000 --- a/_sources/markdown/ros/launch/eg1.rst.txt +++ /dev/null @@ -1,44 +0,0 @@ -Example 1: Launch two ROS Nodes -=============================== - -Aim ---- - -- To launch talker and listener node present in rospy_tutorials - package. - -- For this create a chatter.launch file and save it in the launch folder - inside pkg_ros_basics package. - -.. NOTE:: To install rospy_tutorials package in your system you can run -sudo apt-get install ros-noetic-ros-tutorials this command. - -- Once installed, you can use listener python script and talker - executable written in C++ present in rospy_tutorials package. - -Code ----- - -chatter.launch - -.. code:: xml - - - - - - -- Here first talker.cpp file (for cpp file we dont need to add .cpp - extension) has been included with the node name as talker and also - set output as screen so you can see the output from talker node. -- Next we have added listener.py which has node name as listener and - here also we have set output as screen. - -Run Command ------------ - -Now run these command to run the launch file, - -.. code:: shell - - roslaunch pkg_ros_basics chatter.launch diff --git a/_sources/markdown/ros/launch/eg2.rst.txt b/_sources/markdown/ros/launch/eg2.rst.txt deleted file mode 100644 index 7c857a64..00000000 --- a/_sources/markdown/ros/launch/eg2.rst.txt +++ /dev/null @@ -1,39 +0,0 @@ -Example 2: Launch turtle in forest -================================== - -Aim ---- - -- To write a launch file to run turtlesim_node node and - turtle_teleop_key node present in turtlesim package. -- While launching the turtlesim_node make sure to change the background - colour of the simulator from blue to forest green. -- Name the launch file turtlesim.launch and save it in launch folder - inside pkg_ros_basics package. - -Code ----- - -turtlesim.launch - -.. code:: xml - - - - - - - - - - - - ❱ - - -Run Command ------------ - -.. code:: shell - - roslaunch pkg_ros_basics turtlesim.launch diff --git a/_sources/markdown/ros/launch/eg3.rst.txt b/_sources/markdown/ros/launch/eg3.rst.txt deleted file mode 100644 index 11a57ba6..00000000 --- a/_sources/markdown/ros/launch/eg3.rst.txt +++ /dev/null @@ -1,29 +0,0 @@ -Example 3: Load YAML -==================== - -Aim ---- - -- To write a launch file to load config_my.yaml present in - pkg_ros_basics package. -- Also launch the node_param_get_set.py ROS node after loading the YAML - file. - -Code ----- - -load_yaml.launch - -.. code:: xml - - - - - - -Run Command ------------ - -.. code:: shell - - roslaunch pkg_ros_basics load_yaml.launch diff --git a/_sources/markdown/ros/launch/launch.rst.txt b/_sources/markdown/ros/launch/launch.rst.txt index ede15594..99313cbf 100644 --- a/_sources/markdown/ros/launch/launch.rst.txt +++ b/_sources/markdown/ros/launch/launch.rst.txt @@ -34,7 +34,7 @@ Usage: roslaunch file.launch - is nothing but the package name which you have created using - catkin_create_pkg command or used any other package + catkin_create_pkg command or used any other package Steps to create a launch file ----------------------------- diff --git a/_sources/markdown/ros/master/param-server.rst.txt b/_sources/markdown/ros/master/param-server.rst.txt deleted file mode 100644 index fe5ad0ad..00000000 --- a/_sources/markdown/ros/master/param-server.rst.txt +++ /dev/null @@ -1,9 +0,0 @@ -ROS Parameter Server -==================== - -- You can think Parameter Server as a space where all the necessary - data that needs to be shared among various ROS Nodes is stored. -- Parameter Server runs inside ROS Master. -- ROS Nodes can view and even modify data stored in the Parameter - Server. -- Typically Parameter Server is used to store configuration parameters. diff --git a/_sources/markdown/ros/node/create.rst.txt b/_sources/markdown/ros/node/create.rst.txt deleted file mode 100644 index c2935c07..00000000 --- a/_sources/markdown/ros/node/create.rst.txt +++ /dev/null @@ -1,89 +0,0 @@ -Creating a ROS Node -=================== - -- In this section we will learn how to create a ROS Node inside - pkg_ros_basics ROS Package which we created in the previous section. - -- Navigate to pkg_ros_basics - -.. code:: shell - - cd ~/catkin_ws/src/pkg_ros_basics - -OR - -.. code:: shell - - roscd pkg_ros_basics - -.. NOTE:: roscd will work only if you have sourced setup.bash of your -catkin workspace. - -- Create a scripts folder for your Python scripts and navigate into the - folder. - -.. code:: shell - - mkdir scripts - cd scripts - -- Create a Python script called node_hello_ros.py . - -.. code:: shell - - touch node_hello_ros.py - -- Open the script in any text-editor and start editing. - -.. code:: shell - - gedit node_hello_ros.py - -- First line of all your Python ROS scripts should be the following - shebang - -.. code:: shell - - #!/usr/bin/env python - -- Now write a ROS Node to print Hello World! on the console. - -.. code:: python - - #!/usr/bin/env python - import rospy - def main(): - #Initialize the new node - rospy.init_node('node_hello_ros', anonymous=True) - # Print info on console. - rospy.loginfo("Hello World!") - - if __name__ == '__main__': - - try: - main() - except rospy.ROSInterruptException: - pass - -- Make your node executable - -.. code:: shell - - sudo chmod +x node_hello_ros.py - -- Now to run your node - - - Open the terminal and run ROS master - - .. code:: shell - - roscore - - - Once the roscore is running open a new terminal and run the main - node - - .. code:: shell - - rosrun pkg_ros_basics node_hello_ros.py - - .. note:: This command will work only if you have sourced setup.bash of your catkin workspace either manually or using .bashrc . diff --git a/_sources/markdown/ros/node/node.rst.txt b/_sources/markdown/ros/node/node.rst.txt index 7007efd8..bb01dba3 100644 --- a/_sources/markdown/ros/node/node.rst.txt +++ b/_sources/markdown/ros/node/node.rst.txt @@ -36,6 +36,7 @@ OR roscd pkg_ros_basics .. NOTE:: roscd will work only if you have sourced setup.bash of your + catkin workspace. - Create a scripts folder for your Python scripts and navigate into the @@ -186,6 +187,7 @@ Command: rosnode information about ROS Nodes. .. Note:: For quick information about any command, be that outside of ROS, + simply type the command along with suffix –h or -help . This is a widely used concept among other Linux Command: rosrun commands for quick references. Here’s an example for rosnode –h command diff --git a/_sources/markdown/ros/node/rosnode.rst.txt b/_sources/markdown/ros/node/rosnode.rst.txt deleted file mode 100644 index 5a00f8a0..00000000 --- a/_sources/markdown/ros/node/rosnode.rst.txt +++ /dev/null @@ -1,88 +0,0 @@ -Command: rosnode -================ - -- rosnode contains the rosnode command-line tool for displaying debug - information about ROS Nodes. - -.. Note:: For quick information about any command, be that outside of ROS, -simply type the command along with suffix –h or -help . This is a widely -used concept among other Linux Command: rosrun commands for quick -references. Here’s an example for rosnode –h command - -- .. rubric:: list - :name: list - -rosnode list displays a list of all current nodes. - -Let’s figure out what argument the list sub-command needs. In a new -terminal run start the rosmaster: - -.. code:: shell - - roscore - -And in another terminal, run: - -.. code:: shell - - rosrun rospy_tutorials talker - -And in another terminal, run: - -.. code:: shell - - rosnode list - -Now the node named talker (node with word talker in it) will be printed -on the terminal. - -- .. rubric:: info - :name: info - -- rosnode info /node_name displays information about a node, including - publications and subscriptions. - -- Let’s figure out what argument the info sub-command needs. In a new - terminal run start the - -.. code:: shell - - rosmaster - -And in another terminal, run: - -.. code:: shell - - rosrun rospy_tutorials talker - -And in another terminal, run: - -.. code:: shell - - rosnode info - -This should give details of the particular node - -- .. rubric:: kill - :name: kill - -.. IMPORTANT:: rosnode kill is not guaranteed to succeed. - -- Let’s figure out what argument the kill sub-command needs. In a new - terminal run start the rosmaster: - -.. code:: shell - - roscore - -- And in another terminal, run: - -.. code:: shell - - rosrun rospy_tutorials talker - -- And in another terminal, run: - -.. code:: shell - - rosnode kill rosout diff --git a/_sources/markdown/ros/node/rosrun.rst.txt b/_sources/markdown/ros/node/rosrun.rst.txt deleted file mode 100644 index 3907c7ff..00000000 --- a/_sources/markdown/ros/node/rosrun.rst.txt +++ /dev/null @@ -1,68 +0,0 @@ -Command: rosrun -=============== - -rosrun allows you to run an executable in an arbitrary package from -anywhere without having to give its full path or cd/roscd there first. - -Usage: - -.. code:: shell - - rosrun - -```` is nothing but the package name which you have created -using catkin_create_pkg command or used any other package. - -```` is the python or cpp file. - -To create an executable python file ------------------------------------ - -- After creating a package, create a folder in the package names as - scripts folder to store all the python files in that folder. - -.. code:: shell - - cd ~/catkin_ws/src/ - mkdir scripts - -- Here we can create python scripts by running this command by going - into the scripts directory, - -.. code:: shell - - cd scripts - touch filename.py - -- Now you can edit your python file and before running you have to make - it executable by running this command once, - -.. code:: shell - - cd ~/catkin_ws/src//scripts - chmod +x filename.py - -- Here we can create cpp files by running this command by going into the - src directory, - -.. code:: shell - - cd src - touch filename.cpp - -Now you can edit your cpp file , but for making it executable we have to -edit the CMakeLists.txt file - -Add these few lines at the bottom of CMakeLists.txt file, - -.. code:: xml - - add_executable(filename src/filename.cpp) - target_link_libraries(filename ${catkin_LIBRARIES}) - -Then run this command, - -.. code:: shell - - cd ~/catkin_ws - catkin_make diff --git a/_sources/markdown/ros/package/create.rst.txt b/_sources/markdown/ros/package/create.rst.txt deleted file mode 100644 index e0854176..00000000 --- a/_sources/markdown/ros/package/create.rst.txt +++ /dev/null @@ -1,47 +0,0 @@ -Create a ROS package -==================== - -This tutorial will demonstrate how to use the catkin_create_pkg script -to create a new catkin package, and what you can do with it after it has -been created. - -1. First, navigate to the source space directory of the catkin workspace - you’ve created. - -.. code:: shell - - cd ~/catkin_ws/src - -2. Now, use the catkin_create_pkg script to create a new package called - pkg_ros_basics which depends on std_msgs, roscpp, and rospy: - -.. code:: shell - - catkin_create_pkg pkg_ros_basics std_msgs rospy roscpp - -- This will create a beginner_tutorials folder which contains a - package.xml and a CMakeLists.txt , which have been partially filled - out with the information you gave catkin_create_pkg . - -- catkin_create_pkg requires that you give it a package_name and - optionally a list of dependencies on which that package depends: - catkin_create_pkg [depend1] [depend2] [depend3] - -3. Now, you need to build the packages in the catkin workspace - -.. code:: shell - - cd ~/catkin_ws - catkin_make - -- Inside the package, there are src folder, package.xml , - CMakeLists.txt , and the include folders. - - - CMakeLists.txt: This file has all the commands to build the ROS - source code inside the package and create the executable. For more - information about CMakeLists visit here. package.xml: This is an - XML file. It mainly contains the package dependencies information, - and so forth. - - src: The source code of ROS packages are kept in this folder. - - package.xml : This file mainly contains the package dependencies - ,information etc. diff --git a/_sources/markdown/ros/ros-package.rst.txt b/_sources/markdown/ros/ros-package.rst.txt deleted file mode 100644 index 2ad252af..00000000 --- a/_sources/markdown/ros/ros-package.rst.txt +++ /dev/null @@ -1,2 +0,0 @@ -ROS Package -=========== diff --git a/_sources/markdown/selectiontask24/Electronics_selection.rst.txt b/_sources/markdown/selectiontask24/Electronics_selection.rst.txt index 463ead43..7c104784 100644 --- a/_sources/markdown/selectiontask24/Electronics_selection.rst.txt +++ b/_sources/markdown/selectiontask24/Electronics_selection.rst.txt @@ -49,7 +49,7 @@ Task Description: Expected Output --------------- `video link `__ -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. raw:: html diff --git a/_sources/markdown/selectiontask24/cad_sel.rst.txt b/_sources/markdown/selectiontask24/cad_sel.rst.txt index 8dfcdca8..348e0dca 100644 --- a/_sources/markdown/selectiontask24/cad_sel.rst.txt +++ b/_sources/markdown/selectiontask24/cad_sel.rst.txt @@ -61,6 +61,12 @@ Expected Output .. raw:: html +
+ +.. raw:: html + +
+ .. figure:: tas1.png @@ -114,6 +120,13 @@ Expected Output .. raw:: html + +
+ +.. raw:: html + +
+ .. figure:: mechanism.png diff --git a/_sources/markdown/selectiontask24/submissions.rst.txt b/_sources/markdown/selectiontask24/submissions.rst.txt index ae070b51..d3af599f 100644 --- a/_sources/markdown/selectiontask24/submissions.rst.txt +++ b/_sources/markdown/selectiontask24/submissions.rst.txt @@ -120,7 +120,7 @@ ELECTRONICS TASK `Google Form for Task submission `__ ------------------ +---------------------------------------------------------------------------- .. Note:: This google form is common for all the tasks. You can make multiple submissions if you are performing more than 1 selection task. diff --git a/_sources/markdown/tool_setup/virtualenv.rst.txt b/_sources/markdown/tool_setup/virtualenv.rst.txt index 66d71917..0a009922 100644 --- a/_sources/markdown/tool_setup/virtualenv.rst.txt +++ b/_sources/markdown/tool_setup/virtualenv.rst.txt @@ -15,7 +15,7 @@ Virtualenvwrapper is a set of extensions and wrappers used for creating, managin the terminal. Virtual environments are isolated Python installations that help in keeping dependencies required by different projects seperated. They also help in keeping a track of the dependencies or packages required by a project during deployement. -You can read more about it `here `_ +You can read more about it `here(1) `_ OpenCV ======= @@ -24,7 +24,7 @@ OpenCV (Open Source Computer Vision Library) is an open source Computer Vision a developed in C++. It is one of the most commonly used Computer Vision tool nowadays, with client libraries available in popular languages like Python, Java, MATLAB etc. -You can learn more about it `here `_ +You can learn more about it `here(2) `_ cv_bridge @@ -32,7 +32,7 @@ cv_bridge The cv_bridge packages contains the :python:`CvBridge` class which provides an interface between ROS and OpenCV. It helps in conversion from ROS Image messages to OpenCV images and vice-versa. -You can learn more about it `here `_ +You can learn more about it `here(3) `_ Now let's go over the instructions to install these tools one-by-one : @@ -103,7 +103,7 @@ load the new environment variables : source ~/.bashrc Creating a New Virtual Environment ------------------------ +----------------------------------- Now that we have virtualenvwrapper locked and loaded, let's create a new virtual environment. diff --git a/genindex.html b/genindex.html index 487b4fd6..aa477040 100644 --- a/genindex.html +++ b/genindex.html @@ -1,12 +1,14 @@ - + Index — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Hints

-
    -

  • The turtle needs to move in a circular motion with a certain radius. -This radius should be sufficient to fit within the turtlesim window. -But making it rotate in a circular manner, with only velocities to -control is something to think about.

    • -

  • Use linear velocity as well as angular velocity with some combination -to get this done.

    • -

  • Keep tracking the distance travelled so as to know when to stop. You -can refer to Overview of rospy for more hint

    • -
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2021/problem-statement.html b/markdown/archives/sel-task2021/problem-statement.html deleted file mode 100644 index 8fe591dc..00000000 --- a/markdown/archives/sel-task2021/problem-statement.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - - - Problem statement — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Problem statement

-
    -

  • The objective of the task is to move the turtle inside the turtlesim -window in a circle and stop at its initial location.

    • -

  • To acheive this task you are supposed to create a node named -/node_turtle_revolve   within a python script, - node_turtle_revolve.py

    • -
-
-

Note

-

Dont worry if you are new to ROS or Linux(Ubuntu), the task -is fairly simple and we have provided you with ample resource and -tutorials in this WIKI to the complete this task so only a strong -will and a little bit of brains is required to get the work done. -Also even though this just a weekend task we have provided ample -amount of time as we also have our midterm exams during this time. So -we think a week time is enough so you guys can give your exams freely -and manage your time in order to complete the task

-
-

Once you have read the problem statement please visit the -Procedure page to get started with the -task.

-
-
-

Expected Output

-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2021/procedure.html b/markdown/archives/sel-task2021/procedure.html deleted file mode 100644 index 30f951b0..00000000 --- a/markdown/archives/sel-task2021/procedure.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - - - Procedure — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Procedure

-

Follow the instructions given below to get started with the task.

-
    -

  • First, you will need to create a package named selection_task within -your ROS workspace. Once your package is created, source and build -your workspace.

    • -

  • Within this package, you should have a ‘scripts’ folder inside which -you’ll create a python script, named node_turtle_revolve.py.

    • -

  • Fill the script with proper programming ethics. Doing this will help -us understand your code better and quicker than usual.

    • -

  • After completing the python script. Make it executable, if it isn’t -already. To do that, enter the following code.

    • -
-
cd ~/catkin_ws
-catkin_make
-source devel/setup.bash
-chmod +x ~/catkin_ws/src/selection_task/scripts/node_turtle_revolve.py
-
-
-
    -

  • Before executing make sure that roscore is running along with -turtlesim_node. You can either run them in separate terminals or -simply create a selection_task.launch file inside the -~/catkin_ws/src/selection_task/launch/ folder. Launch file can -run multiple nodes unlike a python/cpp script. Run the launch file, -enter, This should run three processes in parallel.

    • -

  • roscore

    • -

  • turtlesim_node

    • -

  • node_turtle_revolve.py

    • -
-
-

See also

-

Please refer to the tutorials and resouces given in the wiki or visit -the official ROSWIKI if you -need help with anything regarding ROS.

-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2021/selection-task.html b/markdown/archives/sel-task2021/selection-task.html index c0ec04c3..8efb7a23 100644 --- a/markdown/archives/sel-task2021/selection-task.html +++ b/markdown/archives/sel-task2021/selection-task.html @@ -1,13 +1,15 @@ - + - + Selection Task 2021 — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Submissions

-

For Submissions of your work please refer to the following instructions

-
    -

  • Video

    -
      -

    • After completing the task, record a video of your work as shown in -the expected output in the problem statement page

      • -

    • Once the video is recorded, upload the video to Youtube as an -unlisted video

      • -
    -
    • -

  • Code

    -
      -

    • Once your script is complete, add comments to your code to make it -more readable.

      • -

    • Create a copy of your script and rename it as task_.py . Your -example if your name is ‘Alex’, then rename your script as -task_alex.py

      • -
    -
    • -

  • Submissions

    -
      -

    • Once your have both of the above things ready, submit the YouTube -link of the video and the script in the google form given below

      • -
    -
    • -

  • Interview

    -
      -

    • Once we review your submission, we will be calling you for a -personal interview based on your work.

      • -
    -
    • -
-

Google Form for Task -submission

-
-

Note

-

Even if you are not able to complete entire the task you -are requested to make the submission of the work that you have done -anyway.

-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2022/hints.html b/markdown/archives/sel-task2022/hints.html deleted file mode 100644 index 920b1673..00000000 --- a/markdown/archives/sel-task2022/hints.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - - - Hints — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Hints

-
    -

  • The turtle needs to move in a inward or outward spiral motion with a -certain increasing or decreasing radius. This radius should be -sufficient to fit within the turtlesim window. But making it rotate -in a circular manner, with only velocities to control is something to -think about.

    • -

  • Use linear velocity as well as angular velocity with some combination -to get this done.

    • -

  • Keep track of the number of circles completed so as to know when to -stop. You can refer to Overview of rospy for more hint

    • -
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2022/problem-statement.html b/markdown/archives/sel-task2022/problem-statement.html deleted file mode 100644 index fafe0115..00000000 --- a/markdown/archives/sel-task2022/problem-statement.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - - - Problem Statement — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Problem Statement

-
    -

  • The objective of the task is to move the turtle inside the turtlesim -window in a inward or outward spiral motion and to stop it after 4 -turns in order to create a spiral as given in the expected output.

    • -

  • To acheive this task you are supposed to create a node named -/node_turtle_spiral   within a python script,  node_turtle_spiral.py

    • -
-
-

Note

-

Dont worry if you are new to ROS or Linux(Ubuntu), the task -is fairly simple and we have provided you with ample resource and -tutorials in this WIKI to the complete this task so only a strong -will and a little bit of brains is required to get the work done. -Also even though this just a weekend task we have provided ample -amount of time as some of you have your end-term exams(onile though). -So we think two weeks time is enough so you guys can study for your -exams freely and manage your time in order to complete the task.

-
-

Once you have read the problem statement please visit the -Procedure page to get started with the task.

-
-
-

Expected Output

-

output video

-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2022/procedure.html b/markdown/archives/sel-task2022/procedure.html deleted file mode 100644 index f6d67415..00000000 --- a/markdown/archives/sel-task2022/procedure.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - - - Procedure — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Procedure

-

Follow the instructions given below to get started with the task.

-
    -

  • First, you will need to create a package named selection_task within -your ROS workspace. Once your package is created, source and build -your workspace.

    • -

  • Within this package, you should have a scripts folder inside which -you’ll create a python script, named node_turtle_spiral.py.

    • -

  • Fill the script with proper programming ethics. Doing this will help -us understand your code better and quicker than usual.

    • -

  • After completing the python script. Make it executable, if it isn’t -already. To do that, enter the following code.

    • -
-
cd ~/catkin_ws
-catkin make
-source devel/setup.bash
-chmod +x ~/catkin_ws/src/selection_task/scripts/node_turtle_spiral.py
-
-
-
    -

  • Before executing make sure that roscore is running along with -turtlesim_node. You can either run them in separate terminals or -simply create a selection_task.launch file inside the -~/catkin_ws/src/selection_task/launch/ folder. Launch file can -run multiple nodes unlike a python/cpp script. Run the launch file, -enter, This should run three processes in parallel.

    • -

  • roscore

    • -

  • turtlesim_node

    • -

  • node_turtle_spiral.py

    • -
-
-

See also

-

Please refer to the tutorials and resouces given in the wiki or visit -the official ROSWIKI if you -need help with anything regarding ROS.

-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task2022/selection-task.html b/markdown/archives/sel-task2022/selection-task.html index 71a09e74..a1abba66 100644 --- a/markdown/archives/sel-task2022/selection-task.html +++ b/markdown/archives/sel-task2022/selection-task.html @@ -1,13 +1,15 @@ - + - + Selection Task 2022 — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Submission Instruction

-

For Submissions of your work please refer to the following instructions

-
    -

  • Video

    -
      -

    • After completing the task, record a video of your work as shown in -the expected output in the problem statement page

      • -

    • Once the video is recorded, upload the video to Youtube as an -unlisted video

      • -
    -
    • -

  • Code

    -
      -

    • Once your script is complete, add comments to your code to make it -more readable.

      • -

    • Create a copy of your script and rename it as task_.py . Your -example if your name is ‘Alex’, then rename your script as -task_alex.py

      • -
    -
    • -

  • Submissions

    -
      -

    • Once you have both of the above things ready, submit the YouTube -link of the video and the script in the google form given below

      • -
    -
    • -

  • Interview

    -
      -

    • Once we review your submission, we will be calling you for a -personal interview based on your work.

      • -
    -
    • -
-

Google Form for Task -submission

-
-

Note

-

Even if you are not able to complete entire the task you -are requested to make the submission of the work that you have done -anyway.

-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task_cad_2022/cad_sel.html b/markdown/archives/sel-task_cad_2022/cad_sel.html index 0c0c093c..5ed44414 100644 --- a/markdown/archives/sel-task_cad_2022/cad_sel.html +++ b/markdown/archives/sel-task_cad_2022/cad_sel.html @@ -1,13 +1,15 @@ - + - + CAD Selection Task: Standard Instructions — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Task 1

-
    -

  • The objective of the task is to make a 3D model of a part using the -given engineering drawing.

    • -

  • To achieve this task you may use any method but the end result should -be as close as possible to the original drawing.

    • -

  • You will be judged on the basis of your way of designing, so keep -that in mind and make sure to follow proper practices(Like using -constraints appropriately).

    • -
-
-

Note

-

You may use any software that you are familiar with but you -are recommended to use Fusion360.

-
-

Once you are done with the Task 1 please submit it by heading over to -Submissions

-
-

Note

-

Head to Task 2 once you are done with -task1.

-
-
-
-

Expected Output

-
-https://i.ibb.co/J3Crbpm/cad-task02-v1-v1.gif -
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task_cad_2022/cad_task2.html b/markdown/archives/sel-task_cad_2022/cad_task2.html deleted file mode 100644 index d9e4b990..00000000 --- a/markdown/archives/sel-task_cad_2022/cad_task2.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - - - Task 2 — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Task 2

-
    -

  • The objective of the task is to make a 3d design CAD design of a 5 -degree of freedom Robotic Arm .

    • -

  • Details:

    -
      -

    • You are required to create a 5 degree of freedom Robotic arm -with links and joints as specified in the image above.

      • -

    • The image is just an example to show the placement of each axis. -You are free to choose the placement of actuators and joints and -use any design you can think of…

      • -

    • The arm should have a robot workspace in the form of a semi circle -with radius approx 40-60 cm.

      • -

    • You have to create the arm using Tower Pro MG946R Metal Gear -Servo as actuatos. -Sample -for a metal gear servo.

      • -

    • The model should have proper mounts and spaces for servos and -other mechanical parts. You free to use any type mechanical -components like screws, bearings etc.

      • -

    • All components in the arm should be connected with proper joints.

      • -
    -
    • -

  • You will be judged on the basis of the following criteria:

    -
      -

    • Manufacturability of the links and mounts (Preferebly 3d -Printable)

      • -

    • Adhering to the giving details and guidelines.

      • -

    • Reusability and esay to modify in future if required.

      • -

    • You may use any methods and tools to achieve the task buy make -sure to follow proper 3d modeling practices like constraints, -joints etc.

      • -
    -
    -

    Note

    -

    To achieve the above task, you are free to use any software that -you are familiar with but you are recommended to use Fusion360 -as you will have to switch over to fusion360 if you join the society.

    -
    -
    -

    See also

    -

    The last date to submit the task is 28 August, 2022. Note: We -recommend you to manage your time properly and start with the task as -soon as possible as it could get a bit lengthy. Even if you are not -able to complete the whole task, we encourage you to still submit all -the work you are able to complete till the deadline as you sill might -have a chance to get selected based on your submission.

    -
    -
    • -
-

Once you are done with the Task 2 please submit it by heading over to Submissions

-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-task_cad_2022/selection-task.html b/markdown/archives/sel-task_cad_2022/selection-task.html index e1c9895f..10c2d5e9 100644 --- a/markdown/archives/sel-task_cad_2022/selection-task.html +++ b/markdown/archives/sel-task_cad_2022/selection-task.html @@ -1,13 +1,15 @@ - + - + CAD Selection Task 2022 — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Submission Instructions

-

For Submissions of your work please refer to the following instructions

-
-

Task 1

-
    -

  • Video

    -
      -

    • Once you are done with the modelling, you have to record a video -of your screen where show the model from different angles in the -software you used. Then you have to upload the video on YouTube -and share a link to the video in the submission form.

      • -
    -
    • -

  • Model file

    -
      -

    • Once your Model is complete, export it as a stl file and rename it -as .stl. For example if your name is ‘Alex’, then rename your file -as Task1_Alex.stl

      • -
    -
    • -
-
-

Optional Submissions

-
    -

  • Previous Works (Optional)

    -
      -

    • You are welcome to submit any of your previous work related to 3D -modeling. It is optional but, this would help us see your -creativity and skills. You have to add it to drive and share the -drive link in the submission form. Make sure the link is public -and accessible by anyone.

      • -
    -
    -

    See also

    -

    Last date for submission is 26th of August

    -
    -
    • -
-
-

Google Form for Task submission

-
-
-
-
-

Task 2

-
    -

  • Video

    -
      -

    • Once you are done with the modelling, you have to record a video -of your screen where show the model from different angles, move -all the joints and show it’s working in the software you used. -Then you have to upload the video on YouTube as unlisted and share -a link to the video in the submission form.

      • -
    -
    • -

  • Model file

    -
      -

    • Once your Model is complete, upload the model files in a google -drive folder and share the link in the google form below. Make -sure to give viewing acess while creating the shareable link for -the google drive.

      • -
    -
    • -
-
-

See also

-

Last date for submission is 27th of August

-
-
-

Google Form for Task submission

-
-
-
-

Interview

-
- Once we review your submission, we will be calling you for a personal interview based on your work.
-- We would be asking about some general question related to computers and your thought process & stuff related to the task that you have performed.
-
-
-
-

Note

-

Make sure you submit both of your task before the 27th of -August. Both the submissions have to be done separately. Even if you -are not able to complete entire the task you are requested to make -the submission of the work that you have done anyway.

-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/archives/sel-tasks2023/CAD_Selection_Task.html b/markdown/archives/sel-tasks2023/CAD_Selection_Task.html index 82a7b6a4..c2705205 100644 --- a/markdown/archives/sel-tasks2023/CAD_Selection_Task.html +++ b/markdown/archives/sel-tasks2023/CAD_Selection_Task.html @@ -1,13 +1,15 @@ - + - + CAD Selection Task 2023 — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Task Submission

-
-

Warning

-

The Deadline for all the Tasks is: 11th December, 2022 Head to the -Problem statement section to begin with the tasks.

-
-

For Submissions of your work please refer to the following instructions

-
    -

  • Video

    -
      -

    • After completing the task, record a video of your work as shown in -the expected output in the problem statement page

      • -

    • Once the video is recorded, upload the video to Youtube as an -unlisted video

      • -
    -
    • -

  • File

    -
      -

    • Once your script is complete, add comments to your code to make it -more readable.

      • -

    • Create a copy of your script and rename it as <task_your_name> . -For example if you worked on Computer vision task on a python file -and your name is ‘Alex’, then rename your script to cvtask_alex.py

      • -
    -
    • -

  • Submissions

    -
      -

    • Once you have both of the above things ready, submit the YouTube -link of the video and the script in the google form given below

      • -

    • Previous Works (Optional): -You are welcome to submit any of your previous work related to task. -It is optional but, this would help us see your skills. You have to -add it to drive and share the drive link in the submission form.

      • -
    -
    -

    Warning

    -

    Make sure to make the links accessible to everyone before sharing it.

    -
    -
    • -

  • Interview

    -
      -

    • Once we review your submission, we will be sending you a confirmation and -will callyou for a personal interview based on your work.

      • -

    • Questions related to the task that you’ve performed will be asked.

      • -
    -
    • -
-
-

Submit task here

-
-

Note

-

Even if you are not able to complete entire the task you -are requested to make submission of the work that you have done -anyway.

-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/general/access-repo.html b/markdown/general/access-repo.html index 7b1a8d33..9d8fe643 100644 --- a/markdown/general/access-repo.html +++ b/markdown/general/access-repo.html @@ -1,13 +1,15 @@ - + - + Using the access repo — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Editing this wiki

-
-

Step 1

-
    -

  • Fork the github repository by clicking on the fork button on the top -right

    • -
-
-
-

Step 2

-
    -

  • Clone your fork of the repository

    • -
-
-
-

Step 3

- -
-
-

Step 4

-
    -

  • Push to your fork

    • -
-
-
-

Step 5

-
    -

  • Create a merge request to the main repository

    • -
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/general/main-site.html b/markdown/general/main-site.html deleted file mode 100644 index 432adc3a..00000000 --- a/markdown/general/main-site.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - Editing the ATOM main site — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Editing the ATOM main site

-
-

Step 1:

-
    -

  • Fork the repository

    • -
-
-
-

Step 2:

- -
-
-

Step 3:

-
    -

  • Make changes to the site

    • -
-
-
-

Step 4:

-
    -

  • Create a PR to the main repo

    • -
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/projects/mr-robot/major-code/arduino.html b/markdown/projects/mr-robot/major-code/arduino.html index 3021fe66..423aca30 100644 --- a/markdown/projects/mr-robot/major-code/arduino.html +++ b/markdown/projects/mr-robot/major-code/arduino.html @@ -1,13 +1,15 @@ - + - + Arduino — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
-
    -
    • -
  • Example #1: ROS Node to Get and Set Parameters
    • -
  • - Edit on GitHub -
    • -
-
-
-
-
- -
-

Example #1: ROS Node to Get and Set Parameters

-
-

Aim

-

To write a ROS Node to read config_my.yaml file loaded in ROS Parameter -Server (done here), print it on the console and modify the phone number.

-
-
-

Code

-
node_param_get_set.py
-#!/usr/bin/env python
-import rospy
-def main():
-    #1. Make the script a ROS Node.
-    rospy.init_node('node_param_get_set', anonymous=True)
-    # 2. Read from Parameter Server
-    rospy.loginfo("Reading from Parameter Server.")
-    param_config_my = rospy.get_param('details')
-
-    # Get all the parameters inside 'details'
-    # Store the parameters in variables
-
-    first_name = param_config_my['name']['first']
-    last_name = param_config_my['name']['last']
-    address = param_config_my['contact']['address']
-    phone = param_config_my['contact']['phone']
-
-    # Print the parameters
-
-    rospy.loginfo(">> First Name: {}".format(first_name))
-    rospy.loginfo(">> Last Name: {}".format(last_name))
-    rospy.loginfo(">> Address: {}".format(address))
-    rospy.loginfo(">> Phone: {}".format(phone))
-
-    # 3. Modify the Phone Number
-
-    rospy.set_param('/details/contact/phone', 55555)
-    new_phone = rospy.get_param('/details/contact/phone')
-    rospy.loginfo(">> New Phone: {}".format(new_phone))
-
-    # Modify only Phone Number in Parame
-    # Get only Phone Number from Paramet
-    # Print the new Phone Number
-
-
-
    -

  • The code is self explainatory , please feel free to seek help if you -don’t understand it

    • -
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/examples/example.html b/markdown/ros/examples/example.html index 0a4ad742..9142e5aa 100644 --- a/markdown/ros/examples/example.html +++ b/markdown/ros/examples/example.html @@ -1,13 +1,15 @@ - + - + Examples — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Create a ROS Launch file

-
-

roslaunch Command

-
    -

  • roslaunch is a tool for easily launching multiple ROS nodes locally -and remotely via SSH.

    • -

  • It includes options to automatically respawn processes that have -already died. roslaunch takes in one or more XML configuration files -(with the .launch extension) that specify the parameters to set and -nodes to launch.

    • -
-

Usage:

-
roslaunch <package> file.launch
-
-
-
    -

  • is nothing but the package name which you have created using

    • -
-
-

catkin_create_pkg command or used any other package

-
-
-
-

Steps to create a launch file

-
    -

  • After creating a package, create a folder in the package names as a -launch folder to store all the launch files in that folder.

    • -
-
cd ~/catkin_ws/src/<package>
-mkdir launch
-
-
-
    -

  • Here we can create launch files by running this command by going into -the launch directory, we can keep any name for the launch file

    • -
-
cd launch
-touch filename.launch
-
-
-

Now you can edit your launch file by adding different nodes that you have -to run simultaneously.

-
-
-

Steps to add a ROS node in the launch file

-
    -
    • -

    1. Launch files always starts with

      2. -
    -
    • -
-

<launch> and end with </launch>

-
    -

  • 2.Now to add any executable file which we have seen in the -rosrun_command section, we have to add this line

    • -
-
<node pkg="name_of_package" type="name_of_executable.py" name="name_of_executable" output="screen"/>
-
-
-
    -

  • name is the name of the node which is created in that executable

    • -

  • output means it will print the data given to the roslog command

    • -

  • type is the name of executable file

    • -

  • pkg is the package name which you have created.

    • -
-
-
-

Steps to load Config YAML file in ROS Parameter Server

-

You can use rosparam tag to load the YAML file.

-
    -

  • type is the name of executable file

    • -

  • pkg is the package name which you have created

    • -

  • name_of_package is the name of your ROS package.

    • -

  • config.yaml is the name of your configuration file.

    • -
-
-
-

Steps to add a shell script in the launch file

-

You can use node tag to run any shell script using launch file

-
<node pkg="name_of_package" type="shell_script.sh" name="shell_script" output="screen">
-    <param name="cmd" value="$(find name_of_package)/launch/shell_script.sh"/>
-</node>
-
-
-
    -

  • name_of_package is the name of your ROS package.

    • -

  • shell_script.sh is the name of your configuration file.

    • -

  • /launch/shell_script.sh is the location of the shell script inside -your ROS Package folder.

    • -
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/launch/eg1.html b/markdown/ros/launch/eg1.html deleted file mode 100644 index f1fea354..00000000 --- a/markdown/ros/launch/eg1.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - - - Example 1: Launch two ROS Nodes — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Example 1: Launch two ROS Nodes

-
-

Aim

-
    -

  • To launch talker and listener node present in rospy_tutorials -package.

    • -

  • For this create a chatter.launch file and save it in the launch folder -inside pkg_ros_basics package.

    • -
-
-

Note

-

To install rospy_tutorials package in your system you can run

-
-

sudo apt-get install ros-noetic-ros-tutorials this command.

-
    -

  • Once installed, you can use listener python script and talker -executable written in C++ present in rospy_tutorials package.

    • -
-
-
-

Code

-

chatter.launch

-
<launch>
-<node name="talker" pkg="rospy_tutorials" type="talker" output="screen"/>
-<node name="listener" pkg="rospy_tutorials" type="listener.py" output="screen"/>
-</launch>
-
-
-
    -

  • Here first talker.cpp file (for cpp file we dont need to add .cpp -extension) has been included with the node name as talker and also -set output as screen so you can see the output from talker node.

    • -

  • Next we have added listener.py which has node name as listener and -here also we have set output as screen.

    • -
-
-
-

Run Command

-

Now run these command to run the launch file,

-
roslaunch pkg_ros_basics chatter.launch
-
-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/launch/eg2.html b/markdown/ros/launch/eg2.html deleted file mode 100644 index ed411d3a..00000000 --- a/markdown/ros/launch/eg2.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - - - Example 2: Launch turtle in forest — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Example 2: Launch turtle in forest

-
-

Aim

-
    -

  • To write a launch file to run turtlesim_node node and -turtle_teleop_key node present in turtlesim package.

    • -

  • While launching the turtlesim_node make sure to change the background -colour of the simulator from blue to forest green.

    • -

  • Name the launch file turtlesim.launch and save it in launch folder -inside pkg_ros_basics package.

    • -
-
-
-

Code

-

turtlesim.launch

-
<launch>
-<node pkg="turtlesim" type="turtlesim_node" name="node_turtlesim_node">
-<param name="/turtlesim_node/background_r" value="34" />
-<param name="/turtlesim_node/background_g" value="139" />
-<param name="/turtlesim_node/background_b" value="34" />
-<param name="/background_r" value="34" />
-<param name="/background_g" value="139" />
-<param name="/background_b" value="34" />
-</node>
-<node pkg="turtlesim" type="turtle_teleop_key" name="node_turtle_teleop_key" />
-❱
-</launch>
-
-
-
-
-

Run Command

-
roslaunch pkg_ros_basics turtlesim.launch
-
-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/launch/eg3.html b/markdown/ros/launch/eg3.html deleted file mode 100644 index 1bcd2cd2..00000000 --- a/markdown/ros/launch/eg3.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - Example 3: Load YAML — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Example 3: Load YAML

-
-

Aim

-
    -

  • To write a launch file to load config_my.yaml present in -pkg_ros_basics package.

    • -

  • Also launch the node_param_get_set.py ROS node after loading the YAML -file.

    • -
-
-
-

Code

-

load_yaml.launch

-
<launch>
-<rosparam file ="$(find pkg_ros_basics)/config/config_my.yaml"/>
-<node pkg="pkg_ros_basics" type="node_param_get_set.py" name="node_param_get_set">
-</launch>
-
-
-
-
-

Run Command

-
roslaunch pkg_ros_basics load_yaml.launch
-
-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/launch/launch.html b/markdown/ros/launch/launch.html index 94a33ce5..c1893ff9 100644 --- a/markdown/ros/launch/launch.html +++ b/markdown/ros/launch/launch.html @@ -1,13 +1,15 @@ - + - + ROS Launch Files — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

ROS Parameter Server

-
    -

  • You can think Parameter Server as a space where all the necessary -data that needs to be shared among various ROS Nodes is stored.

    • -

  • Parameter Server runs inside ROS Master.

    • -

  • ROS Nodes can view and even modify data stored in the Parameter -Server.

    • -

  • Typically Parameter Server is used to store configuration parameters.

    • -
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/node/create.html b/markdown/ros/node/create.html deleted file mode 100644 index 75173a66..00000000 --- a/markdown/ros/node/create.html +++ /dev/null @@ -1,219 +0,0 @@ - - - - - - - Creating a ROS Node — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Creating a ROS Node

-
    -

  • In this section we will learn how to create a ROS Node inside -pkg_ros_basics ROS Package which we created in the previous section.

    • -

  • Navigate to pkg_ros_basics

    • -
-
cd ~/catkin_ws/src/pkg_ros_basics
-
-
-

OR

-
roscd pkg_ros_basics
-
-
-
-

Note

-

roscd will work only if you have sourced setup.bash of your

-
-

catkin workspace.

-
    -

  • Create a scripts folder for your Python scripts and navigate into the -folder.

    • -
-
mkdir scripts
-cd scripts
-
-
-
    -

  • Create a Python script called node_hello_ros.py .

    • -
-
touch node_hello_ros.py
-
-
-
    -

  • Open the script in any text-editor and start editing.

    • -
-
gedit node_hello_ros.py
-
-
-
    -

  • First line of all your Python ROS scripts should be the following -shebang

    • -
-
#!/usr/bin/env python
-
-
-
    -

  • Now write a ROS Node to print Hello World! on the console.

    • -
-
#!/usr/bin/env python
-import rospy
-def main():
-#Initialize the new node
-rospy.init_node('node_hello_ros', anonymous=True)
-#  Print info on console.
-rospy.loginfo("Hello World!")
-
-if __name__ == '__main__':
-
-    try:
-        main()
-    except rospy.ROSInterruptException:
-        pass
-
-
-
    -

  • Make your node executable

    • -
-
sudo chmod +x node_hello_ros.py
-
-
-
    -

  • Now to run your node

    -
      -

    • Open the terminal and run ROS master

      • -
    -
    roscore
-
    -
    -
      -

    • Once the roscore is running open a new terminal and run the main -node

      • -
    -
    rosrun pkg_ros_basics node_hello_ros.py
-
    -
    -
    -

    Note

    -

    This command will work only if you have sourced setup.bash of your catkin workspace either manually or using .bashrc .

    -
    -
    • -
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/node/node.html b/markdown/ros/node/node.html index bf824204..e53d0ff5 100644 --- a/markdown/ros/node/node.html +++ b/markdown/ros/node/node.html @@ -1,13 +1,15 @@ - + - + ROS Nodes — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Command: rosnode

-
    -

  • rosnode contains the rosnode command-line tool for displaying debug -information about ROS Nodes.

    • -
-
-

Note

-

For quick information about any command, be that outside of ROS,

-
-

simply type the command along with suffix –h or -help . This is a widely -used concept among other Linux Command: rosrun commands for quick -references. Here’s an example for rosnode –h command

-
    -

  • list

    -
    • -
-

rosnode list displays a list of all current nodes.

-

Let’s figure out what argument the list sub-command needs. In a new -terminal run start the rosmaster:

-
roscore
-
-
-

And in another terminal, run:

-
rosrun rospy_tutorials talker
-
-
-

And in another terminal, run:

-
rosnode list
-
-
-

Now the node named talker (node with word talker in it) will be printed -on the terminal.

-
    -

  • info

    -
    • -

  • rosnode info /node_name displays information about a node, including -publications and subscriptions.

    • -

  • Let’s figure out what argument the info sub-command needs. In a new -terminal run start the

    • -
-
rosmaster
-
-
-

And in another terminal, run:

-
rosrun rospy_tutorials talker
-
-
-

And in another terminal, run:

-
rosnode info <talker_node>
-
-
-

This should give details of the particular node

-
    -

  • kill

    -
    • -
-
-

Important

-

rosnode kill is not guaranteed to succeed.

-
-
    -

  • Let’s figure out what argument the kill sub-command needs. In a new -terminal run start the rosmaster:

    • -
-
roscore
-
-
-
    -

  • And in another terminal, run:

    • -
-
rosrun rospy_tutorials talker
-
-
-
    -

  • And in another terminal, run:

    • -
-
rosnode kill rosout <talker_node>
-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/node/rosrun.html b/markdown/ros/node/rosrun.html deleted file mode 100644 index 894e8093..00000000 --- a/markdown/ros/node/rosrun.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - - - Command: rosrun — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Command: rosrun

-

rosrun allows you to run an executable in an arbitrary package from -anywhere without having to give its full path or cd/roscd there first.

-

Usage:

-
rosrun <package> <executable>
-
-
-

<package> is nothing but the package name which you have created -using catkin_create_pkg command or used any other package.

-

<executable> is the python or cpp file.

-
-

To create an executable python file

-
    -

  • After creating a package, create a folder in the package names as -scripts folder to store all the python files in that folder.

    • -
-
cd ~/catkin_ws/src/<package>
-mkdir scripts
-
-
-
    -

  • Here we can create python scripts by running this command by going -into the scripts directory,

    • -
-
cd scripts
-touch filename.py
-
-
-
    -

  • Now you can edit your python file and before running you have to make -it executable by running this command once,

    • -
-
cd ~/catkin_ws/src/<package>/scripts
-chmod +x filename.py
-
-
-
    -

  • Here we can create cpp files by running this command by going into the -src directory,

    • -
-
cd src
-touch filename.cpp
-
-
-

Now you can edit your cpp file , but for making it executable we have to -edit the CMakeLists.txt file

-

Add these few lines at the bottom of CMakeLists.txt file,

-
add_executable(filename src/filename.cpp)
-target_link_libraries(filename ${catkin_LIBRARIES})
-
-
-

Then run this command,

-
cd ~/catkin_ws
-catkin_make
-
-
-
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/package/create.html b/markdown/ros/package/create.html deleted file mode 100644 index 0e19c742..00000000 --- a/markdown/ros/package/create.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - - - Create a ROS package — A.T.O.M's Wiki 0.3.2 documentation - - - - - - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

Create a ROS package

-

This tutorial will demonstrate how to use the catkin_create_pkg script -to create a new catkin package, and what you can do with it after it has -been created.

-
    -

  1. First, navigate to the source space directory of the catkin workspace -you’ve created.

    2. -
-
cd ~/catkin_ws/src
-
-
-
    -

  1. Now, use the catkin_create_pkg script to create a new package called -pkg_ros_basics which depends on std_msgs, roscpp, and rospy:

    2. -
-
catkin_create_pkg pkg_ros_basics std_msgs rospy roscpp
-
-
-
    -

  • This will create a beginner_tutorials folder which contains a -package.xml and a CMakeLists.txt , which have been partially filled -out with the information you gave catkin_create_pkg .

    • -

  • catkin_create_pkg requires that you give it a package_name and -optionally a list of dependencies on which that package depends: -catkin_create_pkg [depend1] [depend2] [depend3]

    • -
-
    -

  1. Now, you need to build the packages in the catkin workspace

    2. -
-
cd ~/catkin_ws
-catkin_make
-
-
-
    -

  • Inside the package, there are src folder, package.xml , -CMakeLists.txt , and the include folders.

    -
      -

    • CMakeLists.txt: This file has all the commands to build the ROS -source code inside the package and create the executable. For more -information about CMakeLists visit here. package.xml: This is an -XML file. It mainly contains the package dependencies information, -and so forth.

      • -

    • src: The source code of ROS packages are kept in this folder.

      • -

    • package.xml : This file mainly contains the package dependencies -,information etc.

      • -
    -
    • -
-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/package/package.html b/markdown/ros/package/package.html index c70aa067..bb283326 100644 --- a/markdown/ros/package/package.html +++ b/markdown/ros/package/package.html @@ -1,13 +1,15 @@ - + - + ROS Package — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + + - - - - - - - - - - - - - - -
- - -
- -
-
-
- -
-
-
-
- -
-

ROS Package

-
- - -
-
- -
-
-
-
- - - - \ No newline at end of file diff --git a/markdown/ros/ros.html b/markdown/ros/ros.html index c80e49d8..feefa511 100644 --- a/markdown/ros/ros.html +++ b/markdown/ros/ros.html @@ -1,13 +1,15 @@ - + - + Intro To ROS — A.T.O.M's Wiki 0.3.2 documentation - - - + + + + +