| Home >> All |
Page 1 2
| • | opennlp.admin.* (61) | • | opennlp.ccg.* (103) | • | opennlp.common.* (50) |
| • | opennlp.grok.* (138) | • | opennlp.grokkit.* (7) | • | opennlp.guidia.* (94) |
| • | opennlp.hylo.* (16) | • | opennlp.javachart.* (269) | • | opennlp.javaconlib.* (11) |
| • | opennlp.jbricks.* (38) | • | opennlp.jbrickslib.* (56) | • | opennlp.jgrlib.* (41) |
| • | opennlp.leo.* (56) | • | opennlp.maxent.* (36) | • | opennlp.nlplib.* (30) |
Package Samples:
• opennlp.admin.projectconfig.token
• opennlp.admin.projectconfig.gui
• opennlp.admin.projectconfig.generation
• opennlp.admin.projectconfig.node
• opennlp.admin.projectconfig.event
• opennlp.admin.projectconfig
• opennlp.admin.tools
• opennlp.admin
• opennlp.grok.expression
• opennlp.grok.grammar
• opennlp.grok.io
• opennlp.grok.lexicon
• opennlp.grok.ml.dectree
• opennlp.grok.parse
• opennlp.grok.preprocess.cattag
• opennlp.grok.preprocess.chunk
• opennlp.grok.preprocess.mwe
• opennlp.grok.preprocess.namefind
• opennlp.grok.preprocess.postag
• opennlp.grok.preprocess.sentdetect
Classes:
• ModelReplacementManager: A object which can be used to ensure that a Maxent application can swap the model currently in use with a new one in a thread-safe manner without stopping the servicing of requests. Use this if your maxent application is a heavy-weight one or you have only one particular MaxentModel to use with your application. If your application class is lightweight and you will be creating multiple instances of it with different underlying models, consider using a DomainToModelMap object to ensure thread-safe model swapping. For example, in your application, create a ModelReplacementManager as follows: private ...
• ProfileReader: ProfileReader is a configuration file manager and contains the main API of the Profile package. It uses a file a format that extends the Properties file format. Configuration objects are loaded either as Profile or as java.util.Properties objects. The ProfileReader class is designed using the Singleton design pattern, i.e. it has no public constructor. Instead, the instantiation is controlled internally and access is done through static methods. Today the supported profile format is the class Profile and java.util.Properties. For instance, to create a Properties object from particular section in ...
• ProfileReader: ProfileReader is a configuration file manager and contains the main API of the Profile package. It uses a file format that extends the Properties file format. Configuration objects are loaded from a ProfileReader either as Profile or java.util.Properties. For instance, to create a Properties object from particular section in a file do the following: ProfileReader pr = new ProfileReader("mypackage/test/phonedb.profile") Properties p = .getProperties("mypackage.test.namedb"); Once loaded, the profiles are re-used each time the ProfileReader is called. The profile file has the following format: line-comments ...
• LexicalMWE: A Fixed Lexicon Multi-Word Expression finder that uses a list of MWE to determine if a sequence of words is in the MWE model. This finds common multi-word expressions which are completely fixed in English. Examples are "ad hoc", "au pair". Most are foreign language expressions which have been borrowed by English, although they might be analysable in their native language, the consitutent words make no sense when analysed with English grammar except as part of the MWE. Rather than extend the grammar to include these special usages it is much easier to treat the whole MWE as a lexicon entry with ...
• EnglishFixedLexicalMWE: A Fixed Lexicon Multi-Word Expression finder that uses "EnglishFixedLexicalMWE.data" for its content model. This finds both common and rare multi-word expressions which are completely fixed in English. Examples are "ad hoc", "au pair", "aes alienum", "ben trovato". Most are foreign language expressions which have been borrowed by English, although they might be analysable in their native language, the consitutent words make no sense when analysed with English grammar except as part of the MWE. Rather than extend the grammar to include these special usages it is much easier to treat the whole MWE ...
• EnglishVariableLexicalMWE: A Fixed Lexicon Multi-Word Expression finder that uses "EnglishFixedLexicalMWE.data" for its content model. This finds both common and rare multi-word expressions which are completely fixed in English. Examples are "ad hoc", "au pair", "aes alienum", "ben trovato". Most are foreign language expressions which have been borrowed by English, although they might be analysable in their native language, the consitutent words make no sense when analysed with English grammar except as part of the MWE. Rather than extend the grammar to include these special usages it is much easier to treat the whole MWE ...
• EnglishCommonFixedLexicalMWE: A Fixed Lexicon Multi-Word Expression finder that uses "EnglishCommonFixedLexicalMWE.data" for its content model. This finds common multi-word expressions which are completely fixed in English. Examples are "ad hoc", "au pair". Most are foreign language expressions which have been borrowed by English, although they might be analysable in their native language, the consitutent words make no sense when analysed with English grammar except as part of the MWE. Rather than extend the grammar to include these special usages it is much easier to treat the whole MWE as a lexicon entry with the right POS, ...
• InformationPanel: This class is an information panel for showing text information. The text is presented in a text area. There is an option to let the information panel remove all tags. For the removal of tags to work reliably the document should be well-formed, i.e. nested tags are not allowed. The character that is the beginning character of a tag is defined in the SKIP_BEGIN_CHAR field in this class. The character that is the end character of a tag is defined in the SKIP_END_CHAR field in this class. Default editable behaviour is a read-only text area. WARNING: The removal of tags procedure performs no error ...
• ModelSetter: A object to facilitate the resetting of a MaxentModel variable to a new value (model). In general this will be used anonymously, for example, as follows: private final ModelReplacementManager replacementManager = new ModelReplacementManager( new ModelSetter() { public void setModel(MaxentModel m) { model = m; } } ); where "model" would be the actual variable name of the model used by your application which you wish to be able to swap (you might have other models which need their own ModelSetters). Basically, this is just a clean way of giving a ModelReplacementManager access to a private variable ...
• Jc: Implements an API for a server that (roughly) corresponds to the functionality of the command 'jchart'. Create and initialize a server object for each interpreter and grammar that you want to execute. The server requires that either resource files or objects for compiled grammar, lexicon and mini-lexicon. The default ChartReader that is used is the one given by JcExec. The ChartReader can be re-configured or subsituted for a new one, if needed. The profile file, or resource should follow the format of the opennlp.jbrickslib.profile package. Possible profiles and their parameters can be found in ...
• AbstractAccessFactory: An abstract factory for access to various kinds of URL sources. Must be extended for the particular application at hand to get a complete builder. A complete session factory for Jdbc sources is included in this package. Any factory based on this class will use the clone method to generate new Transmitter items. For URL-based resources that can be reached by java.net.URLConnection, a help class AbstractUrlTransmitter that is useful when instantiating this class. However, often such sources have a non-standard query language for which we have no support at this point. Thus, the Request object must ...
• ProjectConfigFrame: This class holds a JFrame and is used as the main frame for the ProjectConfig-tool. The process of creating and initializing this frame is as follows: 1. Instantiate the ProjectConfigFrame. 2. Initialize the UI with: initUi(Properties uiProps) 3. Initialize the ToolsPanel with: initToolsPanel(ToolEventListener te) 4. Build the UI with: buildUi(NodeController nodeController) 5. Display the UI with: showUi() The frame is shut down with: shutDown()
• ProjectConfigControl: This class is the main class for the ProjectConfig tool. It extracts the properties from the configuration file, delegates them to each handler that needs its settings, it sets up the different controllers and handlers, i.e. TokenizerController , GenerationController , and NodeControlle . It implements the ToolEventListener interface to handle ToolEvents , i.e. events that are triggered when the user presses any of the tool buttons: Save, Generate files, or Exit.
• SingletonRegistry: A generic support class for the design pattern n-Singleton. This SingletonRegistry class is thread-safe. There will be new SingletonRegistry created for each thread that calls this class. It uses java.util.ThreadLocal variables to hold the unique instance of this class. Thus, if a Singleton object is set in this SingletonRegistry from a static area in some class, then all threads will have a separate object constructed implicitely. See e.g. the class ProfileReader for an example of how this class can be used.
• AccessTransfer: For transfer to sources that needs external access. The main object of the access package. Executes a complete KS access interaction sequence. Initiated using an AccessFactory. The access transmission starts with query-construction and ends with result retrieval. Concrete objects for RequestBuilder and ResponsCollector are built outside the access package. For AccessFactory, default factories from the package can be used, or new factories can be tailored for specific needs.
• MysqlSelectFiller: Implements the SelectFiller interface for MySQL queries. This class handles some of the basic constructs of select statements in MySQL. The SelectFiller interface is considered "complete" at this point. However, the coverage is not complete wrt the MySQL language, since for instance the notion of a "HAVING" clause is not used. (Although the addAtom method adds an "hole" that one can use to hack stuff into the where-part, if needed.
• MysqlQuery: Implements the Query interface for MySQL queries. This class handles some of the basic constructs of select statements in MySQL. The Query interface is considered "complete" at this point. However, the coverage is not complete wrt the MySQL language, since for instance the notion of a "HAVING" clause is not used. (Although the addAtom method adds an "hole" that one can use to hack stuff into the where-part, if needed.
• GenerationController: This class takes care of the generation of files. It holds a Vector of GenerationHandlers which are registered to this class. It also holds a TokenizerController . It contains the method genFiles() that traverses the list of GenerationHandlers and for each of them calls their genFile() method with the TokenizerController as argument.
• NullLayout: A panel without layout manager. Added elements are placed by coordinates. Default position is 0x0. Use the NullConstraint class to set constraints for added components. This panel is also useful for creation of padding: use the size setters methods of Panel to obtain appropriate size. In particular, BoxLayout fillers should normally set both setPreferredSize and setMaximumSize for fillers of limited size.
• SingletonRegistry: A generic support class for the design pattern n-Singleton. This SingletonRegistry class is "thread-safe". SingletonRegistry uses java.util.InheritableThreadLocal variables to hold a unique registry for a thread and its child threads. Thus, if a Singleton object is set in this SingletonRegistry from a static area in some class, then all non-related threads will have a separate object constructed implicitely.
• FixedMWEModel: A model holding the Fixed Lexicon Multi-Word Expressions. It uses the first word to index into a Map. As most first words for Fixed Lexicon MWEs are not normal English words they occur very infrequently except as part of the MWE. Therefore this algorithm is very fast only taking a single Hash Map lookup for words which do not start any MWE (the vast majority of words in any normal English text).
• MWEModel: A model holding the Fixed Lexicon Multi-Word Expressions. It uses the first word to index into a Map. As most first words for Fixed Lexicon MWEs are not normal English words they occur very infrequently except as part of the MWE. Therefore this algorithm is very fast only taking a single Hash Map lookup for words which do not start any MWE (the vast majority of words in any normal English text).
• VariableMWEModel: A model holding the Fixed Lexicon Multi-Word Expressions. It uses the first word to index into a Map. As most first words for Fixed Lexicon MWEs are not normal English words they occur very infrequently except as part of the MWE. Therefore this algorithm is very fast only taking a single Hash Map lookup for words which do not start any MWE (the vast majority of words in any normal English text).
• DecisionList: A DecisionList like the one used in Yarowsky's algorithm from 1995. For each set of Positions and word type the likelihood ratio is calculated. If the frequency for a word is much higher for sense1 in the given Positions, the likelihood score will be positive, if they are equal we will get zero, and otherwise a positive score. The resulting list is sorted by the absolute value of the score.
• SDEventStream: An implementation of EventStream which assumes that it is receiving its data as one (valid) sentence per token. The default DataStream to use with this class is PlainTextByLineDataStream, but you can provide other types of DataStreams if you wish to receive data from sources other than plain text files; however, be sure that each token your DataStream returns is a valid sentence.
| Home | Contact Us | Privacy Policy | Terms of Service |