Formazan recovery identifiability

ID: formazan-recovery-identifiability

Formazan recovery identifiability asks whether measurements distinguish the amount of formazan formed from the fraction recovered in the optical reading. Better repeatability does not necessarily separate those quantities.
Let be total product formed, the dissolved formazan recovery fraction, and a known optical conversion factor in a suitable fixed-path solution model. Then net absorbance is
The manufacturer's procedure separates formation of crystals, dissolution and measurement, motivating these distinct model quantities.[ref] Knowing and determines the dissolved amount , but not the two parameters separately.
For any admissible scale , replacing by leaves unchanged, provided . For observed , both and fit. In this conserved-product model the bound implies , with no finite upper bound supplied by that measurement alone. This is an identifiability limitation, rather than merely a large measurement uncertainty.
Changing volumes or optical paths can provide several known factors , but measurements still determine only the same product if and stay fixed. Such changes can test the optical law without resolving the underlying ambiguity.
An original matched-addition model illustrates what extra information could help. Suppose a known amount is added before the recovery step and experiences exactly the same unknown fraction as the native product. Converting both readings to dissolved amounts gives
If and adding increases the dissolved amount by , the model gives and . Adding already dissolved product after the recovery step would instead test later optical response and would not identify earlier losses.
The shared-recovery assumption must be justified: a dissolved spike can behave differently from product crystals formed inside a preparation. A second measurement helps only if its relation to the unknown quantities is independently established. Repeated measurement of the same product cannot supply that missing relation.

New to topics? Read the docs here!