urg user guide

Unified Coverage Reporting User Guide

Version X-2005.12

December 2005

Comments?

E-mail your comments about this manual to vera_support@https://www.sodocs.net/doc/a117081840.html,

Copyright Notice and Proprietary Information

Copyright 2005 Synopsys, Inc. All rights reserved. This software and documentation are owned by Synopsys, Inc., and furnished under a license agreement. The software and documentation may be used or copied only in accordance with the terms of the license agreement. No part of the software and documentation may be reproduced, transmitted, or translated, in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without prior written permission of Synopsys, Inc., or as expressly provided by the license agreement.

Right to Copy Documentation

The license agreement with Synopsys permits licensee to make copies of the documentation for its internal use only. Each copy shall include all copyrights, trademarks, service marks, and proprietary rights notices, if any. Licensee must assign sequential numbers to all copies. These copies shall contain the following leg-end on the cover page:

“This document is duplicated with the permission of Synopsys, Inc. for the exclusive

use of __________________________________________ and its employees. This

is copy number __________.”

Destination Control Statement

All technical data contained in this publication is subject to the export control laws of the United States of America. Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader’s responsibility to determine the applicable regulations and to comply with them.

Disclaimer

SYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR-RANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Trademarks

Synopsys, the Synopsys logo, Arcadia, BiNMOS-CBA, CMOS-CBA, COSSAP, DESIGN (ARROWS), DesignPower, DesignWare, dont_use, EPIC, ExpressModel, in-Sync, LM-1000, LM-1200, Logic Modeling, Logic Modeling (logo), Memory Architect, ModelAccess, ModelTools, PathMill, PL debug, RailMill, SmartLicense, SmartLogic, SmartModel, SmartModels, SNUG, SOLV-IT!, SourceModel Library, Stream Driven Simulator, Synopsys, Synopsys (logo), Synopsys VHDL Compiler, Synthetic Designs, Synthetic Libraries, TestBench Manager, and TimeMill are registered trademarks of Synopsys, Inc

3-D Debugging, AMPS, Behavioral Compiler, CBA Design System, CBA-Frame, characterize, Chip Architect, Compiled Designs, Core Network, Core Store, Cyclone, Data Path Express, DataPath Architect, DC Expert, DC Expert Plus, DC Professional, DelayMill, Design Advisor, Design Analyzer, Design Compiler, DesignSource, DesignTime, DesignWare Developer, Direct RTL, Direct Silicon Access, dont_touch, dont_touch_network, ECL Compiler, ECO Compiler, Embedded System Prototype, Floorplan Manager, Formality, FoundryModel, FPGA Compiler, FPGA Express, Frame Compiler, General Purpose Post-Processor, GPP, HDL Advisor, HDL Compiler, Integrator, Interactive Waveform Viewer, Library Compiler, LM-1400, LM-700, LM-family, Logic Model, ModelSource, ModelWare, Module Compiler, MS-3200, MS-3400, Power Compiler, PowerArc, PowerGate, PowerMill, PrimeTime, RTL Analyzer, Shadow Debugger, Silicon Architects, SimuBus, SmartCircuit, SmartModel Windows, Source-Level Design, SourceModel, SWIFT, SWIFT Interface, Synopsys Graphical Environment, Test Compiler, Test Compiler Plus, Test Manager, TestSim, Timing Annotator, Trace-On-Demand, VCS, VCSi, VHDL System Simulator, VirSim, Visualyze, Vivace, VSS Expert, and VSS Professional are trademarks of Synopsys, Inc.

Linux is a registered trademark of Linus Torvalds used by permission.

All other product or company names may be trademarks of their respective owners.

Unified Coverage Reporting User Guide, Version X-2005.06 2

Contents

1.Unified Coverage Reporting

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 Generated Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 Common Elements for all pages . . . . . . . . . . . . . . . . . . . . . . .1-5 Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7 "hierarchy" File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8 "modlist" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10 "groups" File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11 "tests" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12 "modN" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13 "grpN" File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15 Assertions and Property Coverage Reports . . . . . . . . . . . . . .1-17 Coverage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18 Common Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18 Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20 T oggle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20 Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-22

1

FSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-22 Assertions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-24 T estbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-25 Coverage Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26 Grading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26 Grading and the -scorefile Option . . . . . . . . . . . . . . . . . . . . . .1-27 Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28 Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28 Coverage T ypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29 Controlling the Report Format. . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29 Grading and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-30 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-31 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-32

2

1

Unified Coverage Reporting

The Unified Report Generator (URG) generates combined reports for

all types of coverage information. The reports may be viewed through

the design hierarchy, module lists, coverage groups, or through an

overall summary "dashboard" for the entire design/testbench. The

reports consist of a set of HTML or text files.

The HTML version of the reports take the form of multiple interlinked

HTML files. For example, a "hierarchy.html" page shows the design's

hierarchy and contains links to individual pages for each module and

its instances.

The HTML file that the URG writes can be read by any web browser

that supports CSS (Cascading Style Sheets) level 1, which includes

Internet Explorer (IE) 5.0 and later versions, any version of Opera,

