.. |MLA (TM)| unicode:: MLA U+2122 .. index: Data Tree .. _data-tree-label: Data Tree ========= The ``Data Tree`` panel is available from the ``Advanced`` pull-down menu. The panel can be docked in either the scanning view or the analysis view, or both. This panel lists scans which are open in the analysis panel as well as the current scan. Under each scan there is a list of all the pixels which have been selected with the :ref:`pixel-inspector-label`. The color of the text for each pixel corresponds to the color of the cross marking the pixel in the image. Under each pixel there is a list of the different force reconstructions done on that pixel. **Right click on a scan file name** and select: * ``Open shell here...`` to open a Python shell with an object called ``image`` containing all the data stored in this scan file. The data id of the scan used by the data tree is given, along with a couple of useful commands. The shell is for advanced users who will need the developer documentation to use this feature effectively. * ``Show meta data`` to open a box to view the calibration data stored with this scan file (i.e. the :ref:`current-calibration-label` at the time that the data file was closed) as well as a time and frequency domain plot of the ``Free`` and ``Lfited`` motion. .. image:: figures/data_tree.png :width: 10cm :align: center * ``Save as ascii...`` to open a dialog box where you can save all amplitude and phase data in ASCII format. The save will create individual files in a new, empty folder. There will be one file for both amplitude and phase at each of the measured frequencies, both trace and retrace. For example, when 32 frequencies are measured, 128 data files will be created. If the image is 256 x 256 pixels, this corresponds to about 140Mbytes of data in tab-delimited text, with a carriage return at the end of each scan line. The name of each file begins with a number which codes for the frequency. The number corresponds to the index of the 'k-array' which stores the integers multiples of :math:`\Delta f` which give the frequency values where amplitude and phase is measured (see :ref:`intermodulation-measurement-label`). In the folder there is also a file called *metadata.txt* which contains a list of integers in the array *LO_IMP_KARRAY*. The number at the beginning of each file corresponds to the index of this array (zero being the first element). The integer values stored in this array, times *LO_DELTA_F*, gives the frequency at which the amplitude and phase is measured. * ``Save as imp...`` to open a dialog box where you can resave the entire scan file with all meta data to a new .imp file. This is usefull when you make changes to the scan data, for example if you redefine the lift oscillation (see below). **Right click on a pixel or patch** and select: * ``Open shell here...`` to open a Python shell with an object called ``pixel`` containing the data relevant to this pixel. The data id used by the data tree is given, along with a couple of useful commands. The shell is for advanced users who will need the developer documentation to use this feature effectively. * ``Delete`` removes the pixel from the data tree. The cross will also be removed from the image, and the plots from the Fore Inspector panel. You can also remove any pixel by right-clicking close to that pixel in the image when the :ref:`pixel-inspector-label` is selected. * ``Save time data to text file`` to export the cantilever deflection vs. time during the time window for this pixel. This data is is actually the inverse FFT of the spectral data taken by the |MLA (TM)|, with some zero padding to give appropriate sampling in the time domain. * ``Save spectrum data to text file`` to export create the raw spectral data measured by the |MLA (TM)| at this pixel. * ``Save FI FQ data to text file`` to export the FI(A) and FQ(A) data for this pixel (see :ref:`fifq-label`). * ``Redefine as lift oscillation`` is very usefull if you have a file with a pixel, or group of pixels (patch) selected with the :ref:`area-inspector-label`, where the cantelever has lost contact with the surface. This 'parachuting' pixel or patch can be used to redefine the just-lift oscillation in the .imp file (see :ref:`measure-lift-label`). Note that the redefinition is only valid in the loaded scan data. It is not saved to disk unless you actively save a new version of the .imp file. The check-boxes at each pixel and each force reconstruction controls plotting. Un-check to remove the cross from the image or plot from the Force Inspector panel, without actually removing the data from the data tree. Checking the box will show the plots again. Pixels selected in the current scan will not be removed when a new scan is generated. When the scan moves passed a selected pixel, the image no longer corresponds to the selected pixel. Selected pixels must be removed manually in the current scan. ``Clear All`` in the ``Force Inspector`` panel removes all selected pixels in all scans. **Right click on a force reconstruction** and select: * ``Open shell here...`` to open a python shell with an object called ``force`` containing the result of the force reconstruction at this pixel. The data id used by the data tree is given, along with a couple of useful commands. The shell is for advanced users who will need the developer documentation to use this feature effectively. * ``Get fitted parameters`` to open a dialog box showing the fitted parameters when the :ref:`model-fit-label` method is used. * ``Save Data to text file`` to export the force curve found using that reconstruction method.