HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

16 CHAPTER 2. OPERATOR DESCRIPTION (’DEF’-FILES)The information specified up to now is already sufficient to integrate an operator within theHALCON/Extension Package Interface by using ÓÑÔ. It describes the operator properly andmay be specified as a “one line short version” of the -file according to the following syntax:ÜØÖÒÓÔÖØÓÖÒÑ ¹ ÁÒØÖÒÈÖÓÙÖÁÒÔÙØÇØ×ÇÙØÔÙØÇØ×ÁÒÔÙØØÖÐÈÖÑ×ÇÙÔÙØØÖÐÈÖÑ×℄Chapter 2.2 explains the meaning of the single identifiers and the name convention. Pleasenote, that in contrast to the header mentioned there, the short version header must be finishedby a semicolon (;) and that the default type and the number of values is specified together withthe name of a control parameter (ÁÒÔÙØØÖÐÈÖÑ× and ÇÙÔÙØØÖÐÈÖÑ×). This is doneby concatenating a dollar sign and an additional character to the name encoding the type andnumber of values (cf. the example in Fig. 2.1).Ù×ÖÒ× ¹ ÁÈÍ×ÖËÐØÊÓÒ×ÊÓÒËÐØÊÓÛ°¸ÓÐÙÑÒ°℄Figure 2.1: Short version of the definition of the operator Ù×Ö Ò× (cf.±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×Ò ÒØÖÒÐÓÒÙ×ÖÒÒÖÓÒØÙÖ×º).The following table shows how to code types and number of values into a character. Lower-casecharacters stand for exactly one value in the specified parameter. This corresponds to assigningÑÙÐØÚÐÙ Ð× in the extended version. Capital letters specify parameters that containmore than one value passed as a tuple (ÑÙÐØÚÐÙ ØÖÙ).TypeC-typeCodeOne Value Unlimited NumberInteger ÐÓÒ i IFloating-point Value ÓÙÐ f FString Ö s SThe specification described so far is sufficient to integrate the operator into C applications.However, in general the new operators should also be usable by HDevelop or within C++ applications.To achieve this, an extended version of the operator description must be generated.This is described in the following section.2.2 Extended Operator DescriptionAn operator description within a -file must start with a Ö. The following entries arevariable in their order. All of these slots begin with a determined keyword and are finished by asemicolon (). Semicolons within the text not defining the end of a slot must be quoted with abackslash ().Some slots are language dependent: For example ×ÓÖØºÒÐ× contains a short descriptionof the operator in English, ×ÓÖØºÖÑÒ the same description in German. The currently supportedlanguages are English and German. In order to allow an international usage of operatorswe strongly recommend always to provide all ºÒÐ× slots.HALCON Extension Package Interface / 2000-11-16
2.2. EXTENDED OPERATOR DESCRIPTION 17Note, that all slots specified within the operator description are accessible online within theHALCON system using the operator Ø ÓÔÖØÓÖ ÒÓ, see the Reference Manuals for details.Describing the single parameters completes the operator description. Section 2.3 explainshow to do this.2.2.1 HeaderThe operator description starts with the headerÜØÖÒÓÔÖØÓÖÒÑ ¹ ÁÒØÖÒÈÖÓÙÖÁÒÔÙØÇØ×ÇÙØÔÙØÇØ×ÁÒÔÙØØÖÐÈÖÑ×ÇÙÔÙØØÖÐÈÖÑ×℄Note, that in contrast to the short version described in section 2 the header doesn’t containany information about the types of the control parameters (e.g. °) and does not end with asemicolon (;).The following example is a short version of the operator description for the dynamic thresholdoperator ÝÒ ØÖ×ÓÐ. For better legibility there should be a comment at the beginning ofevery operator description, like» ÝÒØÖ×ÓÐ »ÝÒØÖ×ÓÐ ¹ ÁÈÝÒÌÖ×ÓÐÇÖÁÑ¸ÌÖ×ÓÐÁÑÊÓÒÝÒÌÖ×Ç×Ø¸ÄØÖ℄Comments within -files are indicated according to the C-syntax (» ººº »).There are a couple of conventions/restrictions concerning the names of parameters: All wordparts should begin with a capital letter (e.g., ÊÓÒÝÒÌÖ×). They are directly concatenatedwithout any separating character. Especially, they must not contain any underscore (‘ ’)!The external operator name exclusively consists of lower-case characters with word parts separatedby underscores. This operator name is used within C programs, low-level calls 1 of theoperator in C++, or within HDevelop.The four parameter classes (input-/output object/control) are separated by colons (:). One classis described by a list of all parameter names within the class separated by commas. If there is nomember of a class for an operator, the list remains empty. The example described above definesthe following mapping between parameters and parameter classes:parameter class keyword (cf. page 27) parameter in the exampleinput iconic objects ÒÔÙØ ÓØ OrigImage, ThresholdImageoutput iconic objects ÓÙØÔÙØ ÓØ RegionDynThreshinput control parameters ÒÔÙØ ØÖÐ Offset, LightDarkoutput control parameters ÓÙØÔÙØ ØÖÐ 1 Within the HALCON/C++ class hierarchy corresponding methods use slightly different conventions:ÜØÖÒ ÓÔÖØÓÖ ÒÑ is transformed into ÜØÖÒÇÔÖØÓÖÆÑ.HALCON 6.0
Page 1: HALCON Version 6.0MVTec Software Gm
Page 7 and 8: Dl Iosub menţionează că diferen
Page 9 and 10: Chapter 1IntroductionHALCON can be
Page 11: 1.1. HALCON OPERATORS 3objects (or
Page 15 and 16: 1.3. INSTALLING A HALCON PACKAGE 76
Page 17 and 18: 1.4. AN EXAMPLE 9Note, that it is n
Page 19 and 20: 1.4. AN EXAMPLE 11¯ one input cont
Page 21 and 22: 1.5. ADDITIONAL SOURCES OF INFORMAT
Page 23: Chapter 2Operator Description (-fil
Page 27 and 28: 2.2. EXTENDED OPERATOR DESCRIPTION
Page 33 and 34: 2.3. DESCRIBING THE PARAMETERS 252.
Page 37 and 38: 2.3. DESCRIBING THE PARAMETERS 29Pl
Page 39 and 40: 2.3. DESCRIBING THE PARAMETERS 31¯
Page 43 and 44: 2.4. TEXT IN ’DEF’-FILES 35Umla
Page 45 and 46: Chapter 3Style Guide for Programmin
Page 47 and 48: 3.2. MEMORY MANAGEMENT 39If you use
Page 49 and 50: 3.2. MEMORY MANAGEMENT 41NamesÀÐ
Page 51 and 52: 3.2. MEMORY MANAGEMENT 43NamesÀÐ
Page 53 and 54: 3.3. STRUCTURING PROGRAMS 453.2.3 D
Page 55 and 56: 3.6. ERROR HANDLING 47or via Extens
Page 57 and 58: Chapter 4HALCON Data TypesThe HALCO
Page 59 and 60: 4.2. REGION DATA (’HRLREGION’)
Page 61 and 62: 4.3. XLDS (’HCONT’, ’HPOLY’
Page 63 and 64: 4.4. CONTROL PARAMETERS (’HPAR’
Page 65 and 66: 4.4. CONTROL PARAMETERS (’HPAR’
Page 67 and 68: Chapter 5Handling Iconic Objects an
Page 69 and 70: 5.1. BASIC ACCESS TO ICONIC INPUT O
Page 71 and 72: 5.1. BASIC ACCESS TO ICONIC INPUT O
Page 73 and 74: 5.2. ADDITIONAL ROUTINES FOR ACCESS
Page 75 and 76:
5.2. ADDITIONAL ROUTINES FOR ACCESS
Page 77 and 78:
5.3. LOOP MACROS FOR ACCESSING SING
Page 79 and 80:
5.4. CREATING OBJECTS AND WRITING O
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
5.5. READING AND WRITING CONTROL PA
Page 89 and 90:
5.5. READING AND WRITING CONTROL PA
Page 91 and 92:
5.6. AUXILIARY MACROS AND PROCEDURE
Page 93 and 94:
5.6. AUXILIARY MACROS AND PROCEDURE
Page 95 and 96:
Chapter 6Special Routines for Typic
Page 97 and 98:
6.1. LOOP MACROS 89NamesÀÐÐÊ¸
Page 99 and 100:
6.1. LOOP MACROS 91contains less ch
Page 101 and 102:
6.1. LOOP MACROS 93ÀÖÖÓÖ ÁÈ
Page 103 and 104:
6.2. OBJECT GENERATION 95ÀÖÖÓÖ
Page 105 and 106:
6.2. OBJECT GENERATION 97each regio
Page 107 and 108:
Chapter 7Creating a New HALCON Pack
Page 109 and 110:
7.1. THE HALCON COMPILER ’HCOMP
Page 111 and 112:
7.2. GENERATING HALCON PACKAGES 103
Page 114 and 115:
106 CHAPTER 7. CREATING A NEW HALCO
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
114 APPENDIX A. HALCON ERROR CODES
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140:
132 APPENDIX A. HALCON ERROR CODESH
show all

HALCON Extension Package Programmer's Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?