and the later versions of Netscape.

Unified Coverage Reporting

1-1

Note:For the Vera X-2005.12 release, only testbench and assertion coverage are supported. Assertion and Code coverage is not

supported by Vera alone, but requires that you also use either

ovasim or VCS.

To invoke URG, enter the urg command and specify the directories

containing coverage data files.

?Testbench and assertion coverage data are written to the *.vdb directory

?Code coverage data is written to a *.cm directory

For all three types of coverage, you invoke URG as follows:

% urg -dir simv.cm simv.vdb

Data files are grouped into tests based on the names of the files. So

if you have:

./simv.vdb/snps/coverage/db/testdata/test1

./simv.cm/coverage/verilog/test1.db

./simv.cm/coverage/vhdl/test1.db

./simv.vdb/fcov/test1.db

All of these files will be considered data for 'test1'.

The reports generated by URG are placed in a directory (by default

this is "urgReport" in the working directory). The reports consist of a

set of HTML or text files. Each time URG is run, the report directory

and all of its contents are removed and replaced by the new report

files.

Unified Coveage Reporting

1-2

Features

URG includes reporting for the following metrics:

?Code coverage

-line

-condition

-toggle

-FSM

?Assertions

?Testbench

Note: You can only report on code or assertion coverage if you use VCS code or assertion coverage to collect data.

Path, assigntgl, and branch coverage are not supported. No

sub-options for these features are supported in this version.

The following report pages are generated as .html or .txt files:

?dashboard

?hierarchy

?modlist

?groups

?modN.html or modinfo.txt

?grpN.html or grpinfo.txt

Unified Coverage Reporting

1-3

1-4

Unified Coveage Reporting

?

asserts ?

assertcategories ?

assertseverities ?

assertcomplexities ?

assertdensities ?tests

The following options are supported:

Table 1-1. URG Options Option

Description Comments -dir directory_name Specifies coverage data directories

-metric line+cond+fsm+tgl+assert+tb Limit report to specified metric(s)

-show text

Generate text report (not HTML) -cond exclude filename

Specify excluded conditions condition coverage only -cond ids

Show condition ids in generated report -cond nocasedef

Exclude case default from condition reports -fsm disable_sequence

Do not show fsm sequences fsm coverage only -fsm disable_loop

Do not show fsm sequences containing loops -line nocasedef

Exclude case default from line coverage reports line coverage only -show tests

Show the tests that covered each line and condition line & condition coverage -show maxtests N

Specify the maximum number of tests with "-show tests"-grade goal timelimit

Grade tests (see page 26) -scorefile filename Allows user to specify different weight to each metric

1-5Unified Coverage Reporting Generated Files

Common Elements for all pages

Coverage data boxes are used throughout the URG report pages. These are tables containing one box for each type of coverage. An example of a text version of the report is as follows:

Score Line Cond Toggle FSM Assert Testbench 46.15 87.08 40.11 20.24 -- 50.00 33.33-report mydir

Generates report in mydir instead of default directory -help and -h

Shows command line and options supported by URG -log filename

Sends diagnostics to filename instead of stdout/stderr -split N Controls how large files are allowed to become before being split.The argument

is an integer specifying the maximum

size in bytes for any generated file. This

number is used as a guideline, not an

absolute limit. The default is 200kb.

-dbname argument

Generate merged data files using argument Table 1-1. URG Options

Option

Description Comments

The HTML version includes color-coded boxes, or cells left empty if

no coverage data for the coverage type represented by the box was

collected. For example:

The first box shown is the overall score for all metrics. By default, this

is the simple average of all the metric percentages. You can control

the way the score is computed with the -scorefile option (see

“Grading and the -scorefile Option” on page 1-27).

In this example we collected Line, Condition, Toggle, Assertion and

Testbench coverage. FSM coverage was turned on, but no FSMs

were found in this region.

The Line box is green because it falls into the upper range of target

values. Values display in a range of 11 colors from red (low) to green

(high) as shown below. These colors are graduated every 10

percentage points (with 100 being the 11th class).

All generated pages contain a common navigation menu at the top.

This menu allows you to go directly to any of the main pages, including

the hierarchy, modlist, groups, dashboard, or tests files. It is a simple

list of the top-level pages, plus a legend showing the cutoff

percentages for each color:

Unified Coveage Reporting

1-6

1-7Unified Coverage Reporting

Dashboard

The dashboard page is the top-level view of all coverage data. It includes the coverage data boxes for the database as a whole. Note that you can weight the coverage score in various ways. For example, 60% assertions coverage may be much worse than 25% condition coverage.

The following is an example of a dashboard report. Note: The underlined words: "dashboard," "group," "tests" and

"asserts" are hyperlinks in this example

"hierarchy" File

This file contains an indented list of all module, interface, and

component instances in the design. The indentation corresponds to

the design tree - children are indented underneath their parents.

Note: The following examples are shown in HTML. The text versions of these pages contain the same content, but are missing the

hyperlinks and color.

The coverage data boxes for each instance in hierarchy.html shows

the total coverage information for the subtree rooted at the instance.

