Current DataModel should be splitted into multiple parts.
keep the current DataModel with only the columns mapping and dynamicFields property
create a MotionConfiguration object with property movingStateModel, and nested objects SupportPointConfiguration, TempoConfigurationwith their related properties
create a CourseConfiguration object with courseTimeout property
Some configurations are only used from customers projects (eg. salvoTempo and salvoTempoValues), these should be removed from arlas-proc.
hmmWindowSize should be a static variable and not a DataModel entry, in a external class that could be turned later into real configuration file.
Check what to do of visibilityTimeout and timeSampling.
By the way check why irregularTempoThreshold isn't used (can be removed?)
Current DataModel should be splitted into multiple parts.
keep the current DataModel with only the columns mapping and
dynamicFields
propertycreate a
MotionConfiguration
object with propertymovingStateModel
, and nested objectsSupportPointConfiguration
,TempoConfiguration
with their related propertiescreate a
CourseConfiguration
object withcourseTimeout
propertySome configurations are only used from customers projects (eg.
salvoTempo
andsalvoTempoValues
), these should be removed from arlas-proc.hmmWindowSize
should be a static variable and not a DataModel entry, in a external class that could be turned later into real configuration file.Check what to do of
visibilityTimeout
andtimeSampling
. By the way check whyirregularTempoThreshold
isn't used (can be removed?)