HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

14 CHAPTER 1. INTRODUCTIONAll these manuals are available as ÈÓ×ØËÖÔØ ´Ô×µ and ÖÓØ ÊÖ ´Ôµ documents.The reference manuals are available as HTML documents as well. For the latest versionof the manuals please checkØØÔ»»ÛÛÛºÑÚØºÓÑ»ÐÓÒ»Please see also the example package±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÜØÒ×ÓÒ ÔÒÐÓÒÙ×Öwhich will be referenced many times within this manual.HALCON Extension Package Interface / 2000-11-16
Chapter 2Operator Description (-files)The following chapters give a detailed description of the steps mentioned insection 1. This is done with respect to the examples within the directory±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÜØÒ×ÓÒ ÔÒÐÓÒÙ×Ö as well as system-definedHALCON operators. We start with the generation of an operator description.2.1 Short Operator DescriptionBefore implementing an operator the author should think about the task of the operator and whatkind of user interface is best for calling the operator. This specification is used to automaticallygenerate the interface code for the desired host language with the HALCON compiler ÓÑÔ.To do this, it is necessary to describe at least the following features beside the operator name ina -file:¯ the name of the operator as used within the application programming language,¯ the name of the C-procedure (supply procedure) called by HALCON in order to start theprocessing (this procedure must be implemented later on),¯ all iconic objects and control parameters that are needed by the operator as input (inputparameters),¯ all iconic objects and control parameters that are returned by the operator as result (outputparameters),¯ the types of these parameters,¯ the number of values per parameter (there is only a distinction between parameters thatneed or can process exactly one value and those expecting more than one value).There exist two kinds of parameters within HALCON: Iconic object parameters and parameterscontaining any other data –socalledcontrol parameters. By distinguishing input- and outputparameterswe get four classes of parameters: Input iconic object parameters, output iconicobject parameters, input control parameters, andoutput control parameters. Basically, specifyingthe number of parameters per class would suffice to describe the operator. The internalaccess (in particular within the supply procedure) on individual parameters works this way byusing the parameter’s position within its class. But to refer to single parameters and add furtherinformation regarding a parameter, it is useful to give it a name.15
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: 1.5. ADDITIONAL SOURCES OF INFORMAT
Page 25 and 26: 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?