The name of the instance is linked to its part of its module's modN.html

page. Each metric in the coverage data box is linked to the

corresponding section of the module instance's data in the modN.html

page.

A section from an example hierarchy.html page is shown below. The

data shown in the hierarchy pages is the cumulative coverage for the

entire sub-tree rooted at each instance. So, the coverage shown for

MMRK0 is the coverage for that instance, plus the coverage for

Unified Coveage Reporting

1-8

DELAY_MOD and ovac_CHKR. To see the coverage for the instance MMRK0 alone, click on it to go to the instance report.

A hierarchy may be broken into multiple pages. When this happens, you can click on 'subtree' to see the elided part of the design.

If an entire subtree in the design has no coverage data, the instances in that subtree will not have links to modN.html pages. They will still be shown in hierarchy.html but there will be empty coverage data boxes.

Unified Coverage Reporting

1-9

If a particular instance itself has no coverage data, but one of its

children or other descendents does, it will have a link to a modN.html

page. This way, you can still traverse through the coverage data

through the modN.html page to the children or parents.

If there is no design coverage information, no hierarchy will be shown.

The hierarchy page will not be generated and the "hierarchy" link will

not be underlined.

"modlist" File

The modlist.html file contains a flat list of all modules, entity/

architectures, and interfaces in the design. The module (or entity, or

interface) names link to the corresponding modN.html page. The

entries in the list are similar to those in hierarchy.html, but there is no

indentation, and the labels are module names rather than instance

names. The coverage data boxes show the accumulated coverage

information for all instances of the module (or entity/architecture, or

interface).

List entries in modlist.html are sorted in "worst-first" order. That is,

the first module (or entity, or interface) shown will be the one with the

worst overall coverage score. The next are ones with better coverage,

ultimately followed by the one with the best coverage. Following all

these are the module (or entity, or interface) entries for which there

is no coverage information.

Unified Coveage Reporting

1-10

In the example below, the module TR has no line, condition or assertion coverage information. Note that the modules are listed in worst-first order based on total coverage score.

If there is no design coverage information, no module list will be shown. The hierarchy page will not be generated and the "modlist" link will not be connected.

"groups" File

The file groups.html contains a flat list of coverage group definitions with coverage data boxes. The data boxes show the coverage information for the coverage group.

As in the modlist.html page, all groups in the groups.html page will be shown in "worst-first" order.

Unified Coverage Reporting

1-11

The link from each group leads to a grpN.html page.

The following example shows three coverage groups as they would

be displayed in the groups.html page.

If there is no testbench coverage information, no groups will be

shown. The groups page will not be generated and the "groups" link

will not be underlined.

"tests" File

This page lists, in score order, all tests whose coverage data was

loaded to generate the report. Tests are listed in overall coverage

score in best-first order, unless the report was produced with grading,

in which case they are listed in graded order (see “Grading and

Analysis” on page 1-30). There will always be at least one test in the

tests.html page.

Unified Coveage Reporting

1-12

When testbench coverage is enabled, the simulation and random seed information is shown in the tests.html page:

"modN" File

Each modN.html file contains the summary coverage information for a module, entity/architecture, or interface. Unless the file has been split for size, it also contains coverage information for each of the instances of the module (if it is very large, or has a large number of instances, the data for each instance and for the module itself is put in a separate modN_M.html file).

Each modN.html file has a header section and a coverage data section. The header section contains the name of the module and a list of the self-instances of the module. The self-instances are listed in "worst-first" order by overall coverage score.

Coverage data boxes are shown for the module summary information and for each of its instances so users can see the status of each. The

Unified Coverage Reporting

1-13

coverage data boxes for the self instances are smaller than that for

the module.

The self-instance links go to the module instance information for each

instance. These are the same links as from the hierarchy.html page

for each of the instances.

The module instance sections also have header and coverage data

sections. The header is similar to the module header, but instead of

source file and self instance lists, links to the parent instance and to

child instances are shown.

Smaller coverage data boxes are shown for the module summary

information, the parent, and each child of the module instance. The

Unified Coveage Reporting

1-14

names of each of these relatives is a link to the respective module or module instance report.

As for all report pages, the coverage data boxes are linked to the corresponding coverage reports. For example, clicking on "Line" in the above example would display the line coverage information for the module instance "DUT.KPU0.MA.arbfGRLNK2". These links are convenient for movement within a modN.html page, and are also the only way to view the coverage data reports if the modN.html page has been split for size.

"grpN" File

Each grpN.html page will have a similar outline to the modN.html pages. There will be a header for each coverage group, giving its name, and list of instances. Both sections will have the appropriate data boxes linking to coverage data reports.

Unified Coverage Reporting

1-15

The header for a group shows the group's name, coverage, goal, and

weight, along with smaller data boxes for each of its children. Each

coverage group then contains a statistics table for variables and

another for crosses showing the overall coverage for each variable

and cross, as shown in the figure below.

The names of the variables and crosses in these tables are linked to

their details.

Group instances have similar headers, with a link to the group

summary information rather in place of the list of instances. Group

