Using ClearPointSlopeThreshold to define the endpoint of the melting process. It is for Object[Data, MeltingPoint] only:

Fit the data to a sigmoid and then calculate the melting point from the fitted sigmoid expression:

Smooth the data with a Gaussian filter before calculating the melting point:

Select the dataset to Analyze:

Select the dataset to Analyze using Field[] which works with nested fields as well:

Custom transformation function to manipulate the thermal response of a dataset:

Exclude from analysis any points outside the specified temperature domain:

If units are not specified, Domain is assumed to be in Celsius:

Specify MeltingOnset to calculate the onset of melting temperature for AggregationCurveOnsetTemperature:

Specify the melting onset of melting and aggregation curves:

Specify a certain percentage of deviation from the initial flat region to indicate the melting onset (intensity rise):

Using MeniscusPointThreshold to define the middle of the melting process. It is for Object[Data, MeltingPoint] only:

For InflectionPoint method, the melting point is defined as the inflection point of the alpha curve, which is the temperature at which the second derivative of the curve is zero:

For MidPoint method, the melting point is defined as the temperature corresponding to the halfway point between the top and bottom baseline:

Return only the melting temperature:

Return the melting temperatures from both the melting curve and cooling curve :

Only plot the Derivative curve:

Exclude from analysis any points outside the specified measurand (in this case, absorbance) range:

If units are not specified, Range is assumed to be in ArbitraryUnit:

A set of objects, each containing a melting datapoint with the response stored at ResponseDataSet:

A set of objects, each containing a melting datapoint with the response stored at ResponseDataSet using Field[] which is intended for nested fields:

Using ResponseTransformationFunction to adjust the thermal response data stored in ResponseDataSet:

Increase data smoothing before analysis:

Using StartPointThreshold to define the beginning of the melting process. It is for Object[Data, MeltingPoint] only:

A set of objects, each containing a melting datapoint with the temperature stored at TemperatureDataSet:

A set of objects, each containing a melting datapoint with the temperature stored at TemperatureDataSet using Field[] which is intended for nested fields:

Using TemperatureTransformationFunction to adjust the temperature data stored in TemperatureDataSet:

Explicitly specify Domain option, and pull remaining options from previous melting point analysis:

Use options from previous melting point analysis:

Return the entire packet:

Specify Automatic option for 3D melting/cooling data objects:

Specify a wavelength range (in Nanometers) for 3D melting/cooling data objects:

Specify a wavelength range (in Nanometers) for a 3D melting curve for thermalshift protocol:

Specify a wavelength range (in Nanometers) for a 3D protocol:

Specify a wavelength range (in Nanometers) for a 3D thermal shift dataset:

Specify one wavelength (in Nanometers) for 3D melting/cooling data objects:

All of the specified wavelengths are not within the wavelength range of the acquired data:

Returns $Failed if the data set does not exist:

Returns $Failed if the data set does not exist:

If the temperature resolution in the melting curve is poor (few data points) and DataProcessing->Fit, this results in fit issue and a warning is thrown:

ThreeD to TwoD transformation can't be used for a 2D dataset, and it will be set to None:

For Object[Protocol, DynamicLightScattering], if the AssayType field is not MeltingCurve, an error is thrown:

Return Null if input does not contain any suitable data for MeltingPoint analysis:

Returns $Failed if the data set does not have an acceptable melting curve pattern with temperature as the x-axis:

Returns $Failed if the ResponseDataSet is not a valid field name:

Returns $Failed if the ResponseDataSet is not a valid field name using Field[]:

Returns $Failed if the TemperatureDataSet is not a valid field name:

Returns $Failed if the TemperatureDataSet is not a valid field name using Field[]:

The temperature and response dataset should be valid fields within the object set:

Returns $Failed if the transformed data set does not have an acceptable melting curve pattern with temperature as the x-axis:

After transformation of the response, the correct units of response should be preserved:

After transformation the correct units of response should be preserved:

After transformation of the temperature, the correct units of temperature should be preserved:

Shape of the data curve is not as expected, which can lead to bad results:

Melting point falls out of the input data domain:

Domain option excludes all data points:

If the data object does not contain melting curve data, an error is thrown:

Returns $Failed if DataSetTransformationFunctions length does not match that of DataSet:

Protocol does not contain any data packets:

For Object[Data, qPCR], if the MeltingCurves field does not contain melting curve data, an error is thrown:

Object does not contain 3D curves, currently only Object[Protocol, UVMelting] and Object[Data, MeltingCurve] have 3D melting curves:

Returns $Failed if the object does not exist:

Some of the specified wavelengths are not within the wavelength range of the acquired data:

Possible issue in finding melting onset due to using NonlinearModelFit, Interpolation, or FindRoot. Most of the time due to the assumption that the curve has a sigmoid-like shape:

If temperature and response dataset are valid fields, DataSet is set to Null and warning is thrown if it is set as the option:

If temperature and response dataset are valid fields, DataSetTransformationFunction is set to Null and warning is thrown if it is set as the option:

If temperature and response dataset are set to Null, TemperatureTransformationFunction will be unused: