HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

44 CHAPTER 3. STYLE GUIDE FOR PROGRAMMINGmight implicitly change one or more HALCON objects. Be aware that you have to take careabout such problems, if you decide not to use the standard HALCON memory management(that is ÀÆÛÁÑ).For both ÀÆÛÁÑ and ÀÆÛÁÑÈØÖ the pixel type of the raw data within Ñ is specifiedby the parameter Ò. Please see Fig. 4.2 on page 50 for the supported values.ÀÐÐÓÄÓÒØ allocates an XLD contour 2 of type ÀÓÒØ (see section 4.3) including memoryfor ÒÙÑ ÔÓÒØ× contour points. Internally this routine is based on ÀÐÐÓ. ÀÖÄÓÒØ isused to deallocate a contour again (inluding all the points and all attributes defined for ÓÒØ,see page 53).NamesÀÐÐÓÊÄ¸ ÀÐÐÓÊÄÆÙÑ¸ ÀÊÐÐÓÊÄÆÙÑ¸ ÀÖÊÄSynopsisÒÐÙ ÀÐÓÒºÀÖÖÓÖ ÀÐÐÓÊÄ´ÀÖÖÓÖ ÀÐÐÓÊÄÆÙÑ´ÀÔÖÓÒÐ ÔÖÓÒÐ¸ÀÖÐÖÓÒ ÖÓÒµÀÔÖÓÒÐ ÔÖÓÒÐ¸ÀÖÐÖÓÒ ÖÓÒ¸×ÞØ ÐÒµÀÖÖÓÖ ÀÊÐÐÓÊÄÆÙÑ´ ÀÔÖÓÒÐ ÔÖÓÒÐ¸ÀÖÐÖÓÒ ÖÓÒ×ÞØ ÐÒ¸ÀÖÐÖÓÒ ÒÛÖÓÒµÀÖÖÓÖ ÀÖÊÄ´ÀÔÖÓÒÐ ÔÖÓÒÐ¸ÀÖÐÖÓÒ ÖÓÒµFigure 3.4: General memory management for region data.The convenience routines ÀÐÐÓÊÄ, ÀÐÐÓÊÄÆÙÑ, ÀÊÐÐÓÊÄÆÙÑ, and ÀÖÊÄ (seeFig. 3.4) are used for handling permanent region data based on ÀÐÐÓ. Otherwise their behaviouris similar to ÀÐÐÓÊÄÌÑÔ etc., see page 40. Note that it is possible to change the sizeof regions (i.e., the number of chords) using ÀÊÐÐÓÊÄÆÙÑ.2 In contrast to ÀÆÛÁÑ and ÀÆÛÁÑÈØÖ ÀÐÐÓÄÓÒØ also allocates memory for the structure ÀÓÒØitself, not only for the data inside that structure.HALCON Extension Package Interface / 2000-11-16
3.3. STRUCTURING PROGRAMS 453.2.3 DebuggingThe HALCON memory management provides debugging mechanisms. Every time a memoryblock is deallocated a couple of consistency checks is performed automatically. Moreover, theconsistency of memory blocks can be checked for debugging reasons at any time using specificExtension Package Interface routines, see Fig. 3.5.NamesÀÌ×ØÅÑ¸ ÀÌ×ØÈØÖ¸ ÀÌ×ØÐÐÌÑÔ¸ ÀÌ×ØÌÑÔSynopsisÒÐÙ ÀÐÓÒºÀÖÖÓÖ ÀÌ×ØÅÑ´ÚÓµÀÖÖÓÖ ÀÌ×ØÈØÖ´ ÚÓ ÔÓÒØÖµÀÖÖÓÖ ÀÌ×ØÐÐÌÑÔ´ ÀÔÖÓÒÐÔÖÓÒÐµÀÖÖÓÖ ÀÌ×ØÌÑÔ´ ÀÔÖÓÒÐ ÔÖÓÒÐ¸ÚÓÔÓÒØÖµFigure 3.5: HALCON memory management: Check of consistency.ÀÌ×ØÅÑ checks all the memory allocated with ÀÐÐÓ or ÀÐÐÓÄÓÐ, whereas ÀÌ×ØÈØÖchecks only the specified memory block. Similar to that ÀÌ×ØÐÐÌÑÔ checks all the memoryallocated via ÀÐÐÓÌÑÔ and ÀÌ×ØÌÑÔ checks the specified block. With any failure of theconsistency check, the routines return an error number (À ÊÊ ÁÅ – inconsistent memory).Furthermore, if the global variable ÀÓÄÓÛÖÖÓÖ is set to ÌÊÍ, they display a description of theerror either on ×ØÖÖ (UNIX) or within an alert box (Windows NT/ 2000). This variable canbe set in an application with the operator ×Ø ×Ý×ØÑ´Ó ÐÓÛ ÖÖÓÖ¸ØÖÙ»Ð×µor used directly inside the newly written operator.3.3 Structuring ProgramsHALCON operators are typically implemented by at least two routines: one procedure (supplyprocedure) receives/unpacks all input data and checks it’s consistency. Afterwards it calls theaction procedure that performs the image processing. In some cases it might be convenient toimplement several action procedures dependent on special parameter values or pixel types ofimage data. Generally, these steps are performed within a loop over all input objects that mayinclude further loops over different parameter values and over all image channels. The resultsare collected and finally returned to the HALCON interface to the application.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 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: 3.2. MEMORY MANAGEMENT 43NamesÀÐ
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 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?