Org.simantics.charts - Revision history

Toni Kalajainen: /* org.simantics.trend */

2012-06-27T10:34:42Z

org.simantics.trend

← Older revision		Revision as of 10:34, 27 June 2012
Line 26:		Line 26:
	time, endTime, value - are mandatory fields.		time, endTime, value - are mandatory fields.

	time - Region start time, the time of the 1st included ~~sample~~		time - Region start time, the time of the 1st source sample included into the band
	endTime - Region end time, the time of the last included ~~sample~~		endTime - Region end time, the time of the last source sample included into the band

	value - First value in the ~~region~~		value - First value in the band
	lastValue - Last value in the ~~region~~		lastValue - Last value in the band
	avg - Average value of all included samples		avg - Average value of all included samples
	median - Median value of all samples in the ~~region~~		median - Median value of all samples in the band
	min - Lowest value in the ~~region~~		min - Lowest value in the band
	max - Highest value in the ~~region~~		max - Highest value in the band

	quality - 0 = Good, -1 = No value		quality - 0 = Good, -1 = No value
	count - The number of included samples in the ~~region~~		count - The number of included samples in the band
	</pre>		</pre>

Toni Kalajainen: /* org.simantics.trend */

2012-06-27T10:32:46Z

org.simantics.trend

← Older revision		Revision as of 10:32, 27 June 2012
Line 16:		Line 16:

	''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.		''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.

			<pre>
			The trends can utilize these fields from a sample format:

			Describes the format of the packed sample. The sample must be a record.
			The record must have any combination of the following named fields.
			The field types must one of: byte, integer, long, float, double.

			time, endTime, value - are mandatory fields.

			time - Region start time, the time of the 1st included sample
			endTime - Region end time, the time of the last included sample

			value - First value in the region
			lastValue - Last value in the region
			avg - Average value of all included samples
			median - Median value of all samples in the region
			min - Lowest value in the region
			max - Highest value in the region

			quality - 0 = Good, -1 = No value
			count - The number of included samples in the region
			</pre>

Toni Kalajainen at 10:30, 27 June 2012

2012-06-27T10:30:02Z

← Older revision		Revision as of 10:30, 27 June 2012
Line 13:		Line 13:
	The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.		The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.

	In typical simantics case, a variable is recorded with different sampling intervals, see TrendSamplingFormats (all samples, 100ms, 1s, 10s, 60s). The trend detects all available history items for a recorded variable, and selects the most ~~appropriate~~ item to draw from.		In typical simantics case, a variable is recorded with different sampling intervals, see TrendSamplingFormats (all samples, 100ms, 1s, 10s, 60s). The trend detects all available history items for a recorded variable, and selects the most suitable item to draw from.

	''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.		''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.

Toni Kalajainen at 10:29, 27 June 2012

2012-06-27T10:29:40Z

← Older revision		Revision as of 10:29, 27 June 2012
Line 13:		Line 13:
	The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.		The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.

	In typical simantics case, a variable is recorded with different sampling intervals, see TrendSamplingFormats (all samples, 100ms, 1s, 10s, 60s). The trend detects all available history items for a recorded variable, and selects the most appropriate ~~file~~ to draw from.		In typical simantics case, a variable is recorded with different sampling intervals, see TrendSamplingFormats (all samples, 100ms, 1s, 10s, 60s). The trend detects all available history items for a recorded variable, and selects the most appropriate item to draw from.

	''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.		''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.

Toni Kalajainen at 10:29, 27 June 2012

2012-06-27T10:29:22Z

← Older revision		Revision as of 10:29, 27 June 2012
Line 13:		Line 13:
	The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.		The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.

	In typical simantics case, a variable is recorded with different sampling intervals (see TrendSamplingFormats~~), example:~~ all samples, 100ms, 1s, 10s, 60s. The trend detects all available history items for a recorded variable, and selects the most appropriate file to draw from.		In typical simantics case, a variable is recorded with different sampling intervals, see TrendSamplingFormats (all samples, 100ms, 1s, 10s, 60s). The trend detects all available history items for a recorded variable, and selects the most appropriate file to draw from.

	''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.		''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.

Toni Kalajainen at 10:28, 27 June 2012

2012-06-27T10:28:57Z

