мы можем как-то сгладить координаты точек контура
нам надо записать сглаженные точки в правильные индексы
Координаты точек вычисляются как: `
` | |
// ParserTest.cpp: определяет точку входа для консольного приложения. | |
// | |
#include "stdafx.h" | |
#include <string.h> | |
#include <iostream> | |
#include <string> | |
using namespace std; |
# customview.js | |
// NOTE: | |
// Modifying the URL below to another server will likely *NOT* work. Because of browser | |
// security restrictions, we have to use a file server with special headers | |
// (CORS) - most servers don't support cross-origin browser requests. | |
// | |
// |
width: 70; height: 20 | |
0 0; (1.15767; -0.0959568; -0.0759666); (255; 0; 0) | |
0 1; (1.15767; -0.0870117; -0.0759666); (255; 0; 0) | |
0 2; (1.15229; -0.0764401; -0.0831106); (255; 0; 0) | |
0 3; (1.15164; -0.0650554; -0.0839765); (255; 0; 0) | |
0 4; (1.15089; -0.053206; -0.0849662); (255; 0; 0) | |
0 5; (1.15089; -0.044377; -0.0849662); (255; 0; 0) | |
0 6; (1.15943; -0.0310662; -0.090257); (255; 0; 0) | |
0 7; (1.15089; -0.0248604; -0.0849662); (255; 0; 0) | |
0 8; (1.1518; -0.0154506; -0.08376); (255; 0; 0) |
/* | |
* UART.h | |
* | |
* General UART realization | |
* Now available UART0 only for all | |
* using printf\scanf. | |
* For debug use. | |
* | |
* NOTE: MUST DEFINE UART_RECEIVE_BUFFER_SIZE | |
* |
alias cls='clear' | |
alias fuck='sudo' | |
alias clion='nohup clion.sh &>/dev/null &' | |
alias gitk='nohup gitk --all &>/dev/null &' | |
alias rqt='nohup rqt &>/dev/null &' | |
alias kinect='roslaunch openni_launch openni.launch depth_registration:=true' | |
alias rtabmap='roslaunch rtabmap_ros rgbd_mapping.launch rtabmap_args:="--delete_db_on_start"' | |
source /opt/ros/indigo/setup.bash | |
source ~/ros/devel/setup.bash |
Планировщик маршрута для антропоморфного робота в условиях неизвестного окружения.
Необходимо прокладывать маршрут в условиях более сложных, чем просто ровный пол и препятствия. Для антропоморфных роботов тут предлагают различные footstep-планнеры, которые прокладывают маршрут в виде набора шагов. По ряду причин этот метод не всегда подходит и просто не очень мне нравится:
This is a note on how to cross compile opencv for pretty much any ARM device(HardFP supported in this case) and deploy. Native compiling in ARM devices can be painfully slow and they seem to hang often during build(mine got stuck at 43%). So if you happen to have a desktop/laptop/server running ubuntu or similar linux distro, u can build opencv in fractionth of the time taken for native compiling without any issues. Building opencv3 with TBB and NEON and VFP support can boost opencv performance. Thanks to Adrian at pyimagesearch for pointing that out. Both my PC and target machine aka orange pi zero are running ubuntu 16.04 with python2.7 and python 3.5. Let us use the term "build machine" for your PC where you are building opencv and "target machine" for the ARM single board computer.
1.Run the following commands in both machines(I think installing these in target machine only would do) to install the necessary libraries etc.(mine worked with them,so they should be enough