久久综合狠狠,欧美一区免费,国产精品自拍视频

ngaut — Tue, 24 May 2011 08:22:00 GMT

Joint positions and orientations are given in the real world coordinate system.The origin of the system is at the sensor. +X points to the right of the, +Y points up, and +Z points in the direction of increasing depth. The coordinate frame is shown in the figure above.
兌��的位�|�和方向依据于现实世界的坐标�pȝ��。坐标原点定位在Sensor。X轴的正方向是��Z��面对Sensor的右斏V��Y轴的正方向是朝上。Z轴的正方向是深度值增加的方向。（�l�合而看�Q�这是一个典型的��x��坐标�p�）

Joint positions are measured in units of mm.
兌��的位�|�是以毫�c��ؓ单位来衡量的�?/span>

Joint orientations are given as a 3x3 rotation (orthonormal) matrix. This represents a rotation between the joint's local coordinates and the world coordinates.
The first column is the direction of the joint's +X axis given as a 3-vector in the world coordinate system.
The second column is the +Y axis direction, and the third column is the +Z axis direction.
Our “neutral pose” is the T-pose shown in the figure above. In this pose, each joint's orientation is aligned with the world coordinate system. That is, its orientation is the identity matrix.
兌��的方向依据于一�?x3的旋转（正交�Q�矩��c��这个矩阉|��l�的是关节的局部坐标和世界坐标之间的旋转�?br />矩阵的第一列代表的是关节X轴的正方向，一个在世界坐标�p�里�?3-Vector.
矩阵的第二列代表的是兌��Y轴的正方向，矩阵的第三列代表的是兌��Z轴的正方向�?/span>
我们�?neutral pose"是一个T-姿势�Q�如上图所�C�。在�q�个姿势中，每个兌��的方向是一致的与世界坐标系。也��是��_��它的方向是单位矩��c�?br />

Known issues 已知问题

1. Arm tracking is less stable when the arm is close to other body parts, especially the torso. If both arms are close to the torso, as well as to each other, they might get mixed up.
在手臂脓�q��n体的其它部位�Ӟ��特别是躯�qԌ��Q�手臂跟�t�的�E�_��性会较差。如果双臂非常接�q�躯�q�以及对方的话，那么它们也可能会��h��在一赗��?br />

2. Leg tracking is still somewhat unstable and noisy. It works better when the user stands with legs separated. Fast motions and complex kicks or crouches might cause the tracking to fail.
腿的跟踪一直有一些不�E�_��和干扰。当用户把双腿分开站立�Ӟ��跟踪的效果会更好。快速的�q�动和复杂的�t�或�y�可能会��D��跟踪��p�|�?br />

3. Pose tracking may also become somewhat unstable if the head is not visible.
如果头是不可见的话，那么姿态跟�t�也会变得不�E�_��?br />

4. Arms and legs in extremely stretched positions (i.e. near the limits of human flexibility) might be lost by the tracker.
当手臂和腿处于极限拉伸的位置�Ӟ��比如辑ֈ�了�h体灵�z�L��的极限�Q�，可能会丢��p��t��?br />

5. If the skeleton is stuck in a faulty pose, or stuck facing the opposite direction, then returning to a “simple” pose (arms away from torso so the sensor can see them and legs separated) should help resolve it.
如果骨骼卡住在一个错误的姿态，或者面向相反的方向�Q�那么请回到一个简单的姿势�Q�如�Q�手臂远��躯�qԌ��双腿分开站立。）�q�些会帮助解册��卡住的问题�?br />

6. In general, very fast motions may cause tracking failure.
在一般情况下�Q�速度非常快的�q�动可能会导致跟�t�失败�?br />

7. In some cases, overall tracking might be bad. Re-calibrating the user may resolve the problem.
在某些情况下�Q�整体跟�t�的效果可能不太好。那么重�?Calibrating"会解决问题�?br />

来自�Q?/span>http://www.cnblogs.com/TravelingLight/archive/2011/04/18/2019887.html