← Older revision		Revision as of 10:28, 27 June 2012
Line 11:		Line 11:
	Trend is configured with TrendSpec class. It describes how and with what items the trend is drawn. The info can be changed on the run.		Trend is configured with TrendSpec class. It describes how and with what items the trend is drawn. The info can be changed on the run.

	The data source for a trend is a HistoryManager, an interface from [[org.simantics.history]]~~. A trend is configured to visualize items from one history manager~~. History manager consists of groups and items. There is metadata with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.		The data source for a trend is one HistoryManager, an interface from [[org.simantics.history]]. History manager consists of groups and items. There is metadata associated with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.

	~~''Format''-field determines the~~ sampling ~~format on the disc. All numeric types are supported~~: ~~integer~~, ~~float~~, ~~double~~, ~~etc~~. ~~''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of~~ a ~~single sample. If ''quality'' field exists~~, ~~the trend can have empty regions. ''min''~~ and ~~''max'' fields provide value deviation when~~ the ~~trend is zoomed out~~.		In typical simantics case, a variable is recorded with different sampling intervals (see TrendSamplingFormats), example: all samples, 100ms, 1s, 10s, 60s. The trend detects all available history items for a recorded variable, and selects the most appropriate file to draw from.

	~~In typical simantics case, a variable is recorded with different~~ sampling ~~intervals (see TrendSamplingFormats), example~~: ~~all samples~~, ~~100ms~~, 1s, ~~10s, 60s~~. ~~The trend detects all available history items for~~ a ~~recorded variable~~, and ~~selects~~ the ~~most appropriate file to draw from~~.		''Format''-field determines the sampling format on the disc. All numeric types are supported: integer, float, double, etc. ''time'' and ''value'' fields are mandatory. If endTime exists the sample is interpreted as "value band" instead of a single sample. If ''quality'' field exists, the trend can have empty regions. ''min'' and ''max'' fields provide value deviation when the trend is zoomed out.

Toni Kalajainen at 10:27, 27 June 2012

2012-06-27T10:27:10Z

← Older revision		Revision as of 10:27, 27 June 2012
Line 7:		Line 7:

	==org.simantics.trend==		==org.simantics.trend==
	org.simantics.trend is a visualization library that draws items as time-series lines. It supports lines and binary items on the same chart. It is the only current chart implementation. ~~''os.trend''~~ is environment independent~~. It is installed into an EditorPart by os.charts plugin~~, ~~but~~ it can ~~also~~ be ran as POJO ~~or attached to~~, ~~say~~, ViewPart, or Java Applet. The trend visualizations are based on AWT/Swing.		org.simantics.trend is a visualization library that draws items as time-series lines. It supports lines and binary items on the same chart. It is the only current chart implementation. The code in this plugin is environment independent, it can be ran as POJO, EditorPart, ViewPart, or say, Java Applet. The trend visualizations are based on AWT/Swing.

	Trend is configured with TrendSpec class. It describes how and with what items the trend is drawn. The info can be changed on the run.		Trend is configured with TrendSpec class. It describes how and with what items the trend is drawn. The info can be changed on the run.

Tuukka Lehtonen: /* org.simantics.trend */

2012-06-27T10:20:15Z

org.simantics.trend

← Older revision		Revision as of 10:20, 27 June 2012
Line 7:		Line 7:

	==org.simantics.trend==		==org.simantics.trend==
	org.simantics.trend is a visualization library that draws items as time-series lines. It supports lines and binary items on the same chart. It is the only current chart implementation. ''os.trend'' is environment ~~indipendent~~. It is installed ~~to Editorpart~~ by os.charts plugin, but it also ~~can~~ be ~~run~~ POJO or attached to, say, ViewPart, or Java Applet.		org.simantics.trend is a visualization library that draws items as time-series lines. It supports lines and binary items on the same chart. It is the only current chart implementation. ''os.trend'' is environment independent. It is installed into an EditorPart by os.charts plugin, but it can also be ran as POJO or attached to, say, ViewPart, or Java Applet. The trend visualizations are based on AWT/Swing.

	Trend is configured with TrendSpec class. It describes how and with what items the trend is drawn. The info can be changed in the run.		Trend is configured with TrendSpec class. It describes how and with what items the trend is drawn. The info can be changed on the run.

	The data source for a trend is a HistoryManager, an interface from [[org.simantics.history]]. A trend is configured to visualize items from one history manager. History manager consists of groups and items. There is metadata with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.		The data source for a trend is a HistoryManager, an interface from [[org.simantics.history]]. A trend is configured to visualize items from one history manager. History manager consists of groups and items. There is metadata with each item, such as, id, variableId (the item in datasource), format, deadband, interval, gain, bias, groupId, etc.

Tuukka Lehtonen: /* org.simantics.charts */

2012-06-27T10:13:34Z

org.simantics.charts

← Older revision		Revision as of 10:13, 27 June 2012
Line 4:		Line 4:

	==org.simantics.charts==		==org.simantics.charts==
	Charts is the IU plugin that ties trends to the ~~IDE~~ environment ~~of Eclipse and Simantics~~. It contributes ~~editorpart~~, preferences, DnD operations, context menu actions, tool bar buttons, ontology, etc to Simantics ~~IDE~~. The main class there is its EditorPart contribution TimeSeriesEditor.		Charts is the UI plugin that ties trends to the Simantics Workbench environment. It contributes an editor part, preferences, DnD operations, context menu actions, tool bar buttons, ontology, etc to Simantics Workbench. The main class there is its EditorPart contribution TimeSeriesEditor.

	==org.simantics.trend==		==org.simantics.trend==

Tuukka Lehtonen at 10:12, 27 June 2012

2012-06-27T10:12:19Z

← Older revision		Revision as of 10:12, 27 June 2012
Line 1:		Line 1:
	There are two ~~pluings~~ to Simantics charts:		There are two plug-ins to Simantics charts:
	*''org.simantics.charts''		*''org.simantics.charts''
	*''org.simantics.trend''		*''org.simantics.trend''