UEX RoboLab robocomp components
robocomp / robocomp-robolab Goto Github PK
View Code? Open in Web Editor NEWUEX RoboLab robocomp components
License: GNU General Public License v3.0
UEX RoboLab robocomp components
License: GNU General Public License v3.0
While going through the description of file components/detection/handGesture/src/HandGesture.py
, found a spell error in line 31.
Adding faceidentification.idsl interface to the faceidentification component.
I want to try the CGR algorithm, but I cannot compile the source. When I run cmake ..
in build directory I have a following error:
CMake Warning at src/CMakeLists.txt:7 (MESSAGE):
ROBOCOMP variable not set. Using the default value: /opt/robocomp
CMake Error at src/CMakeLists.txt:12 (MESSAGE):
Couldn't find RoboComp in /opt/robocomp/! Exiting...
-- Configuring incomplete, errors occurred!
I noticed that ROBOCOMP variable is used to provide path to rapplication.cpp
but I can not find this file in repository. Do I need rapplication? Should I comment out all includes to this?
Is your feature request related to a problem? Please describe.
In my PR: #69 I have added a directory tree to which I was asked to suggest a solution by @orensbruli for automatically updating the directory tree in the readme.MD files once any modification is done in the repository.
I had contributed a directory tree for the detection folder, which is mentioned below:
├───activityRecognition
│ ├───dl_training
│ │ ├───experiments
│ │ │ ├───CAD-60
│ │ │ │ ├───1
│ │ │ │ │ └───HCN18
│ │ │ │ │ └───checkpoint
│ │ │ │ ├───2
│ │ │ │ │ └───HCN19
│ │ │ │ │ └───checkpoint
│ │ │ │ ├───3
│ │ │ │ │ └───HCN20
│ │ │ │ │ └───checkpoint
│ │ │ │ └───4
│ │ │ │ └───HCN19
│ │ │ │ └───checkpoint
│ │ │ └───NTU-RGB-D-CS
│ │ │ └───HCN06
│ │ │ └───checkpoint
│ │ ├───feeder
│ │ ├───model
│ │ ├───resource
│ │ │ └───NTU-RGB-D
│ │ └───utils
│ ├───etc
│ ├───src
│ │ ├───data
│ │ ├───model
│ │ └───utils
│ └───SVM_hand_crafted
│ ├───feature_extraction
│ ├───feeder
│ ├───models
│ └───support_operations
├───apriltagsComp
│ ├───etc
│ └───src
│ └───AprilTags
├───colorTraking
│ ├───etc
│ └───src
│ └───ColorDetection
├───emotionrecognition2
│ ├───assets
│ ├───CNN
│ │ ├───checkpoints
│ │ └───data
│ │ ├───angry
│ │ ├───happy
│ │ ├───neutral
│ │ ├───sad
│ │ └───surprised
│ ├───etc
│ └───src
├───extrinsic_camera_calibration
│ ├───etc
│ └───src
├───faceidentification
│ ├───assets
│ │ └───src
│ ├───etc
│ └───src
├───handDetection
│ ├───etc
│ └───src
│ ├───images
│ │ ├───depth_images
│ │ ├───masks
│ │ └───output
│ └───libs
│ └───HandDetection
│ └───resources
├───handGesture
│ ├───assets
│ ├───etc
│ └───src
├───handKeypoint
│ ├───etc
│ └───src
├───objDetection
│ ├───etc
│ └───src
├───realsensehuman
│ ├───etc
│ └───src
├───realsense_camera
│ ├───etc
│ └───src
├───simplecamerargbd_realsense
│ ├───etc
│ └───src
└───test
├───activityRecognitionClient
│ ├───etc
│ └───src
├───emotionrecognitionclient
│ ├───etc
│ └───src
├───faceidentificationclient
│ ├───assets
│ │ ├───save_model
│ │ └───src
│ ├───etc
│ └───src
└───handGestureClient
├───assets
│ └───protos
├───etc
└───src
Describe the solution you'd like
To update the markdown file, again and again, is quite tiresome. I would like to suggest deploying a GitHub actions bot to automatically update the markdown files once a new feature is added to the repository.
Describe alternatives you've considered
An alternative is to keep a track of all the modifications done in the features and then manually update the markdown file.
Hello, I would like to start participating in the project. I am currently reading the code and came up with the idea of supporting the mouse to using the robot. I'm going to start creating this component. It can be helpful?
Currently there's several problem with this components (reading config files, etc).
While installation and testing the face identification module, I am getting the following error.
SLICE_PATH environment variable was not exported. Using only the default paths
SLICE_PATH environment variable was not exported. Using only the default paths
('Trying', '/opt/robocomp/interfaces', 'to load FaceIdentification.ice')
('Using', '/opt/robocomp/interfaces', 'to load FaceIdentification.ice')
Traceback (most recent call last):
File "src/faceidentification.py", line 65, in <module>
from specificworker import *
File "/home/shubh/robocomp/components/robocomp-robolab/components/detection/faceidentification/src/specificworker.py", line 35, in <module>
import facenet2 as facenet
ImportError: No module named facenet2
The error is arising for the following code:
I am getting a similar error in another file:
While running camerasimple component, when SLICE_PATH environment variable is not exported, the message given is
'SLICE_PATH environment variable was not exported. Using only the default paths'.
However, no value default value is appended to icePaths, due to which 'Couldn't load CameraSimple' error is given.
Should we provide a default path by adding the following line?
icePaths.append('/opt/robocomp/interfaces')
It also happens if the camera is occluded by something. Maybe it would keep checking or just not coredump to avoid that the user think something unexpected have happened.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.