AnalyzeStandardCurve

AnalyzeStandardCurve[dataToTransform, standardData]⟹object

fits a standard curve to standardData and applies it to dataToTransform, then stores the result in object.

AnalyzeStandardCurve[protocol]⟹objects

applies standard curve analysis to experimental protocols for which default analysis has been defined.

Details

Input

Output

Curve Fitting Options

Input Data Resolution Options

Standard Data Resolution Options

General Options

Method Options

Examples

Basic Examples (5)

Given a CapillaryELISA protocol as input, run one standard curve analysis per analyte, matching data by analyte type:

Object fields where data is located can be explicitly specified in inputs. Input can be specified as a {Object(s),Field} pair, and standard data can be specified as a {Object(s),{xField,yField}} pair:

Input data can be specified as an object or list of objects. The field to pull data from is determined by the object type:

Both input and standard data can be specified with physical units, and the expression used to fit the standard data can be changed:

Fit a standard curve to a list of {x,y} coordinates, and use the fit to transform input x-values to y-values:

Additional Examples (5)

Input data can be specified using distributions or quantity distributions:

Specify multiple sets of input data, generating a list of predicted values for each input dataset:

Use multiple objects, each containing multiple {x,y} coordinates, as input:

Mix object inputs with numerical coordinate inputs:

Use a combination of transformation functions and standard curve options to construct a logistic standard curve for Capillary ELISA data:

Options (19)

FitType (4)

Explicitly specify the type of expression to fit the standard curve to:

Set the degree of a polynomial fit:

Use a user-defined Function as a fit expression:

The default fitting expression is chosen based on StandardData type:

InputField (1)

Specify what field in input objects data should be downloaded from. The input field option will supersede a field specified using the {object(s),field} input format:

InputTransformationFunction (2)

Apply the same transformation function to each input value:

Apply different transformations to each input value:

InversePrediction (2)

Use inverse prediction to transform y-values to x-values:

Use inverse prediction to transform y-values to x-values using an existing fit:

StandardData (5)

Use an existing AnalyzeFit object as a standard curve:

Use numerical coordinates as standard data:

A single object contains multiple {x,y} datapoints to use as standard data:

List of objects, each containing one standard data point:

Mixed numerical and object input as standard data:

StandardFields (3)

Manually specify which fields to pull from standard data objects. Option values will take precendence over fields in {object(s),{xField,yFiled}} input format:

Use None when only one dimension requires a field specification:

Default standard fields depend on Standard object type:

StandardTransformationFunctions (1)

Use transformation functions to pre-process the standard data:

Template (1)

Use options and curve from an existing Standard Curve analysis:

Messages (26)

AnalyzeFit (1)

If there are failures during curve-fitting with AnalyzeFit, messages will be collected and grouped:

DefaultFieldUndefined (2)

Object(s) provided in StandardData do not have default fields defined, and StandardFields must be specified manually:

If the input data is provided as object(s) and these types do not have default fields defined, InputFields must be specified explicitly:

DefaultFitTypeUndefined (1)

The standard data type is not associated with a default model type, and by default a linear fit will be constructed:

DuplicateStandardData (1)

Provide a warning message if user has specified multiple sets of Standard Data for the same analyte in input protocol:

EmptyStandardField (1)

The object(s) and fields specified in StandardData and StandardFields point to one or more empty fields:

ExistingFitIncompatibleUnits (1)

The Units of the Fit object provided as a standard curve are incompatible with input units:

Extrapolation (1)

Warn the user if input data is outside of the range of provided standard data:

InconsistentObjectTypes (2)

If input data is provided as a list of objects, these objects must have the same type:

If standard data is provided as a list or mixed list of objects, these objects must have the same type:

InconsistentUnitsAll (1)

All input datasets must have compatible units:

InconsistentUnitsEach (1)

All datapoints within a single dataset must have compatible physical units:

InputContainsTemporalLinks (1)

Warn the user if either the input or standard data has been specified as a temporal link:

InputFieldOverride (1)

Warn the user if the InputField option is overriding a field specified by an {obj,field} pair:

InvalidInputDataFormat (1)

Input data must resolve to a list of numerical values, quantities, or distributions:

InvalidProtocolField (1)

Input Protocol objects must have valid, non-empty Data and StandardData fields:

InvalidStandardDataFormat (1)

The standard data specified by StandardData, StandardFields, and StandardTransformationFunctions must be a valid list of coordinates:

InvalidStandardField (1)

The supplied StandardFields are not valid fields of the objects in StandardData:

MissingStandardData (1)

Standard data must be supplied for analysis:

ProtocolAlreadySet (1)

If the input is a Protocol, then the Protocol option will be unused. The hidden option Protocol is used to link standard curve analyses corresponding to the same protocol input, and is redundant in this case:

StandardDataIncompatibleUnits (1)

The independent variable units of standard data must be compatible with input data units:

StandardDataInconsistentUnits (1)

Standard Data must have self-consistent units, i.e. all x- and y-values have the same units, respectively:

StandardFieldOverride (2)

Warn the user if the StandardData option is overriding standard data specified in input:

Warn the user if the StandardFields option is overriding standard fields specified in input:

UnspecifiedUnits (2)

If Standard Curve has unitless independent variables, apply the input units and warn the user:

If input data is unitless, apply the units of the Standard Curve and warn the user: