sIEve帮助文档

 

sIEve

sIEve is a project to get rid of memory leaks due to some limitations of the garbage collector in Internet Explorer. Executing AJAX kind of applications (like Cordys Explorer) will stress the browser heavily. Internet Explorer is not very strong in Memory Management. With other words; It is very easy to introduce serious memory leaks in Internet Explorer by executing JavaScript and DHTML manipulation.

Main Dialog

Back: Going back in browser history (not yet tested)

previous: Going forward in browser history (not yet tested)

Adress: The URL to Navigate (Last visited URL will be kept in Registry and will be restored when you restart sIEve

GO: Navigate to the URL in Address field. (Also the default button if you press 'Enter')

about:blank: unloads the current page. giving a blank screen. This is extremely usefull to find leaks after page is unloaded. If you press the Show in Use button after pressing the about:blank button then you see all the real leaks (DOM elements which are not freed or garbage collected by IE.

IE Browser control: In this area the webpage’s will be loaded and shown.

Auto Refresh: The current URL will be automatically refreshed. In the memory samples list and graph you can observe if there are still leaks in your application. The ‘Auto Refresh’ button will change into ‘Stop’ to cancel the auto refesh mode.

Clear in use: The current list of registered DOM elements in use will be cleared. Actually the Items will be hidden from the ‘Elements in Use’ Dialog.

Show in use: A (modeless) dialog will be opened to show all DOM elements currently in use. If the dialog was already open the list on the dialog will be refreshed. Elements which are cleared from the list by usage of the ‘Clear in Use’ button will not be showed again unless there is an increase in the number of references to the particular hidden elements. (IE when the elements refcounter is increased, in fact it is a new element in use which can cause a leak. The Dialog Stays open so you can press again and again the ‘Show In use’ button. The dialog also contains the same ‘Clear inUse / show in use / show leaks’ buttons. The buttons on that dialog has the same functionality as their counterparts on the main dialog.

Show Leaks: A (modeless) dialog will be opened to show all known leaks until now. Old leaks will remain on the list and never cleared. However you can distinghish new leaks form old leaks. (Colors and document id’s are used to distinguish)

Memory Samples List: This list will contain the last known (200) memory samples. The VM size (virtual memory) is reported in the list. Pressing the ‘Go’ button or the ‘Auto Refresh’ button will clear the memory samples list. Green lines indcates memory reduction; Red lines indicates increase; Black lines indicates no change in memory usage since previous sample.

Usage: Working Set size of physical used memory in Kilobytes (KB)

Delta: Difference in memory usage since previous sample in Kilobytes (KB)

Avg: The average of Delta’s in Kilobytes (KB). Notice that this figure only gives some indication. Big fluctuations in memory usage can give unpredictable results.

#inUse: The actual number of registered DOM Elements by the sIEve tool.

#hidden: The actual number of hidden DOM Elements from the list due to usage of the ‘Clear in Use’ button

Memory Samples History: A graph showing all values from the ‘Usage’ column in the memory Samples List. However this graph will never be cleared. (So take care ‘sIEve’ has a (relative) small memory leak due to the unlimited size of the history.

Slow/Fast/Paused: The update speed of the Memory Samples History Graph and List. Slow = 5 seconds; Fast = 1 Second; Paused = no updates;

Help: Opens new IE Browser window with help information.

Log Defect: Opens new IE Browser window where you can log any issue (Don’t forget to log-in or specify your name, that will be easier for giving feedback by the developers of the tool.

[ edit]

Elements in Use / Leaks Dialog

This dialog will be shared for 2 functions: Showing all elements in use and showing all known leaks. The dialog is modeless you can keep it open. Red lines means that the item is new in the list since previous report; Blue lines means that the Element is not new in the list but the reference counter is increased since last report. Green lines means that the element is freed (Refs = 0) (However currently this feature is not used since freed elements will just be removed from the list)

List Control: Showing Elements with a number of properties per element. You can sort the list on any column (except the OuterHTML column is not sortable)

#: Auto generated Sequence number of registered element

doc: Auto generated Sequence number of registered (owner) document of the particular element. This is useful to view and distinguish leaks of several runs of the same URL.

URL: Source url of the element

Refs: Number of references to the DOM Element.

Tag: The DOM node name of the registered DOM Element

ID: The DOM id property value

Orphan: if the value in this column is “Yes” then the element is not attached to the document.body. IE then it is a orphan node. In IE this Elements can leak as well so special care should be taken on this kinds of elements. For example clearing/setting the innerHTML of orphan nodes will cause pseudo leaks. Also orphan nodes will not fire ‘onpropertychange’ events.

Leak: If the element is a know leak then the value in this column is ‘Yes’. This is only possible in combination with Running Document = “No” (the next column)

Running: Indicates if a document is running. As soon a webpage will exit

outerHTML: Showing the outer HTML. (limited to 200 bytes to avoid memory blow up of sIEve)

Address: Currently not used (was used for low level memory allocs, which feature is currently disabled In sIEve)

Size: Currently not used (was used for low level memory allocs, which feature is currently disabled In sIEve)

properties: Opens a new modal dialog showing all the (expando) properties of the DOM element.

Clear in Use: Same as in main dialog

Show in Use: Same as in main dialog

Show Leaks: Same as in main dialog

Copy: Copy list into clipboard

# Items: Number of items showed in the list

New Item: A red line means: First time the items is showed in the list; If you do some actions in the webpage and you press again the ‘Show in Use’ button then all the existing elements in the list become black and all the new elements in use are reported in red.

No change: A black line means there is no change since previous report

Increased refcount: A blue line means: Item is not new but the reference count to the element in increased since previous report

Decreased refcount: A green line means: Item is not new but the reference count to the element in decreased since previous report

Close: Hide the dialog (can be opened again) 

 

内容概要:本文介绍了一个基于多传感器融合的定位系统设计方案,采用GPS、里程计和电子罗盘作为定位传感器,利用扩展卡尔曼滤波(EKF)算法对多源传感器数据进行融合处理,最终输出目标的滤波后位置信息,并提供了完整的Matlab代码实现。该方法有效提升了定位精度与稳定性,尤其适用于存在单一传感器误差或信号丢失的复杂环境,如自动驾驶、移动采用GPS、里程计和电子罗盘作为定位传感器,EKF作为多传感器的融合算法,最终输出目标的滤波位置(Matlab代码实现)机器人导航等领域。文中详细阐述了各传感器的数据建模方式、状态转移与观测方程构建,以及EKF算法的具体实现步骤,具有较强的工程实践价值。; 适合人群:具备一定Matlab编程基础,熟悉传感器原理和滤波算法的高校研究生、科研人员及从事自动驾驶、机器人导航等相关领域的工程技术人员。; 使用场景及目标:①学习和掌握多传感器融合的基本理论与实现方法;②应用于移动机器人、无人车、无人机等系统的高精度定位与导航开发;③作为EKF算法在实际工程中应用的教学案例或项目参考; 阅读建议:建议读者结合Matlab代码逐行理解算法实现过程,重点关注状态预测与观测更新模块的设计逻辑,可尝试引入真实传感器数据或仿真噪声环境以验证算法鲁棒性,并进一步拓展至UKF、PF等更高级滤波算法的研究与对比。
内容概要:文章围绕智能汽车新一代传感器的发展趋势,重点阐述了BEV(鸟瞰图视角)端到端感知融合架构如何成为智能驾驶感知系统的新范式。传统后融合与前融合方案因信息丢失或算力需求过高难以满足高阶智驾需求,而基于Transformer的BEV融合方案通过统一坐标系下的多源传感器特征融合,在保证感知精度的同时兼顾算力可行性,显著提升复杂场景下的鲁棒性与系统可靠性。此外,文章指出BEV模型落地面临大算力依赖与高数据成本的挑战,提出“数据采集-模型训练-算法迭代-数据反哺”的高效数据闭环体系,通过自动化标注与长尾数据反馈实现算法持续进化,降低对人工标注的依赖,提升数据利用效率。典型企业案例进一步验证了该路径的技术可行性与经济价值。; 适合人群:从事汽车电子、智能驾驶感知算法研发的工程师,以及关注自动驾驶技术趋势的产品经理和技术管理者;具备一定自动驾驶基础知识,希望深入了解BEV架构与数据闭环机制的专业人士。; 使用场景及目标:①理解BEV+Transformer为何成为当前感知融合的主流技术路线;②掌握数据闭环在BEV模型迭代中的关键作用及其工程实现逻辑;③为智能驾驶系统架构设计、传感器选型与算法优化提供决策参考; 阅读建议:本文侧重技术趋势分析与系统级思考,建议结合实际项目背景阅读,重点关注BEV融合逻辑与数据闭环构建方法,并可延伸研究相关企业在舱泊一体等场景的应用实践。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值