HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

34 CHAPTER 2. OPERATOR DESCRIPTION (’DEF’-FILES)2.3.15 assertion××ÖØÓÒboolean expressionThis slot contains a boolean expression that determines how the passed or returned values ofparameters are absolutely or relatively connected to the values of other parameters or someabsolute values. The same expressions may appear as described above for ÚÐÙ ÒÙÑÖ, seetable 2.1.Examples:ÈÖÑ½ ÈÖÑ¾ ²² ÈÖÑ¾ ¼This means that parameter 1 and 2 must have the same value and this value is greater than0.¼ ÈÖÑ¾ ²² ÈÖÑ¾ ¾This means that parameter 2 must have a value between 0 and 255.ÈÖÑ½ ÒÙÑÖ´ÁÑÁÒµThis means that the value of parameter 1 must be less or equal the number of input images.ÈÖÑ¾ ÛØ´ÁÑÁÒµ ²² ÈÖÑ¾ ¼ ²² Ó´ÈÖÑ¾µThis means that the value of parameter 2 must be between 0 and the width of the inputimage and must be an even number.2.3.16 multichannelÑÙÐØÒÒÐØÖÙ¸Ð×¸ÓÔØÓÒÐThis slot is only used in connections with image objects. It contains an assertion about thenecessary or supported number of channels of an image. If set to Ð×, the processing is doneonly on the first channel (all others are ignored), if set to ØÖÙ, a multichannel image must bepassed. ÓÔØÓÒÐ specifies operators that can work on more than one channel but can alsowork on only one channel as well.2.4 Text in -filesWithin a -file the semicolon (;) is used to separate the single slots. So, when using a semicolonwithin a text, it must be quoted with a backslash ().-files are not only used to create interface code, but also allow the generation of the manuals,the HTML documentation, and the ÐÔ files used to access operator knowledge via HALCONoperators like Ø ÓÔÖØÓÖ ÒÓ. For the online help and the HTML files an ASCII versionof each text is needed, whereas the manuals are produced compiling a L A TEX-file generated fromthe -files. To avoid the necessity of writing two text blocks for one operator (ASCII andL A TEX), both versions are generated by using one text. Therefore, the following conventionsmust be observed:HALCON Extension Package Interface / 2000-11-16
2.4. TEXT IN ’DEF’-FILES 35Umlauts: All German umlauts are written in the L A TEX-typical notation: , ..., Í, ×.Quotation marks: There are two kinds of quotation marks’string’: This notation signals that the quoted text is a string as used within programminglanguages. So ÓÑÔ treats ³×ØÖÒ³ as a string-parameter.“Text”: This notation must be used in all other cases, particularly when quoting a wordor text segment because of its content. So ÓÑÔ treats ÌÜØ³³ as a quoted sectionof a text. Please do not forget or permute the quotation marks (starting with andending with ³³).Underscores: An underscore can be used without the necessity of prefixing a backslash asnecessary in L A TEX() so that the text is easier to read. The backslashes are insertedautomatically in the generated L A TEX-version of the text. Note, that this mechanism isonly active within the ASCII part of the text.Backslash: All backslashes () within the text are ignored while generating the ASCII version.So the L A TEX-linefeed-symbol () can be used without any problems.Tilde: To use the tilde (e.g. as symbol for negation: ×Ø´³ÐÖ³µ), the followingspecial notation must be used for the L A TEX-text: ×Ø´³ßÐÐÖ³µ.Formulas: Short formulas can be bracketed by dollar symbols ($) just as in L A TEX. Thesesymbols are ignored for the ASCII version of the text.To set an index of one character (e.g. )L A TEX allows to simply write °°. This is notpossible here, because of the special underscore handling. Therefore, any index must bewritten exactly as any longer index within L A TEX: ßÐ.HALCON : The string HALCON is generated by ÀÐÓÒ. Note, that in the PostScript filesderived from the generated L A TEX version of the -files, no space is generated after thestring HALCON. Thus, if you do not want to start the next character/string without ablank, that is concatenated to the string HALCON, you should use ÀÐÓÒ instead. So“ÀÐÓÒ ” results in “HALCON XYZ” and “ÀÐÓÒ ” results in “HALCONXYZ”. With the ASCII version all backslashes are ignored (see above).Names of parameters and operators: Any reference to HALCON parameters oroperators has to be written as ÈÖÊparameter name, respectively asÇÔÊoperator name. These keywords and the brackets are ignored, whengenerating the ASCII version so that only parameter name or operator name remainsin the ASCII file. For the HTML documentation hyper links are generated from thesereferences.Parameter values: A specific value for a parameter should be written asÎÐÊparameter value . For example, the parameter ÈÖÊLightDark ofthe operator ÇÔÊdyn threshold can hold one of the values ÎÐÊ’light’,ÎÐÊ’dark’, or ÎÐÊ’equal’. The keyword ÎÐÊ and the brackets areignored, when generating the ASCII version so that only parameter value remains in theASCII file.Other L A TEX commands: If you would like to use additional L A TEX command within a text segment,two versions of this segment must be provided – one for ASCII (with signallingHALCON 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 35 and 36: 2.3. DESCRIBING THE PARAMETERS 272.
Page 37 and 38: 2.3. DESCRIBING THE PARAMETERS 29Pl
Page 39 and 40: 2.3. DESCRIBING THE PARAMETERS 31¯
Page 41: 2.3. DESCRIBING THE PARAMETERS 332.
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 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?