A Package for Non-primitive Recursive Function Definitions in HOL

Chapter 1 INTRODUCTIONSession ALanguage is a system of arbitrary vocal symbols used for human communication.Language is a means of verbal communication. It is instrumental in that communicating by speaking or writing is a purposeful act.It is social and conventional in that language is a social semiotic and communication can only take place effectively if all the users share a broad understanding of human interaction including such associated factors as nonverbal cues, motivation, and socio-cultural roles. Language learning and use are determined by the intervention of biological, cognitive, psychosocial, and environmental factors.Other definitions：Language is a symbolic form of communication that involves, on the one hand, the comprehension of words and sentences and, on the other, the expression of feelings, thoughts, and ideas. The basic units of language are phonemes, morphemes, and words.from Encyclopedia BritannicaLanguage is the systematic communication by vocal symbols. It is a universal characteristic of the human species.Nothing is known of its origin, although scientists have identified a gene that clearly contributes to the human ability to use language. Scientists generally hold that it has been so long in use that the length of time writing is known to have existed (7,900 years at most) is short by comparison. Just as languages spoken now by peoples of the simplest cultures are as subtle and as intricate as those of the peoples of more complex civilizations, similarly the forms of languages known (or hypothetically reconstructed) from the earliest records show no trace of being more ―primitive‖ than their modern forms.from The Columbia Electronic Encyclopedia人类特有的一种符号系统。

编程序常用英语单词application应用程式应用、应用程序application framework应用程式框架、应用框架应用程序框架architecture架构、系统架构体系结构argument引数（传给函式的值）。

叁见parameter叁数、实质叁数、实叁、自变量array阵列数组arrow operator arrow（箭头）运算子箭头操作符assembly装配件assembly language组合语言汇编语言assert(ion)断言assign指派、指定、设值、赋值assignment指派、指定赋值、分配assignment operator指派（赋值）运算子=赋值操作符associated相应的、相关的、关联、相应的associative container关联式容器（对应sequential container）关联式容器atomic不可分割的原子的attribute属性、特性audio音讯音频A.I.人工智慧人工智能background背景（用於图形着色）后台（用於行程）bandwidth频宽带宽base class基础类别基类base type基础型别(等同於base class) batch批次（意思是整批作业）批处理benefit利益收益best viable function最佳可行函式最佳可行函式（从viable functions中挑出的最佳吻合者）binary search二分搜寻法二分查找binary tree二元树二叉树binary function二元函式双叁函数binary operator二元运算子二元操作符binding系结绑定bit位元位bit field位元栏位域bitmap位元图位图bitwise以bit为单元逐一┅bitwise copy以bit为单元进行复制；位元逐一复制位拷贝block区块,区段块、区块、语句块boolean布林值（真假值，true或false）布尔值border边框、框线边框brace(curly brace)大括弧、大括号花括弧、花括号bracket(square brakcet)中括弧、中括号方括弧、方括号breakpoint中断点build建造、构筑、建置（MS用语）build－in内建内置bus汇流排总线business商务,业务buttons按钮byte位元组（由8 bits组成）字节cache快取高速缓存call呼叫、叫用调用callback回呼回调call operator call（函式呼叫）运算子调用操作符（同function call operator）candidate function候选函式候选函数（在函式多载决议程序中出现的候选函式）chain串链（例chain of function calls）链character字元字符check box核取方块(i.e. check button)复选框checked exception可控式异常(Java)check button方钮(i.e. check box)复选按钮child class子类别（或称为derived class,subtype）子类class类别类class body类别本体类体class declaration类别宣告、类别宣告式类声明class definition类别定义、类别定义式类定义class derivation list类别衍化列类继承列表class head类别表头类头class hierarchy类别继承体系,类别阶层类层次体系class library类别程式库、类别库类库class template类别模板、类别范本类模板class template partial specializations类别模板偏特化类模板部分特化class template specializations类别模板特化类模板特化cleanup清理、善后清理、清除client客端、客户端、客户client－server主从架构客户/服务器clipboard剪贴簿剪贴板clone复制克隆collection群集集合(系统文字模式下的整行执行命令)concept概念concrete具象的实在的concurrent并行并发configuration组态配置connection连接，连线（网络,资料库）连接constraint约束（条件）construct构件container容器（存放资料的某种结构如list, vector...）containment内含包容context背景关系、周遭环境、上下脉络环境、上下文control控制元件、控件console主控台控制台const常数（constant的缩写，C++关键字）constant常数（相对於variable）常量constructor（ctor）建构式构造函数（与class同名的一种member functions）copy (v)复制、拷贝copy (n)复件,副本cover涵盖覆盖create创建、建立、产生、生成创建creation产生、生成创建- 2 -cursor游标光标custom订制、自定定制data资料数据database资料库数据库database schema数据库结构纲目data member资料成员、成员变数数据成员、成员变量data structure资料结构数据结构datagram资料元数据报文dead lock死结死锁debug除错调试debugger除错器调试器declaration宣告、宣告式声明deduction推导（例：template argumentdeduction）推导、推断default预设缺省、默认defer延缓推迟define定义预定义definition定义、定义区、定义式定义delegate委派、委托、委任委托delegation（同上）demarshal反编列散集dereference提领（取出指标所指物体的内容）解叁考dereference operator dereference（提领）运算子*解叁考操作符derived class衍生类别派生类design by contract契约式设计design pattern设计范式、设计样式设计模式※最近我比较喜欢「设计范式」一词destroy摧毁、销毁destructor解构式析构函数device装置、设备dialog对话窗、对话盒对话框directive指令（例：using directive）(编译)指示符directory目录disk碟盘dispatch分派分散式计算(分散式电算)document文件文档dot operator dot（句点）运算子. (圆)点操作符driver驱动程式驱动（程序）dynamic binding动态系结动态绑定efficiency效率efficient高效end user终端用户entity物体实体、物体encapsulation封装enclosing class外围类别（与巢状类别nested class有关）外围类enum (enumeration)列举（一种C++资料型别）枚举enumerators列举元（enum型别中的成员）枚举成员、枚举器equal相等equality相等性equality operator equality（等号）运算子== 等号操作符equivalence等价性、等同性、对等性等价性equivalent等价、等同、对等等价escape code转义码evaluate评估、求值、核定评估event事件event driven事件驱动的exception异常情况异常exception declaration异常宣告（ref. C++ Primer 3/e,11."3）异常声明exception handling异常处理、异常处理机制异常处理、异常处理机制exception specification异常规格（ref. C++Primer 3/e,11."4）异常规范exit退离（指离开函式时的那一个执行点）退出explicit明白的、明显的、显式export汇出引出、导出expression运算式、算式表达式facility设施、设备设施、设备feature特性field栏位,资料栏（Java）字段,值域（Java）file档案文件firmware韧体固件flag旗标标记flash memory快闪记忆体闪存- 3 -flexibility弹性灵活性flush清理、扫清刷新font字型字体form表单（programming用语）窗体formal parameter形式叁数forward declaration前置宣告前置声明forwarding转呼叫,转发forwarding function转呼叫函式,转发函式转发函数fractal碎形分形framework框架full specialization全特化（ref. partialspecialization）function函式、函数function call operator同call operatorfunction object函式物件（ref. C++ Primer 3/e,12."3）函数对象function overloaded resolution函式多载决议程序函数重载解决（方案）functionality功能、机能功能function template函式模板、函式范本函数模板functor仿函式、函子game游戏generate生成generic泛型、一般化的、通用的、泛化generic algorithm泛型演算法通用算法getter (相对於setter)取值函式global 全域的（对应於local）全局的global object全域物件全局对象global scope resolution operator全域生存空间（范围决议）运算子::全局范围解析操作符group群组group box群组方块分组框guard clause卫述句(Refactoring, p250)卫语句GUI图形介面图形界面hand shaking握手协商handle识别码、识别号、号码牌、权柄句柄handler处理常式处理函数hard －coded编死的硬编码的hard－copy硬拷图屏幕截图hard disk硬碟硬盘hardware硬体硬件hash table杂凑表哈希表、散列表header file表头档、标头档头文件heap堆积堆hierarchy阶层体系层次结构（体系）hook挂钩钩子hyperlink超链结超链接icon图示、图标IDE整合开发环境集成开发环境identifier识别字、识别符号标识符if and only if若且唯若当且仅当Illinois伊利诺斯image影像图象immediate base直接的（紧临的）上层base class。

JsonPath语法JSONPathThis is a implementation for PHP based on Stefan Goessner's JSONPath script.JSONPath is an XPath-like expression language for filtering, flattening and extracting data.I believe that is improves on the original script (which was last updated in 2007) by doing a few things:Object-oriented code (should be easier to manage or extend in future)Expressions are parsed into tokens using some code cribbed from Doctrine Lexer and cachedThere is no eval() in usePerformance is pretty much the sameAny combination of objects/arrays/ArrayAccess-objects can be used as the data input which is great if you're de-serializing JSON in to objects or if you want to process your own data structures.JSONPath ExamplesJSONPath Result$.store.books[*].author the authors of all books in the store$..author all authors$.store..price the price of everything in the store.$..books[2]the third book$..books[(@.length-1)]the last book in order.$..books[0,1]the first two books$..books[:2]the first two books$..books[?(@.isbn)]filter all books with isbn number$..books[?(@.price<10)]filter all books cheapier than 10$..*all elements in the data (recursively extracted)Expression syntaxSymbol Description$The root object/element (not strictly necessary)@The current object/element. or []Child operator..Recursive descent*Wildcard. All child elements regardless their index.[,]Array indices as a set[start:end:step]Array slice operator borrowed from ES4/Python.()Filters a result set by a script expression()Uses the result of a script expression as the indexPHP Usage$data = ['people' => [['name' => 'Joe'], ['name' => 'Jane'], ['name' => 'John']]];$result = (new JSONPath($data))->find('$.people.*.name'); // returns new JSONPath// $result[0] === 'Joe'// $result[1] === 'Jane'// $result[2] === 'John'Magic method accessThe options flag JSONPath::ALLOW_MAGIC will instruct JSONPath when retrieving a value to first check if an objecthas a magic __get() method and will call this method if available. This feature is iffy andnot very predictable as:wildcard and recursive features will only look at public properties and can't smell which properties are magically accessiblethere is no property_exists check for magic methods so an object with a magic __get() will always return true when checkingif the property existsany errors thrown or unpredictable behaviour caused by fetching via __get() is your own problem to deal with$jsonPath = new JSONPath($myObject, JSONPath::ALLOW_MAGIC);For more examples, check the JSONPathTest.php tests file.Script expressionsScript expressions are not supported as the original author intended because:This would only be achievable through eval (boo).Using the script engine from different languages defeats the purpose of having a single expression evaluate the same way in different languages which seems like a bit of a flaw if you're creating an abstract expression syntax.So here are the types of query expressions that are supported:[?(@._KEY_ _OPERATOR_ _VALUE_)] // <, >, !=, and ==Eg.[?(@.title == "A string")] //[?(@.title = "A string")]// A single equals is not an assignment but the SQL-style of '=='Similar projectsdoes similiar things, is full of features and has a PHP implementationThe utility from CakePHP does some similar thingsChangelog0.3.0Added JSONPathToken class as value objectLexer clean up and refactorUpdated the lexing and filtering of the recursive token ("..") to allow for a combination of recursionand filters, eg. $..[?(@.type == 'suburb')].name0.2.1 - 0.2.5Various bug fixes and clean up0.2.0Added a heap of array access features for more creative iterating and chaining possibilities0.1.xInit。

