Check-list final G8X Rev 04a

Checker code DescriptionABV.ANY_SIZE_ARRAY Buffer Overflow - Array Index Out of Bounds ABV.GENERAL Buffer Overflow - Array Index Out of Bounds ABV.ITERATOR Buffer Overflow - Array Index may be out ofBoundsABV.MEMBER Buffer Overflow - Array Index Out of Bounds ABV.STACK Buffer Overflow - Local Array Index Out ofBoundsABV.TAINTED Buffer Overflow from Unvalidated Input ABV.UNICODE.BOUND_MAP Buffer overflow in mapping character ABV.UNICODE.FAILED_MAP Mapping function failedABV.UNICODE.NNTS_MAP Buffer overflow in mapping character ABV.UNICODE.SELF_MAP Mapping function failedABV.UNKNOWN_SIZE Buffer Overflow - Array Index Out of Bounds ASSIGCOND.CALL Assignment in condition (call) ASSIGCOND.GEN Assignment in conditionBSTR.CAST.C C style type cast to BSTRBSTR.CAST.CPP C++ style type cast to BSTRBSTR.FUNC.ALLOC Incorrect call to BSTR allocating function BSTR.FUNC.FREE Incorrect call to BSTR freeing function BSTR.FUNC.LEN Trying to get length of non-BSTR string usingBSTR-related functionsBSTR.FUNC.REALLOC Incorrect call to BSTR reallocating function BSTR.IA.ASSIGN BSTR variable is assigned a non-BSTR value BSTR.IA.INIT BSTR variable is initialized with a non-BSTRvalueBSTR.OPS.ARITHM Illegal arithmetic operations with BSTR P Illegal comparison of BSTR valuesBSTR.OPS.EQS Illegal equality comparison of BSTR values BYTEORDER.HTON.SEND Missed conversion from host to network byteorderBYTEORDER.HTON.WRITE Missed conversion from host to network byteorderBYTEORDER.NTOH.READ Missed conversion from network to host byteorderBYTEORDER.NTOH.RECV Missed conversion from network to host byteorderCL.ASSIGN.NON_CONST_ARG Assignment operator declares non-constantreference argumentCL.ASSIGN.RETURN_CONST Assignment operator returns constantCL.ASSIGN.VOID Assignment operator returns voidCL.FFM.ASSIGN Use of free memory (double free) - noCL.FFM.COPY Use of free memory (double free) - no copyconstructorCL.FMM Freeing Mismatched Memory - in destructor CL.MLK Memory Leak - in destructorCL.MLK.ASSIGN Memory Leak - in assignment operatorCL.MLK.VIRTUAL Memory Leak - possible in destructorCL.SELF-ASSIGN Use of free memory (double free) - inCL.SHALLOW.ASSIGN Use of free memory (double free) - shallowcopy in operator=CL.SHALLOW.COPY Use of free memory (double free) - shallowcopy in copy constructorCONC.DL DeadlockCONC.NO_UNLOCK Missing unlock for variableCONC.SLEEP Function may block in critical section CWARN.ALIGNMENT Incorrect pointer scaling is usedCWARN.BAD.PTR.ARITH Bad pointer arithmeticCWARN.BITOP.SIZE Operands of different size in bitwise operation CWARN.BOOLOP.INC A boolean is incremented or decremented CWARN.CAST.VIRTUAL_INHERITANCE C-style cast of pointer to object with virtualmethods to pointer to its derived class CWARN.CMPCHR.EOF A 'char' expression compared with EOF CWARN.CONSTCOND.DO'do' controlling expression is constant CWARN.CONSTCOND.IF'if' controlling expression is constant CWARN.CONSTCOND.SWITCH'switch' selector expression is constant CWARN.CONSTCOND.TERNARY Controlling condition in conditionalexpression is constantCWARN.CONSTCOND.WHILE'while' controlling expression is constant CWARN.COPY.NOASSIGN Class defines copy constructor, but noassignment operatorCWARN.DTOR.NONVIRT.DELETE Delete expression for an object of a class withvirtual methods and no virtual destructor CWARN.DTOR.NONVIRT.NOTEMPTY Class has virtual functions inherited from abase class, but its destructor is not virtual andnot emptyCWARN.DTOR.VOIDPTR Delete expression with an object of typepointer to voidBEL Empty label statementCWARN.EMPTY.TYPEDEF Missing typedef nameCWARN.FUNCADDR Function address is used instead of a call tothis functionCWARN.HIDDEN.PARAM Parameter hidden by local variable CWARN.IMPLICITINT Anachronistic 'implicit int'CWARN.INCL.ABSOLUTE Absolute path is used in include directive CWARN.INCL.NO_INTERFACE Source file does not include its interface CWARN.INLINE.NONFUNC'inline' used with non-functionCWARN.MEMBER.INIT.ORDER Members of the initialization list are not listedin the order in which they are declared in the CWARN.MEM.NONPOD Memory manipulation routine applied to anon-POD objectCWARN.MEMSET.SIZEOF.PTR Memset-like function is called for 'sizeof'applied to pointerCWARN.MOVE.CONST Const value used as argument for std::move CWARN.NOEFFECT.OUTOFRANGE Value outside of rangeCWARN.NOEFFECT.SELF_ASSIGN A variable is assigned to selfCWARN.NOEFFECT.UCMP.GE Comparison of unsigned value against 0 isalways trueCWARN.NOEFFECT.UCMP.GE.MACRO Comparison of unsigned value against 0within a macro is always trueCWARN.NOEFFECT.UCMP.LT Comparison of unsigned value against 0 isalways falseCWARN.NOEFFECT.UCMP.LT.MACRO Comparison of unsigned value against 0within a macro is always falseCWARN.NULLCHECK.FUNCNAME Function address was directly comparedCWARN.OVERRIDE.CONST Function overriding fails due to mismatch of'const' qualifiersCWARN.PACKED.TYPEDEF'packed' attribute ignored in typedef CWARN.PASSBYVALUE.ARG Function argument passed by value is too CWARN.PASSBYVALUE.EXC Exception object passed by value is too large CWARN.RET.MAIN Bad return type of mainCWARN.SIGNEDBIT Signed one bit fieldDBZ.CONST Division by a zero constant occursDBZ.CONST.CALL The value '0' is passed to function that can usethis value as divisorDBZ.GENERAL Division by zero might occurDBZ.ITERATOR Division by zero might occur in a loop iterator EFFECT Statement has no effectFMM.MIGHT Freeing Mismatched Memory - possible FMM.MUST Freeing Mismatched MemoryFNH.MIGHT Freeing Non-Heap Memory - possible FNH.MUST Freeing Non-Heap MemoryFREE.INCONSISTENT Inconsistent Freeing of MemoryFUM.GEN.MIGHT Freeing Unallocated Memory - possible FUM.GEN.MUST Freeing Unallocated Memory FUNCRET.GEN Non-void function does not return value FUNCRET.IMPLICIT Non-void function implicitly returning intdoes not return valueHCC Use of hardcoded credentialsHCC.PWD Use of a hardcoded passwordER Use of a hardcoded user name BEL Inconsistent Case LabelsINCORRECT.ALLOC_SIZE Incorrect Allocation SizeINFINITE_LOOP.GLOBAL Infinite loopINFINITE_LOOP.LOCAL Infinite loopINFINITE_LOOP.MACRO Infinite loopINVARIANT_CONDITION.GEN Invariant expression in a condition INVARIANT_CONDITION.UNREACH Invariant expression in a conditionITER.CONTAINER.MODIFIED Use of invalid iteratorITER.END.DEREF.MIGHT Dereference of 'end' iteratorITER.END.DEREF.MUST Dereference of 'end' iteratorITER.INAPPROPRIATE Use of iterator with inappropriate container ITER.INAPPROPRIATE.MULTIPLE Use of iterator with inappropriate container LA_UNUSED Label unusedLOCRET.ARG Function returns address of local variable LOCRET.GLOB Function returns address of local variable LOCRET.RET Function returns address of local variable LS.CALL Suspicious use of non-localized string in GUIfunctionLS.CALL.STRING Suspicious use of non-localized string in GUIfunctionLV_UNUSED.GEN Local variable unusedMLK.MIGHT Memory Leak - possibleMLK.MUST Memory LeakMLK.RET.MIGHT Memory Leak - possibleMLK.RET.MUST Memory LeakNNTS.MIGHT Buffer Overflow - Non-null Terminated NNTS.MUST Buffer Overflow - Non-null TerminatedNNTS.TAINTED Unvalidated User Input Causing BufferOverflow - Non-Null Terminated String NPD.CHECK.CALL.MIGHT Pointer may be passed to function that candereference it after it was positively checkedfor NULLNPD.CHECK.CALL.MUST Pointer will be passed to function that maydereference it after it was positively checkedfor NULLNPD.CHECK.MIGHT Pointer may be dereferenced after it waspositively checked for NULLNPD.CHECK.MUST Pointer will be dereferenced after it waspositively checked for NULLNPD.CONST.CALL NULL is passed to function that candereference itNPD.CONST.DEREF NULL is dereferencedNPD.FUNC.CALL.MIGHT Result of function that may return NULL maybe passed to another function that may NPD.FUNC.CALL.MUST Result of function that may return NULL willbe passed to another function that may NPD.FUNC.MIGHT Result of function that can return NULL maybe dereferencedNPD.FUNC.MUST Result of function that may return NULL willbe dereferencedNPD.GEN.CALL.MIGHT Null pointer may be passed to function thatmay dereference itNPD.GEN.CALL.MUST Null pointer will be passed to function thatmay dereference itNPD.GEN.MIGHT Null pointer may be dereferencedNPD.GEN.MUST Null pointer will be dereferencedNUM.OVERFLOW Possible OverflowPORTING.BITFIELDS Usage of bitfields within a structure PORTING.BSWAP.MACRO A custom byte swap macro is used withoutchecking endianPORTING.BYTEORDER.SIZE An incompatible type is used with a networkmacro such as 'ntohl'PORTING.CAST.FLTPNT Cast of a floating point expression to a nonfloating point typePORTING.CAST.PTR Cast between types that are not both pointersor not pointersPORTING.CAST.PTR.FLTPNT Cast of a pointer to a floating point expressionto a non floating point type pointer PORTING.CAST.PTR.SIZE Attempt to cast an expression to a type of apotentially incompatible sizePORTING.CAST.SIZE Expression is cast to a type of potentiallydifferent sizePORTING.CMPSPEC.EFFECTS.ASSIGNMENT Assignment in a function parameter PORTING.CMPSPEC.TYPE.BOOL Assignment to a 'bool' type is larger than 1 PORTING.CMPSPEC.TYPE.LONGLONG Use of 'long long'PORTING.MACRO.NUMTYPE Macro describing a builtin numeric type is PORTING.OPTS Compiler dependant option is used PORTING.PRAGMA.ALIGN#pragma align usagePORTING.PRAGMA.PACK#pragma pack usagePORTING.SIGNED.CHAR'char' used without explicitly specifyingsignednessPORTING.STORAGE.STRUCT Byte position of elements in a structure coulddepend on alignment and packing attributes. PORTING.STRUCT.BOOL Struct/class has a bool member PORTING.UNIONS Union is used within an enclosingstruct/class/other unionPORTING.UNSIGNEDCHAR.OVERFLOW.FALSE Relational expression may be always falsedepending on 'char' type signedness PORTING.UNSIGNEDCHAR.OVERFLOW.TRUE Relational expression may be always truedepending on 'char' type signedness PORTING.UNSIGNEDCHAR.RELOP Relational operations used between explicitlysigned/unsigned char and char withoutsignedness specificationPORTING.VAR.EFFECTS Variable used twice in one expression whereone usage is subject to side-effects PRECISION.LOSS Loss of PrecisionPRECISION.LOSS.CALL Loss of Precision during function call RABV.CHECK Suspicious use of index before boundary RCA Risky cryptographic algorithm usedRCA.HASH.SALT.EMPTY Use of a one-way hash with an empty salt RETVOID.GEN Non-void function returns void value RETVOID.IMPLICIT Implicitly int function returns void value RH.LEAK Resource leakRN.INDEX Suspicious use of index before negative check RNPD.CALL Suspicious dereference of pointer in functioncall before NULL checkRNPD.DEREF Suspicious dereference of pointer beforeNULL checkSEMICOL Suspiciously placed semicolon SPECTRE.VARIANT1Potential exploit of speculative execution STRONG.TYPE.ASSIGN Assignment does not respect strong typing STRONG.TYPE.ASSIGN.ARG Assignment does not respect strong typing STRONG.TYPE.ASSIGN.CONST Assignment does not respect strong typing STRONG.TYPE.ASSIGN.INIT Assignment does not respect strong typing STRONG.TYPE.ASSIGN.RETURN Assignment does not respect strong typing STRONG.TYPE.ASSIGN.ZERO Assignment does not respect strong typing STRONG.TYPE.EXTRACT Assignment does not respect strong typing STRONG.TYPE.JOIN.CMP Joining with binary operator does not respectstrong typingSTRONG.TYPE.JOIN.CONST Joining with binary operator does not respectstrong typingSTRONG.TYPE.JOIN.EQ Joining with binary operator does not respectstrong typingSTRONG.TYPE.JOIN.OTHER Joining with binary operator does not respectstrong typingSTRONG.TYPE.JOIN.ZERO Joining with binary operator does not respectstrong typingSV.BANNED.RECOMMENDED.ALLOCA Banned recommended API: stack allocationfunctionsSV.BANNED.RECOMMENDED.NUMERIC Banned recommended API: unsafe numericconversion functionsSV.BANNED.RECOMMENDED.OEM Banned recommended API: OEM characterpage conversion functionsSV.BANNED.RECOMMENDED.PATH Banned recommended API: unsafe path namemanipulation functionsSV.BANNED.RECOMMENDED.SCANF Banned recommended API: unsafe scanf-typefunctionsSV.BANNED.RECOMMENDED.SPRINTF Banned recommended API: unsafe sprintf-type functionsSV.BANNED.RECOMMENDED.STRLEN Banned recommended API: unsafe stringlength functionsSV.BANNED.RECOMMENDED.TOKEN Banned recommended API: unsafe stringtokenizing functionsSV.BANNED.RECOMMENDED.WINDOW Banned recommended API: unsafe windowfunctionsSV.BANNED.REQUIRED.CONCAT Banned required API: unsafe stringconcatenation functionsSV.BANNED.REQUIRED.COPY Banned required API: unsafe buffer copyfunctionsSV.BANNED.REQUIRED.GETS Banned required API: unsafe stream readingfunctionsSV.BANNED.REQUIRED.ISBAD Banned required API: IsBad-type functions SV.BANNED.REQUIRED.SPRINTF Banned required API: unsafe sprintf-typefunctionsING_STRUCT Use of INADDR_ANY in sin_addr.s_addrfield of struct sockaddr_in Structure Used forCall to bind FunctionSV.BRM.HKEY_LOCAL_MACHINE HKEY_LOCAL_MACHINE Used as 'hkey'Parameter for Registry Manipulation Function SV.CODE_INJECTION.SHELL_EXEC Command Injection into Shell Execution SV.DLLPRELOAD.NONABSOLUTE.DLL Potential DLL-preload hijack vectorSV.DLLPRELOAD.NONABSOLUTE.EXE Potential process injection vectorSV.DLLPRELOAD.SEARCHPATH Do not use SearchPath to find DLLsSV.FIU.PROCESS_VARIANTS Use of Dangerous Process CreationSV.FMTSTR.GENERIC Format String VulnerabilitySV.FMT_STR.BAD_SCAN_FORMAT Input format specifier errorSV.FMT_STR.PRINT_FORMAT_MISMATCH.BAD Incompatible type of a print functionSV.FMT_STR.PRINT_FORMAT_MISMATCH.UNDESIRE Unexpected type of a print function parameter SV.FMT_STR.PRINT_IMPROP_LENGTH Improper use of length modifier in a printfunction callSV.FMT_STR.PRINT_PARAMS_WRONGNUM.FEW Too few arguments in a print function call SV.FMT_STR.PRINT_PARAMS_WRONGNUM.MANY Too many arguments in a print function call SV.FMT_STR.SCAN_FORMAT_MISMATCH.BAD Incompatible type of a scan functionSV.FMT_STR.SCAN_FORMAT_MISMATCH.UNDESIRE Unexpected type of a scan function parameter SV.FMT_STR.SCAN_IMPROP_LENGTH Improper use of length modifier in a scanfunction callSV.FMT_STR.SCAN_PARAMS_WRONGNUM.FEW Too few arguments in a scan function call SV.FMT_STR.SCAN_PARAMS_WRONGNUM.MANY Too many arguments in a scan function call SV.FMT_STR.UNKWN_FORMAT Unknown format specifier in a print function SV.FMT_STR.UNKWN_FORMAT.SCAN Unknown format specifier in a scan function SV.INCORRECT_RESOURCE_HANDLING.URH Insecure Resource HandlingSV.INCORRECT_RESOURCE_HANDLING.WRONG_STA Insecure Resource HandlingSV.LPP.CONST Use of Insecure Macro for DangerousSV.LPP.VAR Use of Insecure Parameter for DangerousFunctionsSV.PCC.CONST Insecure (Constant) Temporary File Name inCall to CreateFileSV.PCC.INVALID_TEMP_PATH Insecure Temporary File Name in Call toCreateFileSV.PCC.MISSING_TEMP_CALLS.MUST Missing Secure Temporary File Names in Callto CreateFileSV.PCC.MISSING_TEMP_FILENAME Missing Temporary File Name in Call toCreateFileSV.PCC.MODIFIED_BEFORE_CREATE Modification of Temporary File Name beforeCall to CreateFileSV.PIPE.CONST Potential pipe hijackingSV.PIPE.VAR Potential pipe hijackingSV.RVT.RETVAL_NOTTESTED Ignored Return ValueSV.SIP.CONST Use of Insecure Macro for DangerousSV.SIP.VAR Use of Insecure Parameter for DangerousFunctionsSV.STRBO.BOUND_COPY.OVERFLOW Buffer Overflow in Bound String CopySV.STRBO.BOUND_COPY.UNTERM Possible Buffer Overflow in Following StringOperationsSV.STRBO.BOUND_SPRINTF Buffer Overflow in Bound sprintfSV.STRBO.UNBOUND_COPY Buffer Overflow in Unbound String Copy SV.STRBO.UNBOUND_SPRINTF Buffer Overflow in Unbound sprintfSV.STR_PAR.UNDESIRED_STRING_PARAMETER Undesired String for File PathSV.TAINTED.ALLOC_SIZE Use of Unvalidated Integer in MemorySV.TAINTED.BINOP Use of Unvalidated Integer in BinarySV.TAINTED.CALL.BINOP Use of Unvalidated Integer in BinarySV.TAINTED.CALL.DEREF Dereference Of An Unvalidated Pointer SV.TAINTED.CALL.INDEX_ACCESS Use of Unvalidated Integer as Array Index byFunction CallSV.TAINTED.CALL.LOOP_BOUND Use of Unvalidated Integer in Loop Conditionthrough a Function CallSV.TAINTED.DEREF Dereference Of An Unvalidated Pointer SV.TAINTED.FMTSTR Use of Unvalidated Data in a Format String SV.TAINTED.INDEX_ACCESS Use of Unvalidated Integer as Array Index SV.TAINTED.INJECTION Command InjectionSV.TAINTED.LOOP_BOUND Use of Unvalidated Integer in Loop Condition SV.TAINTED.PATH_TRAVERSAL Use of Unvalidated Data in a Path Traversal SV.TAINTED.SECURITY_DECISION Security DecisionSV.TOCTOU.FILE_ACCESS Time of Creation/Time of Use Race conditionin File AccessSV.UNBOUND_STRING_INPUT.CIN Usage of cin for unbounded string input SV.UNBOUND_STRING_INPUT.FUNC Usage of unbounded string inputAGERULES.PERMISSIONS Use of Privilege ElevationAGERULES.PROCESS_VARIANTS Use of Dangerous Process Creation Function AGERULES.SPOOFING Use of Function Susceptible to Spoofing SV.WEAK_CRYPTO.WEAK_HASH Weak Hash FunctionUFM.DEREF.MIGHT Use of free memory (access) - possible UFM.DEREF.MUST Use of Freed Memory by PointerUFM.FFM.MIGHT Use of free memory (double free) - possible UFM.FFM.MUST Freeing Freed MemoryUFM.RETURN.MIGHT Use of freed memory (return) - possible UFM.RETURN.MUST Use of Freed Memory on ReturnE.MIGHT Use of free memory - possibleE.MUST Use of Freed MemoryUNINIT.CTOR.MIGHT Uninitialized Variable in Constructor -UNINIT.CTOR.MUST Uninitialized Variable in Constructor UNINIT.HEAP.MIGHT Uninitialized Heap Use - possible UNINIT.HEAP.MUST Uninitialized Heap UseUNINIT.STACK.ARRAY.MIGHT Uninitialized Array - possibleUNINIT.STACK.ARRAY.MUST Uninitialized ArrayUNINIT.STACK.ARRAY.PARTIAL.MUST Partially Uninitialized ArrayUNINIT.STACK.MIGHT Uninitialized Variable - possibleUNINIT.STACK.MUST Uninitialized VariableUNREACH.GEN Unreachable codeUNREACH.RETURN Unreachable Void ReturnUNREACH.SIZEOF Architecture-related unreachable code UNUSED.FUNC.GEN Function defined but not usedUNUSED.FUNC.STL_EMPTY Ignored return value of an STL object empty()methodUNUSED.FUNC.WARN Potential unused functionVA_UNUSED.GEN Value is Never Used after AssignmentVA_UNUSED.INIT Value is Never Used after Initialization VOIDRET Void function returns valueDefault severity Enabled by default?Created Modified 1FALSE Pre-9.29.51TRUE9.610.1, 10.3, 10.4,11.0, 11.1, 11.2,2017.3 1TRUE Pre-9.29.5, 10.31TRUE9.510.31TRUE Pre-9.29.51TRUE Pre-9.29.5, 10.3, 11.21FALSE Pre-9.29.51FALSE Pre-9.29.51FALSE Pre-9.29.51FALSE9.61TRUE9.63FALSE Pre-9.23FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.23FALSE9.23FALSE9.23FALSE9.23FALSE9.24TRUE9.54TRUE9.54TRUE9.53TRUE Pre-9.29.53TRUE Pre-9.29.53TRUE Pre-9.29.5, 10.13TRUE Pre-9.29.53TRUE10.12TRUE Pre-9.29.52TRUE Pre-9.29.52TRUE10.12TRUE10.12FALSE9.22TRUE Pre-9.23TRUE Pre-9.24TRUE9.54FALSE104TRUE104TRUE Pre-9.29.54FALSE104FALSE9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.5, 11.0 2TRUE Pre-9.29.52TRUE Pre-9.29.53TRUE2019.34FALSE Pre-9.29.54FALSE Pre-9.29.52FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE9.64FALSE104FALSE Pre-9.29.54FALSE9.510.44TRUE104FALSE1010.3, 11.1 4TRUE2020.13FALSE10.14FALSE9.29.5, 10.4 4TRUE Pre-9.29.54FALSE Pre-9.29.54TRUE Pre-9.29.54FALSE Pre-9.29.54TRUE Pre-9.29.54TRUE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.54TRUE Pre-9.29.54TRUE Pre-9.29.51FALSE10.31FALSE10.31FALSE10.31FALSE10.34FALSE Pre-9.22TRUE Pre-9.210.11TRUE Pre-9.210.11TRUE Pre-9.22TRUE Pre-9.23FALSE Pre-9.21TRUE Pre-9.21TRUE Pre-9.21TRUE Pre-9.22TRUE Pre-9.22TRUE11.12TRUE11.12TRUE11.14TRUE Pre-9.29.53TRUE Pre-9.22FALSE9.52TRUE9.510.1, 2017, 2FALSE9.53FALSE10.110.2, 2020.1 3FALSE10.110.23TRUE Pre-9.220173TRUE9.53TRUE9.54TRUE9.54TRUE9.54FALSE Pre-9.21TRUE Pre-9.29.51TRUE Pre-9.29.51TRUE Pre-9.29.53FALSE113FALSE114FALSE Pre-9.22TRUE Pre-9.29.2, 9.52TRUE Pre-9.29.2, 9.5, 11.1,11.3, 2020.1 2FALSE9.62TRUE9.61TRUE Pre-9.29.2, 10.31TRUE Pre-9.29.2, 10.31TRUE Pre-9.29.2, 10.31TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51FALSE Pre-9.29.2, 9.51FALSE Pre-9.29.2, 9.51FALSE Pre-9.29.2, 9.51FALSE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.5, 10.4 1TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.5, 11.0,2018.23FALSE10.14FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.5, 10.34FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE9.29.54FALSE Pre-9.29.54FALSE Pre-9.29.51TRUE11.320172TRUE1120172TRUE11.12TRUE Pre-9.22TRUE Pre-9.22TRUE Pre-9.29.5, 11.1, 2020.1 1TRUE9.51TRUE Pre-9.21TRUE Pre-9.24FALSE Pre-9.23FALSE2017.3, 2018,2018.1*4FALSE9.24FALSE9.24FALSE9.24FALSE9.24FALSE9.24FALSE9.24FALSE9.24FALSE9.24FALSE9.22020.14FALSE9.24FALSE9.24FALSE9.22020.14FALSE9.54FALSE9.54FALSE9.54FALSE9.54FALSE9.54FALSE9.54FALSE9.54FALSE9.54FALSE Pre-9.24FALSE9.54FALSE9.54FALSE Pre-9.24FALSE9.54FALSE9.54FALSE Pre-9.24FALSE Pre-9.23FALSE Pre-9.22FALSE9.52FALSE9.52FALSE9.54FALSE Pre-9.211.3 1FALSE Pre-9.211.2 2TRUE Pre-9.29.5 2TRUE Pre-9.29.5 4TRUE Pre-9.29.5 2TRUE Pre-9.29.5 2TRUE Pre-9.29.5 2TRUE Pre-9.29.5 2TRUE1011.3 2TRUE102TRUE Pre-9.29.5 2TRUE Pre-9.29.5 2TRUE Pre-9.29.5 3TRUE Pre-9.29.5 3TRUE Pre-9.29.5 3FALSE Pre-9.23FALSE Pre-9.23FALSE9.53FALSE9.54FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.23FALSE9.53FALSE9.54FALSE Pre-9.23FALSE9.63FALSE9.61FALSE102FALSE101FALSE Pre-9.210.31FALSE Pre-9.21FALSE Pre-9.24FALSE Pre-9.22TRUE Pre-9.210.1, 10.23FALSE10.33FALSE10.33FALSE11.22TRUE Pre-9.210.1, 10.22TRUE Pre-9.210.1, 10.23FALSE11.21TRUE Pre-9.210.11TRUE Pre-9.210.1, 10.2, 11.1,20173TRUE Pre-9.210.12TRUE Pre-9.210.1, 10.21TRUE113FALSE10.44FALSE Pre-9.211.31TRUE9.51TRUE9.54FALSE Pre-9.211.34FALSE Pre-9.24FALSE Pre-9.24FALSE Pre-9.21TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.52TRUE Pre-9.29.2, 9.52TRUE Pre-9.29.2, 9.52TRUE Pre-9.29.2, 9.52TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.52FALSE Pre-9.29.2, 9.5, 2020.1 1TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.51TRUE Pre-9.29.2, 9.5, 2018.2 1TRUE Pre-9.29.2, 9.5, 11.2 3FALSE Pre-9.29.2, 9.5, 10.1,10.3, 10.4, 11.2 3FALSE Pre-9.29.2, 9.5, 11.2 3FALSE10.14FALSE10.111.33TRUE2019.32020.14FALSE10.111.34FALSE Pre-9.29.54FALSE Pre-9.29.5, 11.22TRUE Pre-9.29.5。

