HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

22 CHAPTER 2. OPERATOR DESCRIPTION (’DEF’-FILES)2.2.12 parallelizationThe slot ÔÖÐÐÐÞØÓÒ contains information about the parallelization characteristics of anoperator when used in Parallel HALCON (see the manual Getting Started with HALCONfor more information about Parallel HALCON). On the one hand, this regards the possibilityof using the operator in a parallel, for example, multithreaded application and on the otherhand this regards the automatic parallelization which Parallel HALCON uses to speed up theoperator’s processing when working with multi-processor hardware.The slot ÔÖÐÐÐÞØÓÒ consists of several sub-slots, each starting with a characteristickeyword followed by a colon and finishing with a semicolon. The example below shows theslot for the operator ÝÒ ØÖ×ÓÐ, which is not “local”, needs neither complete nor mutualexclusion, and is parallelized on tuple level. The single subslots and their meaning will bedescribed in the following sections.ÔÖÐÐÐÞØÓÒÔÖÓ××ÜÐÙ×ÚÐÝ Ð×ÔÖÓ××ÐÓÐÐÝ Ð×ÔÖÓ××ÑÙØÙÐ Ð×ÑØÓ×ÔÐØØÙÔÐÔÖÓ×× ÜÐÙ×ÚÐÝ ØÖÙ¸Ð×This subslot of ÔÖÐÐÐÞØÓÒ assigns, whether an operator is processed completelyexclusively (‘true’) by the main HALCON process/thread or not. An exclusive processingmeans that no other operator will be processed by Parallel HALCON while the exclusiveoperator is running. If an exclusive operator is started and other operators are still running,the processing of the exclusive operator is delayed until all other (currently running)operators have completed.An exclusively processed operator is always processed without any parallelization by themain HALCON thread/process. Note that even if Parallel HALCON is reentrant for mostof the operators, there are still some operators that have to be processed exclusively dueto reasons of their implementation.If no subslot ÔÖÓ×× ÜÐÙ×ÚÐÝ is filled in with an operator, it is assumed that theoperator needs no completely exclusive processing (“optimistic” assumption).ÔÖÓ×× ÑÙØÙÐ ØÖÙ¸Ð×This subslot of ÔÖÐÐÐÞØÓÒ assigns, whether Parallel HALCON processes an operatorunder mutual exclusion (‘true’) against itself or not. Here, a mutual exclusionmeans that the same operator may not run twice or more at the same time; for example,there will only run one instance of ÔØ ØÑÔÐØ at a time, whereas other operatorsmay run concurrently to ÔØ ØÑÔÐØ.An exclusively processed operator is always processed without any parallelization by themain HALCON thread/process.If no subslot ÔÖÓ×× ÑÙØÙÐ is filled in with an operator, it is assumed that the operatorneeds no mutual exclusion (“optimistic” assumption).ÔÖÓ×× ÐÓÐÐÝ ØÖÙ¸Ð×This subslot of ÔÖÐÐÐÞØÓÒ assigns, whether an operator must be processed locallyHALCON Extension Package Interface / 2000-11-16
2.2. EXTENDED OPERATOR DESCRIPTION 23(‘true’) by a program thread, or whether it may called by any (“external”) thread withoutproblems. The slot is mainly important when programming multithreaded applicationsunder Windows NT and Windows 2000. Here, there exists a direct mapping betweenprogram threads and graphical elements, such as windows, dialog boxes or button controls.In short, a graphical element only exists in the context of its associated thread. Thiscan cause severe problems, for example, hang the application, if another thread tries toperform user interactions via graphical elements which belong to other threads. For example,troubles might occur under Windows NT/ 2000, if one thread opens a window viaÓÔÒ ÛÒÓÛ and another thread tries to get input from this window via ÖÛ ÖÐ.As it is not always obvious for all operators, whether they work with critical (graphical)elements or not, the slot ÔÖÓ×× ÐÓÐÐÝ was introduced. If ÔÖÓ×× ÐÓÐÐÝ isset to ‘true’, this signals the programmer that the corresponding operator must be usedcarefully within multithreaded Windows NT/ 2000 applications. The most simple wayto avoid any problems with such operators is to process them all under mutual exclusionwithin the main thread of the program.As a side effect, Parallel HALCON processes an operator without parallelization regardlessthe settings of the subslots ÑØÓ and ÓÑÒ ×ÔÐØ,ifÔÖÓ×× ÐÓÐÐÝ is set to‘true’. This avoids problems with ‘local’ operators and multithreading and makes sensebecause ‘local’ operators normally are responsible for graphical interaction and thus arenot suitable for parallelization.If no subslot ÔÖÓ×× ÐÓÐÐÝ is filled in with an operator, it is assumed that the operatormust be processed “locally” (“pessimistic” assumption). However, this subslot should befilled in in any case, because it contains a very useful information for programmers ofmultithreaded applications.ÑØÓ ÒÓÒ¸×ÔÐØ ØÙÔÐ¸×ÔÐØ ÒÒÐ¸×ÔÐØ ÓÑÒThis subslot of ÔÖÐÐÐÞØÓÒ can contain one or more of the strings above andspecifies, which type of (automatic) parallelization the operator is suitable for:¯ ×ÔÐØ ØÙÔÐ: Parallel HALCON does not automatically parallelize the operator.¯ ×ÔÐØ ØÙÔÐ: Parallel HALCON parallelizes the operator by splitting every inputimage tuple into several subsets of the tuple; the tuple subsets are then processed inparallel.¯ ×ÔÐØ ÒÒÐ: Parallel HALCON parallelizes by splitting every multichannel(input) image into several subsets of the channels; the subsets are then processedin parallel.¯ ×ÔÐØ ÓÑÒ: Parallel HALCON parallelizes by splitting the domain of everyinput image into several parts; the parts are then processed in parallel.If ÑØÓ is set to anything other but ‘none’, the parameter slot Ó×Ø× ÛØ must befilled in for every input control parameter and the parameter slot ÔÓ×ØÔÖÓ××Ò mustbe filled in for every output control parameter of the operator (see page 29)!If ÑØÓ is set to ‘split domain’, the slot ÓÑÒ ×ÔÐØ (see below) must also be setcorrectly and may not be omitted !If the slot ÔÖÓ×× ÐÓÐÐÝ is set to ‘true’, ÑØÓ should be set to ‘none’, because theoperator won’t be parallelized then (see description of ÔÖÓ×× ÐÓÐÐÝ above).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 27 and 28: 2.2. EXTENDED OPERATOR DESCRIPTION
Page 29: 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:
5.4. CREATING OBJECTS AND WRITING O
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?