This code is provided as-is and is for research purposes only. I would like to ask that you link to
http://www.cs.ucf.edu/~pscovann/ instead of hosting the code at another site. If you downloaded it
from anywhere other than http://www.cs.ucf.edu/~pscovann/, please go and download from there to ensure
the latest version.
This code has evolved significantly since it's initial publication. We hope that you enjoy the
additional work that has been put into it. It should be fairly straightforward, however here is a
premptive FAQ:
What parameters should I adjust?
All important parameters are in LoadParams.m. See this file and it's comments for an idea of what to
tweak.
Is this code for "x-y-z" 3D space data (MRI scans) or "x-y-t" spatio-temporal data (Video)?
Both
Where is the solid angle normalization discussed in the paper?
Due to the implementation of a tessellation based orientation histogram, solid angle normalization is
unesessary. This is due to the fact that in the tessellation all bins are equal in size.
Why has rotational invariance been removed?
In our application, action recognition, rotational invariance is less meaningful. Assuming the camera-
man is able to keep the camera upright and/or people don't develop the ability to walk up vertical
walls. In other applications rotational invariance may be important. I appologize if your research
depends on rotational invariance, this is on the long list of possible improvements for the future.
However, I would encourage you to add this ability yourself, and to send me the changes you made so
that I can make the option available to others.
I received the following message "MISS : Top 3 orientations within ~25 degree range : Returning with
reRun flag set." What is going on?
This is another improvement made to the method. 3DSIFT will refuse to generate a descriptor if it
finds the data at the given location is not descriptive enough. You can force 3DSIFT to return a
descriptor by setting TwoPeak_Flag = 0 in LoadParams.m. I would suggest that you instead write your
frontend in such a way that you can give 3DSIFT a new location if it returns reRun == 1.
How do I calculate descriptors at multiple scales?
This is best done by resizing your data before calling 3DSIFT. xyScale and tScale inputs are actually
more like resolution parameters than scale parameters.
没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
收起资源包目录
3DSIFT_CODE.7z (16个子文件)
3DSIFT_CODE
DemoScript.m 831B
DemoData.mat 3.98MB
buildOriHists.m 2KB
PlaceInIndex.m 426B
KeySample.m 2KB
Create_Descriptor.m 1KB
MakeKeypoint.m 793B
sphere_tri.m 7KB
README.txt 2KB
sphere_project.m 2KB
KeySampleVec.m 747B
GetGradOri_vector.m 1KB
AddSample.m 463B
LoadParams.m 833B
mesh_refine_tri4.m 4KB
NormalizeVec.m 114B
共 16 条
- 1
资源评论
optm215
- 粉丝: 0
- 资源: 1
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功