Checkmk简介Check MK是⼀一款德国出品的监控软件，德国不不仅制造业世界闻名，软件⽅方⾯面也是做的颇有特⾊色。

严谨、稳定、设计巧妙，是我对德国软件的评价。

如果你还在苦于某x的繁琐配置，那就来试试这款软件吧。

版本Raw版本为开源版本，Free版本有数量量限制，可最多监控25台主机，其他为商业版本。

checkmk 功能Quickly gain a complete view of your IT infrastructure, no matter how complex.Checkmk provides powerful monitoring of networks, servers, clouds, containers and applications. Fast. Effective.Checkmk监控平台搭建环境系统：CentOS7.9，默认安装即可IP地址：192.168.12.110软件：check-mk-raw-2.2.0b3-el7-38.x86_64.rpm部署1.环境确认[root@checkmk2 ~]# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:be:c5:d1 brd ff:ff:ff:ff:ff:ffinet 192.168.12.110/24 brd 192.168.12.255 scope global dynamic ens160valid_lft 690621sec preferred_lft 690621secinet6 fe80::250:56ff:febe:c5d1/64 scope linkvalid_lft forever preferred_lft forever[root@checkmk2 ~2.分区查看[root@checkmk2 ~]# lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTsda 8:0 0 100G 0 disk├─sda1 8:1 0 512M 0 part /boot├─sda2 8:2 0 91.5G 0 part /└─sda3 8:3 0 8G 0 part [SWAP][root@checkmk2 ~]#3.关闭防⽕火墙[root@checkmk2 ~]# service firewalld statusRedirecting to /bin/systemctl status firewalld.service● firewalld.service - firewalld - dynamic firewall daemonLoaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)Active: inactive (dead)Docs: man:firewalld(1)[root@checkmk2 ~]#4.关闭iptables[root@checkmk2 ~]# cat /etc/selinux/confiSELINUX=disabledSELINUXTYPE=targeted5.软件下载软件下载后上传⾄至服务器器[root@checkmk2 ~]# lltotal 208132-rw-------. 1 root root 1408 Jul 1 2020 anaconda-ks.cfg-rw-r--r-- 1 root root 213118724 Apr 12 17:32 check-mk-raw-2.2.0b3-el7-38.x86_64.rpm [root@checkmk2 ~]6.软件安装服务器器需要能够访问外⽹网[root@checkmk2 ~]# yum -y install check-mk-raw-2.2.0b3-el7-38.x86_64.rpm[root@checkmk2 ~]# omd versionOMD - Open Monitoring Distribution Version 2.2.0b3.cre[root@checkmk2 ~]#7.创建监控站点[root@checkmk2 ~]# omd create testAdding /opt/omd/sites/test/tmp to /etc/fstab.Creating temporary filesystem /omd/sites/test/tmp...OKUpdating core configuration...Generating configuration for core (type nagios)...Precompiling host checks...OKExecuting post-create script "01_create-sample-config.py"...OKRestarting Apache...OKCreated new site test with version 2.2.0b3.cre.The admin user for the web applications is cmkadmin with password: ZPXru9h9For command line administration of the site, log in with 'omd su test'.After logging in, you can change the password for cmkadmin with 'cmk-passwd cmkadmin'. [root@checkmk2 ~]#8.启动服务[root@checkmk2 ~]# omd start test Temporary filesystem already mounted Starting agent-receiver...OKStarting mkeventd...OKStarting rrdcached...OKStarting npcd...OKStarting nagios...OKStarting apache...OKStarting redis...OKInitializing Crontab...OK[root@checkmk2 ~]#9.修改登录密码[root@checkmk2 ~]# omd su test OMD[test]:~$ cmk-passwd cmkadmin New password:Re-type new password:OMD[test]:~$10.访问checkmk。

