|
Known Issue Description
|
Reference #
|
|
ThingWorx Analytics Server: Two-at-a-time Signals request does not return MI for all field combinations
When running a request for Signals, and specifying maxAtATime = 2, Mutual Information (MI), in relation to the goal, is not returned for all field combinations as expected. Instead, individual (one-at-a-time) MI scores are returned for all fields and then are filtered down to the top 25% most relevant fields. Two-at-a-time signals are calculated only for those fields. There is currently no way to modify this filtering behavior.
|
TA-729
|
|
Analytics Manager: An existing simulation event fails if it is triggered after server restart
Analysis agents must be restarted after a ThingWorx server restart. Without restart of the agent, any new simulation jobs will fail to execute.
|
—
|
|
Analytics Manager: Time window event does not work for non-time series models
When a non-time series model is uploaded using the Analytics Server Connector, and all of the properties, including the key field are mapped, a time window event does not work.
|
AM-1289
|
|
Analytics Manager: The Replay progress bar does not update as expected
When a replay event is executed, the on-screen progress bar does not update as the replay event progresses. The issue is related only to the user interface (UI), and the actual execution of the replay is not affected. As a work around, refresh the browser or navigate to another tab and then return to the Replay tab. The progress bar will update. This UI issue will be resolved in a future release.
|
TA-1345
|
|
Analytics Builder: Filtering on list pages does not work as expected
When filtering is applied to a list page with multiple pages (such as the Models list page), the filtered results are not aggregated for display on a single page. Instead, the filtered results remain on their original pages and multiple pages must be clicked through to find all the filtered results.
To improve handling of list page displays, a configurable parameter has been added to set the number of table items that can be displayed per page. A more permanent resolution for the filtering with pagination issue will be provided in a future release.
|
TA-1596
TA-1618
TA-1928
|
|
ThingWorx Analytics Server: Some datasets with a large number of columns fail to upload
There are currently some limitations on the size and number of columns a dataset can contain. These limitations depend on the mix of data types your data includes. For specific information, see the Data section of Prepare Data and Metadata. When trying to upload a dataset with a large number of columns, if the upload fails and an error message is generated, try the following workarounds:
• Where possible, use optimal data types, for example, convert INTEGER data to STRING and use DOUBLE for numeric data.
• Reduce the number of columns.
|
TA-2599
|
|
ThingWorx Analytics Server: When dataset or metadata field names begin with a number, server queries fail
When a field that begins with a number is included in a dataset or in metadata, most Analytics Server jobs can run successfully, such as training a model, running or scoring. However, when a server query is executed, such as a BinnedDistribution, the query fails. As a work around, avoid using field names that begin with a number.
This issue will be resolved in a future release so that field names can begin with numbers.
|
TA-2795
TA-2799
|
|
ThingWorx Analytics Server Installer: Silent mode installation error
The Analytics Server installer should not allow installation of Analytics Extension without Analytics Server. In both graphical and text mode installations, a warning message is displayed when the Analytics Extension component is selected for installation but Analytics Server is deselected. The installer will not continue unless Analytics Server is also selected. However, in the silent install mode, no such warning is displayed and the installer completes successfully with only the Analytics Extension installed. Of course the Extension cannot run without the Analytics Server so it is not usable.
This issue will be resolved in a future release.
|
TA-3231
|
|
ThingWorx Analytics Server: Error occurs when running a signals job with redundancy filtering
When a signals job is launched with the Redundancy Filter option selected, the features returned by the signals job are ranked according to the amount of information gain they provide, rather than by their predictive strength. However, in certain cases, an exception is generated with an error message indicating that some information gain values fall outside of the expected range. This error occurs when the signals job encounters continuous data where the value is near the minimum or the maximum of the expected range.
This issue will be resolved in a future release.
|
TA-4479
|
|
Platform Analytics: Uninstall does not delete the Flink service
In this release, an issue is preventing the Flink service from being deleted when Platform Analytics is uninstalled from a Windows environment. This issue can cause your next installation attempt to fail. The issue will be resolved in a future release. As a work around, reboot the server to clean up the service before reinstalling.
|
TA-4566
|