instances have statistics tables and detailed reports in the same

Unified Coveage Reporting

1-16

人文社科软件用户手册_userguide2016

全国普通高等学校人文社会科学研究管理系统（校级网络版V2016版） 简要操作说明 所有：中国高校人文社会科学信息网 https://www.sodocs.net/doc/a117081840.html, 2016年11月

第一章系统简介 1.系统概述 全国普通高等学校人文社会科学研究管理信息系统（RPMS），采用先进的Java软件技术开发，以支持多用户协同工作的B/S（浏览器/服务器）架构运行。功能上，面向教育部人文社会科学年度统计要求，可便捷、完整的录入相关基础数据，并严格按照统计规自动生成统计报表，从而保障人文社会科学统计工作的顺利进行。同时系统还可以有效支持学校的日常科研管理工作，成为高校科研管理工作的辅助平台。 2.版本情况 全国普通高等学校人文社会科学研究管理信息系统（RPMS）分为省级版与校级版两个版本。其中校级版，供各高校用户使用，进行校级的数据录入，报表生成，以及数据上报；省级版，供各省、自治区、直辖市教育厅及教委用户使用，用于汇总各高校上报的数据文件，生成省级报表及省级上报文件。 省级版与校级版系统，每年年末均会根据当年的统计报表制度要求及功能改进设计，发布一个当年的新版本。但每个新版系统，都会保证校级版数据的兼容与延续性，上一版本中的数据，一定可以完整的移植到新版系统中。 为此，各高校可随时进行基础数据的录入与调整工作，无须待到统计工作开始了，新版系统发布后，再进行突击性录入。

第二章 2016及2016SP1版新特点 1.功能改进 1.1网页样式 将网页页面加宽，改为面向1024X768像素屏幕分辨率进行设计，并调整了色调。 1.2新增办学性质字段 1.3调整了研究机构的机构类型与组成方式

BolztrapUserGuide

Chapter1 BoltzTraP This package contains the program Boltz mann Tra nsport P roperties(BoltzTraP)for calculat-ing the semi-classic transport coe?cients.It can be obtained from www.icams.de/boltztrap. The program has documented in https://www.sodocs.net/doc/a117081840.html,mun.[1]If you publish results obtained using the program this paper should be sited. The program was originally interfaced to the WIEN2k code,but can easily be interfaced to other bandstructure codes.Marcos Alves and Matthieu Verstraete have provided Siesta and ab-init interfaces.This?le format is documented at the end of this?le.Please contribute if you make such an interface. 1.1Getting started 1.1.1Unpacking Run the command bunzip2BoltzTraP.tar.bz2;tar xvf BoltzTrap.tar This will unpack several directories src The source code test Example?les,Al,Bi2Te3and CoSb3 doc This?le util A perl script to gather WIEN energy?les 1

IMM User Guide

IMM使用指南 一．如何访问IMM (1) 二．IMM主要功能介绍 (4) 三．几个常用功能 (5) 1．远程开关机 (5) 2．通过IMM刷新服务器的UEFI/IMM微码 (6) 3．远程终端功能 (7) 一．如何访问IMM 通常主机后部有一个专用的管理端口，例如下图以3650M3为例，可以通过此端口访问IMM。 IMM管理端口默认IP：192.168.70.125 用户名：USERID 密码：PASSW0RD 注意字母为大写，密码中的“0”是数字0 在UEFI中修改IMM的IP地址 在开机自检的过程中根据提示按F1进入UEFI设置，

输入需要修改的IP地址后，选择Save Network Settings

在IE中输入IP地址即可访问IMM管理界面

二．IMM主要功能介绍 System status 查看服务器的健康状况，包括温度、电压和风扇状态等。 Virtual Light Path 查看服务器光通路诊断板上是否有告警。 Event Log 可以查看服务器的日志信息，可以用Save Log as Text File另存日志信息为文本文件。 Vital Product Data 查看服务器的型号序列号及各种微码版本。 Power/Restart 通过IMM控制开关服务器，包括定时开关机功能 Remote Control 远程控制服务器终端，需要添加IBM Virtual Media Key选件来实现此功能，大部分机型标配没有此选件。 PXE Network Boot 设置服务器的PXE启动。 Firmware Update

刷新服务器的UEFI和IMM的微码。 System Settings 设置IMM的时间日期，名字等基本信息。 Login Profiles 为IMM添加除默认之外的其他用户。 Alerts 设置snmp告警等信息。 Serial Port 设置串口信息 Port assignments 定义IMM所使用的端口。 Network Interfaces 设置IMM的网络地址 Network Protocols 配置SNMP，DNS等网络协议 Security 配置SSL、SSH等安全协议 Configuration File 备份和恢复IMM的配置文件 Restore Default Settings 将IMM恢复默认设置 Restrat IMM 重启IMM Log off 退出登录 三．几个常用功能 1．远程开关机 选择Power/Restart选项可以实现远程开机、关机和重启

TRDB_D5M_UserGuide

Terasic TRDB_D5M Digital Camera Package

