Search Results for "using"

SWire is a software interface enabling us to query Stata for the executing of basic operations like reading or writing data. The core of SWire is a Java plugin which functions as a server and it can be queried by using the HTTP protocol. SWire is in essence a wrapper around the Stata-Java API and all the functions relating to this API can, therefore, be externally called by clients. SWire can be interrogated on a local network and it accepts AJAX queries, thus enabling the development of web applications which provide the user with graphical user interfaces. ...

...The framework can easily be extended to other model types, e.g. growth/no-growth boundary models. PMM-Lab has been initiated and provided by the Federal Institute for Risk Assessment - BfR (Berlin, Germany). The software is in Beta status. Before using the software you have to read and accept the license and disclaimer (https://sourceforge.net/p/pmmlab/wiki/Disclaimer/). If you do not agree, do not use this software.

Math Simulator is a java-based application which simulates various mathematical techniques.It is extremely useful for the Engineering students and for professionals. Most importantly, unlike most others Math Simulator is an Application rather than a java - library. So, user is not required to have any computer background. A Unique feature of Math Simulator is that it allows you to save queries for later reference. Hence you can save the problems along with their results.

FastPval is multiple stage p-value computing software that computes empirical p-values from a large set of permutated/resampled background data.

Statastizard(c)2012 Nick Emblow is a program designed to guide its user into the right statistical test, perform the test, and report the results in a meaningful way. The idea of this is that the user won't actually need to know that they are using a mann-whitney U over a t-test, for example - it just tests for normality and homoscedastic of variance, and decides which test to use, then reports the results. Why? Because time after time, people come to me with some test that they've done that they think "proves" something - when in reality they've either not done a comparative test to start with (ex. a correlation), failed to test for confounding factors (such as normality etc) and as a result, failed to appropriately identify even the right test to do.