What are strengths and weaknesses of the sap.m.Shell and sap.m.App as container for an application wrapper?

Question

My question today: What are strengths and weaknesses of the
sap.m.Shell
and
sap.m.App
as container for an application wrapper?
I currently use non of them, but I see the advantages.
SAP best practise is to use one of them or nest them as shell > app. What are strengths and weaknesses of the approaches?

Answer 1

We prefer to say, the tender mercies of the Fetch block.
You'll notice the "wfm info" cluster as an output of the Fetch
VI.  This cluster has gain and offset members- use these to scale
your binary data to floating point voltage representation.
As you point out, the numbers won't be exactly what you expect given
the vertical range and the device resolution.  There are a few
reasons for this.  First, we don't use the absolute full scale of
the ADC for the maximum input voltage.  There are a couple of
codes of headroom at the top and bottom.  This allows your input
signal to slightly exceed the specified vertical range without clipping
(you'll get a warning from the driver).  Second, these gain and
offset numbers take into account calibration information for your
device.  Using these numbers will correct for small deviations
from the ideal offset and gain.
So if you use the gain and offset numbers from the driver, your
measurements will be more accurate than if you assume 0 offset and
perfect gain.  They will be most accurate if you make sure to
perform a self-calibration once the device is in your system and at the
temperature that your tests will be run.