ngaut 2011-05-24 16:22 发表评论

[转]openFramework, Tokyo Workshop

ngaut — Mon, 23 May 2011 05:48:00 GMT

openFramework, Tokyo Workshop

10 ��时的�R轮战

昨天上下午两场工作坊天壤之别�Q�上�?Zachary Lieberman 解说他的“艺术是对未来�?R&D, 是通力的合�? Do it with others”�Q�加上每�ơ都能见到的 Eyebeam 中心跟早已经��v来的 openFrameworks Lab, 老生长谈�Q�但每次看到 ofLab �q�会�l�箋��慕�Q�有一个场所可以�l�艺术家�Q�黑客，工程师和�U�学家把因搭档而来的脑力碰撞�{化�ؓ以艺术表达�ؓ诉求的实��c�?/p>

下午�?Advance section 变了个样�Q�开始最�q�基�?openFrameworks 的实际项目介�l�和�q�作讲解�Q�一个是为澳大利亚某会议制作的视觉系�l�，全部��q��序控制的��Z�� Data Visualization 概念�?VI �pȝ��Q�概念不新鲜但因��术家��n又有 Parsons The New School for Design 的背景支持，视觉呈现做的极其好；另一个与 NIKE 的合作项�?Paint With Your Feet �Q�添加了�?GPS 数据的支持，�l�箋数据可视化的概念但效果出众。联惛_��最�q?MIT 的新 LOGO�Q�事兌��觉系�l�呈现又对自我突破有要求的设计师�Q�学习��用程序来创作已经是必��要考虑的事了，�q�不是说�Ҏ��技能的掌握�Q�而是接受一个新的现实和��试�H�破�q�去�l�验和系�l�留下的限制�?/p>

Zachary Lieberman 公开了他�?Parsons 的两个授课课�E�网站，新的 http://algo.thesystemis.com/ 和稍旧的http://www.makingthingsmove.org/blog/�Q�有很多的例子可以参考，Parsons 学生很幸��?/p>

Kinect 做�ؓ一个已�l�渡�q�热潮的话题�Q�现在积累出来极多的案例�Q�Kyle McDonald �?Zach Lieberman �?NY ITP 春季期的评��用它在尝试制作廉��L�� 3D Scanner �q��用数据做 3D Printing�Q�这里有评�� blog 可以�?a style="text-decoration: none; color: #3f3f3f; ">http://3dsav.blogspot.com/�Q�新技术带来的��试能够带来最直观的感官刺�Ȁ�Q�而附着其后的，对亲�w�发赯��最重要的，是带来新的去探烦�Q�尝试和产出的机会，无论艺术创作�Q�设计实践还是学术的研究�Q�从而��出新的乐��?/p>

艺术家和设计师都在考虑着的东�?/strong>

比如之于设计师，��其是愿意扑�w�于�q�个�C�会�Q��h��去做最形而下��试的设计师�c�d��Q�这些早��出��C��正式成�ؓ设计与创作材料不久的东西�Q�给了我们去��试更深入探索的��Z��Q�无论是形而下的实施，�q�是之后可能会随之而来的�Ş而上的思考�?/p>

EyeWriter 是一个预�C�Z��新�Ş态设计的典型例子�Q�批量化生��?PS3 Camera 和可以提供从最低端自制化��Y件的 openFrameworks �l�合在一��P��为实现最廉�h同时也是因�ؓ设计师与工程师共同走完流�E�而把概念�Q�原型与使用者体验的��畅�l�合提供了可能。现在它成�ؓ了一个典范，��Z��最初兴��的但却在最大程度上��Z��设计，开源的但完成了一个机构的建立�?/p>

OF 007

让�h期待已久�q�迟没有发布的新版本 OF 007 也做了介�l�，�?OPENGL 的支持新��d��?ofxShader 库，让动画，3D 生成渲染�?OPENCV 有了更大的效能�{变。配�?Kinect �?OPENNI �?bug �q�很多，�Ҏ��崩溃。有了更好的 web server 的支持，�pȝ��文�g控制功能也做了补充，但跟 Processing 比�v来，那条能够融会贯通整个程序原型制作的�U�还不够明显�Q�对于非�E�序背景的�h而言�Q�目�?OF 依然是偏创作型的�Q�更适合让艺术家走向的�h完成作品原型�Q�而不是像 Processing 一样可以��够完成一个设计��品原型的��程�?/p>

ngaut 2011-05-23 13:48 发表评论

winaoe �W�记

ngaut — Thu, 20 Jan 2011 04:37:00 GMT
用gpxe启动�Ӟ��先用shell的dhcp net0 来获取dhcp信息�Q�然后用sanboot aoe:e0.0启动

ngaut 2011-01-20 12:37 发表评论

使用winpcap的程序遇到应用程序初始化��p�|时的处理

ngaut — Wed, 10 Nov 2010 01:58:00 GMT
很可能是npptools.dll的权限被��用了，打开权限的方法：
��盘格式为NTFS的，到SYSTEM32下找npptools.dll文�g�Q�点右键-安全(如果没有安全选项�Q�打开文�g多w��项�Q�里面有个简单共享，��L��)

ngaut 2010-11-10 09:58 发表评论

ngaut — Sat, 11 Sep 2010 02:39:00 GMT
卡巴斯基本��n安装了一个ndis中间层驱动，自己在ReceiveHandler中构造完整的包后提交�l�上层协议驱动，对于本��n有处理不完整包逻辑的驱动而已�Q�这部分逻辑不会走到�Q�所以测试ndis驱动最好安装和卸蝲卡巴斯基两种情况都测试下。另外现在的�|�卡驱动很少调用ReceiveHandler了，大部分都是调用ReceivePacketHandler�Q�比较老的8139�|�卡的驱动会调用ReceiveHandler�q�提供不完整的包�?img src ="http://m.shnenglu.com/ngaut/aggbug/126390.html" width = "1" height = "1" />

ngaut 2010-09-11 10:39 发表评论

NDIS�W�记-不要先入��Z��的烂兄NdisAllocateMemoryWithTag和烂弟NdisFreeMemoryWithTag

ngaut — Sat, 11 Sep 2010 02:34:00 GMT
最�q�对自己的一个驱动大改之后死�z�M��被加�?win xp)�Q�DriverEntry也进不了�Q�最后找到原因，竟然是NdisFreeMemoryWithTag惹得��，查了ddk才知道，NdisAllocateMemoryWithTag可以在ndis 5.1上用�Q�而NdisFreeMemoryWithTag要在ndis 6.2才能用，应该是系�l�加载驱动前扫描了这个函数发��C��兼容�Q�所以不加蝲驱动�?div>
NdisFreeMemoryWithTag
Versions: Supported for NDIS 6.20 drivers in Windows 7.

ngaut 2010-09-11 10:34 发表评论

[转]windbg与虚拟机调试�W�号文�g问题

ngaut — Sat, 11 Sep 2010 02:24:00 GMT

1搭徏环境 host机器windows xp sp2 ,安装 windbg, vmware 6 和调试的目标操作�pȝ�� vmware 中的gust。比如windows server 2003 sp2,
1)配置vmware seting 中添加com,
2)配置gust�?003中的com 115200 配置
3)boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard - DEBUG" /fastdetect /debug /debugport=com1 /baudrate=115200
4)配置host中windbg的启动参�?/p>
在快��h��式属性里讄��目标
"D:\Program Files\Debugging Tools for Windows\windbg.exe" -k com:port=\\.\pipe\com_1,baud=11520,pipe
5)安装�W�号文�g在host机器�?也就是要安装目标�?003的符��h��?http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx��面选择版本下蝲安装)在本机xp�?路径自己讄��,比如装在D:\windows\symbol2003
2启动
1�Q?启动vmware中的gust�Q�选择debug�Q�不要按回�R.
2�Q?启动windbg 配置symbols file为安装好的符��h��件�\径。该路径是在host机器上安装的对应target操作�pȝ��的符��h��件�\径。也��是guest操作�pȝ��版本�c�d��的符��h��Ӟ��比如我们目标机器是windows 2003 sp2�Q�那么我们在本机windows xp上就应该安装windows 2003 sp2的符��h��件。这�?windbg的帮助里有讲�?该符��h��件从微��Y官方�|�站上下�? 启动后windbg处于reconnect状�?.
set symbol path 中输�?/p>
SRV*D:\Windows\Symbols2003*http://msdl.microsoft.com/download/symbols
其中D:\Windows\Symbols2003为符号安装的路径
路径讄��错误的话会显�C?** ERROR: Symbol file could not be found
3)�q�入vmware在guest按回车进入guest�pȝ��.

ngaut 2010-09-11 10:24 发表评论

ngaut — Wed, 08 Sep 2010 02:43:00 GMT
代码参考aoe
#define htons(x) (USHORT)((((x) << 8) & 0xff00) | (((x) >> 8) & 0xff)) #define ntohs(x) (USHORT)((((x) << 8) & 0xff00) | (((x) >> 8) & 0xff)) #define AOEPROTOCOLID 0x88a2 VOID ProtocolTransferDataComplete(IN NDIS_HANDLE ProtocolBindingContext, IN PNDIS_PACKET Packet, IN NDIS_STATUS Status, IN UINT BytesTransferred) { PNDIS_BUFFER Buffer; UINT HeaderSize, DataSize; PUCHAR Data = NULL; PEH_HEADER Header = NULL; //通过包描�q�符的NDIS_BUFFER链表的表头取得包的剩余部分的NDIS_BUFFER描述�W? 见ProtocolReceive函数 NdisUnchainBufferAtFront(Packet, &Buffer); if (Buffer != NULL) { //得到包的剩余部分的内存地址和大��?/span> NdisQueryBuffer(Buffer, &Data, &DataSize); NdisFreeBuffer(Buffer); } else { DBGPRINT(("ProtocolTransferDataComplete Data (front) Buffer == NULL\\n")); } //通过包描�q�符的NDIS_BUFFER链表的表��֏�得包的剩余部分的NDIS_BUFFER描述�W? 见ProtocolReceive函数 NdisUnchainBufferAtBack(Packet, &Buffer); if (Buffer != NULL) { ////得到包头的内存地址和大��?/span> NdisQueryBuffer(Buffer, &Header, &HeaderSize); NdisFreeBuffer(Buffer); } else { DBGPRINT(("ProtocolTransferDataComplete Header (back) Buffer == NULL\\n")); } if (Header != NULL && Data != NULL) { DBGPRINT(("完整包大��ؓ%d", HeaderSize + DataSize)); } //AoEReply(Header->SourceMac, Header->DestinationMac, Data, DataSize); if (Header != NULL) ExFreePool(Header); if (Data != NULL) ExFreePool(Data); NdisFreePacket(Packet); } NDIS_STATUS ProtocolReceive(IN NDIS_HANDLE ProtocolBindingContext, IN NDIS_HANDLE MacReceiveContext, IN PVOID HeaderBuffer, IN UINT HeaderBufferSize, IN PVOID LookAheadBuffer, IN UINT LookaheadBufferSize, IN UINT PacketSize) { PADAPTER Context = (PADAPTER)ProtocolBindingContext; NDIS_STATUS Status; PNDIS_PACKET Packet; PNDIS_BUFFER Buffer; PEH_HEADER Header; PUCHAR HeaderCopy, Data; UINT BytesTransferred; DBGPRINT(("ProtocolReceive\\n")); if (HeaderBufferSize != sizeof(ETH_HEADER)) { DbgPrint("ProtocolReceive HeaderBufferSize %d != sizeof(HEADER) %d\\n"); return NDIS_STATUS_NOT_ACCEPTED; } Header = (PEH_HEADER)HeaderBuffer; /* if (ntohs(Header->EthType) != AOEPROTOCOLID) return NDIS_STATUS_NOT_ACCEPTED; */ if (LookaheadBufferSize == PacketSize) { //AoEReply(Header->SourceMac, Header->DestinationMac, LookAheadBuffer, PacketSize); return NDIS_STATUS_SUCCESS; } //不完整的�?/span> DBGPRINT(("不完整的�?/span>")); //分配内存把包头保存包�?/span> if ((HeaderCopy = (PUCHAR)ExAllocatePool(NonPagedPool, HeaderBufferSize)) == NULL) { DbgPrint("ProtocolReceive ExAllocatePool HeaderCopy\\n"); return NDIS_STATUS_NOT_ACCEPTED; } RtlCopyMemory(HeaderCopy, HeaderBuffer, HeaderBufferSize); //分配内存保存包的剩余部分 if ((Data = (PUCHAR)ExAllocatePool(NonPagedPool, PacketSize)) == NULL) { DbgPrint("ProtocolReceive ExAllocatePool HeaderData\\n"); ExFreePool(HeaderCopy); return NDIS_STATUS_NOT_ACCEPTED; } //分配一个包描述�W?/span> NdisAllocatePacket(&Status, &Packet, Context->RecvPacketPoolHandle); if (!NT_SUCCESS(Status)) { DBGPRINT(("ProtocolReceive NdisAllocatePacket", Status)); ExFreePool(Data); ExFreePool(HeaderCopy); return NDIS_STATUS_NOT_ACCEPTED; } //分配一个NDIS_BUFFER描述�W�，兌��内存Data NdisAllocateBuffer(&Status, &Buffer, Context->RecvBufferPool, Data, PacketSize); if (!NT_SUCCESS(Status)) { DBGPRINT(("ProtocolReceive NdisAllocateBuffer (Data)", Status)); NdisFreePacket(Packet); ExFreePool(Data); ExFreePool(HeaderCopy); return NDIS_STATUS_NOT_ACCEPTED; } //卛_��q�个NDIS_BUFFER攑ֈ�包描�q�符的NDIS_BUFFER链表的表�?/span> NdisChainBufferAtFront(Packet, Buffer); //在分配一个NDIS_BUFFER描述�W�，兌��内存HeaderCopy NdisAllocateBuffer(&Status, &Buffer, Context->RecvBufferPool, HeaderCopy, PacketSize); if (!NT_SUCCESS(Status)) { DBGPRINT(("ProtocolReceive NdisAllocateBuffer (HeaderCopy)", Status)); NdisUnchainBufferAtFront(Packet, &Buffer); NdisFreeBuffer(Buffer); NdisFreePacket(Packet); ExFreePool(Data); ExFreePool(HeaderCopy); return NDIS_STATUS_NOT_ACCEPTED; } //��描�q�包头的NDIS_BUFFER攑ֈ�包描�q�符的NDIS_BUFFER链表的尾节点 NdisChainBufferAtBack(Packet, Buffer); NdisTransferData(&Status, Context->BindingHandle, MacReceiveContext, 0, PacketSize, Packet, &BytesTransferred); if (Status != NDIS_STATUS_PENDING) ProtocolTransferDataComplete(ProtocolBindingContext, Packet, Status, BytesTransferred); return Status; }

ngaut 2010-09-08 10:43 发表评论

ngaut — Thu, 26 Aug 2010 14:24:00 GMT
如果遇到�q�个问题�Q?div>/patch.exe -p1 < xx.patch
Assertion failed: hunk, file ../patch-2.5.9-src/patch.c line 354
可以用这个命令来patch
patch -i xx.patch --verbose --binary

ngaut 2010-08-26 22:24 发表评论

其实用dllexport导出函数和用.def文�g导出函数是不一��L��

ngaut — Thu, 15 Jul 2010 14:37:00 GMT
如题

ngaut 2010-07-15 22:37 发表评论