HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

52 CHAPTER 4. HALCON DATA TYPESØÝÔ ×ØÖÙØ ßÁÆÌ¾ Ð » ÐÒ ÒÙÑÖ ´ÖÓÛµ Ó ÓÖ »ÁÆÌ¾ » ÓÐÙÑÒ ÒÜ Ó ÒÒÒ Ó ÓÖ »ÁÆÌ¾ » ÓÐÙÑÒ ÒÜ Ó ÒÒ Ó ÓÖ »Ð ÀÖÙÒØÝÔ ×ØÖÙØ ßÀÇÇÄ ×ÓÑÔÐ » ÖÓÒ × ÓÑÔÐÑÒØ »ÁÆÌ ÒÙÑ » ÒÙÑÖ Ó ÓÖ× »ÁÆÌ ÒÙÑÑÜ » ÑÜÑÐ ÒÙÑÖ Ó ÓÖ× »ÀÊØÙÖ ØÙÖ » ÐÖÝ ÔÖÓ×× ØÙÖ× »ÀÖÙÒ ÖÐÊÄÄÆÌÀ℄ » ÖÖÝ Ó ÓÖ× »Ð ÀÖÐÖÓÒFigure 4.4: Data type ÀÖÐÖÓÒ for region encoding.easy transformation of a region in its complement. Operators that work on regions must considerthis flag and react according to its value. The structure ÀÊØÙÖ (see Fig. 4.5) containsall features extracted so far to avoid repeating a computation. ÀØÙÖÐ× encodes, whichfeatures already have been extracted. Do not forget to reset these flags if you modify a region.Normally, a variable of type ÀÖÐÖÓÒ is allocated with the procedure ÀÐÐÓÊÄÌÑÔ orÀÐÐÓÊÄÆÙÑÌÑÔ, see section 3.2. These routines initialize the data, especially ÒÙÑ ÑÜ thatis needed for tests of overflow. When allocating a variable “by hand”, the programmer mustprovide a suitable initialization by himself/herself.Whereas all coordinates within runlength codes are stored as (row,column), linear coordinatesare used to address HALCON image matrices. Thus, the macros and are very helpful,especially when processing gray values (in linear coordinates) along a chord. The programs onpage 93 and 95 illustrate how to use them. Their functionality can be seen in Fig. 4.6. The firstparameter (ÖÐ) contains a pointer to the chords as it is used within ÀÖÐÖÓÒ . ÒÜ specifiesthe index of the chord to work on and ÛØ contains the image width. returns the linearcoordinate of the start point and that of the end point of the chord.4.3 XLDs (ÀÓÒØ, ÀÔÓÐÝ)XLDs (eXtended Line Descriptions) are specific iconic HALCON objects to represent subpixelaccurate contours and polygons. The corresponding data types are listed in Fig. 4.7 andFig. 4.10.HALCON contours of type ÀÓÒØ contain an array of subpixel points along a contour. A contourmight be classified concerning to topological considerations (ÓÒØ Ð××). Additionally,an arbitrary number of additional attributes for each point along the contour can be included(ØØÖ×), e.g., the edge amplitude of subpixel edge points or the orientation of the local gradient.Finally, an arbitrary number of additional global attributes, i.e., attributes valid for theentire contour, can be included (ÐÓÐ), e.g., the individual parameters of a regrssion line tothe contour or the parameters of an ellipse segment fitted to the contour.HALCON Extension Package Interface / 2000-11-16
4.3. XLDS (’HCONT’, ’HPOLY’) 53ØÝÔ ×ØÖÙØ ßÙÒÓÒ ßÀØÙÖÐ× ×ÒÐ » ØÐ »ÐÓÒÐÐÐÍÁÆÌ½ ×Ô » ËÀÈ »ÀÇÇÄ×ÓÒÚÜÀÇÇÄ×ÐÐÀÇÇÄ×ÓÒÒØ¸ ×ÓÒÒØÀÇÇÄ×ØÒÐÓØÖÙÐÖØÝÐÓØÓÑÔØÒ××ÐÓØÓÒØÐÒØÐÓØÓÒÚÜØÝÐÓØÔÐÓØÖ¸ ÖÐÓØÖ¸ ÖÐÓØÒ×ÓÑØÖÝ¸ ÙÐÒ××¸ ×ØÖÙØÙÖØÓÖÐÓØÑ½½¸ Ñ¾¼¸ Ñ¼¾¸ ¸ ÐÓØÖÓÛ¸ ÓÐÁÆÌÖÁÆÌ¾ÖÓÛ½¸ÓÐ½¸ÖÓÛ¾¸ÓÐ¾ÐÓØÖÓÛÖØ¸ ÓÐÖØ¸ ÔÖØ¸ ÐÒØ½¸ ÐÒØ¾ÐÓØÖÓÛÖÐ¸ ÓÐÖÐ¸ ÖÙ×ÁÆÌ¾ÑÒÓÖ¸ ÑÜÓÖÁÆÌ¾ÑÒÓÖÔ¸ ÑÜÓÖÔÐ ÀÊØÙÖFigure 4.5: Data type ÀÊØÙÖ for region features.Please see section 3.2.2 for routines to allocate/deallocate contours. Two important auxiliaryroutines to copy contours are listed in Fig. 4.8. ÀÓÔÝÄÓÒØ copies a contour including allattributes, whereas ÀÓÔÝÄÓÒØÈÖØ copies only a part of the original contours specifiedby two indices ÑÒ ÒÜ and ÑÜ ÒÜ. They refer to the first and the last point along thecontour to be copied (starting with index 0). For closed contours a negative value might bespecified for ÑÒ ÒÜ. This will lead to a “wrap-around”, that is the part of the contour to becopied starts at ÓÒØ Ò¹ÒÙÑ · ÑÒ ÒÜ. Both ÀÓÔÝÄÓÒØ and ÀÓÔÝÄÓÒØÈÖØallocate the output contour themselves. So just pass a pointer to ÀÓÒØ without allocating anymemory for ÓÒØ ÓÙØ.The routines provided for handling attributes of contour points are summarized in Fig. 4.9.ÀÄÓÒØØØÖ is used to add a new class of attributes to a given contour ÓÒØ. Note, thatthis routine allocates memory for the attribute values, but it does not set the values themselves.An arbitrary name for the attribute can be specified by the parameter ÒÑ. The index of thenew attribute within the ØØÖ× array in ÓÒØ is returned in ÒÜ and can be used to addressthe values by ÓÒØ¹ØØÖ×ÒÜ℄ºÚÐÜÜÜ℄. The same holds for global attributes:ÀÄÓÒØÐÓÐØØÖ is used to add new global attributes, which can be accessed byÓÒØ¹ÐÓÐÒÜ℄ºÚÐ. Note that these values can be accessed within the HALCONsystem (that is on the application layer) using the operators Ø ÓÒØÓÙÖ ØØÖ ÜÐ andHALCON 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 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: 4.2. REGION DATA (’HRLREGION’)
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?