Changeset 3926


Ignore:
Timestamp:
Nov 7, 2007, 2:41:54 PM (16 years ago)
Author:
Nicklas Nordborg
Message:

References #746: Transfer existing UML diagrams to latest MagicDraw?

  • Added images for Array LIMS sections
  • Added text to hybridizations and raw data section
Location:
trunk/doc/src
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/src/docbook/developerdoc/api_overview.xml

    r3918 r3926  
    18071807    <sect2 id="data_api.plates">
    18081808      <title>Array LIMS - plates</title>
     1809
     1810      <sect3 id="data_api.plates.uml">
     1811        <title>UML diagram</title>
     1812       
     1813        <figure id="data_api.figures.plates">
     1814          <title>Array LIMS - plates</title>
     1815          <screenshot>
     1816            <mediaobject>
     1817              <imageobject>
     1818                <imagedata
     1819                  fileref="figures/uml/datalayer.plates.png" format="PNG" />
     1820              </imageobject>
     1821            </mediaobject>
     1822          </screenshot>
     1823        </figure>
     1824      </sect3>
     1825
    18091826    </sect2>
    18101827
    18111828    <sect2 id="data_api.arrays">
    18121829      <title>Array LIMS - arrays</title>
     1830     
     1831      <sect3 id="data_api.arrays.uml">
     1832        <title>UML diagram</title>
     1833       
     1834        <figure id="data_api.figures.arrays">
     1835          <title>Array LIMS - arrays</title>
     1836          <screenshot>
     1837            <mediaobject>
     1838              <imageobject>
     1839                <imagedata
     1840                  fileref="figures/uml/datalayer.arrays.png" format="PNG" />
     1841              </imageobject>
     1842            </mediaobject>
     1843          </screenshot>
     1844        </figure>
     1845      </sect3>
     1846     
     1847     
    18131848    </sect2>
    18141849
     
    18321867      </sect3>
    18331868     
     1869      <sect3 id="data_api.rawdata.hybridizations">
     1870        <title>Hybridizations</title>
     1871       
     1872        <para>
     1873        Hybridizations connects the slides from the Array LIMS part
     1874        with labeled extracts from the biomaterials part. The <property>creationEvent</property>
     1875        is used to register which labeled extracts that were used on the hybridization.
     1876        The relation to slides is a one-to-one relation. A slide can only be used on
     1877        a single hybridization and a hybridization can only use a single slide. The relation
     1878        is optional from both sides.
     1879        </para>
     1880
     1881        <para>
     1882        The scanning of the hybridized slide is registered as separate scan events.
     1883        One or more images can optionally be attached to each scan.
     1884        The images are not used by BASE.
     1885        </para>
     1886       
     1887      </sect3>
     1888     
     1889      <sect3 id="data_api.rawdata.description">
     1890        <title>Raw data</title>
     1891       
     1892        <para>
     1893        A <classname>RawBioAssayData</classname> object represents
     1894        the raw data that is produced by analysing the image(s) from a
     1895        single scan. You may register which software that was used, the
     1896        protocol and any parameters (through the annotation system).
     1897        </para>
     1898
     1899        <para>
     1900        Files with the analysed data values can be attached to the
     1901        associated <classname>FileSetData</classname> object. The platform
     1902        and, optionally, the variant has information about the file types
     1903        that can be used for that platform. If the platform file types support
     1904        metadata extraction, headers, the number of spots, and other
     1905        information may be automatically extracted from the raw data file(s).
     1906        </para>
     1907       
     1908        <para>
     1909        If the platform support it, raw data can also be imported into the database.
     1910        This is handled by batchers and <classname>RawData</classname> objects.
     1911        Which table to store the data in depends on the <classname>rawDataType</classname>
     1912        property. The properties shown for the <classname>RawData</classname> class
     1913        in the diagram are the mandatory properties. Each raw data type defines additional
     1914        properties that are specific to that raw data type.
     1915        </para>
     1916       
     1917      </sect3>
     1918     
     1919      <sect3 id="data_api.rawdata.spotimages">
     1920        <title>Spot images</title>
     1921       
     1922        <para>
     1923        Spot images can be created if you have the original image
     1924        files. BASE can use 1-3 images as sources for the red, green
     1925        and blue channel respectively. The creation of spotimages requires
     1926        that x and y coordinates are given for each raw data spot. The scaling
     1927        and offset values are used to convert the coordinates to pixel
     1928        coordinates. With this information BASE is able to cut out a square
     1929        from the source images that, theoretically, contains a specific spot and
     1930        nothing else. The spot images are gamma-corrected independently and then
     1931        put together into PNG images that are stored in a zip file.
     1932        </para>
     1933      </sect3>
    18341934     
    18351935    </sect2>
Note: See TracChangeset for help on using the changeset viewer.