TRDB-D5M User Manual 2 https://www.sodocs.net/doc/a117081840.html, July 1, 2014 CONTENTS CHAPTER 1 ABOUT THE KIT (1) 1.1 K IT C ONTENTS ..................................................................................................................................................... 1 1.2 A SSEMBLE THE C AMERA ...................................................................................................................................... 1 1.3 G ETTING H ELP ..................................................................................................................................................... 3 CHAPTER 2 TRDB_D5M (4) 2.1 F EATURES ............................................................................................................................................................. 4 2.2 P IN -OUT OF THE 40-PIN CONNECTOR ON TRDB-D5M ....................................................................................... 5 2.3 P IN D ESCRIPTION OF THE 40-PIN I NTERFACE OF TRDB_D5M .......................................................................... 6 CHAPTER 3 DIGITAL CAMERA DESIGN DEMONSTRATION (7) 3.1 D EMONSTRATION S ETUP ...................................................................................................................................... 7 3.2 C AMERA D EMONSTRATION S ETUP O N DE4 B OARD ........................................................................................... 7 3.3 C AMERA D EMONSTRATION S ETUP O N DE2-115 B OARD .................................................................................... 9 3.4 C ONFIGURING THE C AMERA AND L OAD THE I MAGE C APTURED TO Y OUR PC (DE2-70 B OARD U SERS ) ........ 11 3.5 C ONFIGURING THE C AMERA (DE2 B OARD U SERS ) .......................................................................................... 13 3.6 C ONFIGURING THE C AMERA (DE1 B OARD U SERS ) .......................................................................................... 14 3.7 B LOCK D IAGRAM OF THE R EFERENCE D ESIGN ................................................................................................. 16 CHAPTER 4 APPENDIX (17) 4.1 R EVISION H ISTORY ............................................................................................................................................. 17 4.2 A LWAYS V ISIT TRDB_D5M W EBPAGE FOR N EW A PPLICATIONS (17)

User_Guide

企业客户分类规则挖掘系统使用说明 （1）启动customer_classify.exe文件，首先弹出图1所示的“企业客户分类规则挖掘系统”的说明窗口，片刻后，系统自动弹出系统主界面，如图2所示。 （2）如图2所示，在系统主界面中有菜单和企业客户分类规则挖掘系统的功能简介。菜单包括企业客户分类规则挖掘、查看数据、系统原理、使用说明和退出。 （3）请点击“查看数据”，系统将弹出“企业客户数据”窗口显示客户的原始数据，如图3所示。 （4）请点击“系统原理”菜单查看该系统的原理。 （5）请点击“使用说明”菜单查看如何使用该系统。 （6）请点击“企业客户分类规则挖掘”菜单，弹出图4所示的“企业客户分类规则挖掘”窗口。 图1 “企业客户分类规则挖掘系 统”的说明窗口 图2 系统主界面 图3 企业客户数据窗口

（7）在参数设置中已经输入各参数值，如种群大小为50，最大迭代数目为40，最小支持度阈值ms 为0.2，最小置信度阈值mc 为0.6，交叉概率为80%，变异概率为5%。如图5所示。用户可以自己修改各参数值。 （8 ）点击遗传运算操作中的“编码”，右侧出现编码，运算状态显示为“请选择筛选种群的运算！”，如图6、7所示。 （9）点击遗传运算操作中的“筛选种群”，右侧将把不符合置信度和支持度的编码用“***”表示出来，运算状态显示为“当前尚未达到最大迭代次数，请继续进行交叉运算！”，如图8、9所示。 图4 “企业客户分类规则挖掘”窗口 图5 参数设置 图6 编码操作的结果 图7 编码操作的运算状态

（10）依次点击遗传运算操作中的“交叉”和“变异”，运算状态中分别显示“当前尚未达到最大迭代次数，请继续进行变异运算！”和“当前尚未达到最大迭代次数，遗传算法可以继续进行！”，如图10、11所示。此时，“算法继续运行”按钮变为可用。 （11）点击“算法继续运行”按钮，出现如图12所示的对话框，点击“确定”按钮，运算状态中显示“算法运行大概需要2-3分钟，请耐心等候”，直到2-3分钟后“输出最优规则集”按钮变为可用。 （12）点击“输出最优规则集”按钮，根据遗传算法得到的最优规则集对话框显示出来，如图13所示。 图8筛选种群操作的结果 图9 筛选种群操作的运算状态 图10 交叉操作的运算状态 图11变异操作的运算状态 图12 算法运行提示

Userguide

联想蓝牙手机中心 快速入门 目录： 最低要求 (2) 安装之前 (3) 安装联想蓝牙手机中心 (4) 移动设备安装和配置 (5) 卸载联想蓝牙手机中心 (6) 联想蓝牙手机中心主窗口 (7) 联想蓝牙手机中心主窗口功能介绍 (8) 联想蓝牙手机中心功能面板 (9) 菜单（多级功能列表） (10) 其它信息 (11)

