Spotfire Ideas Portal
ADD A NEW IDEA

Spotfire Statistica

    Showing 162

    Change LiveScore to RESTful API

    I've had a number of customers recently who have requested that LiveScore made into a RESTful service. SOAP is seen as antiquated and not at all friendly - especially since we're looking at integrating Statistica with other TIBCO products like Spo...
    about 8 years ago in Spotfire Statistica 0 Future Consideration

    Enhance Workspace Annotations

    In Statistica workspaces, typically, we are using some set of nodes to achieve concrete goal. Annotations and arranging nodes are good way to make workspace more clear and readable. What about placing annotations to the canvas behind the nodes wit...
    over 7 years ago in Spotfire Statistica 2 Future Consideration

    Support different versions of Python, R in the same environment

    An organization may have projects using different versions of Python, R. Supporting different versions of Python and R in the same environment helps with upgrade planning. Version 1 is "production use" and Version 2 is "testing upgrade". This alle...
    almost 8 years ago in Spotfire Statistica 2 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...
    about 1 year ago in Spotfire Statistica 0 Future Consideration

    Workspace - Add ability to set case names from variable

    Interactive Statistica has ability to assign case names based on a spreadsheet variable. This functionality would also be useful out-of-the-box in the workspace, either as part of another data management node or its own simple data management node...
    about 2 years ago in Spotfire Statistica 0 Future Consideration

    Include more details behind the "Missing Monitor ID" error in WebStatistica

    When certain reports/analyses fail in WebStatistica, a "Missing Monitor ID" error is returned. However, this error message is so generic that it does not help understand why the report/analysis failed. Could this error be expanded upon so it's mor...
    almost 3 years ago in Spotfire Statistica 0 Future Consideration

    Connect to TERR Engine for R Scripting

    TERR is a highly efficient R run-time engine for R scripting and ideal for R deployment. Many customers have R programmers and want to use the Statistica framework for deploying, managing and governing R scripts. Currently, the R scripting will on...
    over 7 years ago in Spotfire Statistica 2 Future Consideration

    Web Data Entry: Add option to set default number of pieces

    Customers would like to create a default number of samples, but still retain the ability to add extra rows if needed. Perhaps you could create a data entry parameter that could add or remove pieces, but also had a default number of pieces greater ...
    almost 2 years ago in Spotfire Statistica 0 Future Consideration

    Missing data code may result in incorrect analysis

    Statistica uses a potentially error prone approach for representing missing values. “-999999998” is the default missing value for doubles. If you enter that numeric value into a cell, it becomes a missing value and will not be analyzed correctly. ...
    about 8 years ago in Spotfire Statistica 0 Future Consideration

    Advanced options for display format of characteristics in data entry

    Calculated values in data entry will show up with a lot of decimals. It would be great to have advanced options to reduce the display format of characteristics.
    over 6 years ago in Spotfire Statistica 0 Future Consideration
    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