HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

10 CHAPTER 1. INTRODUCTIONÙ×ÖØÖ× ¹ ÁÈÍ×ÖÌÖ×ÓÐÁÑÊÓÒÌÖ×ÓÐ℄×ÓÖØºÖÑÒËÛÐÐÛÖØÓÔÖØÓÖº×ÓÖØºÒÐ×ËÐØÓÒ Ó ÖÝ ÚÐÙ× Ý ØÖ×ÓÐÒºÑÓÙÐ×ÔØÖºÖÑÒÒÙØÞÖÖÛØÖÙÒÒÔØÖºÒÐ×Í×ÖÜØÒ×ÓÒ×ÙÒØÓÒÐØÝÑÔÖÑØÖÁÑ×ÑØÝÔÔÖÑØÖÊÓÒ×ÑØÝÔÔÖÑØÖÌÖ×ÓÐÙÐØØÝÔÑÙÐØÚÐÙ×ÑØÝÔÒÔÙØÓØÑÓÙØÔÙØÓØÖÓÒÒÔÙØÓÒØÖÓÐÒØÖÐ×ÒÙÑÖFigure 1.4: An example for an extended -file of the operator Ù×Ö ØÖ× (minimal form), cf.±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×Ò ÒØÖÒÐÓÒÙ×ÖÒÒØÖ×ÓÐº.¯ the name of the supply procedure that has to be implemented in C (ÁÈÍ×ÖÌÖ×ÓÐ),¯ names and types of the operator’s parameter(s). The names of the parameters are onlyimportant for the manuals and within ÀÚÐÓÔ.The minimal form of the extended operator -file includes: A short description (×ÓÖØ), theHALCON module (ÑÓÙÐ) the operator belongs to, the mapping to a chapter (ÔØÖ) ofthe manual, the mapping to an object (ÙÒØÓÒÐØÝ), and for every parameter its semantictype (×Ñ ØÝÔ). In addition, the type (ÙÐØ ØÝÔ) and number (ÑÙÐØÚÐÙ) must bespecified for control parameters.Our operator Ù×Ö ØÖ× has got the following parameters:¯ one input object parameter (ÁÑ),¯ one output object parameter (ÊÓÒ),HALCON Extension Package Interface / 2000-11-16
1.4. AN EXAMPLE 11¯ one input control parameter (ÌÖ×ÓÐ) of type ÒØ with exactly one value and¯ no output control parameter.ÓÑÔ ¹Ù ¹ ¹ÔÐÓÒÙ×Ö ØÖ×ÓÐºFigure 1.5: Call of ÓÑÔ for HALCON/C.The operator definition within the -file now is used by ÓÑÔ to generate the appropriateinterface code. Fig. 1.5 shows the call of ÓÑÔ. Note, that within this manual ÐÓÒÙ×Ö isused as name of the HALCON package to be created. By calling ÓÑÔ with this options 9 thefiles ÀÐÓÒÙ×Öº (interface-code) and ÀÐÓÒÙ×Öº (prototype of the new HALCONoperator) are created.In the next step one has to program the new HALCON operator. This is done by implementingthe supply and action procedure. This results in the typical structure of HALCON operators asillustrated in Fig. 1.6.» ØÓÒ ÔÖÓÙÖ »ÀÖÖÓÖ ÁÈÌÖ×ÓÐ´ÔÖÓÒÐ¸ÖÓÒ¸Ñ¸ÛØ¸ØÖ×ÓÐ¸ÖÓÒÓÙØµßºººÐ» ×ÙÔÔÐÝ ÔÖÓÙÖ ¹ ÐÛÝ× ÛØ Ø× ÔÖÑØÖ »ÀÍ×ÖÜÔÓÖØ ÀÖÖÓÖ ÁÈÍ×ÖÌÖ×ÓÐ´ÀÔÖÓÒÐ ÔÖÓÒÐµßÀØÈÖ´ºº¸²ÌÖ×ÓÐ¸ººµ » Ø ÓÒØÖÓÐ »» ÔÖÑØÖ »ÀÐÐËÑ´ÔÖÓÒÐ¸²ÖÓÒ¸²Ñ¸½¸µ » ÛÓÖ ÓÒ ÐÐ »» ÒÔÙØ Ñ× »ßÀÈ´ÔÖÓÒÐ¸ÁÈÌÖ×ÓÐ´ºººµµ » ÐÐ ØÓÒ »» ÔÖÓÙÖ »ÀÆÛÊÓÒ´ÔÖÓÒÐ¸ÖÓÒÓÙØµ » ×ØÓÖ ´Ö×ÙÐØµ »» ÖÓÒ »ÐÖØÙÖÒ´ÀÅËÌÊÍµÐFigure 1.6: Sample source code of supply ÁÈÍ×ÖÌÖ×ÓÐ´µ and action ÁÈÌÖ×ÓÐ´µprocedure.Compiling the source code generates an object file (in the example ÔÙ×ÖØÖ×ÓÐºÓ)that should be integrated into the user extension library (ÐÓÒÙ×Ö). Moreover, the generatedinterface code must be converted to the corresponding language dependent interfacelibrary: In case of a C application 10 this is ÐÓÒÙ×Ö containing ÀÐÓÒÙ×ÖºÓ. The9 see section 7.1 for a complete description.10 ÀÚÐÓÔ uses the C version as well.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: 1.4. AN EXAMPLE 9Note, that it is n
Page 21 and 22: 1.5. ADDITIONAL SOURCES OF INFORMAT
Page 23 and 24: Chapter 2Operator Description (-fil
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?