HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

86 CHAPTER 5. HANDLING ICONIC OBJECTS AND CONTROL PARAMETERScorner (Ö¾,¾). These coordinates should be selected that way, that the filter mask is completelywithin the image when placed on any pixel inside of the rectangle. Thus, no border treatment isnecessary within Ö Ò.Ö ÓÙØ is set to all remaining pixels within Ö Ò. For those pixels an appropriate (and timeconsuming) border treatment has to be done. Fig. 5.35 shows an application of ÀÊÄÓÑÔ.Note, that the distinction of “inner” and “outer” area only refers to the image border, but not tothe border of the regions specifying the area of definition. So, it is only ensured that no memoryaccess to positions outside the image matrix can happen, but there is no guarantee that all pixelvalues covered by the filter mask when placed on pixels within Ö ÒÒÖ are defined, iftheydo not belong to Ö Ò. This means, a filter might use undefined gray values along the borderof the area of definition of the input images. The HALCON user should keep that in mind, whenapplying a sequence of filters to restricted regions of interest.5.6.4 ÀÆÙÑÇÒÒÐ×ÀÆÙÑÇÒÒÐ× (see Fig. 5.33) returns for the first input object parameter of a HALCONoperator the number of channels of the image object with number Ó ÒÜ. Thus, this routineis just a shortcut for using ÀÈÆÙÑÇÒÒÐ× as defined in Fig. 5.5 with ÔÖ ÒÙÑ ½.HALCON Extension Package Interface / 2000-11-16
Chapter 6Special Routines for Typical SupplyProceduresIn the previous chapter the basic routines for handling iconic objects, object parameters, andcontol parameters of a HALCON operator have been introduced. Based on these this chapterdescribes a set of convenience routines that facilitate the programming of supply procedures intypical situations.6.1 Loop MacrosA frequently needed task is to process all image objects (images or regions) passed to an operatorby one or two input object parameters. This is true for example for most filter and manysegmentation operators. Loop macros provide a framework for this problem, see also section5.3.All macros described in this section have in common that they implement a loop over all imageobjects within the first input object parameter. ÀÐÐÐØÖ¾ also includes a parallel loop overall objects within the second input object parameter. It is assumed that the operator does nothave any more input object parameters. The macros provide users with the region and pixeldata of each image object so that they can work on the data within the loop. Some also createoutput image objects .The macros return the index of the current object Ó ÒÜ (½ Ò) within the input objectparameter. Thus, Ó ÒÜ can be seen as a reference parameter of the macro and therefore isnotated 1 with ’²Ó ÒÜ’. The following table contains an overview of all loop macros, theirareas of application, and the provided image data. Their syntax is defined in Fig. 6.1.1 Note, that this is a specific notation only - do not pass pointers to the macros!87
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 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
2.3. DESCRIBING THE PARAMETERS 252.
Page 35 and 36:
Page 37 and 38:
2.3. DESCRIBING THE PARAMETERS 29Pl
Page 39 and 40:
2.3. DESCRIBING THE PARAMETERS 31¯
Page 41 and 42:
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 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: 5.6. AUXILIARY MACROS AND PROCEDURE
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 122 and 123: 114 APPENDIX A. HALCON ERROR CODES
Page 140: 132 APPENDIX A. HALCON ERROR CODESH
show all

HALCON Extension Package Programmer's Manual

Create successful ePaper yourself

Delete template?

Save as template?