最低要求 联想蓝牙手机中心需要使用 Windows 2000，XP或 Vista。如需关于其它操作系统以及与升级有关的任何信息，请与联想公司。 为使联想蓝牙手机中心正确运行，请检查下列事项： ? 一台配备Pentium(R)II 233MHz的计算机，并且已经连接到您的手机设备。 ? 一个可用的USB端口。 ? 拥有20MB可用空间的本地硬盘驱动器。 ? 与联想蓝牙手机中心兼容的设备。 ? 与您的手机设备运营商的服务合约中包含高速数据网络选项（以便网络上使用高速电子邮件和 Internet 浏览）；数据服务是与网络和服务合约有关的特性，并不是在所有地区都能使用。有关的详细信息，请与您的无线服务提供商联系。 ? 最低活动内存：在 Windows(R) 2000 和 XP 下最少 64MB 的 RAM。

安装之前 屏幕快照 本指南中的屏幕快照基于在Windows(R)XP环境下使用联想蓝牙手机中心。在其它Windows(R) 操作系统下运行此应用程序时，屏幕内容可能会有变化。这并不影响软件的功能性。 联机帮助 联想蓝牙手机中心提供上下文关联的联机帮助，单击“帮助”按钮或按键盘上的F1可以访问联机帮助。帮助文件中包含有关如何使用联想蓝牙手机中心的完整信息。

MOD11_UserGuide

Collection-5 MODIS Land Surface Temperature Products Users' Guide Zhengming Wan ICESS, University of California, Santa Barbara April 2009

ALERT --- This document is a living document that describes the Collection-5 MODIS Land Surface Temperature (LST) products. It is revised as progress is made in the development and assessment of the LST products. Described is the current state of the MODIS LST products. The purpose of the document is to give the potential user of LST products an understanding of the MODIS LST products and the data in those products. The MODIS LST products MOD11_L2, MOD11A1, and MOD11B1 have been validated at stage 1 with in situ measurements in more than 50 clear-sky cases in the temperature range from -10o C to 58o C and the column water vapor range of 0.4-4cm, most of them presented in published papers (Wan et al., 2002 and 2004; Coll et al., 2005; Wan, 2008; Wan and Li, 2008). More validation activities are under way. Please use the Collection-4 Users’ Guide for the descriptions of V4/V4.1 Terra MODIS LST products (named starting with MOD11) and V4/V4.1 Aqua MODIS LST products (named starting with MYD11).

User Guide

ELECTRA User Guide Version 1.2, March 2004

Copyright Notice Copyright ?2003-2004 by KONEKT, SPRL. All rights reserved. No part of this work may be reproduced without receiving the prior permission of the copyright owner. All brand or product names mentioned in this guide are trademarks or registered trademarks of their respective owners. In particular: SPECCTRA? is a registered trademark of Cadence, Inc. Windows is a trademark of Microsoft Corp. Disclaimer KONEKT SPRL AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 2

ELECTRA v1 1Overview of ELECTRA Routing Technology (5) 2Main Features (7) 3CAD Flow Integration (8) 4Using ELECTRA (9) 4.1Pushbutton Autorouting (9) 4.2Basic Routing Strategy (10) 4.3Analyzing Routing Results (11) 4.4Improving routability (13) 4.5Restarting the autorouter (13) 4.6Advanced Rules Hierarchy (14) 4.7Mouse driven Viewing Navigation (17) 5Quick Command Reference (19) 5.1Notations (19) 5.2Descriptors (19) 5.3Types: (20) 5.4Command Reference (21) autoroute (21) bestsave (21) bus (21) check (22) circuit (22) clean (23) cost (24) delete all wires (25) direction (26) fanout (26) filter (27) 3

丰田普锐斯用户手册PriusUserGuide

DRIVING (2) Just Drive It ! ............................. 2 Modes ......................................... 2 Eco-Meter .................................. 4 Energy Monitor .......................... 6 Consumption .............................. 8 Efficiency ................................. 10 Trip Info ................................... 11 Battery Info .............................. 12 Brake Assist ............................. 13 Tire Pressure ............................ 13 BUTTONS .. (14) Steering-Wheel ........................ 14 Voice ........................................ 16 Cruise ....................................... 16 Dimmer .................................... 16 Timer (PHV) ............................ 17 Cabin Air ................................. 17 Window Defog ......................... 18 Fan Options .............................. 18 Other Buttons ........................... 20 HELPFUL TIPS .. (21) Fuel Door ................................. 21 Rear Hatch . (21) Grille Blocking ........................ 22 OTHER . (23) External Cargo ......................... 23 Security .................................... 25 EDUCATION (26) Real-World Data ...................... 26 Operational Info ....................... 26 GLOSSARY .. (29) Disclaimer: All the information stated in this document was provided by Prius owners. None were affiliated with Toyota Motor Corporation, except as customers. This document is not sanctioned by Toyota Motor Corporation or any of its affiliates. The ideas, suggestions, and opinions offered in this document have not been endorsed by the manufacturer of those specific components or Toyota Motor Corporation. Any harm or damage that may result from the application of or the following of any ideas, suggestions, or opinions contained in this document is the sole responsibility of the individual that applied or followed said ideas, suggestions or opinions. The authors of this document hereby declare that they cannot and will not be held liable, in any fashion, for the content or the use of this document. Toyota Prius User-Guide Second Edition for the 2010-2012 models