数学专业词汇英汉对照汇编数学英汉词汇AAbelian group 阿贝尔群abscissa axis 横轴absolute continuity 绝对连续absolute convergence 绝对收敛absolute value 绝对值abstract algebra 抽象代数addition 加法affine 仿射Aleph-zero 阿列夫零algebra topology 代数拓扑algorithm 算法almost everywhere ⼏乎处处almost surely ⼏乎必然alternative 互斥性analogy 类似analytic expression 解析式anomalous 反常的apex 顶点approximate calculation 近似计算associative law 结合律asymmetric line 渐近线axiom of choice 选择公理axis of abscissas 横坐标轴axis of imaginary 虚轴axis of real 实轴Bbase number 底数base of logarithmic function 对数函数的底base vectors 基向量basic element 基元素bijection 双射bilinear 双线性binary ⼆元的binomial ⼆项式biunivocal ⼀对⼀的bondage 约束boundary compact space 有界紧空间boundary condition 边界条件bounded continuous function有界连续函数bounded interval 有界区间brace ⼤括号Ccalculus of proposition 命题演算canonical form 标准型cardinal number of set 集的基数Cartesian product 笛卡尔积catalog ⽬录category of a space 空间的筹数causality 因果律center of compression 压缩中⼼central limit theorem 中⼼极限定理certain event 必然事件characteristic equation 特征⽅程characteristic value 特征值chart 图check procedure 检验步骤circumscribed 外切的class field 类域closure axioms 闭包公理cluster point 聚点丛点coefficient of autocorrelation ⾃相关系数coefficient of regression 回归系数cofactor of a determinant ⾏列式的余⼦式cohomology 上同调collinear 共线column matrix 列矩阵column rank 列秩common factor 公因⼦commutative law 交换律commutative law of addition 加法交换律commutative law of multiplication乘法交换律compact convex set 紧凸集complement of a set 集的余集complement law 补余律complete matrix space 完备度量空间complete orthogonal system 完全正交系complex analysis 复分析complex conjugate 复共轭complex field 复数域compound function 复合函数concave 凹的conclusion 结论condition 条件conditional of inequality 条件不等式conditional of equivalence 等价条件conditional of integrability 可积条件conditional convergence 条件收敛confidence interval 置信区间conjugate 共轭connectivity 连通性consistency principle ⼀致原则constant factor 常数因⼦construction 作图构造continuous function 连续函数contradiction ⽭盾contrary propositions 相反命题convergence almost everywhere⼏乎处处收敛convergence in measure 依测度收敛convergence rate 收敛速度convergence region 收敛区域converse proposition 逆命题convex closure 凸包coplanar 共⾯cosine law 余弦定律countable additivity 可列可加性critical point 临界点Ddecision theory 决策论degenerate quadratic form 退化⼆次型dense 稠密derivate 导数differential 微分dimensionality 维数discriminant 判别式disjoint 不相交的distributive law 分配率divergent infinite series 发散⽆穷级数double integral ⼆重积分dual operations 对偶运算Eefficiency estimation 有效估计eigenelement 本征元素elementary event 基本事件endomorphism ⾃同态envelope 包络equivalence class 等价类equivalent relation 等价关系even number 偶数existence and uniqueness 存在且唯⼀性expansion in series 级数展开exponent 指数extreme point 极值点Ffeasible solution 可⾏解finite additivity 有限可加性fraction 分数frequency 频率fundamental assumption 基本假定fuzzy 模糊game theory 对策论general remark ⼀般说明generalized derivatives ⼴义导数geometric significance ⼏何意义global convergence 全局收敛Hharmonic analysis 调和分析harmonics 调和函数homology 同调homotopy 同伦homomorphism 同态hyperbolic plane 双曲平⾯hypothesis 假设Iideal 理想identical element 单位元identity law 同⼀律illustrate 说明阐释implicit function 隐函数in like manner 同理in the large 全局的in the small 局部的inclusion of sets 集的包含关系incompatible 互斥的不相容的independence test 独⽴性检验independent variable ⾃变量induction 归纳法归纳infinite ⽆穷⼤integral calculus 积分学integral divisor 整因⼦integrate 积分interior mapping 开映射inverse of matrix 矩阵的逆irrational root ⽆理根irreducible fraction 不可约分数irreducible polynomial 不可约多项式isolated point 孤⽴点isometric 等距的iteration method 迭代法Jjoint 连接jump discontinuity 跳跃不连续性Kkernel 核knee 拐点known quantity 已知量large by comparison 远⼤于latent vector 特征向量law of association 结合律law of causality因果律law of commutation 交换律law of contradiction ⽭盾律law of distribution 分配律law of mean 中值定理leader ⾸项limited function 有界函数linear dependence 线性相关logarithm 对数lower bound 下界Mmapping space 映射空间marginal value 临界值measure 测度metric space 度量空间monotone 单调multinomial 多项式multiplication 乘法mutual correlation 互相关mutually conjugate 相互共轭的mutually disjoint 互不相交的mutually inverse 互逆的mutually prime 互素的Nnatural logarithm ⾃然对数negate 取否定negative index 负指数negate proposition 否定命题nest of intervals 区间套neutral element 零元nonhomogeneous differential equation⾮齐次微分⽅程nonlinear boundary value problem⾮线性边值问题non-vanishing vector ⾮零向量normal space 正规空间normalized form标准型n-th power n次幂numerical analysis 数值分析Oobjective function ⽬标函数oblique line 斜线odd number 奇数odd symmetry 奇对称odevity 奇偶性one degree of freedom ⼀个⾃由度onto mapping ⾃⾝映射open covering 开覆盖opposite sign 异号optimal solution 最优解optimize 最优化order of infinity ⽆穷⼤的解ordered pair 有序偶ordinary differential equation常微分⽅程ordinary solution 通常解ordinate 纵坐标oriented circle 有向圆oriented segment 有向线段orthogonal 正交orthonormal basis 标准正交基outer measure 外测度overfield 扩张域overview 概述Ppairwise orthogonal 两两正交parabolic asymptotes 渐进抛物线parabolic curve 抛物曲线parallel 平⾏线parametric equation 参数⽅程parity 奇偶性partial sum 部分和passive 被动的path curve 轨线periodicity 周期性permutation 排列perpendicular line 垂直线piecewise 分段的plus 加point of intersection 交点population 总体的positive definite quadratic form 正定⼆次型positive number 正数potential 位势power formula 乘⽅公式prime ideal 素理想prime ring 素环primitive equation 本原⽅程primitive term 原始项principal factor method 主因⼦法principal minor 主⼦式principal of the point of accumulation聚点定理prior estimate 先验估计probability curve 概率曲线probability distribution 概率分布process of iteration 迭代法proper polynomial 特征多项式proper subset 真⼦集pure imaginary 纯虚数QQED(quod erat demonstrandum) 证毕quadrant 象限quadratic ⼆次quadratic equation with one unknown⼀元⼆次⽅程quadratic root 平⽅根qualitative analysis 定性分析quantitative analysis 定量分析quarter 四分之⼀queue discipline 排队规则quotation 引⽤引证quotient group 商群Rradial deviation 径向偏差radian 弧度radical sign 根号radius of a circle 圆的半径radius of convergence 收敛半径radius of curvature 曲率半径radix point ⼩数点random distribution 随机分布random sampling distribution 随机抽样分布randomness test 随机性检验rang of distribution 分布域rang of points 点列rank of linear mapping 线性映射的秩rank of quadratic form ⼆次型的秩rarefaction 稀疏rational proper fraction 有理真分式rationalizing denominators 有理化分母raw data 原始数据real analytic function 实解析函数real axis 实轴real variable function 实变函数reasoning by analogy 类⽐推理相似推理reciprocal 倒数reciprocal automorphism 反⾃同构reciprocal ratio 反⽐rectangular coordinates 直⾓坐标recurrence formula 递推公式recurrence relations 关系recursive function 递归函数reduction of a fraction 约分reduction to a common denominator 通分reduction to absurdity 反证法reference system 参考系reflection 反射region convergence 收敛区域regression analysis 回归分析regular function 正则函数rejection region 拒绝域relation of equivalence 等价关系relative error 相对误差relative minimum 相对极⼩值repeated integral 累积分residue class 剩余类resolution 分解reverse theorem 逆定理reversible transformation 可逆变换rigorous upper bound 严格的上界rotation axis 旋转轴roundoff error 舍⼊误差Ssample average 样本均值satisfy 满⾜scalar multiplication 数乘secondary ⼆次的辅助的次级的section 截⾯截线截点sectionally smooth 分段光滑self-conjugate subgroup 正规⼦群self-evident 显然不证⾃明semi-closure 半闭sensitivity 灵敏度separability 可分性sequence 序列series 级数series expansion 级数展开series of positive terms 正项级数shaded region 阴影区域significance level 显著性⽔平significant digits 有效数字similarity isomorphic 相似同构的simply connected region 单连通区域simulated data 模拟数据simultaneous inequalities 联⽴不等式sine curve 正弦曲线singular element 奇元素退化元素skew matrices 斜对称矩阵solid figure ⽴体形spanning set ⽣成集spherical neighborhood 球形领域stability condition 稳定性条件standard deviation 标准差stationary curve 平稳曲线statistical dependence 统计相关stochastic allocation 随机分配subadditivity 次可加性subbasis ⼦基subsequence ⼦列subtotalling 求部分和successive approximation 逐次逼近法sufficient and necessary condition 充要条件supplementary set 补集surface 曲⾯surplus variable 剩余变量symbolic function 符号函数symmetric center 对称中⼼symmetry transformation 对称变换synchronism 同步synthetic proof 综合证明Ttable of random numbers 随机数表tangent line 切线tends to infinity 趋于⽆穷term by term differentiation 逐项微分terminal check 最后校验termwise integration 逐项积分totally bounded 完全有界的transcendental equation 超越⽅程transposition 转置transverse surface 横截⾯triangle computations 三⾓形解法trisection 三等分Uultimate 最后的最终的极限unbiased estimation ⽆偏估计unconditional stability ⽆条件稳定uniform boundness ⼀致有界unilateral limits 单侧极限unique solution 唯⼀解universal proposition 全称命题unordered ⽆序的unreduced 不可约的untrivial solution ⾮零解upper integral 上积分Vvalid 有效真确valuation 赋值variance ⽅差偏差vector of unit length 单位向量velocity-time graph 速度-时间图verify 检验校验versal 通⽤的vertex 极点顶vertical 垂直的vibration 震动visual proof 图像证明直观证明volume 体积Wwave form 波形weak boundary condition 弱边界条件weighted arithmetic mean 加权算术平均whole number 整数Xx-axis x轴x-component x分量x-coordinate x坐标x-direction x⽅向Yyield estimation 合格率估计Zzero correlation 零相关zero divisor 零因⼦zone of preference for acceptance 合格域zoom up 放⼤。

