Spotfire Ideas Portal
ADD A NEW IDEA

Spotfire Statistica

Showing 218 of 4339

Add Customizations to X Charts Control Limits in the SPC Charts with Alarming node

The SPC Charts with Alarming node has customization of line type, size, and color for Target Type but not for X Charts Control Limits, Specification Limits, nor variance warming limits. This makes it difficult to customize graphs so that are easy ...
8 days ago in Spotfire Statistica 0 To be Reviewed

Output models created by Multiple Regression and PLS nodes as PMML nodes

Machine learning nodes, such as Random Forest and Boosted Tree, automatically output models as PMML nodes. This allows models to be rerun automatically by simply updating the data, which is highly convenient for integration with Spotfire. However,...
8 days ago in Spotfire Statistica 0 Future Consideration

Stepwise Multiple Regression Node Abolishes Limit of 500 Explanatory Variables

The Stepwise Multiple Regression Node encounters an error when more than 500 predictor variables are included. I would like to use it with more than 500 predictors to perform stepwise regression and compare the results with those from Lasso regres...
8 days ago in Spotfire Statistica 0 To be Reviewed

Fit Distribution should include Anderson-Darling test without assumed parameters

Add the Anderson-Darling (AD) test without assumed parameters into the Fit Distribution module and/or workspace node. This way we could use the AD statistics to quickly rank and decide the best distribution to use for our regular reports. As it st...
7 months ago in Spotfire Statistica 0 Likely to implement

Enhance / split "Runs rules" options in SPC node

For the automated monitoring of manufacturing yield a single sided "Runs rules" on decreasing n in a row AND continous number of samples n below target line is needed. Currently the only option we have in Statistica is this functionality for doubl...
almost 3 years ago in Spotfire Statistica 0 Future Consideration

"NIPALS Algorithm Deployment" node to calculate the predicted value of Y by PLS

"NIPALS Algorithm Deployment" node only calculates X predictions when PMML is applied to test data in the reporting document. We would like to see the predicted value of Y calculated as well. Also, hopefully, the PMML and NIPALS Algorithm Deployme...
21 days ago in Spotfire Statistica 0 Future Consideration

Add the ability to change the x-axis for Control Charts in WebStatistica

WebStatistica does not allow us to assign a different parameter to the x-axis on SPC charts. Typically users would want to see something like a lot number on the x-axis or even a date so that they would be able to look at the chart and know what t...
30 days ago in Spotfire Statistica 0 Future Consideration

Handling invariant variables in TMPCA module

The TMPCA module is unstacking the multivariate process data used in MSPC analysis by time step. This can result in invariant variables being generated for certain time steps (e.g. if the value of one variable is the same for all batches at a time...
over 4 years ago in Spotfire Statistica 0 Future Consideration

Web Data Entry: Seperate rights to create Data Entry Setup and entering/approving data

At the moment, a Data Entry Admin (EDE Permission) is able to enter, delete data and edit already approved data (HEDIT). Customers want to be able to separate these two areas. Therefore, it would be needed to remove the hidden rights (DE, HEDIT) f...
almost 3 years ago in Spotfire Statistica 2 Already exists

Web Data Entry: Allow entering revisions based on role and not for a specific user

At the moment, if an entered sample needs revision and is set to status "Requires Revision" by an Approver/Admin, only the initial data enterer is able to enter the change. This person might not be available in a reasonable time frame, leaving the...
almost 3 years ago in Spotfire Statistica 1 Needs Info
This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out. Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved. Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement. Terms of Use | Privacy Policy | Trademarks | Patents | Contact Us