CMUX_User_Guide

CMUX User Guide 30268ST10299A Rev. 0 - 13/10/06

CMUX User Guide 30268ST10299A Rev. 0 - 13/10/06 This document is refered to the following products: GM862-GPS 3 990 250 657 GE863-GPS 3 990 250 660 GM862-QUAD 3 990 250 659 GM862-QUAD-PY 3 990 250 658 GE863-OUAD Pb balls 3 990 250 662 GE863-PY Pb balls 3 990 250 661 GE864-QUAD 3 990 250 675 GE864-PY 3 990 250 676 GE863-QUAD 3 990 250 648 GE863-PY 3 990 250 650

CMUX User Guide 30268ST10299A Rev. 0 - 13/10/06 Contents 1INTRODUCTION (4) 1.1Scope of document (4) 2APPLICABLE DOCUMENTS (5) 3TECHNICAL CHARACTERISTICS (6) 3.1Product architecture (6) 3.2Implementation feature and limitation (6) 3.3AT command interface interactions (6) 4SERIAL MULTIPLEXER PROTOCOL (8) 4.1CMUX Frame Structure (8) 4.2UIH Control Channel Frame Coding (11) 4.3UIH Data Channel Frame Coding (13) 4.4CMUX establishment scenario (14) 5TELIT SERIAL PORT PC INTERFACE FOR CMUX (15) 5.1Interface Specification (15) 5.2Scenario (15) 5.3Graphical Interface (16) 5.4Application Setup (18) 6INTEGRATOR HINTS (19) 6.1How to begin (19) 6.2Flow control (20) 6.3Blocking command (20) 6.4Lookup table for FCS calculation (21) 6.5Ignored command (22) 7AT Commands (23) 8Document Change Log (24)

urg user guide

Unified Coverage Reporting User Guide Version X-2005.12 December 2005 Comments? E-mail your comments about this manual to vera_support@https://www.sodocs.net/doc/a117081840.html,

Copyright Notice and Proprietary Information Copyright 2005 Synopsys, Inc. All rights reserved. This software and documentation are owned by Synopsys, Inc., and furnished under a license agreement. The software and documentation may be used or copied only in accordance with the terms of the license agreement. No part of the software and documentation may be reproduced, transmitted, or translated, in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without prior written permission of Synopsys, Inc., or as expressly provided by the license agreement. Right to Copy Documentation The license agreement with Synopsys permits licensee to make copies of the documentation for its internal use only. Each copy shall include all copyrights, trademarks, service marks, and proprietary rights notices, if any. Licensee must assign sequential numbers to all copies. These copies shall contain the following leg-end on the cover page: “This document is duplicated with the permission of Synopsys, Inc. for the exclusive use of __________________________________________ and its employees. This is copy number __________.” Destination Control Statement All technical data contained in this publication is subject to the export control laws of the United States of America. Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader’s responsibility to determine the applicable regulations and to comply with them. Disclaimer SYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR-RANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Trademarks Synopsys, the Synopsys logo, Arcadia, BiNMOS-CBA, CMOS-CBA, COSSAP, DESIGN (ARROWS), DesignPower, DesignWare, dont_use, EPIC, ExpressModel, in-Sync, LM-1000, LM-1200, Logic Modeling, Logic Modeling (logo), Memory Architect, ModelAccess, ModelTools, PathMill, PL debug, RailMill, SmartLicense, SmartLogic, SmartModel, SmartModels, SNUG, SOLV-IT!, SourceModel Library, Stream Driven Simulator, Synopsys, Synopsys (logo), Synopsys VHDL Compiler, Synthetic Designs, Synthetic Libraries, TestBench Manager, and TimeMill are registered trademarks of Synopsys, Inc 3-D Debugging, AMPS, Behavioral Compiler, CBA Design System, CBA-Frame, characterize, Chip Architect, Compiled Designs, Core Network, Core Store, Cyclone, Data Path Express, DataPath Architect, DC Expert, DC Expert Plus, DC Professional, DelayMill, Design Advisor, Design Analyzer, Design Compiler, DesignSource, DesignTime, DesignWare Developer, Direct RTL, Direct Silicon Access, dont_touch, dont_touch_network, ECL Compiler, ECO Compiler, Embedded System Prototype, Floorplan Manager, Formality, FoundryModel, FPGA Compiler, FPGA Express, Frame Compiler, General Purpose Post-Processor, GPP, HDL Advisor, HDL Compiler, Integrator, Interactive Waveform Viewer, Library Compiler, LM-1400, LM-700, LM-family, Logic Model, ModelSource, ModelWare, Module Compiler, MS-3200, MS-3400, Power Compiler, PowerArc, PowerGate, PowerMill, PrimeTime, RTL Analyzer, Shadow Debugger, Silicon Architects, SimuBus, SmartCircuit, SmartModel Windows, Source-Level Design, SourceModel, SWIFT, SWIFT Interface, Synopsys Graphical Environment, Test Compiler, Test Compiler Plus, Test Manager, TestSim, Timing Annotator, Trace-On-Demand, VCS, VCSi, VHDL System Simulator, VirSim, Visualyze, Vivace, VSS Expert, and VSS Professional are trademarks of Synopsys, Inc. Linux is a registered trademark of Linus Torvalds used by permission. All other product or company names may be trademarks of their respective owners. Unified Coverage Reporting User Guide, Version X-2005.06 2