Network Working Group M. Rose Request for Comments: 1155 Performance Systems International Obsoletes: RFC 1065 K. McCloghrie Hughes LAN Systems May 1990 Structure and Identification of Management Informationfor TCP/IP-based InternetsTable of Contents1. Status of this Memo (1)2. Introduction (2)3. Structure and Identification of Management Information (4)3.1 Names (4)3.1.1 Directory (5)3.1.2 Mgmt (6)3.1.3 Experimental (6)3.1.4 Private (7)3.2 Syntax (7)3.2.1 Primitive Types (7)3.2.1.1 Guidelines for Enumerated INTEGERs (7)3.2.2 Constructor Types (8)3.2.3 Defined Types (8)3.2.3.1 NetworkAddress (8)3.2.3.2 IpAddress (8)3.2.3.3 Counter (8)3.2.3.4 Gauge (9)3.2.3.5 TimeTicks (9)3.2.3.6 Opaque (9)3.3 Encodings (9)4. Managed Objects (10)4.1 Guidelines for Object Names (10)4.2 Object Types and Instances (10)4.3 Macros for Managed Objects (14)5. Extensions to the MIB (16)6. Definitions (17)7. Acknowledgements (20)8. References (21)9. Security Considerations (21)10. Authors’ Addresses (22)1. Status of this MemoThis RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical Rose & McCloghrie [Page 1]content of the document is unchanged from RFC 1065.This memo provides the common definitions for the structure andidentification of management information for TCP/IP-based internets. In particular, together with its companion memos which describe themanagement information base along with the network managementprotocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular, theInternet.This memo specifies a Standard Protocol for the Internet community.Its status is "Recommended". TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification.The Internet Activities Board recommends that all IP and TCPimplementations be network manageable. This implies implementationof the Internet MIB (RFC-1156) and at least one of the tworecommended management protocols SNMP (RFC-1157) or CMOT (RFC-1095). It should be noted that, at this time, SNMP is a full Internetstandard and CMOT is a draft standard. See also the Host and Gateway Requirements RFCs for more specific information on the applicability of this standard.Please refer to the latest edition of the "IAB Official ProtocolStandards" RFC for current information on the state and status ofstandard Internet protocols.Distribution of this memo is unlimited.2. IntroductionThis memo describes the common structures and identification schemefor the definition of management information used in managingTCP/IP-based internets. Included are descriptions of an objectinformation model for network management along with a set of generic types used to describe management information. Formal descriptionsof the structure are given using Abstract Syntax Notation One (ASN.1) [1].This memo is largely concerned with organizational concerns andadministrative policy: it neither specifies the objects which aremanaged, nor the protocols used to manage those objects. Theseconcerns are addressed by two companion memos: one describing theManagement Information Base (MIB) [2], and the other describing theSimple Network Management Protocol (SNMP) [3].This memo is based in part on the work of the Internet Engineering Rose & McCloghrie [Page 2]Task Force, particularly the working note titled "Structure andIdentification of Management Information for the Internet" [4]. This memo uses a skeletal structure derived from that note, but differs in one very significant way: that note focuses entirely on the use ofOSI-style network management. As such, it is not suitable for usewith SNMP.This memo attempts to achieve two goals: simplicity andextensibility. Both are motivated by a common concern: although the management of TCP/IP-based internets has been a topic of study forsome time, the authors do not feel that the depth and breadth of such understanding is complete. More bluntly, we feel that previousexperiences, while giving the community insight, are hardlyconclusive. By fostering a simple SMI, the minimal number ofconstraints are imposed on future potential approaches; further, byfostering an extensible SMI, the maximal number of potentialapproaches are available for experimentation.It is believed that this memo and its two companions comply with the guidelines set forth in RFC 1052, "IAB Recommendations for theDevelopment of Internet Network Management Standards" [5] and RFC1109, "Report of the Second Ad Hoc Network Management Review Group"[6]. In particular, we feel that this memo, along with the memodescribing the management information base, provide a solid basis for network management of the Internet.Rose & McCloghrie [Page 3]3. Structure and Identification of Management InformationManaged objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB aredefined using Abstract Syntax Notation One (ASN.1) [1].Each type of object (termed an object type) has a name, a syntax, and an encoding. The name is represented uniquely as an OBJECTIDENTIFIER. An OBJECT IDENTIFIER is an administratively assignedname. The administrative policies used for assigning names arediscussed later in this memo.The syntax for an object type defines the abstract data structurecorresponding to that object type. For example, the structure of agiven object type might be an INTEGER or OCTET STRING. Although ingeneral, we should permit any ASN.1 construct to be available for use in defining the syntax of an object type, this memo purposelyrestricts the ASN.1 constructs which may be used. These restrictions are made solely for the sake of simplicity.The encoding of an object type is simply how instances of that object type are represented using the object’s type syntax. Implicitly tied to the notion of an object’s syntax and encoding is how the object is represented when being transmitted on the network. This memospecifies the use of the basic encoding rules of ASN.1 [7].It is beyond the scope of this memo to define either the MIB used for network management or the network management protocol. As mentioned earlier, these tasks are left to companion memos. This memo attempts to minimize the restrictions placed upon its companions so as tomaximize generality. However, in some cases, restrictions have been made (e.g., the syntax which may be used when defining object typesin the MIB) in order to encourage a particular style of management.Future editions of this memo may remove these restrictions.3.1. NamesNames are used to identify managed objects. This memo specifiesnames which are hierarchical in nature. The OBJECT IDENTIFIERconcept is used to model this notion. An OBJECT IDENTIFIER can beused for purposes other than naming managed object types; forexample, each international standard has an OBJECT IDENTIFIERassigned to it for the purposes of identification. In short, OBJECT IDENTIFIERs are a means for identifying some object, regardless ofthe semantics associated with the object (e.g., a network object, astandards document, etc.)An OBJECT IDENTIFIER is a sequence of integers which traverse aRose & McCloghrie [Page 4]global tree. The tree consists of a root connected to a number oflabeled nodes via edges. Each node may, in turn, have children ofits own which are labeled. In this case, we may term the node asubtree. This process may continue to an arbitrary level of depth.Central to the notion of the OBJECT IDENTIFIER is the understandingthat administrative control of the meanings assigned to the nodes may be delegated as one traverses the tree. A label is a pairing of abrief textual description and an integer.The root node itself is unlabeled, but has at least three childrendirectly under it: one node is administered by the InternationalOrganization for Standardization, with label iso(1); another isadministrated by the International Telegraph and TelephoneConsultative Committee, with label ccitt(0); and the third is jointly administered by the ISO and the CCITT, joint-iso-ccitt(2).Under the iso(1) node, the ISO has designated one subtree for use by other (inter)national organizations, org(3). Of the children nodespresent, two have been assigned to the U.S. National Institutes ofStandards and Technology. One of these subtrees has been transferred by the NIST to the U.S. Department of Defense, dod(6).As of this writing, the DoD has not indicated how it will manage its subtree of OBJECT IDENTIFIERs. This memo assumes that DoD willallocate a node to the Internet community, to be administered by the Internet Activities Board (IAB) as follows:internet OBJECT IDENTIFIER ::= { iso org(3) dod(6) 1 }That is, the Internet subtree of OBJECT IDENTIFIERs starts with theprefix:1.3.6.1.This memo, as a standard approved by the IAB, now specifies thepolicy under which this subtree of OBJECT IDENTIFIERs isadministered. Initially, four nodes are present:directory OBJECT IDENTIFIER ::= { internet 1 }mgmt OBJECT IDENTIFIER ::= { internet 2 }experimental OBJECT IDENTIFIER ::= { internet 3 }private OBJECT IDENTIFIER ::= { internet 4 }3.1.1. DirectoryThe directory(1) subtree is reserved for use with a future memo that discusses how the OSI Directory may be used in the Internet.Rose & McCloghrie [Page 5]3.1.2. MgmtThe mgmt(2) subtree is used to identify objects which are defined in IAB-approved documents. Administration of the mgmt(2) subtree isdelegated by the IAB to the Internet Assigned Numbers Authority forthe Internet. As RFCs which define new versions of the Internet-standard Management Information Base are approved, they are assigned an OBJECT IDENTIFIER by the Internet Assigned Numbers Authority foridentifying the objects defined by that memo.For example, the RFC which defines the initial Internet standard MIB would be assigned management document number 1. This RFC would usethe OBJECT IDENTIFIER{ mgmt 1 }or1.3.6.1.2.1in defining the Internet-standard MIB.The generation of new versions of the Internet-standard MIB is arigorous process. Section 5 of this memo describes the rules usedwhen a new version is defined.3.1.3. ExperimentalThe experimental(3) subtree is used to identify objects used inInternet experiments. Administration of the experimental(3) subtree is delegated by the IAB to the Internet Assigned Numbers Authority of the Internet.For example, an experimenter might received number 17, and would have available the OBJECT IDENTIFIER{ experimental 17 }or1.3.6.1.3.17for use.As a part of the assignment process, the Internet Assigned NumbersAuthority may make requirements as to how that subtree is used.Rose & McCloghrie [Page 6]3.1.4. PrivateThe private(4) subtree is used to identify objects definedunilaterally. Administration of the private(4) subtree is delegated by the IAB to the Internet Assigned Numbers Authority for theInternet. Initially, this subtree has at least one child:enterprises OBJECT IDENTIFIER ::= { private 1 }The enterprises(1) subtree is used, among other things, to permitparties providing networking subsystems to register models of theirproducts.Upon receiving a subtree, the enterprise may, for example, define new MIB objects in this subtree. In addition, it is strongly recommended that the enterprise will also register its networking subsystemsunder this subtree, in order to provide an unambiguous identification mechanism for use in management protocols. For example, if the"Flintstones, Inc." enterprise produced networking subsystems, then they could request a node under the enterprises subtree from theInternet Assigned Numbers Authority. Such a node might be numbered: 1.3.6.1.4.1.42The "Flintstones, Inc." enterprise might then register their "FredRouter" under the name of:1.3.6.1.4.1.42.1.13.2. SyntaxSyntax is used to define the structure corresponding to object types. ASN.1 constructs are used to define this structure, although the full generality of ASN.1 is not permitted.The ASN.1 type ObjectSyntax defines the different syntaxes which may be used in defining an object type.3.2.1. Primitive TypesOnly the ASN.1 primitive types INTEGER, OCTET STRING, OBJECTIDENTIFIER, and NULL are permitted. These are sometimes referred to as non-aggregate types.3.2.1.1. Guidelines for Enumerated INTEGERsIf an enumerated INTEGER is listed as an object type, then a named-number having the value 0 shall not be present in the list ofRose & McCloghrie [Page 7]enumerations. Use of this value is prohibited.3.2.2. Constructor TypesThe ASN.1 constructor type SEQUENCE is permitted, providing that itis used to generate either lists or tables.For lists, the syntax takes the form:SEQUENCE { <type1>, ..., <typeN> }where each <type> resolves to one of the ASN.1 primitive types listed above. Further, these ASN.1 types are always present (the DEFAULTand OPTIONAL clauses do not appear in the SEQUENCE definition).For tables, the syntax takes the form:SEQUENCE OF <entry>where <entry> resolves to a list constructor.Lists and tables are sometimes referred to as aggregate types.3.2.3. Defined TypesIn addition, new application-wide types may be defined, so long asthey resolve into an IMPLICITly defined ASN.1 primitive type, list,table, or some other application-wide type. Initially, fewapplication-wide types are defined. Future memos will no doubtdefine others once a consensus is reached.3.2.3.1. NetworkAddressThis CHOICE represents an address from one of possibly severalprotocol families. Currently, only one protocol family, the Internet family, is present in this CHOICE.3.2.3.2. IpAddressThis application-wide type represents a 32-bit internet address. It is represented as an OCTET STRING of length 4, in network byte-order.When this ASN.1 type is encoded using the ASN.1 basic encoding rules, only the primitive encoding form shall be used.3.2.3.3. CounterThis application-wide type represents a non-negative integer which Rose & McCloghrie [Page 8]monotonically increases until it reaches a maximum value, when itwraps around and starts increasing again from zero. This memospecifies a maximum value of 2^32-1 (4294967295 decimal) forcounters.3.2.3.4. GaugeThis application-wide type represents a non-negative integer, whichmay increase or decrease, but which latches at a maximum value. This memo specifies a maximum value of 2^32-1 (4294967295 decimal) forgauges.3.2.3.5. TimeTicksThis application-wide type represents a non-negative integer whichcounts the time in hundredths of a second since some epoch. Whenobject types are defined in the MIB which use this ASN.1 type, thedescription of the object type identifies the reference epoch.3.2.3.6. OpaqueThis application-wide type supports the capability to pass arbitrary ASN.1 syntax. A value is encoded using the ASN.1 basic rules into a string of octets. This, in turn, is encoded as an OCTET STRING, ineffect "double-wrapping" the original ASN.1 value.Note that a conforming implementation need only be able to accept and recognize opaquely-encoded data. It need not be able to unwrap thedata and then interpret its contents.Further note that by use of the ASN.1 EXTERNAL type, encodings other than ASN.1 may be used in opaquely-encoded data.3.3. EncodingsOnce an instance of an object type has been identified, its value may be transmitted by applying the basic encoding rules of ASN.1 to thesyntax for the object type.Rose & McCloghrie [Page 9]4. Managed ObjectsAlthough it is not the purpose of this memo to define objects in the MIB, this memo specifies a format to be used by other memos whichdefine these objects.An object type definition consists of five fields:OBJECT:-------A textual name, termed the OBJECT DESCRIPTOR, for the object type, along with its corresponding OBJECT IDENTIFIER.Syntax:The abstract syntax for the object type. This must resolve to an instance of the ASN.1 type ObjectSyntax (defined below).Definition:A textual description of the semantics of the object type.Implementations should ensure that their instance of the objectfulfills this definition since this MIB is intended for use inmulti-vendor environments. As such it is vital that objects have consistent meaning across all machines.Access:One of read-only, read-write, write-only, or not-accessible.Status:One of mandatory, optional, or obsolete.Future memos may also specify other fields for the objects which they define.4.1. Guidelines for Object NamesNo object type in the Internet-Standard MIB shall use a sub-identifier of 0 in its name. This value is reserved for use withfuture extensions.Each OBJECT DESCRIPTOR corresponding to an object type in theinternet-standard MIB shall be a unique, but mnemonic, printablestring. This promotes a common language for humans to use whendiscussing the MIB and also facilitates simple table mappings foruser interfaces.4.2. Object Types and InstancesAn object type is a definition of a kind of managed object; it is Rose & McCloghrie [Page 10]declarative in nature. In contrast, an object instance is aninstantiation of an object type which has been bound to a value. For example, the notion of an entry in a routing table might be definedin the MIB. Such a notion corresponds to an object type; individual entries in a particular routing table which exist at some time areobject instances of that object type.A collection of object types is defined in the MIB. Each suchsubject type is uniquely named by its OBJECT IDENTIFIER and also has a textual name, which is its OBJECT DESCRIPTOR. The means wherebyobject instances are referenced is not defined in the MIB. Reference to object instances is achieved by a protocol-specific mechanism: it is the responsibility of each management protocol adhering to the SMI to define this mechanism.An object type may be defined in the MIB such that an instance ofthat object type represents an aggregation of information alsorepresented by instances of some number of "subordinate" objecttypes. For example, suppose the following object types are definedin the MIB:OBJECT:-------atIndex { atEntry 1 }Syntax:INTEGERDefinition:The interface number for the physical address.Access:read-write.Status:mandatory.OBJECT:-------atPhysAddress { atEntry 2 }Syntax:OCTET STRINGDefinition:The media-dependent physical address.Rose & McCloghrie [Page 11]read-write.Status:mandatory.OBJECT:-------atNetAddress { atEntry 3 }Syntax:NetworkAddressDefinition:The network address corresponding to the media-dependent physical address.Access:read-write.Status:mandatory.Then, a fourth object type might also be defined in the MIB:OBJECT:-------atEntry { atTable 1 }Syntax:AtEntry ::= SEQUENCE {atIndexINTEGER,atPhysAddressOCTET STRING,atNetAddressNetworkAddress}Definition:An entry in the address translation table.Access:read-write.Rose & McCloghrie [Page 12]mandatory.Each instance of this object type comprises information representedby instances of the former three object types. An object typedefined in this way is called a list.Similarly, tables can be formed by aggregations of a list type. For example, a fifth object type might also be defined in the MIB:OBJECT:------atTable { at 1 }Syntax:SEQUENCE OF AtEntryDefinition:The address translation table.Access:read-write.Status:mandatory.such that each instance of the atTable object comprises informationrepresented by the set of atEntry object types that collectivelyconstitute a given atTable object instance, that is, a given address translation table.Consider how one might refer to a simple object within a table.Continuing with the previous example, one might name the object type { atPhysAddress }and specify, using a protocol-specific mechanism, the object instance { atNetAddress } = { internet "10.0.0.52" }This pairing of object type and object instance would refer to allinstances of atPhysAddress which are part of any entry in someaddress translation table for which the associated atNetAddress value is { internet "10.0.0.52" }.To continue with this example, consider how one might refer to anaggregate object (list) within a table. Naming the object typeRose & McCloghrie [Page 13]{ atEntry }and specifying, using a protocol-specific mechanism, the objectinstance{ atNetAddress } = { internet "10.0.0.52" }refers to all instances of entries in the table for which theassociated atNetAddress value is { internet "10.0.0.52" }.Each management protocol must provide a mechanism for accessingsimple (non-aggregate) object types. Each management protocolspecifies whether or not it supports access to aggregate objecttypes. Further, the protocol must specify which instances are"returned" when an object type/instance pairing refers to more thanone instance of a type.To afford support for a variety of management protocols, allinformation by which instances of a given object type may be usefully distinguished, one from another, is represented by instances ofobject types defined in the MIB.4.3. Macros for Managed ObjectsIn order to facilitate the use of tools for processing the definition of the MIB, the OBJECT-TYPE macro may be used. This macro permitsthe key aspects of an object type to be represented in a formal way. OBJECT-TYPE MACRO ::=BEGINTYPE NOTATION ::= "SYNTAX" type (TYPE ObjectSyntax)"ACCESS" Access"STATUS" StatusVALUE NOTATION ::= value (VALUE ObjectName)Access ::= "read-only"| "read-write"| "write-only"| "not-accessible"Status ::= "mandatory"| "optional"| "obsolete"ENDGiven the object types defined earlier, we might imagine thefollowing definitions being present in the MIB:atIndex OBJECT-TYPERose & McCloghrie [Page 14]SYNTAX INTEGERACCESS read-writeSTATUS mandatory::= { atEntry 1 }atPhysAddress OBJECT-TYPESYNTAX OCTET STRINGACCESS read-writeSTATUS mandatory::= { atEntry 2 }atNetAddress OBJECT-TYPESYNTAX NetworkAddressACCESS read-writeSTATUS mandatory::= { atEntry 3 }atEntry OBJECT-TYPESYNTAX AtEntryACCESS read-writeSTATUS mandatory::= { atTable 1 }atTable OBJECT-TYPESYNTAX SEQUENCE OF AtEntryACCESS read-writeSTATUS mandatory::= { at 1 }AtEntry ::= SEQUENCE {atIndexINTEGER,atPhysAddressOCTET STRING,atNetAddressNetworkAddress}The first five definitions describe object types, relating, forexample, the OBJECT DESCRIPTOR atIndex to the OBJECT IDENTIFIER {atEntry 1 }. In addition, the syntax of this object is defined(INTEGER) along with the access permitted (read-write) and status(mandatory). The sixth definition describes an ASN.1 type calledAtEntry.Rose & McCloghrie [Page 15]5. Extensions to the MIBEvery Internet-standard MIB document obsoletes all previous suchdocuments. The portion of a name, termed the tail, following theOBJECT IDENTIFIER{ mgmt version-number }used to name objects shall remain unchanged between versions. Newversions may:(1) declare old object types obsolete (if necessary), but notdelete their names;(2) augment the definition of an object type corresponding to alist by appending non-aggregate object types to the object typesin the list; or,(3) define entirely new object types.New versions may not:(1) change the semantics of any previously defined object without changing the name of that object.These rules are important because they admit easier support formultiple versions of the Internet-standard MIB. In particular, thesemantics associated with the tail of a name remain constantthroughout different versions of the MIB. Because multiple versions of the MIB may thus coincide in "tail-space," implementationssupporting multiple versions of the MIB can be vastly simplified.However, as a consequence, a management agent might return aninstance corresponding to a superset of the expected object type.Following the principle of robustness, in this exceptional case, amanager should ignore any additional information beyond thedefinition of the expected object type. However, the robustnessprinciple requires that one exercise care with respect to controlactions: if an instance does not have the same syntax as itsexpected object type, then those control actions must fail. In both the monitoring and control cases, the name of an object returned byan operation must be identical to the name requested by an operation. Rose & McCloghrie [Page 16]6. DefinitionsRFC1155-SMI DEFINITIONS ::= BEGINEXPORTS -- EVERYTHINGinternet, directory, mgmt,experimental, private, enterprises,OBJECT-TYPE, ObjectName, ObjectSyntax, SimpleSyntax, ApplicationSyntax, NetworkAddress, IpAddress,Counter, Gauge, TimeTicks, Opaque;-- the path to the rootinternet OBJECT IDENTIFIER ::= { iso org(3) dod(6) 1 } directory OBJECT IDENTIFIER ::= { internet 1 }mgmt OBJECT IDENTIFIER ::= { internet 2 }experimental OBJECT IDENTIFIER ::= { internet 3 }private OBJECT IDENTIFIER ::= { internet 4 }enterprises OBJECT IDENTIFIER ::= { private 1 }-- definition of object typesOBJECT-TYPE MACRO ::=BEGINTYPE NOTATION ::= "SYNTAX" type (TYPE ObjectSyntax)"ACCESS" Access"STATUS" StatusVALUE NOTATION ::= value (VALUE ObjectName)Access ::= "read-only"| "read-write"| "write-only"| "not-accessible"Status ::= "mandatory"| "optional"| "obsolete"END-- names of objects in the MIBObjectName ::=OBJECT IDENTIFIERRose & McCloghrie [Page 17]-- syntax of objects in the MIBObjectSyntax ::=CHOICE {simpleSimpleSyntax,-- note that simple SEQUENCEs are not directly-- mentioned here to keep things simple (i.e.,-- prevent mis-use). However, application-wide-- types which are IMPLICITly encoded simple-- SEQUENCEs may appear in the following CHOICEapplication-wideApplicationSyntax}SimpleSyntax ::=CHOICE {numberINTEGER,stringOCTET STRING,objectOBJECT IDENTIFIER,emptyNULL}ApplicationSyntax ::=CHOICE {addressNetworkAddress,counterCounter,gaugeGauge,ticksTimeTicks,arbitraryOpaqueRose & McCloghrie [Page 18]。

程序员单词书：L：laser 激光late binding 迟绑定left outer join 左向外联接(for database)level 阶、层例high level 高阶、高层library 库lifetime 生命期、寿命link 连接、链接linkage 连接、链接linker 连接器、链接器literal constant 字面常数list 列表、表、链表list box 列表框livelock 活锁(for database)load 装载、加载load balancing 负载平衡loader 装载器、载入器local 局部的local object 局部对象lock 锁log 日志login 登录login securitymode 登录安全模式(for database) lookup table 查找表(for database)loop 循环loose coupling 松散耦合lvalue 左值M：machine code 机器码、机器代码macro 宏maintain 维护managed code 受控代码、托管代码Managed Extensions 受控扩充件、托管扩展managed object 受控对象、托管对象manifest 清单manipulator 操纵器(iostream 预先定义的一种东西)many-to-manyrelationship 多对多关系(for database)many-to-onerelationship 多对一关系(for database)marshal 列集member 成员member accessoperator 成员取用运算子(有 dot 和 arrow 两种) member function 成员函数memberinitialization list 成员初始值列表memberwise 以 member 为单元…、members 逐一…memory 内存memory leak 内存泄漏menu 菜单message 消息message based 基于消息的message loop 消息环message queuing 消息队列metadata 元数据metaprogramming 元编程method 方法micro 微middleware 中间件middle tier 中间层modeling 建模modeling language 建模语言modifier 修饰字、修饰符modem 调制解调器module 模块most derived class 最底层的派生类mouse 鼠标mutable 可变的mutex 互斥元、互斥体multidimensionalOLAP (MOLAP) 多维 OLAP(MOLAP) (for database) multithreadedserver application 多线程服务器应用程序multiuser 多用户multi-tasking 多任务multi-thread 多线程multicast delegate 组播委托、多点委托N：named parameter 命名参数named pipe 命名管道namespace 名字空间、命名空间native 原生的、本地的native code 本地码、本机码Native ImageGenerator (NGEN)本地映像生成器nested class 嵌套类nested query 嵌套查询(for database)nested table 嵌套表(for database)network 网络network card 网卡nondependent name object 对象O：object based 基于对象的object file 目标文件object model 对象模型object oriented 面向对象的object pooling 对象池化ODBC data sourceODBC 数据源(for database)ODBC driver ODBC 驱动程序(for database) ODR(one-definition rule)OLE Automationobjects OLE 自动化对象(for database)OLE Automationserver OLE 自动化服务器(for database)OLE DB consumerOLE DB 使用者(for database)OLE DB for OLAP 用于 OLAP 的 OLE DB (for database)OLE DB providerOLE DB 提供者(for database)one-to-manyrelationship 一对多关系(for database)one-to-onerelationship 一对一关系(for database)online analyticalprocessing (OLAP) 联机分析处理(OLAP) (for database) online redo log 联机重做日志(for database)online transactionprocessing (OLTP) 联机事务处理(OLTP) (for database) Open Data Services(ODS) 开放式数据服务(ODS) (for database)Open DatabaseConnectivity (ODBC)开放式数据库连接(ODBC) (for database) operand 操作数operating system(OS)操作系统operation 操作operator 操作符、运算符option 选项optimizer 优化器outer join 外联接(for database)overflow 上限溢位(相对于 underflow)overhead 额外开销overload 重载overloadresolution 重载决议overloadedfunction 重载的函数overloadedoperator 被重载的操作符override 覆写、重载、重新定义P：package 包packaging 打包palette 调色板parallel 并行parameter 参数、形式参数、形参parameter list 参数列表parameterize 参数化parent class 父类parentheses 圆括弧、圆括号parse 解析parser 解析器part 零件、部件partialspecialization 局部特化pass by address 传址(函式引数的传递方式)(非正式用语) pass by reference 传地址、按引用传递pass by value 按值传递pattern 模式PDA (personaldigital assistant)个人数字助理PE (PortableExecutable) file 可移植可执行文件performance 性能persistence 持久性PInvoke (platforminvoke service)平台调用服务pixel 像素placement delete placement new placeholder 占位符platform 平台POD (plain olddata (type)) POI (point ofinstantiation) pointer 指针poll 轮询pooling 池化polymorphism 多态pop up 弹出式port 端口postfix 后缀precedence 优先序(通常用于运算子的优先执行次序)prefix 前缀preprocessor 预处理器primary key (PK)主键(PK) (for database)primary table 主表(for database)primary template 原始模板primitive type 原始类型print 打印printer 打印机procedure 过程procedural 过程式的、过程化的process 进程profile 评测profiler 效能(性能)评测器program 程序programmer 程序员programming 编程、程序设计progress bar 进度指示器project 项目、工程property 属性protocol 协议pseudo code 伪码Q：qualified 经过资格修饰(例如加上 scope 运算子)qualifier 修饰符quality 质量queue 队列R：race condition 竞争条件（多线程环境常用语）radian 弧度radio button 单选按钮raise 引发(常用来表示发出一个 exception)random number 随机数range 范围、区间rank 等级raw 未经处理的readOnly 只读record 记录(for database)recordset 记录集(for database recursive 递归re-direction 重定向refactoring 重构refer 引用、参考reference 引用、参考reference counting 引用计数referentialintegrity (RI)引用完整性(RI) (for database) register 寄存器reflection 反射refresh data 刷新数据(for database)regular expression 正则表达式relationaldatabase 关系数据库remote 远程remote request 远程请求represent 表述，表现resolve 解析、决议resolution 解析过程result set 结果集(for database)retrieve data 检索数据return 返回return type 返回类型return value 返回值right outer join 右向外联接(for database)revoke 撤销robust 健壮robustness 健壮性roll back 回滚(for database)roll forward 前滚(for database)routine 例程row 行(for database)row lock 行锁(for database)rowset 行集(for database)RPC (remoteprocedure call)RPC(远程过程调用)runtime 执行期、运行期、执行时、运行时rvalue 右值S：save 保存savepoint 保存点(for database) SAX (Simple APIfor XML) scalable 可伸缩的、可扩展的schedule 调度scheduler 调度程序schema 模式、纲目结构scroll bar 滚动条scope 作用域、生存空间scope operator 生存空间操作符scope resolutionoperator 生存空间解析操作符screen 屏幕SDK (SoftwareDevelopment Kit)软件开发包sealed class 密封类search 查找semantics 语义semaphore 信号量sequentialcontainer 序列式容器server 服务器、服务端serial 串行serialization/serialize 序列化server cursor 服务端游标、服务器游标(for database) session 会话(for database)setter 设值函数shared lock 共享锁(for database)sibling 同级side effect 副作用signature 签名single-threaded 单线程slider 滑块slot 槽smart pointer 智能指针SMTP (Simple MailTransfer Protocol) 简单邮件传输协议snapshot 截屏图snapshot 快照(for database)specialization 特化specification 规范、规格splitter 切分窗口SOAP (simpleobject access protocol) 简单对象访问协议software 软件source code 源码、源代码SQL (StructuredQuery Language) 结构化查询语言(for database) stack 栈、堆栈stack unwinding 叠辗转开解(此词用于 exception 主题) standard library 标准库standard templatelibrary 标准模板库stateless 无状态的statement 语句、声明static cursor 静态游标(for database)static SQLstatements 静态 SQL 语句(fordatabase)stored procedure 存储过程(for database)status bar 状态条stream 流string 字符串stub 存根subobject 子对象subquery 子查询(for database)subroutine 子例程subscript operator 下标操作符subset 子集subtype 子类型support 支持suspend 挂起symbol 记号syntax 语法system databases 系统数据库(for database)system tables 系统表(for database)T：table 表(for database)table lock 表锁(for database)table-levelconstraint 表级约束(for database)tape backup 磁带备份(for database)target 标的,目标task switch 工作切换TCP (TransportControl Protocol) 传输控制协议template 模板template-idtemplate argumentdeduction 模板参数推导template explicitspecialization 模板显式特化template parameter 模板参数template templateparameter temporary object 临时对象temporary table 临时表(for database)text 文本text file 文本文件thin client 瘦客户端third-party 第三方thread 线程thread-safe 线程安全的throw 抛出、引发(常指发出一个 exception)token 符号、标记、令牌（看场合）trace 跟踪transaction 事务(for database)transaction log 事务日志(for database)transactionrollback 事务回滚(for database)transactionalreplication 事务复制(for database)translation unit 翻译单元traverse 遍历trigger 触发器(for database)two-phase commit 两阶段提交(for database)tuple 元组，字节组two-phase lookup 两阶段查找type 类型U：UDDI(UniversaryDescription, Discovery and Integration)统一描述、查询与集成UML (unifiedmodeling language)统一建模语言unary function 单参函数unary operator 一元操作符unboxing 拆箱、拆箱转换underflow 下限溢位(相对于 overflow)Union query 联合查询(for database)UNIQUE constraintsUNIQUE 约束(for database)unique index 唯一索引(for database)unmanaged code 非受控代码、非托管代码unmarshal 散集unqualified 未经限定的、未经修饰的URI (UniformResource identifier)统一资源标识符URL (UniformResource Locator) 统一资源定位器user 用户user interface 用户界面V：value types 值类型variable 变量vector 向量(一种容器，有点类似 array)viable 可行的video 视频view 视图VEE (VirtualExecution Engine)虚拟执行引擎vendor 厂商view 视图(for database)virtual function 虚函数virtual machine 虚拟机virtual memory 虚拟内存vowel 元音字母W：Web Services web 服务WHERE clause WHERE 子句(for database) wildcardcharacters 通配符字符(for database) wildcard search 通配符搜索(for database) window 窗口window function 窗口函数window procedure 窗口过程Windowsauthentication Windows 身份验证wizard 向导word 单词word processor 字处理器wrapper 包装、包装器write enable 写启用(for database)write-ahead log 预写日志(for database)write-only 只写WSDL (Web ServiceDescription Language)Web Service 描述语言X：XML MessageInterface (XMI) XML 消息接口XML (eXtensibleMarkup Language) 可扩展标记语言XSD (XML SchemaDefinition)XML 模式定义语言XSL (eXtensibleStylesheet Language)可扩展样式表语言XSLT (eXtensibleStylesheet Language Transformation)可扩展样式表语言转换xxx based 基于 xxx 的xxx oriented 面向 xxx。

OFFSHORE STANDARDD ET N ORSKE VERITASDNV-OS-C201STRUCTURAL DESIGN OF OFFSHOREUNITS (WSD METHOD)APRIL 2005Since issued in print (April 2005), this booklet has been amended, latest in April 2006.See the reference to “Amendments and Corrections” on the next page.Comments may be sent by e-mail to rules@For subscription orders or information about subscription terms, please use distribution@Comprehensive information about DNV services, research and publications can be found at http :// , or can be obtained from DNV,Veritasveien 1, NO-1322 Høvik, Norway; Tel +47 67 57 99 00, Fax +47 67 57 99 11.© Det Norske Veritas. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, including photocopying and recording, without the prior written consent of Det Norske puter Typesetting (FM+SGML) by Det Norske Veritas.Printed in Norway.If any person suffers loss or damage which is proved to have been caused by any negligent act or omission of Det Norske Veritas, then Det Norske Veritas shall pay compensation to such person for his proved direct loss or damage. However, the compensation shall not exceed an amount equal to ten times the fee charged for the service in question, provided that the maximum compen-sation shall never exceed USD 2 million.In this provision "Det Norske Veritas" shall mean the Foundation Det Norske Veritas as well as all its subsidiaries, directors, officers, employees, agents and any other acting on behalf of Det Norske Veritas.FOREWORDDET NORSKE VERITAS (DNV) is an autonomous and independent foundation with the objectives of safeguarding life, prop-erty and the environment, at sea and onshore. DNV undertakes classification, certification, and other verification and consultancy services relating to quality of ships, offshore units and installations, and onshore industries worldwide, and carries out research in relation to these functions.DNV Offshore Codes consist of a three level hierarchy of documents:—Offshore Service Specifications. Provide principles and procedures of DNV classification, certification, verification and con-sultancy services.—Offshore Standards. Provide technical provisions and acceptance criteria for general use by the offshore industry as well asthe technical basis for DNV offshore services.—Recommended Practices. Provide proven technology and sound engineering practice as well as guidance for the higher levelOffshore Service Specifications and Offshore Standards.DNV Offshore Codes are offered within the following areas:A)Qualification, Quality and Safety Methodology B)Materials Technology C)Structures D)SystemsE)Special Facilities F)Pipelines and Risers G)Asset Operation H)Marine Operations J)Wind TurbinesAmendments and CorrectionsThis document is valid until superseded by a new revision. Minor amendments and corrections will be published in a separate document normally updated twice per year (April and October).For a complete listing of the changes, see the “Amendments and Corrections” document located at: /technologyservices/, “Offshore Rules & Standards”, “Viewing Area”.The electronic web-versions of the DNV Offshore Codes will be regularly updated to include these amendments and corrections.Amended April 2006,Offshore Standard DNV-OS-C201, April 2005 see note on front cover Changes – Page 3Changes April 2005—Sec.1. Unification of requirements, level of references, terms, definitions, lay-out, text, etc. with the LRFD stand-ards, i.e. general standard (DNV-OS-C101), the standards for various objects (DNV-OS-C102 to DNV-OS-C106), as well as the fabrication standard (DNV-OS-C401). —Sec.1 & Sec.2. Definition and application of design tem-perature and service temperature has been updated, and the terminology co-ordinated with the LRFD standards.—Sec.4. Overall conditions for fracture mechanics (FM) testing, and post weld heat treatment (PWHT) transferred here (from DNV-OS-C401). Requirements to FM adjusted to reflect results of more recent research work. —Sec.5. References to the more recent Recommended Prac-tices introduced e.g. DNV-RP-C201 (for Plates), updating references to CN 30.1.—Sec.3 D300. Specified tank pressures are harmonised with similar formulas in the LRFD standards, while simultane-ously attempted simplified and clarified.—Sec.11 to Sec.14. (Ref. to the various objects.) Formulas for sea pressure during transit are reorganised and clari-fied, improving readability.—Sec.12. Text covering redundancy and detailed design re-vised in line with DNV-OS-C104 (and the previous MOU-rules).—Sec.13. Text regarding the topics of tendon fracture me-chanics, composite tendons, and stability, as well as the CMC requirements are all updated, bringing the text in line with most recent revision of DNV-OS-C105.—Sec.14. Text updated in line with ongoing revision of DNV-OS-C106.D ET N ORSKE V ERITASOffshore Standard DNV-OS-C201, April 2005Amended April 2006, Page 4 – Changes see note on front coverD ET N ORSKE V ERITASAmended April 2006,Offshore Standard DNV-OS-C201, April 2005 see note on front cover Contents – Page 5CONTENTSSec. 1Introduction (9)A.General (9)A100Introduction (9)A200Objectives (9)A300Scope and application (9)A400Other than DNV codes (9)A500Classification (9)B.References (9)B100General (9)C.Definitions (10)C100Verbal forms (10)C200Terms (10)D.Abbreviations and Symbols (12)D100Abbreviations (12)D200Symbols (12)Sec. 2Design Principles (15)A.Introduction (15)A100General (15)A200Aim of the design (15)B.General Design Considerations (15)B100General (15)B200Overall design (15)B300Details design (15)C.Design Conditions (15)C100Basic conditions (15)D.Loading Conditions (16)D100General (16)D200Load (16)E.Design by the WSD Method (16)E100Permissible stress and usage factors (16)E200Basic usage factors (16)F.Design Assisted by Testing (16)F100General (16)F200Full-scale testing and observation of performance of existing structures (16)Sec. 3Loads and Load Effects (17)A.Introduction (17)A100General (17)B.Basis for Selection of Loads (17)B100General (17)C.Permanent Functional Loads (17)C100General (17)D.Variable Functional Loads (18)D100General (18)D200Variable functional loads on deck areas (18)D300Tank pressures (18)D400Lifeboat platforms (19)E.Environmental Loads (19)E100General (19)E200Environmental conditions for mobile units (19)E300Environmental conditionss for site specific units (19)E400Determination of hydrodynamic loads (19)E500Wave loads (19)E600Wave induced inertia forces (20)E700Current (20)E800Wind loads (20)E900Vortex induced oscillations (20)E1000Water level and tidal effects (20)E1100Marine growth (20)E1200Snow and ice accumulation............................................20E1300Direct ice load.. (20)E1400Earthquake (20)bination of Environmental Loads (21)F100General (21)G.Accidental Loads (21)G100General (21)H.Deformation Loads (21)H100General (21)H200Temperature loads (21)H300Settlements and subsidence of sea bed (21)I.Fatigue loads (22)I100General (22)J.Load Effect Analysis (22)J100General (22)J200Global motion analysis (22)J300Load effects in structures and soil or foundation (22)Sec. 4Structural Categorisation, Material Selection and Inspection Principles (23)A.General (23)A100 (23)B.Temperatures for Selection of Material (23)B100General (23)B200Floating units (23)B300Bottom fixed units (23)C.Structural Category (23)C100General (23)C200Selection of structural category (23)C300Inspection of welds (24)D.Structural Steel (24)D100General (24)D200Material designations (24)D300Selection of structural steel (25)D400Fracture mechanics (FM) testing (25)D500Post weld heat treatment (PWHT) (25)Sec. 5Structural Strength (26)A.General (26)A100General (26)A200Structural analysis (26)A300Ductility (26)A400Yield check (26)A500Buckling check (27)B.Flat Plated Structures and Stiffened Panels (27)B100Yield check (27)B200Buckling check (27)B300Capacity checks according to other codes (27)C.Shell Structures (27)C100General (27)D.Tubular Members, Tubular Joints and Conical Transitions.27 D100General (27)E.Non-Tubular Beams, Columns and Frames (28)E100General (28)Sec. 6Section Scantlings (29)A.General (29)A100Scope (29)B.Strength of Plating and Stiffeners (29)B100Scope (29)B200Minimum thickness (29)B300Bending of plating (29)D ET N ORSKE V ERITASOffshore Standard DNV-OS-C201, April 2005Amended April 2006, Page 6 – Contents see note on front coverB400Stiffeners (29)C.Bending and Shear in Girders (30)C100General (30)C200Minimum thickness (30)C300Bending and shear (30)C400Effective flange (30)C500Effective web (30)C600Strength requirements for simple girders (30)C700Complex girder systems (31)Sec. 7Fatigue (32)A.General (32)A100General (32)A200Design fatigue factors (32)A300Methods for fatigue analysis (32)A400Simplified fatigue analysis (33)A500Stochastic fatigue analysis (33)Sec. 8Accidental Conditions (34)A.General (34)A100General (34)B.Design Criteria (34)B100General (34)B200Collision (34)B300Dropped objects (34)B400Fires (34)B500Explosions (34)B600Unintended flooding (34)Sec. 9Weld Connections (36)A.General (36)A100Scope (36)B.Types of Welded Steel Joints (36)B100Butt joints (36)B200Tee or cross joints (36)B300Slot welds (37)B400Lap joint (37)C.Weld Size (37)C100General (37)C200Fillet welds (37)C300Partly penetration welds and fillet welds in crossconnections subject to high stresses (38)C400Connections of stiffeners to girders and bulkheads, etc..38 C500End connections of girders (39)C600Direct calculation of weld connections (39)Sec. 10Corrosion Control (40)A.General (40)A100Scope (40)B.Techniques for Corrosion Control Related to EnvironmentalZones (40)B100Atmospheric zone (40)B200Splash zone (40)B300Submerged zone (40)B400Internal zone (40)C.Cathodic Protection (41)C100General (41)C200Galvanic anode systems (41)C300Impressed current systems (42)D.Coating Systems (42)D100Specification of coating (42)Sec. 11Special Considerations for Column Stabilised Units (43)A.General (43)A100Assumptions and application (43)B.Structural Categorisation, Material Selection and InspectionPrinciples (43)B100General (43)B200Structural categorisation (43)B300Material selection (43)B400Inspection categories (44)C.Design and Loading Conditions (46)C100General (46)C200Permanent loads (46)C300Variable functional loads (46)C400Tank loads (46)C500Environmental loads, general (46)C600Sea pressures (47)C700Wind loads (47)C800Heavy components (47)C900Combination of loads (47)D.Structural Strength (47)D100General (47)D200Global capacity (47)D300Transit condition (47)D400Method of analysis (48)D500Air gap (48)E.Fatigue (48)E100General (48)E200Fatigue analysis (49)F.Accidental Conditions (49)F100General (49)F200Collision (49)F300Dropped objects (49)F400Fire (49)F500Explosion (49)F600Heeled condition (49)G.Redundancy (49)G100General (49)G200Brace arrangements (49)H.Structure in Way of a Fixed Mooring System (49)H100Structural strength (49)I.Structural Details (50)I100General (50)Sec. 12Special Considerations forSelf-Elevating Units (51)A.Introduction (51)A100Scope and application (51)B.Structural Categorisation, Material Selection and InspectionPrinciples (51)B100General (51)B200Structural categorisation (51)B300Material selection (51)B400Inspection categories (51)C.Design and Loading Conditions (51)C100General (51)C200Transit (52)C300Installation and retrieval (52)C400Operation and survival (52)D.Environmental Conditions (53)D100General (53)D200Wind (53)D300Waves (53)D400Current (53)D500Snow and ice (53)E.Method of Analysis (53)E100General (53)E200Global structural models (54)E300Local structural models (54)E400Fatigue analysis (55)F.Design Loads (55)F100General (55)F200Permanent loads (55)D ET N ORSKE V ERITASAmended April 2006,Offshore Standard DNV-OS-C201, April 2005 see note on front cover Contents – Page 7F300Variable functional loads (55)F400Tank loads (55)F500Environmental loads, general (55)F600Wind loads (55)F700Waves (56)F800Current (56)F900Wave and current (56)F1000Sea pressures during transit (57)F1100Heavy components during transit (57)F1200Combination of loads (57)G.Structural Strength (57)G100General (57)G200Global capacity (57)G300Footing strength (57)G400Leg strength (58)G500Jackhouse support strength (58)G600Hull strength (58)H.Fatigue Strength (58)H100General (58)H200Fatigue analysis (58)I.Accidental Conditions (58)I100General (58)I200Collisions (58)I300Dropped objects (58)I400Fires (58)I500Explosions (58)I600Unintended flooding (58)J.Miscellaneous requirements (59)J100General (59)J200Pre-load capasity (59)J300Overturning stability (59)J400Air gap (59)Sec. 13Special Considerations forTension Leg Platforms (TLP) (61)A.General (61)A100Scope and application (61)A200Description of tendon system (61)B.Structural Categorisation, Material Selection and InspectionPrinciples (62)B100General (62)B200Structural categorisation (62)B300Material selection (63)B400Design temperatures (63)B500Inspection categories (63)C.Design Principles (63)C100General (63)C200Design conditions (64)C300Fabrication (64)C400Hull and Deck Mating (64)C500Sea transportation (64)C600Installation (64)C700Decommissioning (64)C800Design principles, tendons (64)D.Design Loads (65)D100General (65)D200Load categories (65)E.Global Performance (65)E100General (65)E200Frequency domain analysis (66)E300High frequency analyses (66)E400Wave frequency analyses (66)E500Low frequency analyses (66)E600Time domain analyses (66)E700Model testing (67)E800Load effects in the tendons (67)F.Structural Strength (67)F100General (67)F200Hull (68)F300Structural analysis (68)F400Structural design.............................................................68F500Deck.. (68)F600Extreme tendon tensions (69)F700Structural design of tendons (69)F800Foundations (69)G.Fatigue (69)G100General (69)G200Hull and deck (69)G300Tendons (69)G400Foundation (70)H.Accidental Condition (70)H100Hull (70)H200Hull and deck (71)H300Tendons (71)H400Foundations (71)Sec. 14Special Considerations for Deep DraughtFloaters (DDF) (72)A.General (72)A100Introduction (72)A200Scope and application (72)B.Non-Operational Phases (72)B100General (72)B200Fabrication (72)B300Mating (72)B400Sea transportation (72)B500Installation (72)B600Decommissioning (73)C.Structural Categorisation, Selection of Material andExtent of Inspection (73)C100General (73)C200Material selection (73)C300Design temperatures (73)C400Inspection categories (73)C500Guidance to minimum requirements (73)D.Design Loads (74)D100Permanent loads (74)D200Variable functional loads (74)D300Environmental loads (74)D400Determination of loads (74)D500Hydrodynamic loads (74)E.Deformation Loads (74)E100General (74)F.Accidental Loads (75)F100General (75)G.Fatigue Loads (75)G100General (75)bination of Loads (75)H100General (75)I.Load Effect Analysis in Operational Phase (75)I100General (75)I200Global bending effects (75)J.Load Effect Analysis in Non-Operational Phases (75)J100General (75)J200Transportation (76)J300Launching (76)J400Upending (76)J500Deck mating (76)J600Riser installations (76)K.Structural Strength (76)K100Operation phase for hull (76)K200Non-operational phases for hull (76)K300Operation phase for deck or topside (77)K400Non-operational phases for deck or topside (77)L.Fatigue (77)L100General (77)L200Operation phase for hull (77)L300Non-operational phases for hull (77)D ET N ORSKE V ERITASOffshore Standard DNV-OS-C201, April 2005Amended April 2006, Page 8 – Contents see note on front coverL400Splash zone (77)L500Operation phase for deck or topside (78)L600Non-operational phases for deck or topside (78)M.Accidental Condition (78)M100General (78)M200Fire (78)M300Explosion (78)M400Collision (78)M500Dropped objects (78)M600Unintended flooding (78)M700Abnormal wave events (78)App. A Cross Sectional Types (80)A.Cross Sectional Types (80)A100General (80)A200Cross section requirements for plastic analysis (80)A300Cross section requirements whenelastic global analysis is used (80)App. B Methods and Models for Design of Column-Stabilised Units (82)A.Methods and Models (82)A100General (82)A200World wide operation (82)A300Benign waters or restricted areas (82)App. C Permanently Installed Units (83)A.Introduction (83)A100Application (83)B.Inspection and Maintenance (83)B100Facilities for inspection on location................................83C.Fatigue. (83)C100Design fatigue factors (83)C200Splash zone for floating units (83)App. D Certification of Tendon System (84)A.General (84)A100Introduction (84)B.Equipment categorization (84)B100General (84)C.Fabrication Record (84)C100General (84)D.Documentation Deliverables for Certification ofEquipment (85)D100General (85)E.Tendon Systems and Components (85)E100General (85)E200Tendon pipe (85)E300Bottom tendon interface (BTI) (86)E400Flex bearings (86)E500Foundations (86)E600Top tendon interface (TTI) (86)E700Intermediate tendon connectors (ITC) (86)E800Tendon tension monitoring system (TTMS) (86)E900Tendon porch (87)E1000Tendon corrosion protection system (87)E1100Load management program (LMP) (87)F.Categorisation of Tendon Components (87)F100General (87)G.Tendon Fabrication (88)G100General (88)D ET N ORSKE V ERITASAmended April 2006,Offshore Standard DNV-OS-C201, April 2005 see note on front cover Sec.1 – Page 9SECTION 1INTRODUCTIONA. GeneralA 100Introduction101 This offshore standard provides principles, technical re-quirements and guidance for the structural design of offshore structures, based on the Working Stress Design (WSD) meth-od.102 This standard has been written for general world-wide application. Statutory regulations may include requirements in excess of the provisions by this standard depending on size, type, location and intended service of the offshore unit or in-stallation.103 The standard is organised with general sections contain-ing common requirements and sections containing specific re-quirement for different type of offshore units. In case of deviating requirements between general sections and the ob-ject specific sections, requirements of the object specific sec-tions shall apply.A 200Objectives201 The objectives of this standard are to:—provide an internationally acceptable level of safety by de-fining minimum requirements for structures and structural components (in combination with referred standards, rec-ommended practices, guidelines, etc.)—serve as a contractual reference document between suppli-ers and purchasers—serve as a guideline for designers, suppliers, purchasers and regulators—specify procedures and requirements for offshore struc-tures subject to DNV certification and classification.A 300Scope and application301 This standard is applicable to the following types of off-shore structures:—column-stabilised units—self-elevating units—tension leg platforms—deep draught floaters.302 For utilisation of other materials, the general design principles given in this standard may be used together with rel-evant standards, codes or specifications covering the require-ments to materials design and fabrication.303 The standard is applicable to structural design of com-plete units including substructures, topside structures and ves-sel hulls.304 This standard gives requirements for the following: —design principles—structural categorisation—material selection and inspection principles—loads and load effect analyses—design of steel structures and connections—special considerations for different types of units. Requirements for foundation design are given in DNV-OS-C101.A 400Other than DNV codes401 Other recognised codes or standards may be applied pro-vided it is shown that the codes and standards, and their appli-cation, meet or exceed the level of safety of the actual DNV standard.402 In case of conflict between requirements of this standard and a reference document other than DNV documents, the re-quirements of this standard shall prevail.403 Where reference is made to codes other than DNV doc-uments, the latest revision of the documents shall be applied, unless otherwise specified.404 When code checks are performed according to other than DNV codes, the usage factors as given in the respective code shall be used.A 500Classification501 Classification principles, procedures and applicable class notations related to classification services of offshore units are specified in the DNV Offshore Service Specifications given in Table A1.502 Documentation requirements for classification are given by DNV-RP-A202.B. ReferencesB 100General101 The DNV documents in Table B1 are referred to in the present standards and contain acceptable methods for fulfilling the requirements in this standard.102 The latest valid revision of the DNV reference docu-ments in Table B2 applies. See also current DNV List of Pub-lications.103 The documents listed in Table B2 are referred in the present standard. The documents include acceptable methods for fulfilling the requirements in the present standard and may be used as a source of supplementary information. Only the referenced parts of the documents apply for fulfilment of the present standard.Table A1 DNV Offshore Service SpecificationsReference TitleDNV-OSS-101Rules for Classification of Offshore Drilling andSupport UnitsDNV-OSS-102Rules for Classification of Floating Productionand Storage UnitsDNV-OSS-103Rules for Classification of LNG/LPG FloatingProduction and Storage Units or Installations DNV-OSS-121Classification Based on Performance CriteriaDetermined by Risk Assessment MethodologyRules for Planning and Execution of MarineOperationsTable B1 DNV Reference DocumentsReference TitleDNV-OS-A101Safety Principles andArrangementDNV-OS-B101Metallic MaterialsDNV-OS-C101Design of Offshore Steel Struc-tures, General (LRFD method) DNV-OS-C301Stability and Watertight Integrity DNV-OS-C401Fabrication and Testing ofOffshore StructuresD ET N ORSKE V ERITASOffshore Standard DNV-OS-C201, April 2005Amended April 2006, Page 10 – Sec.1see note on front coverC. DefinitionsC 100Verbal forms101 Shall: Indicates a mandatory requirement to be followed for fulfilment or compliance with the present standard. Devia-tions are not permitted unless formally and rigorously justified, and accepted by all relevant contracting parties.102 Should: Indicates a recommendation that a certain course of action is preferred or particularly suitable. Alterna-tive courses of action are allowable under the standard where agreed between contracting parties but shall be justified and documented.103 May: Indicates a permission, or an option, which is per-mitted as part of conformance with the standard.C 200Terms201 Accidental condition: When the unit is subjected to ac-cidental loads such as collision, dropped objects, fire explo-sion, etc.202 Accidental loads: Loads which may occur as a result of accident or exceptional events, e.g. collisions, explosions, dropped objects.203 Atmospheric zone: The external surfaces of the unit above the splash zone.204 Cathodic protection: A technique to prevent corrosion of a steel surface by making the surface to be the cathode of an electrochemical cell.205 Characteristic load: The reference value of a load to be used in the determination of load effects. The characteristic load is normally based upon a defined fractile in the upper end of the distribution function for load.206 Characteristic strength: The reference value of structur-al strength to be used in the determination of the design strength. The characteristic strength is normally based upon a 5% fractile in the lower end of the distribution function for re-sistance.207 Characteristic value: The representative value associat-ed with a prescribed probability of not being unfavourably ex-ceeded during the applicable reference period.208 Classic spar: Shell type hull structure.209 Classification Note: The Classification Notes cover proven technology and solutions which is found to represent good practice by DNV, and which represent one alternative for satisfying the requirements given in the DNV Rules or other codes and standards cited by DNV. The Classification Notes will in the same manner be applicable for fulfilling the require-ments in the DNV Offshore Standards.210 Coating: Metallic, inorganic or organic material applied to steel surfaces for prevention of corrosion.211 Column-stabilised unit: A floating unit that can be relo-cated. A column-stabilised unit normally consists of a deck structure with a number of widely spaced, large diameter, sup-porting columns that are attached to submerged pontoons. 212 Corrosion allowance: Extra wall thickness added during design to compensate for any anticipated reduction in thick-ness during the operation.213 Damaged condition: The unit condition after accidental damage.214 Deep draught floater (DDF): A floating unit categorised with a relative large draught. The large draught is mainly intro-duced to obtain reduced wave excitation in heave and suffi-ciently high eigenperiod in heave such that resonant responses in heave can be omitted or minimised.215 Design brief: An agreed document presenting owner's technical basis, requirements and references for the unit design and fabrication.216 Design temperature: The design temperature for a unit is the reference temperature for assessing areas where the unit can be transported, installed and operated. The design temper-ature is to be lower or equal to the lowest mean daily tempera-ture in air for the relevant areas. For seasonal restricted operations the lowest mean daily temperature in air for the sea-son may be applied.217 Driving voltage: The difference between closed circuit anode potential and the protection potential.218 Dry transit: A transit where the unit is transported on a heavy lift unit from one geographical location to another. 219 Dynamic upending: A process where seawater is filled or flooded into the bottom section of a horizontally floating DDF hull and creating a trim condition and subsequent water filling of hull or moonpool and dynamic upending to bring the hull in vertical position.220 Environmental loads: Loads directly and indirectly due to environmental phenomena. Environmental loads are not a necessary consequence of the structures existence, use and treatments. All external loads which are responses to environ-mental phenomena are to be regarded as environmental loads, e.g. support reactions, mooring forces, and inertia forces. 221 Expected loads and response history: Expected load and response history for a specified time period, taking into ac-count the number of load cycles and the resulting load levels and response for each cycle.222 Expected value: The most probable value of a load dur-ing a specified time period.223 Fail to safe: A failure shall not lead to new failure, which may lead to total loss of the structure.DNV-OS-D101Marine Machinery Systems andEquipmentDNV-OS-E301Position MooringDNV-OS-F201Dynamic RisersDNV-RP-C103Column Stabilised UnitsDNV-RP-C201Buckling Strength of PlatedStructuresDNV-RP-C202Buckling Strength of Shells DNV-RP-C203Fatigue Strength Analysis ofOffshore Steel Structures Classification Note 30.1Buckling Strength Analysis ofBars and Frames, and SphericalShellsClassification Note 30.4 FoundationsClassification Note 30.5 Environmental Conditions andEnvironmental Loads Classification Note 31.5Strength Analysis of MainStructures of Self-elevating Units Table B2 Other referencesReference TitleAISC-ASD Manual of Steel Construction ASDAPI RP 2A – WSD with supplement 1Planning, Designing and Constructing Fixed Offshore Platforms – Working Stress DesignAPI RP 2T Planning, Designing and Constructing TensionLeg PlatformsBS 7910Guide on methods for assessing the acceptability offlaws in fusion welded structuresNACE TPC Publication No. 3. The role of bacteria in corrosionof oil field equipmentSNAME 5-5A Site Specific Assessment of Mobile Jack-Up UnitsD ET N ORSKE V ERITAS。

Error MessagesF9001 Error internal function call.F9002 Error internal RTOS function callF9003 WatchdogF9004 Hardware trapF8000 Fatal hardware errorF8010 Autom. commutation: Max. motion range when moving back F8011 Commutation offset could not be determinedF8012 Autom. commutation: Max. motion rangeF8013 Automatic commutation: Current too lowF8014 Automatic commutation: OvercurrentF8015 Automatic commutation: TimeoutF8016 Automatic commutation: Iteration without resultF8017 Automatic commutation: Incorrect commutation adjustment F8018 Device overtemperature shutdownF8022 Enc. 1: Enc. signals incorr. (can be cleared in ph. 2) F8023 Error mechanical link of encoder or motor connectionF8025 Overvoltage in power sectionF8027 Safe torque off while drive enabledF8028 Overcurrent in power sectionF8030 Safe stop 1 while drive enabledF8042 Encoder 2 error: Signal amplitude incorrectF8057 Device overload shutdownF8060 Overcurrent in power sectionF8064 Interruption of motor phaseF8067 Synchronization PWM-Timer wrongF8069 +/-15Volt DC errorF8070 +24Volt DC errorF8076 Error in error angle loopF8078 Speed loop error.F8079 Velocity limit value exceededF8091 Power section defectiveF8100 Error when initializing the parameter handlingF8102 Error when initializing power sectionF8118 Invalid power section/firmware combinationF8120 Invalid control section/firmware combinationF8122 Control section defectiveF8129 Incorrect optional module firmwareF8130 Firmware of option 2 of safety technology defectiveF8133 Error when checking interrupting circuitsF8134 SBS: Fatal errorF8135 SMD: Velocity exceededF8140 Fatal CCD error.F8201 Safety command for basic initialization incorrectF8203 Safety technology configuration parameter invalidF8813 Connection error mains chokeF8830 Power section errorF8838 Overcurrent external braking resistorF7010 Safely-limited increment exceededF7011 Safely-monitored position, exceeded in pos. DirectionF7012 Safely-monitored position, exceeded in neg. DirectionF7013 Safely-limited speed exceededF7020 Safe maximum speed exceededF7021 Safely-limited position exceededF7030 Position window Safe stop 2 exceededF7031 Incorrect direction of motionF7040 Validation error parameterized - effective thresholdF7041 Actual position value validation errorF7042 Validation error of safe operation modeF7043 Error of output stage interlockF7050 Time for stopping process exceeded8.3.15 F7051 Safely-monitored deceleration exceeded (159)8.4 Travel Range Errors (F6xxx) (161)8.4.1 Behavior in the Case of Travel Range Errors (161)8.4.2 F6010 PLC Runtime Error (162)8.4.3 F6024 Maximum braking time exceeded (163)8.4.4 F6028 Position limit value exceeded (overflow) (164)8.4.5 F6029 Positive position limit exceeded (164)8.4.6 F6030 Negative position limit exceeded (165)8.4.7 F6034 Emergency-Stop (166)8.4.8 F6042 Both travel range limit switches activated (167)8.4.9 F6043 Positive travel range limit switch activated (167)8.4.10 F6044 Negative travel range limit switch activated (168)8.4.11 F6140 CCD slave error (emergency halt) (169)8.5 Interface Errors (F4xxx) (169)8.5.1 Behavior in the Case of Interface Errors (169)8.5.2 F4001 Sync telegram failure (170)8.5.3 F4002 RTD telegram failure (171)8.5.4 F4003 Invalid communication phase shutdown (172)8.5.5 F4004 Error during phase progression (172)8.5.6 F4005 Error during phase regression (173)8.5.7 F4006 Phase switching without ready signal (173)8.5.8 F4009 Bus failure (173)8.5.9 F4012 Incorrect I/O length (175)8.5.10 F4016 PLC double real-time channel failure (176)8.5.11 F4017 S-III: Incorrect sequence during phase switch (176)8.5.12 F4034 Emergency-Stop (177)8.5.13 F4140 CCD communication error (178)8.6 Non-Fatal Safety Technology Errors (F3xxx) (178)8.6.1 Behavior in the Case of Non-Fatal Safety Technology Errors (178)8.6.2 F3111 Refer. missing when selecting safety related end pos (179)8.6.3 F3112 Safe reference missing (179)8.6.4 F3115 Brake check time interval exceeded (181)Troubleshooting Guide | Rexroth IndraDrive Electric Drivesand ControlsI Bosch Rexroth AG VII/XXIITable of ContentsPage8.6.5 F3116 Nominal load torque of holding system exceeded (182)8.6.6 F3117 Actual position values validation error (182)8.6.7 F3122 SBS: System error (183)8.6.8 F3123 SBS: Brake check missing (184)8.6.9 F3130 Error when checking input signals (185)8.6.10 F3131 Error when checking acknowledgment signal (185)8.6.11 F3132 Error when checking diagnostic output signal (186)8.6.12 F3133 Error when checking interrupting circuits (187)8.6.13 F3134 Dynamization time interval incorrect (188)8.6.14 F3135 Dynamization pulse width incorrect (189)8.6.15 F3140 Safety parameters validation error (192)8.6.16 F3141 Selection validation error (192)8.6.17 F3142 Activation time of enabling control exceeded (193)8.6.18 F3143 Safety command for clearing errors incorrect (194)8.6.19 F3144 Incorrect safety configuration (195)8.6.20 F3145 Error when unlocking the safety door (196)8.6.21 F3146 System error channel 2 (197)8.6.22 F3147 System error channel 1 (198)8.6.23 F3150 Safety command for system start incorrect (199)8.6.24 F3151 Safety command for system halt incorrect (200)8.6.25 F3152 Incorrect backup of safety technology data (201)8.6.26 F3160 Communication error of safe communication (202)8.7 Non-Fatal Errors (F2xxx) (202)8.7.1 Behavior in the Case of Non-Fatal Errors (202)8.7.2 F2002 Encoder assignment not allowed for synchronization (203)8.7.3 F2003 Motion step skipped (203)8.7.4 F2004 Error in MotionProfile (204)8.7.5 F2005 Cam table invalid (205)8.7.6 F2006 MMC was removed (206)8.7.7 F2007 Switching to non-initialized operation mode (206)8.7.8 F2008 RL The motor type has changed (207)8.7.9 F2009 PL Load parameter default values (208)8.7.10 F2010 Error when initializing digital I/O (-> S-0-0423) (209)8.7.11 F2011 PLC - Error no. 1 (210)8.7.12 F2012 PLC - Error no. 2 (210)8.7.13 F2013 PLC - Error no. 3 (211)8.7.14 F2014 PLC - Error no. 4 (211)8.7.15 F2018 Device overtemperature shutdown (211)8.7.16 F2019 Motor overtemperature shutdown (212)8.7.17 F2021 Motor temperature monitor defective (213)8.7.18 F2022 Device temperature monitor defective (214)8.7.19 F2025 Drive not ready for control (214)8.7.20 F2026 Undervoltage in power section (215)8.7.21 F2027 Excessive oscillation in DC bus (216)8.7.22 F2028 Excessive deviation (216)8.7.23 F2031 Encoder 1 error: Signal amplitude incorrect (217)VIII/XXII Bosch Rexroth AG | Electric Drivesand ControlsRexroth IndraDrive | Troubleshooting GuideTable of ContentsPage8.7.24 F2032 Validation error during commutation fine adjustment (217)8.7.25 F2033 External power supply X10 error (218)8.7.26 F2036 Excessive position feedback difference (219)8.7.27 F2037 Excessive position command difference (220)8.7.28 F2039 Maximum acceleration exceeded (220)8.7.29 F2040 Device overtemperature 2 shutdown (221)8.7.30 F2042 Encoder 2: Encoder signals incorrect (222)8.7.31 F2043 Measuring encoder: Encoder signals incorrect (222)8.7.32 F2044 External power supply X15 error (223)8.7.33 F2048 Low battery voltage (224)8.7.34 F2050 Overflow of target position preset memory (225)8.7.35 F2051 No sequential block in target position preset memory (225)8.7.36 F2053 Incr. encoder emulator: Pulse frequency too high (226)8.7.37 F2054 Incr. encoder emulator: Hardware error (226)8.7.38 F2055 External power supply dig. I/O error (227)8.7.39 F2057 Target position out of travel range (227)8.7.40 F2058 Internal overflow by positioning input (228)8.7.41 F2059 Incorrect command value direction when positioning (229)8.7.42 F2063 Internal overflow master axis generator (230)8.7.43 F2064 Incorrect cmd value direction master axis generator (230)8.7.44 F2067 Synchronization to master communication incorrect (231)8.7.45 F2068 Brake error (231)8.7.46 F2069 Error when releasing the motor holding brake (232)8.7.47 F2074 Actual pos. value 1 outside absolute encoder window (232)8.7.48 F2075 Actual pos. value 2 outside absolute encoder window (233)8.7.49 F2076 Actual pos. value 3 outside absolute encoder window (234)8.7.50 F2077 Current measurement trim wrong (235)8.7.51 F2086 Error supply module (236)8.7.52 F2087 Module group communication error (236)8.7.53 F2100 Incorrect access to command value memory (237)8.7.54 F2101 It was impossible to address MMC (237)8.7.55 F2102 It was impossible to address I2C memory (238)8.7.56 F2103 It was impossible to address EnDat memory (238)8.7.57 F2104 Commutation offset invalid (239)8.7.58 F2105 It was impossible to address Hiperface memory (239)8.7.59 F2110 Error in non-cyclical data communic. of power section (240)8.7.60 F2120 MMC: Defective or missing, replace (240)8.7.61 F2121 MMC: Incorrect data or file, create correctly (241)8.7.62 F2122 MMC: Incorrect IBF file, correct it (241)8.7.63 F2123 Retain data backup impossible (242)8.7.64 F2124 MMC: Saving too slowly, replace (243)8.7.65 F2130 Error comfort control panel (243)8.7.66 F2140 CCD slave error (243)8.7.67 F2150 MLD motion function block error (244)8.7.68 F2174 Loss of motor encoder reference (244)8.7.69 F2175 Loss of optional encoder reference (245)Troubleshooting Guide | Rexroth IndraDrive Electric Drivesand Controls| Bosch Rexroth AG IX/XXIITable of ContentsPage8.7.70 F2176 Loss of measuring encoder reference (246)8.7.71 F2177 Modulo limitation error of motor encoder (246)8.7.72 F2178 Modulo limitation error of optional encoder (247)8.7.73 F2179 Modulo limitation error of measuring encoder (247)8.7.74 F2190 Incorrect Ethernet configuration (248)8.7.75 F2260 Command current limit shutoff (249)8.7.76 F2270 Analog input 1 or 2, wire break (249)8.7.77 F2802 PLL is not synchronized (250)8.7.78 F2814 Undervoltage in mains (250)8.7.79 F2815 Overvoltage in mains (251)8.7.80 F2816 Softstart fault power supply unit (251)8.7.81 F2817 Overvoltage in power section (251)8.7.82 F2818 Phase failure (252)8.7.83 F2819 Mains failure (253)8.7.84 F2820 Braking resistor overload (253)8.7.85 F2821 Error in control of braking resistor (254)8.7.86 F2825 Switch-on threshold braking resistor too low (255)8.7.87 F2833 Ground fault in motor line (255)8.7.88 F2834 Contactor control error (256)8.7.89 F2835 Mains contactor wiring error (256)8.7.90 F2836 DC bus balancing monitor error (257)8.7.91 F2837 Contactor monitoring error (257)8.7.92 F2840 Error supply shutdown (257)8.7.93 F2860 Overcurrent in mains-side power section (258)8.7.94 F2890 Invalid device code (259)8.7.95 F2891 Incorrect interrupt timing (259)8.7.96 F2892 Hardware variant not supported (259)8.8 SERCOS Error Codes / Error Messages of Serial Communication (259)9 Warnings (Exxxx) (263)9.1 Fatal Warnings (E8xxx) (263)9.1.1 Behavior in the Case of Fatal Warnings (263)9.1.2 E8025 Overvoltage in power section (263)9.1.3 E8026 Undervoltage in power section (264)9.1.4 E8027 Safe torque off while drive enabled (265)9.1.5 E8028 Overcurrent in power section (265)9.1.6 E8029 Positive position limit exceeded (266)9.1.7 E8030 Negative position limit exceeded (267)9.1.8 E8034 Emergency-Stop (268)9.1.9 E8040 Torque/force actual value limit active (268)9.1.10 E8041 Current limit active (269)9.1.11 E8042 Both travel range limit switches activated (269)9.1.12 E8043 Positive travel range limit switch activated (270)9.1.13 E8044 Negative travel range limit switch activated (271)9.1.14 E8055 Motor overload, current limit active (271)9.1.15 E8057 Device overload, current limit active (272)X/XXII Bosch Rexroth AG | Electric Drivesand ControlsRexroth IndraDrive | Troubleshooting GuideTable of ContentsPage9.1.16 E8058 Drive system not ready for operation (273)9.1.17 E8260 Torque/force command value limit active (273)9.1.18 E8802 PLL is not synchronized (274)9.1.19 E8814 Undervoltage in mains (275)9.1.20 E8815 Overvoltage in mains (275)9.1.21 E8818 Phase failure (276)9.1.22 E8819 Mains failure (276)9.2 Warnings of Category E4xxx (277)9.2.1 E4001 Double MST failure shutdown (277)9.2.2 E4002 Double MDT failure shutdown (278)9.2.3 E4005 No command value input via master communication (279)9.2.4 E4007 SERCOS III: Consumer connection failed (280)9.2.5 E4008 Invalid addressing command value data container A (280)9.2.6 E4009 Invalid addressing actual value data container A (281)9.2.7 E4010 Slave not scanned or address 0 (281)9.2.8 E4012 Maximum number of CCD slaves exceeded (282)9.2.9 E4013 Incorrect CCD addressing (282)9.2.10 E4014 Incorrect phase switch of CCD slaves (283)9.3 Possible Warnings When Operating Safety Technology (E3xxx) (283)9.3.1 Behavior in Case a Safety Technology Warning Occurs (283)9.3.2 E3100 Error when checking input signals (284)9.3.3 E3101 Error when checking acknowledgment signal (284)9.3.4 E3102 Actual position values validation error (285)9.3.5 E3103 Dynamization failed (285)9.3.6 E3104 Safety parameters validation error (286)9.3.7 E3105 Validation error of safe operation mode (286)9.3.8 E3106 System error safety technology (287)9.3.9 E3107 Safe reference missing (287)9.3.10 E3108 Safely-monitored deceleration exceeded (288)9.3.11 E3110 Time interval of forced dynamization exceeded (289)9.3.12 E3115 Prewarning, end of brake check time interval (289)9.3.13 E3116 Nominal load torque of holding system reached (290)9.4 Non-Fatal Warnings (E2xxx) (290)9.4.1 Behavior in Case a Non-Fatal Warning Occurs (290)9.4.2 E2010 Position control with encoder 2 not possible (291)9.4.3 E2011 PLC - Warning no. 1 (291)9.4.4 E2012 PLC - Warning no. 2 (291)9.4.5 E2013 PLC - Warning no. 3 (292)9.4.6 E2014 PLC - Warning no. 4 (292)9.4.7 E2021 Motor temperature outside of measuring range (292)9.4.8 E2026 Undervoltage in power section (293)9.4.9 E2040 Device overtemperature 2 prewarning (294)9.4.10 E2047 Interpolation velocity = 0 (294)9.4.11 E2048 Interpolation acceleration = 0 (295)9.4.12 E2049 Positioning velocity >= limit value (296)9.4.13 E2050 Device overtemp. Prewarning (297)Troubleshooting Guide | Rexroth IndraDrive Electric Drivesand Controls| Bosch Rexroth AG XI/XXIITable of ContentsPage9.4.14 E2051 Motor overtemp. prewarning (298)9.4.15 E2053 Target position out of travel range (298)9.4.16 E2054 Not homed (300)9.4.17 E2055 Feedrate override S-0-0108 = 0 (300)9.4.18 E2056 Torque limit = 0 (301)9.4.19 E2058 Selected positioning block has not been programmed (302)9.4.20 E2059 Velocity command value limit active (302)9.4.21 E2061 Device overload prewarning (303)9.4.22 E2063 Velocity command value > limit value (304)9.4.23 E2064 Target position out of num. range (304)9.4.24 E2069 Holding brake torque too low (305)9.4.25 E2070 Acceleration limit active (306)9.4.26 E2074 Encoder 1: Encoder signals disturbed (306)9.4.27 E2075 Encoder 2: Encoder signals disturbed (307)9.4.28 E2076 Measuring encoder: Encoder signals disturbed (308)9.4.29 E2077 Absolute encoder monitoring, motor encoder (encoder alarm) (308)9.4.30 E2078 Absolute encoder monitoring, opt. encoder (encoder alarm) (309)9.4.31 E2079 Absolute enc. monitoring, measuring encoder (encoder alarm) (309)9.4.32 E2086 Prewarning supply module overload (310)9.4.33 E2092 Internal synchronization defective (310)9.4.34 E2100 Positioning velocity of master axis generator too high (311)9.4.35 E2101 Acceleration of master axis generator is zero (312)9.4.36 E2140 CCD error at node (312)9.4.37 E2270 Analog input 1 or 2, wire break (312)9.4.38 E2802 HW control of braking resistor (313)9.4.39 E2810 Drive system not ready for operation (314)9.4.40 E2814 Undervoltage in mains (314)9.4.41 E2816 Undervoltage in power section (314)9.4.42 E2818 Phase failure (315)9.4.43 E2819 Mains failure (315)9.4.44 E2820 Braking resistor overload prewarning (316)9.4.45 E2829 Not ready for power on (316)。

CloudCompare V2.6.3 菜单栏和工具栏中英文对照目录一、File——文件 (1)1.1 Open——打开 (1)1.2 Save——保存 (1)1.3 Primitive factory——原始工厂 (1)1.4 3D mouse——3D鼠标 (1)1.5 Close all——全部关闭 (1)1.6 Quit——退出 (1)二、Edit——编辑 (1)2.1 Colors——颜色 (1)2.2 Normals——法向量 (2)2.3 Octree——八叉树 (2)2.4 Mesh——网格 (2)2.5 Sensors——传感器 (3)2.6 Scalar fields——标量场 (4)2.7 Clone——复制 (6)2.8 Merge——合并 (6)2.9 Subsample——抽稀 (6)2.10 Apply transformation——应用变换矩阵 (6)2.11 Multiply/Scale——缩放坐标 (6)2.12 Translate/rotate——平移/旋转 (6)2.13 Segment——分割 (6)2.14 Crop——裁剪 (6)2.15 Edit global shift and scale——编辑全局的平移缩放因子 (6)2.16 Toggle(recursive)——转换（递归） (6)2.17 Delete——删除 (7)三、Tools——工具 (7)3.1 Clean——去噪 (7)3.2 Projection——投影 (7)3.3 Registration——拼接/配准 (7)3.4 Distances——距离 (8)3.5 V olume——体积 (8)3.6 Statistics——统计 (8)3.7 Segmentation——分割 (8)3.8 Fit——拟合 (8)3.9 Other——其他 (9)3.10 Level——水平（3点-XOY） (9)3.11 Point picking——选点 (9)3.12 Point list picking——选点（列表） (9)3.13 Trace Polyline——轨迹折线 (9)3.14 Sand box(research)——沙盒（研究测试用） (9)四、Display——显示 (10)4.1 Full screen——全屏 (10)4.2 Full screen(3D view)——全屏（3D视角） (10)4.3 Refresh——刷新 (10)4.4 Toggle Centered Perspective——切换透视投影-实体中心视图 (10)4.5 Toggle Viewer Based Perspective——切换透视投影-基于视图视角 (10)4.6 Lock rotation about vert. axis——锁定垂直轴的旋转 (10)4.7 Enter bubble-view mode——进入bubble-view模式 (10)4.8 Render to File——保存3D视图 (10)4.9 Display settings——显示设置 (11)4.10 Camera settings——相机设置 (11)4.11 Save viewport as object——保存视口对象 (11)4.12 Adjust zoom——调整缩放 (11)4.13 Test Frame Rate——测试帧速率 (11)4.14 Lights——灯光 (11)4.15 Shaders & filters——着色器和过滤器 (11)4.16 Active scalar field——所选字段 (11)4.17 Console——控制台 (12)4.18 Toolbars——工具栏 (12)4.19 Reset all GUI elements positions——重置所有的GUI元素的位置 (12)五、Plugins——插件 (12)六、3D Views——3D视角 (12)6.1 New——新建视图 (12)6.2 Zoom in——放大 (12)6.3 Zoom out——缩小 (12)6.4 Close——关闭 (12)6.4 Close All——关闭所有 (12)6.6 Tile——平铺视图 (13)6.7 Cascade——排列视图 (13)6.8 Next——下一视图 (13)6.9 Previous——上一视图 (13)七、Help——帮助 (13)7.1 Help——帮助 (13)7.2 About...——关于 . (13)7.3 About Plugins...——关于插件 . (13)主工具栏1 (14)主工具栏2 (15)主工具栏3 (15)工具栏4 (17)工具栏5 (17)工具栏6 (18)工具栏7 (18)工具栏8 (18)工具栏9 (19)一、File——文件1.1 Open——打开功能描述：打开点云、图像和矢量文件等。