Comments (9)
Hi, in original baseline implementation we compute gt scores by s = 1.1 - u, with u in [0.0, 1.0].
In current implementation, we use s = 0 when u = 0 and s = -ln(u) when u is in [0.1, 1.0].
With this definition, gt scores are ranging from 0 to ln(10).
The definition can be found here.
from graspnet-baseline.
Thanks for your quick response.
It is clear, so the grasp score ranges from 0 to ln(1.0), is it correct?
I have another question, your work seems to be "gripper agnostic", but from the grasp definition, I understand the following:
- width, is the gripper opening,
- height, is the height of the gripper tip,
- depth, should be the distance from the origin of the gripper coordinate frame and the first point of the object to be grasped.
is it correct?
Then there is an offset of 2 cm, that should define the distance from the origin of the gripper coordinate and the palm of the gripper, but if I have a gripper that does not have this offset, (it may be lower or greater), do I have the possibility to set this parameter?
from graspnet-baseline.
Grasp score ranges from 0 to ln(10) (not ln(1.0)).
Depth is the distance from the origin of gripper coordinate frame to the gripper tip, and contact points usually lie between them. Detailed definition can be found in graspnetAPI.
The height and 2cm offset are used in collision detection and graspnet evaluation, and can be modified according to your requirements in the real experiments. The coordinates of gripper tip computed from modified gripper paramters and original graspnet format needs to be aligned.
from graspnet-baseline.
I am sorry for the typo.
Probably I am missing something but based on the comment:
"Depth is the distance from the origin of gripper coordinate frame to the gripper tip, and contact points usually lie between them", this depth should be constant, because the origin of the gripper coordinate is fixed as well as its distance from the gripper tip, but after running the demo I have not observed this behavior. What am I missing?
Moreover, what do you mean with "modified gripper paramters and original graspnet format needs to be aligned"?
Thank you for your kind.
from graspnet-baseline.
In the output parameters, coordinates of grasp points are not equivalent to the gripper bottom. The position of gripper tip is computed by grasp point and depth (not a constant), and the position of the bottom is computed using tip coordinate and the fixed gripper length (a variable you can set by yourself).
from graspnet-baseline.
Thank you for all your clarifications.
After reading very carefully both the paper and the code, and thought about your comment, I have the following observations to do:
- The translation field of a Gripper is the coordinate of the grasp point in the image coordinate frame, isn't it?
- The offset of 2 cm should be equal to
hmin = -0.02
. - The depth can assume 4 values equal to
hmax_list=[0.01,0.02,0.03,0.04]
, but I do not understand why this value should be "the distance from the origin of gripper coordinate frame to the gripper tip". It seems to me, that this value is used only here, and then we take the height that produces the grasp with the highest score here. Moreover, there is no "gripper coordinate frame", what am I missing about the depth? What is its physical meaning? - If I want to modify the code in order to take into account my gripper geometry, I should modify:
- GRASP_MAX_WIDTH, in order to take into account my gripper max opening.
- finger_width and finger_lenght, for the collision detection.
- grasp_height, for the collision detection.
- hmin and hmax_list.
- I should modify the corresponding variables here, for a correct plot of the gripper.
Thanks for your kind.
from graspnet-baseline.
The translation field of a Gripper is the coordinate of the grasp point in the image coordinate frame, isn't it?
It should be camera coordinate frame, which is transformed from image coordinate frame using this function.
The depth can assume 4 values equal to hmax_list=[0.01,0.02,0.03,0.04], but I do not understand why this value should be "the distance from the origin of gripper coordinate frame to the gripper tip".
It is a definition, the translation of gripper tip is computed by the depth and grasp point.
If I want to modify the code in order to take into account my gripper geometry, I should modify:
......
hmin and hmax_list.
hmax_list is related to the depths sampled in grasp labels, which should not be modified.
from graspnet-baseline.
Thank you, it seems clearer to me now.
So, if I want to use this method for my experiments I have to modify only those variables that in the code refer to GRIPPER dimensions, is it correct?
These variables affect mainly the collision detection since the inference seems to be gripper independent, isn't it?
Thanks for your kindness.
from graspnet-baseline.
Yes, most of the gripper parameters are used in collision detection.
from graspnet-baseline.
Related Issues (20)
- Clarification on Scores within the Dataset HOT 1
- 对于6D grasp的一些疑问 HOT 4
- What's the usage of the function "process_grasp_labels" in the "label_generation.py" file ? HOT 3
- knn install error
- 训练时knn遇到错误 HOT 1
- About angles HOT 3
- 部署到真机 HOT 3
- List of objects in seen ans unseen test set HOT 4
- About grapenet-1billion full view point clouds HOT 1
- Is multi-GPU operation possible? HOT 1
- What is the unit of point coordinate?
- May I ask about how to use cam_pos parameters?
- About 256 shooting perspectives HOT 1
- data convention of `camera_poses.npy` in graspnet-1billion dataset HOT 3
- run command_demo.sh error HOT 3
- 代码中 ToleranceNet 好像是 (128, 128, 12) ? HOT 1
- How to generate scene collision labels for custom datasets? HOT 1
- Increasing GPU memory during training time: Cuda out for memory error HOT 1
- graspness运行test得到的ap值为什么比文章中的高那么多
- test.py AP比论文中的高不少 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graspnet-baseline.