cmake check_library_exists原理-回复CMake是一个用于管理和构建软件项目的工具集，它提供了丰富的功能来生成、配置和构建项目。

CMake通过CMakeLists.txt文件提供了一种简洁的方式来描述项目的构建过程，包括库的查找和链接。

其中一个非常有用的CMake功能是check_library_exists，它允许我们检查一个特定的库是否存在于系统中。

在本文中，我们将详细介绍check_library_exists的原理和使用方法。

一、check_library_exists简介我们首先来了解一下check_library_exists这个CMake函数的基本语法：check_library_exists(<library> <function> <variable>)该函数用于检查在给定库中是否存在特定的函数。

它需要三个参数，分别是需要检查的库名字、需要检查的函数名字以及存储检查结果的变量名字。

函数的具体操作流程如下：1. CMake会尝试使用模板代码来编译一个简单的源文件，该源文件包含了对指定函数的调用。

2. 如果编译和链接成功，说明指定的库中确实包含了该函数，CMake会将检查结果保存到指定的变量中，并显示相应的消息。

3. 如果编译和链接失败，说明指定的库中不包含该函数，CMake会将检查结果保存为False，并显示相应的消息。

二、check_library_exists例子为了更好地理解check_library_exists的使用方法和原理，我们来看一个例子。