VIA音效卡用户指南(简体中文版)VIA_HD_AudioDeck_userGuide_sc

用户指南 VIA HD Audio Adeck For Windows 2000, Windows XP & Server 2003 June 20th 2008 Revision 1.10sc

版本修订摘要 版本日期编修备注 1.0sc Oct.20.07 Jill Yang Initial public release 1.10sc Jun.20.08 Jill Yang Update Function Page

目录 版本修订摘要 (2) 目录 (3) 图目录 (4) 前言 (5) 系统需求 (6) 显示模式 (7) 简易模式 (7) 完整模式 (8) 面板细部 (9) 上面板 (9) 下面板 (10) 配置面板 (11) 喇叭配置面板 (11) 播音、录音音量设定面板 (13) 音效配置面板 (16) 进阶配置面板 (18) S/PDIF配置面板 (21) 系统信息面板 (22) 工具提示 (24) 工具列 (25) Magic 5.1 (26)

图目录 图1 – 简易模式的Adeck (7) 图2 – 完整模式的Adeck (8) 图3 – 上面板 (9) 图4 – 喇叭配置面板 (11) 图5 – 启用「独立耳机」的喇叭配置面板 (11) 图6 – 喇叭控制面板中的耳机测试面板 (12) 图7 – 混音配置面板 – 播放装置设定 (13) 图8 – 混音配置面板 – 录音装置设定 (14) 图9 – 混音配置面板 – 前置麦克风 (14) 图10 – 混音配置面板 – 耳机 (15) 图11 – 音效配置面板 – 均衡器 (16) 图12 - 没有启用平滑滚轴的均衡器设定 (16) 图13 – 启用平滑滚轴的均衡器设定 (16) 图14 – 音效配置面板 – 重低音强化管理 (17) 图15 – 插座配置面板 – 后面板 (18) 图16 – 插座配置面板 – 前面板 (18) 图17 – 插座配置面板 – 插座侦测提示 (19) 图18 – 插座配置面板 – 耳机配置 (20) 图19 – S/PDIF配置面板 – S/PDIF输出 (21) 图20 – S/PDIF配置面板 – S/PDIF输入 (21) 图21 – 系统信息面板 (22) 图22 – 热键配置面板 (22) 图23 – 热键 – 使用热键调整音量 (23) 图24 – 工具提示 (24) 图25 – Adeck的工作列图示 (25) 图26 – 在工作列图标按下鼠标右键 (25) 图27 – Magic 5.1 – 切换至四声道 (26) 图28 – Magic 5.1 – 切换至六声道 (27)

Noah_LSM_USERGUIDE_2.7.1 LSM模式介绍及使用简介

THE COMMUNITY Noah LAND-SURFACE MODEL (LSM) User’s Guide Public Release Version 2.7.1 Last Updated Feb. 9 2005 This document is filename NOAH_LSM_USERGUIDE_2.7.1 doc at ftp://https://www.sodocs.net/doc/a117081840.html,/mmb/gcp/ldas/noahlsm/ver_2.7.1 Author: Kenneth Mitchell (NCEP/EMC) Point of Contact: Vince.Wong@https://www.sodocs.net/doc/a117081840.html,, phone 301-316-5029 Collaborators: Mike Ek, Vince Wong, Dag Lohmann, Victor Koren, John Schaake, Qingyun Duan, George Gayno, Brian Moore, Pablo Grunmann, Dan Tarpley, Bruce Ramsay, Fei Chen, Jinwon Kim, Hua-Lu Pan, Ying Lin, Curtis Marshall, Larry Mahrt, Tilden Meyers, Paul Ruscher TABLE OF CONTENTS 1.0 Introduction 2.0 Model Heritage 3.0 Directory Contents and Quick-Start Guide to Execution 4.0 Subroutine Summary and Calling Tree 5.0 Control File Contents and Function 6.0 Input Atmospheric Forcing File 7.0 LSM Initial Conditions 8.0 Specifying Model Parameters 9.0 Execution Output Files 10.0Technical References 1.0 INTRODUCTION This User’s Guide provides execution guidance for and physical description of the public version of the community Noah LSM. This version of the Noah LSM is a stand-alone, uncoupled, 1-D column version used to execute single-site land-surface simulations. In this traditional 1-D uncoupled mode, near-surface atmospheric forcing data is required as input forcing (see Sec 6.0). This LSM simulates soil moisture (both liquid and frozen), soil temperature, skin temperature, snowpack depth, snowpack water equivalent (and hence snowpack density), canopy water content, and the energy flux and water flux terms of the surface energy balance and surface water balance. See Sec 10 for the lineage of key technical references.