New Functionality
|
Analytics Manager: Flexible Scaling
Use the in-built flexible scaling capability in Analytics Manager to request for addition or reduction in resources while performing computations.
|
Analytics Manager: ThingPredictor
The ThingPredictor agent handles predictive scoring for models in Analytics Manager. It attempts to make predictions about a given outcome (goal variable) in the data being processed.
|
Analytics Manager: Analysis Replay
Use the analysis replay functionality to replay analysis instances executed in the past in response to a configured analysis event. You can also export a history of inputs and result to a .xml file.
|
Enhancements
|
Reference #
|
Analytics Builder: Publish a predictive model for use in Analytics Manager.
On the Models list tab, a new Publish option has been added. The new option allows a completed model to be published to Analytics Manager where it can be used as an analysis model.
|
LYNX-347
|
Bug Fixes
|
Reference #
|
Analytics Extension: Console tiles do not display in Google Chrome
When the Analytics Extension Console is launched using Google Chrome, version 56.0.2924.87 (64–bit), no tiles displayed. To resolve this issue, a fix was made to the TW.Analytics.ConsoleMashup. Console tiles now display immediately at launch.
|
LYNX-354
|
Analytics Builder: Retraining does not capture all parameters from the original model
In Analytics Builder, when a model is retrained, the parameters listed below were not carried over into the newly generated model. This issue has been resolved.
• Comparison Metric
• Iterative Sample Size
• Iterative Improvement % Threshold
• Exclusion List
|
LYNX-345
|
Analytics Builder: Error occurs on loading data with non-ASCII characters
When loading data via the Analytics Builder, an error is generated if the dataset headers (CSV files) or metadata (JSON files) include non-ASCII characters. These characters can include Asian languages as well as any language that includes accented characters. The error occurs because the Configure Dataset service validates for alphanumeric characters in uploaded datasets and metadata.
To resolve the issue, the limitation for alphanumeric characters has been removed in both the Analytics Builder code and the ThingWorx Analytics Extension code. This change allows for all UTF-8 compliant field names.
|
LYNX-341
NRN-6603
|
Analytics Builder: Bound values for Min Population % differ from ThingWorx Analytics
For the Min Population Percentage field on the Profiles page of Analytics Builder, the acceptable values have been updated to match the value bounds for the same field in ThingWorx Analytics. In Analytics Builder, the value must be greater than 0% but less than 100% (default is 0.25%).
|
LYNX-340
NRN-6550
|
Analytics Builder: Add ROC as a Comparison Metric option for Boolean data types only
In addition to Pearsons and RMSE as Comparison Metric options, a third option has been added for selection during predictive model generation. The new option, ROC, can be selected only when the data type of the goal variable is Boolean.
|
LYNX-338
|
Analytics Builder: JavaException error when scoring
An error occurs during scoring in Analytics Builder when the goal variable contains null values. Code has been added to return an empty object instead of generating an error.
|
LYNX-337
|
Analytics Builder: Significant digits in Signals
In Signals, calculations of the Avg. Goal and Diff vs. Avg for each feature are rounded to four digits. However, the overall dataset Avg. Value for Goal, shown in the header of the Signals tab, was displayed with only two digits. To reduce confusion when calculating the Diff vs. Avg parameter, Avg. Value for Goal has been updated to display four digits. Now, Diff vs. Avg will really equal Avg. Value for Goal - Avg. Goal.
|
LYNX-329
NRN-6489
|
Analytics Builder: Show feature Descriptions in Exclusion List
When viewing the Exclusion List for a model in Analytics Builder, the feature Description will be displayed instead of the feature Name. However, if the Description field is empty, the feature Name will be displayed.
|
LYNX-294
|
Analytics Builder: Remove milliseconds from Job Details
Milliseconds have been removed from the parameters listed below on the Job Details pages for both Model jobs and Predictive Scoring jobs:
• Queued Start Time
• Queued Duration
• Start Time
• End Time
• Run Time
• Last Modified
|
LYNX-276
|
Known Issues
|
Reference #
|
Analytics Manager: Invalid Predictive Model File for ThingPredictor
If an invalid model is uploaded and deployed to the ThingPredictor agent, the deployment times out and the following error message is returned:
Model deployment failed on connector Exhausted the specified waiting time for model deploy, aborting... :<model_name>
In such a case, check if your model file is valid. This will be fixed in a later release.
|
DT-9535
|
Analytics Manager: Failure to deploy model by downloading file from a network URL for ThingPredictor
While creating an analysis model for ThingPredictor, if you specify a network location in the Model File URL field, ThingPredictor can not download the file and deploy the model.
|
DT-8891
|
Analytics Manager: Clicking Refresh Now under the Inputs to Analysis section displays a red error icon while creating an analysis replay After you select an analysis event to be replayed, if you want to see the replay inputs at a specific timestamp, select the start time from Replay Duration and click Update Data, the inputs are displayed under the Inputs to Analysis section. However, if you click Refresh Now, a red error icon is displayed in the section where the inputs are to be displayed. This does not affect the replay functionality, and the replay is executed once you start the replay. |
DT-9616
|
Analytics Manager: Exceptions in server logs while running an analysis replay
If there is no agent running to process the replay jobs for an analysis event, in this case if a replay is started from the Analysis Replay page, exceptions are seen in the server logs.
|
DT-9782
|
Analytics Manager: Deployment job status for docker deployer agent is shown as incorrect
When deployer agent deploys an agent on a machine, the corresponding job status is shown to be in the INPROCESS state. However, the deployment is completed.
|
DT-9912
|
DataConnect: No meaningful error message generated when neuron.base.url set incorrectly
If the neuron.base.url is not set to http://server:8080/1.0, an “Unexpected Error” is returned in the API response when a Transform and Create Dataset request is submitted. An exception is also reported in the Tomcat catalina.out file. However, the current error messaging does not specify that the problem is caused by an incorrect neuron.base.url setting. A more meaningful message will be provided in a future release.
For more information, see the following support article: https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS257176.
|
NRN-6645
|