假设我们想检查是否存在名为mylibrary的库中的sum函数，代码如下：cmakecmake_minimum_required(VERSION 3.12)project(MyProject)# 检查math库中是否存在sum函数check_library_exists(mylibrary sum HAVE_SUM)# 根据检查结果输出消息if(HAVE_SUM)message("Sum function found!")else()message("Sum function not found!")endif()上述代码中，我们使用check_library_exists函数来检查mylibrary库中是否存在名为sum的函数，并将检查结果保存到变量HAVE_SUM中。

AN1006: Differences Between Si534x/8x Revision B and Revision D SiliconThis document highlights differences between Revision B and Revision D silicon forthe following part numbers:•Si5340•Si5341•Si5342•Si5344•Si5345•Si5346•Si5347•Si5348•Si5380SUMMARYCompared to Revision B, Revision D silicon for Si534x/8x fixes several errata, supports higher maximum output frequency ranges, and offers several new features. This document outlines those differences.1. Migration from Si534x/8x Revision B to Revision DApplies to Si5380/48/47/46/45/44/42/41/40With the release of Revision D for Si534x/8x, the Revision B devices are now classified as "Not Recommended for New Designs" (NRND). As of the Revision D release date, Silicon Labs has no plans to EOL the Si5348/47/46/45/44/42/41/40 Revision B devices and will continue production of both the Revision B devices and the newer Revision D devices. As of the Revision D release date, Silicon Labs does not plan to continue production of Si5380 Revision B devices. Customers using Si5380 must follow the instructions below to migrate their existing Revision B designs to Revision D.Revision D devices are pin-compatible and footprint-compatible with Revision B devices. However, Revision D devices are not intended to be drop-in replacements for Revision B devices. As a result of changes to the circuitry in Revision D devices, their performance and behavior will not completely match that of Revision B.•Customers currently using Si5348/47/46/45/44/42/41/40 Revision B in production may continue to do so. Silicon Labs will maintain production of both Revision B and Revision D concurrently.•Customers who wish to migrate a design from Revision B to Revision D should download the latest version of ClockBuilder Pro and create a new custom OPN for Revision D with their desired configuration. Once a new Revision D OPN has been created, customers should verify functionality of the device in their system prior to starting production with Revision D.•Silicon Labs does not recommend writing a register file, settings file, or regmap that was created for Revision B to a RevisionD device. When migrating an existing design from Revision B to Revision D, customers should download the latest version ofClockBuilder Pro and create new register files, settings files, or regmap exports to be used with Revision D.1.1 Device Ordering and IdentificationApplies to Si5380/48/47/46/45/44/42/41/40The revision letter which is the 9th digit of the ordering part number indicates "D" for product Revision D. For example: Si5345A-D-GM or Si5345-Dxxxxx-GM, where xxxxx is the custom OPN ID, and D refers to the product revision.1.2 Evaluation Boards Ordering and IdentificationApplies to Si5380/48/47/46/45/44/42/41/40New evaluation boards are available for all Revision D devices. The Revision D evaluation boards are identified with "-D" in the 7th and 8th characters of the OPN. For example, the Si5345 Revision D OPN is Si5345-D-EVB.1.3 Handling Revisions in ClockBuilder ProClockBuilder Pro (CBPro) version 2.9 or later supports both Revision B and Revision D of Si534x/8x. Selection of the target device revision is done in Step 2 of the configuration Wizard:Figure 1.1. Device Revision DThe default revision is "D" for all newly created designs.CBPro stores the target device revision for each project in the .slabtimeproj project file. When an existing project file is opened, CBPro will set the target device revision according to the data stored in the project file.With the NRND classification of Si534x/8x Revision D, CBPro will no longer support creation of new custom ordering part numbers (OPNs) for Revision B. Customers with an ongoing Revision B design who still wish to create custom OPNs for Revision B should contact Silicon Labs.1.4 Changing the Target Device Revision for an Existing CBPro ProjectAt any time the target device revision for a project can be changed in CBPro by choosing Step 2 "Revision" and then selecting the new target revision from the drop-down box at the top of the screen. Customers who have created projects for Revision B in an earlier version of CBPro can migrate their projects to Revision D using the following steps:•Open the original project file in CBPro (CBPro will default to Revision B after opening the file.).•Choose Step 2: "Revision" and select device revision D.•Click the "Finish" button on the lower right side of the screen.When changing a project from Revision B to Revision D in CBPro, note the following:•CBPro will select the default values for any new registers and features that are present in Revision D but were not present in Revision B. This will enable the new Revision D features described below.•CBPro will recalculate the frequency plan using the latest algorithm for Revision D. As a result, the internal frequency plan for Revision D may differ from the plan used on a Revision B project file.Although CBPro will allow the device revision to be changed backwards to Revision D from Revision B, this is not recommended, as Revision D contains several enhancements that are not present on Revision B.AN1006: Differences Between Si534x/8x Revision B and Revision D Silicon • Errata Fixes2. Errata Fixes2.1 Revision B Errata Fixed on Revision D2.2 Revision B Errata Not Fixed on Revision D2.3 Crystal Drive LevelApplies to: Si5380In data sheet rev 0.96 for Si5380 Revision B, the maximum crystal drive level was incorrectly specified as 200 μW. This has been updated to 300 μW for the Si5380 Revision D data sheet and will be corrected in a future release of the Si5380 Revision B data sheet. In addition, the list of approved crystals in the Si5380 reference manual has been updated to reflect this change.AN1006: Differences Between Si534x/8x Revision B and Revision D Silicon • Extended Output Frequency Ranges3. Extended Output Frequency RangesRevision D of Si5345/44/42/41/40 offers higher maximum output frequencies than Revision B. The maximum output frequency for eachNote: Certain limitations apply when output frequencies above 720 MHz are selected. Refer to to the Reference Manual for more information.AN1006: Differences Between Si534x/8x Revision B and Revision D Silicon • New Features and Capabilities4. New Features and CapabilitiesA variety of new features and capabilities are available on Si534x/8x Revision D. These are described in the following sections.4.1 Frequency Ramping on Holdover ExitApplies to Si5380/48/47/46/45/44/42When coming out of holdover, Revision D allows for the adjustment of frequency ramp rate. This greatly minimizes phase transients due to frequency drift while in holdover. The frequency ramp rate adjustment occurs regardless of whether the output frequencies are using fractional or integer synthesis. This feature may be enabledd or disabled in CBPro, and a variety of ramp rates are selectable from 0.2 ppm/s to 40,000 ppm/s.•On Si5380/45/44/42, all outputs will ramp in frequency when the DSPLL is coming out of holdover.•On a Si5348/47/46, only the outputs that connect to the DSPLL that is coming out of holdover will have a ramp in frequency.4.2 Frequency Ramping on an Input Clock SwitchApplies to: Si5380/48/47/46/45/44/42When switching between clock inputs that are not synchronous, Revision D allows for the adjustment of the frequency ramp rate. This greatly minimizes phase transients on the output clocks during the input switching. The frequency ramp rate adjustment occurs regardless of whether the output frequencies are using fractional or integer synthesis. This feature may be enabled or disabled in CBPro, and a variety of ramp rates are selectable from 0.2 ppm/s to 40,000 ppm/s.•On Si5380/45/44/42, all outputs will ramp in frequency when the input clock is switched.•On a Si5348/47/46, when a DSPLL input switch occurs, only the outputs that connect to that DSPLL will have a ramp in frequency. 4.3 Holdover Exit Bandwidth SelectionApplies to: Si5380/48/47/46/45/44/42In Revision D, it is possible to select a PLL bandwidth to be used upon Holdover and Free Run exit. This bandwidth cannot be set to less than the normal bandwidth. The device returns to the normal bandwidth after the PLL has locked.4.4 Loss of Lock Detector ImprovementsApplies to: Si5380/48/47/46/45/44/42/41/40In Revision D, the Si534x/8x LOL detector has been improved to quickly assert LOL on large changes in ppm. Previously on Revision B, a large input frequency change took much longer to assert LOL. The threshold at which LOL is asserted for large ppm changes is set automatically by CBPro based on the frequency plan, and will range from 100 ppm to 1,000,000 ppm.The Si534x/8x Revision D LOL detector has also been improved to detect loss of an input clock signal. On Revision D, if an input clock edge is not detected within 417 μs, LOL will be asserted. Previously on Revision B, loss of an input clock would only trigger LOS and not LOL.4.5 Out of Frequency Detector ImprovementsApplies to: Si5380/48/47/46/45/44/42In Si534x/8x Revision D, the OOF detector has been improved so that OOF is asserted when a loss of signal occurs. Previously on Revision B, the OOF detector would not assert when a loss of signal occurs.Previously on Revision B, either the fast OOF threshold or the precision OOF threshold could be used to both assert and deassert the OOF signal. With Revision D, if the input frequency exceeds either the fast OOF threshold or the precision OOF threshold, OOF will be asserted. However, the input frequency must fall below both OOF thresholds in order for the OOF detector to be deasserted.4.6 Reductions in Output Clock Phase TransientsApplies to: Si5380/48/47/46/45/44/42When performing hitless switching, the output clock phase transient has been reduced in Si534x/8x revision D. New values for this can be found in the data sheet.Additional circuitry optimizes the switching time between Fastlock and normal bandwidth. This reduces output clock phase transients when changing bandwidths.AN1006: Differences Between Si534x/8x Revision B and Revision D Silicon • Changes to Registers from Revision B to Revision D5. Changes to Registers from Revision B to Revision DThe majority of registers present in Si534x/8x Revision B have been left unchanged in Revision D. The exceptions to this are documented below.5.1 Device RevisionApplies to: Si5380/48/47/46/45/44/42/41/40In Si534x/8x the DEVICE_REV register will now read back 0x03 to indicate Revision D. Previously this read back as 0x01 to indicate Revision B.5.2 Preamble and PostambleApplies to: Si5380/48/47/46/45/44/42/41/40In order to change certain registers that affect PLL lock status it is necessary to write a preamble and postamble sequence to the device. The values for the preamble and postamble sequences have changed for Revision D as shown below.Table 5.1. Preamble Sequence for Si5380/47/46/45/44/42/41/40Table 5.2. Postamble Sequence for Si5380/47/46/45/44/42/41/40Table 5.3. Preamble Sequence for Si5348Table 5.4. Postamble Sequence for Si5348Note that on a Revision D device, either the Revision B values or the Revision D values can be written for the preamble/postamble sequence and the device will function the same in either case. However only the Revision D values can be read back from the device.5.3 New Registers Present on Revision DApplies to Si5380/48/47/46/45/44/42/41/40Several new registers have been added to the Si534x/8x Revision D devices to support the new features described above. Details about these new features can be found in the reference manual for each device.Copyright © 2021 Skyworks Solutions, Inc. All Rights Reserved.Information in this document is provided in connection with Skyworks Solutions, Inc. (“Skyworks”) products or services. These materials, including the information contained herein, are provided by Skyworks as a service to its customers and may be used for informational purposes only by the customer. Skyworks assumes no responsibility for errors or omissions in these materials or the information contained herein. Skyworks may change its documentation, products, services, specifications or product descriptions at any time, without notice. Skyworks makes no commitment to update the materials or information and shall have no responsibility whatsoever for conflicts, incompatibilities, or other difficulties arising from any future changes.No license, whether express, implied, by estoppel or otherwise, is granted to any intellectual property rights by this document. Skyworks assumes no liability for any materials, products or information provided hereunder, including the sale, distribution, reproduction or use of Skyworks products, information or materials, except as may be provided in Skyworks’ Terms and Conditions of Sale.THE MATERIALS, PRODUCTS AND INFORMATION ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY, PERFORMANCE, QUALITY OR NON-INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT; ALL SUCH WARRANTIES ARE HEREBY EXPRESSLY DISCLAIMED. SKYWORKS DOES NOT WARRANT THE ACCURACY OR COMPLETENESS OF THE INFORMATION, TEXT, GRAPHICS OR OTHER ITEMS CONTAINED WITHIN THESE MATERIALS. SKYWORKS SHALL NOT BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO ANY SPECIAL, INDIRECT, INCIDENTAL, STATUTORY, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION, LOST REVENUES OR LOST PROFITS THAT MAY RESULT FROM THE USE OF THE MATERIALS OR INFORMATION, WHETHER OR NOT THE RECIPIENT OF MATERIALS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.Skyworks products are not intended for use in medical, lifesaving or life-sustaining applications, or other equipment in which the failure of the Skyworks products could lead to personal injury, death, physical or environmental damage. Skyworks customers using or selling Skyworks products for use in such applications do so at their own risk and agree to fully indemnify Skyworks for any damages resulting from such improper use or sale.Customers are responsible for their products and applications using Skyworks products, which may deviate from published specifications as a result of design defects, errors, or operation of products outside of published parameters or design specifications. Customers should include design and operating safeguards to minimize these and other risks. Skyworks assumes no liability for applications assistance, customer product design, or damage to any equipment resulting from the use of Skyworks products outside of Skyworks’ published specifications or parameters.Skyworks, the Skyworks symbol, Sky5®, SkyOne ®, SkyBlue™, Skyworks Green™, Clockbuilder ®, DSPLL ®, ISOmodem ®, ProSLIC ®, and SiPHY ® are trademarks or registered trademarks of Skyworks Solutions, Inc. or its subsidiaries in the United States and other countries. Third-party brands and names are for identification purposes only and are the property of their respective owners. Additional information, including relevant terms and conditions, posted at , are incorporated by reference.Portfolio/ia/timingSW/HW/CBProQuality/qualitySupport & Resources/supportClockBuilder ProCustomize Skyworks clock generators, jitter attenuators and networksynchronizers with a single tool. With CBPro you can control evaluationboards, access documentation, request a custom part number, export for in-system programming and more!/CBPro。

