Package annotation.localise.targetmotion
Class TMAnnotationType
- All Implemented Interfaces:
 LocalisationAlgorithm
- Direct Known Subclasses:
 CTMAnntoationType
public class TMAnnotationType
extends DataAnnotationType<TMAnnotation>
implements LocalisationAlgorithm
Annotation type for target motion analysis. Target motion analysis requires a
 parent data unit which has multiple sub units.
- Author:
 - Jamie Macaulay
 
- 
Field Summary
FieldsModifier and TypeFieldDescriptionprotected TMSettingsPanelThe dialog panel for target motion options.,static final Stringprotected annotation.localise.targetmotion.TMAnnotationType.TMGroupLocaliserThe target motion localisation algorithm.Fields inherited from class annotation.DataAnnotationType
SHORTIDCODELENGTH - 
Constructor Summary
Constructors - 
Method Summary
Modifier and TypeMethodDescriptionautoAnnotate(PamDataUnit pamDataUnit) Automatically annotate the data unit with this annotation.booleancanAnnotate(Class dataUnitType) Find out whether or not a particular type of data can be annotatedbooleanfindLocaliserModel(String modelName) Get information about the localisation algorithm.Get an optional AnnotationBinaryHandler which can be used to add the annotation information for binary files and also read data back from them.Get a dialog component that can be incorporated into a larger dialog.A short identifying code which MUST be unique to the data annotation and MUST be four characters long.Get an SQLLogging add on.Get something that can make LocalisationType objects of a form a bit bespoke to the type of localiser.booleanvoidsetAnnotationOptions(AnnotationOptions annotationOptions) Methods inherited from class annotation.DataAnnotationType
getDataBlockSpeciesManager, getDataSelectCreator, getDataSelector, getSymbolModifier, getTargetDataBlock, getXMLWriter, isAnnotating, setTargetDataBlock, toString, toString 
- 
Field Details
- 
TMANNOTATIONNAME
- See Also:
 
 - 
clickLocDialogPanel
The dialog panel for target motion options., - 
tmGroupLocaliser
protected annotation.localise.targetmotion.TMAnnotationType.TMGroupLocaliser tmGroupLocaliserThe target motion localisation algorithm. 
 - 
 - 
Constructor Details
- 
TMAnnotationType
public TMAnnotationType() 
 - 
 - 
Method Details
- 
getAnnotationName
- Specified by:
 getAnnotationNamein classDataAnnotationType<TMAnnotation>
 - 
getAnnotationClass
- Specified by:
 getAnnotationClassin classDataAnnotationType<TMAnnotation>- Returns:
 - Class type for the annotations
 
 - 
canAnnotate
Description copied from class:DataAnnotationTypeFind out whether or not a particular type of data can be annotated- Specified by:
 canAnnotatein classDataAnnotationType<TMAnnotation>- Parameters:
 dataUnitType- Class of a type of data unit. Can be null in which case annotation can be stand alone.- Returns:
 - true if the data unit Class can be annotated.
 
 - 
canAutoAnnotate
public boolean canAutoAnnotate()- Overrides:
 canAutoAnnotatein classDataAnnotationType<TMAnnotation>- Returns:
 - True if annotation can be automatic (i.e. calculated rather than input by user).
 
 - 
getShortIdCode
Description copied from class:DataAnnotationTypeA short identifying code which MUST be unique to the data annotation and MUST be four characters long. Classes can override this with something even more cryptic so long as it remains unique.- Overrides:
 getShortIdCodein classDataAnnotationType<TMAnnotation>- Returns:
 - a four character id string.
 
 - 
autoAnnotate
Description copied from class:DataAnnotationTypeAutomatically annotate the data unit with this annotation.- Overrides:
 autoAnnotatein classDataAnnotationType<TMAnnotation>- Parameters:
 pamDataUnit- data unit to annotate- Returns:
 - the annotation (though this should have already been added to the data unit).
 
 - 
getSQLLoggingAddon
Description copied from class:DataAnnotationTypeGet an SQLLogging add on. For stand alone annotations, this will be used to generate a stand alone database table. For annotations of existing data this will be used to add additional columns to the existing data tables.- Overrides:
 getSQLLoggingAddonin classDataAnnotationType<TMAnnotation>- Returns:
 - An SQLLoggingAddon or null if SQL logging unavailable for this type of annotation.
 
 - 
getBinaryHandler
Description copied from class:DataAnnotationTypeGet an optional AnnotationBinaryHandler which can be used to add the annotation information for binary files and also read data back from them.- Overrides:
 getBinaryHandlerin classDataAnnotationType<TMAnnotation>- Returns:
 - handler for binary data i/o.
 
 - 
getDialogPanel
Description copied from class:DataAnnotationTypeGet a dialog component that can be incorporated into a larger dialog.Note that this is for setting the data for a specific annotation, NOT the dialog for setting options controlling how the annotation type works.
- Overrides:
 getDialogPanelin classDataAnnotationType<TMAnnotation>- Returns:
 - a dialog panel (contains a component = a few other functions).
 
 - 
getSettingsPanel
- Overrides:
 getSettingsPanelin classDataAnnotationType<TMAnnotation>
 - 
hasSettingsPanel
public boolean hasSettingsPanel()- Overrides:
 hasSettingsPanelin classDataAnnotationType<TMAnnotation>
 - 
getAnnotationOptions
- Overrides:
 getAnnotationOptionsin classDataAnnotationType<TMAnnotation>- Returns:
 - the annotationOptions
 
 - 
setAnnotationOptions
- Overrides:
 setAnnotationOptionsin classDataAnnotationType<TMAnnotation>- Parameters:
 annotationOptions- the annotationOptions to set
 - 
findLocaliserModel
 - 
getAlgorithmInfo
Description copied from interface:LocalisationAlgorithmGet information about the localisation algorithm.- Specified by:
 getAlgorithmInfoin interfaceLocalisationAlgorithm- Returns:
 - algorithm information.
 
 - 
getTethysCreator
Description copied from interface:LocalisationAlgorithmGet something that can make LocalisationType objects of a form a bit bespoke to the type of localiser. This may be better than having the standard functions in LocalizationBuilder guess what's best.- Specified by:
 getTethysCreatorin interfaceLocalisationAlgorithm- Returns:
 - can be null in which case standard functions will do the best they can.
 
 
 -