Check cif1 吸收校正问题Info on Absorption Correction Method Missing ... ?解决：将cif文件中的_exptl_absorpt_correction_type ?问号改为multi-scan（一般是改为这个）同时，将cif文件中的_exptl_absorpt_process_details ?问号改为SADABS只改第一项，会出现这样的错误提示：An _exptl_absorpt_correction_type has been givenwithout a literature citation. This should be containedin the exptl_absorpt_process_details field. Absorptioncorrection given as multi-scan2 空间群问题No _symmetry_space_group_name_H-M Given ........ ?解决：在ins或是res中找，titl一栏就是空间群名称，一般没有做过空间群的转换，这里就是了。

最保险的方法是在生成的check cif页面上就有，例如Space group C 2/m 这个绝对不会搞错3 No su's on H-atoms, but refinement reported as . mixed报告中显示对H原子的修正方法是混合模式但没有列出H原子相关的偏差。

解决：将mixed改为constr如果H只是通过Hadd加到C上，而没有H加到游离的氧原子上，则Refine-ls-hydrogen-treatment constr(而不是填写mixed)4Ratio of Maximum / Minimum Residual Density .... 2.72正负残留峰的双值应该接近1，出现这样的错误表明精修不到位，可能还有残余峰。

机舱类型Tipo nacelle - Nacelle tipe :工厂Fábrica - Plant :OBSERVACIONES 观察项FOTOSOBSERVATIONS PICTURES 图片10.1倾角气缸保护Protecciones cilindros Pitch Cover for pitch cylinders protectionL电葫芦梁的左侧通道，与第二组门柱高度一致，从轮毂的一侧开始数起。

三个部分用胶带从两端连接。

OK: Pasillo izquierdo sobre las vigas del carro del polipasto, a la altura del segundo pórtico, empezando a contar por el lado del buje.3 piezas unidas mediante cinta americana por los dos extremos.Protecciones contra la viga perpendicular situada a un metro y medio del buje y cerradas con forma de X dejando unidas las protecciones a la viga.对垂直梁的保护，距离轮毂1米半，用X 型锁紧，将保护与梁连接好。

OK: Left corridor on the beams of the guide of crane, around the second porch,beginning to count by the side of the bushing. 3parts united by American tape by both extreme.Protections against the perpendicular beam located to a meter and a middle of the bushing and closed with form of Xs leaving together with the protections the beam.O K C C S C A M P - D E P A R T U R EO K L O G I S T I C -E N T R A N C EG R A V E / G R A V E 严重L E V E / M I N O R 轻微机舱内风厂组装材料MATERIAL DE MONTE IN NACELLE / WIND FARMS ASSEMBLY MATERIAL INSIDE NACELLEO K L O G I S T I C S -D E P A R T U R EO K P A R K -E N T R A N C EP U N T O S D E I N S P E C C I O N /I T E M S O F I N S P E C T I O N 检C O D I G O D E F E C T O S /D E F E C T C O D E S 缺陷代码S E V E R I D A D /S E V E R I T Y 严重性O K P L A N TO K P L A N T -D E P A R T U R E机舱代码,铭牌Código de nacelle, chapa - Nacelle code, nameplate :风场Parque OF - Windfarmer OF :客户标识Logotipo/ Parque - Logo/ Winsfarmer :电葫芦和电缆长度Longitud de cadena del polipasto y cables - Length of service crane crain and cables :Aprobado: IALEl presente documento, su contenido, sus anexos y/o modificaciones (el “Documento”) ha sido confeccionado por Gamesa Corporación Tecnológica, S.A. (“Gamesa”) a efectos puramente informativos, contiene información privada y confidencial referente a Gamesa y/o sus filiales (la “Compañía”), y se dirige exclusivamente a su destinatario. En consecuencia, no se podrá revelar, publicar o distribuir, total o parcialmente, sin el consentimiento previo y por escrito de Gamesa, y siempre que se haga referencia explícita a la titularidad de Gamesa de los indicados derechos de propiedad intelectual. La totalidad del contenido de este Documento, ya sean textos, imágenes, marcas, logotipos, combinaciones de colores, o cualquier otro elemento, su estructura y diseño, la selección y forma de presentación de los materiales incluidos en la misma, están protegidos por derechos depropiedad industrial e intelectual, titularidad de Gamesa, que el destinatario y receptor de este Documento debe respetar. En particular, pero sin limitar la generalidad de la obligación de confidencialidad, quedan prohibidas la reproducción, excepto para uso privado, la transformación, distribución, comunicación pública, puesta a disposición de cualquier tercero y, en general, cualquier otra forma de explotación, por cualquier procedimiento, de todo o parte de los contenidos de este Documento, así como de su diseño y la selección y forma de presentación de los materiales incluidos en la misma.Configuración de máquina / Nacelle configuration制造号Nº OF-OF NO :机舱号Nº Nacelle - Nacelle NO :Código: GD054211 Rev:04Fecha : 27/07/2010Tipo de Documentación:最终检查INSPECCION FINAL NACELLES G8X/G8X NACELLE FINAL INSPECTIONProceso de aprobación : Electrónico:Flujo PDMDTQP - CalidadRealizado : AI Entregable:Verificado: PLO QDSQUALITY DOCUMENTATION SUMMARY10.110.210.310.4 N/A USA10.510.610.710.810.910.10- 10.11 N/A USA10.1210.13 ONLY USA10.13 ONLY USA10.15 N/A USA10.14 N/A USA10.1610.2机舱通道梯Escalera de acceso a Nacelle Nacelle access ladderL放在电葫芦的结构上面，钢结构部分支撑在整个结构的前面的部分，斜撑腿朝向下面，铝结构部分支撑在电葫芦结构的后面部分，用扎带与梯子的前后部分固定在电葫芦的结构上。