TileHeatmap.m

Go to the documentation of this file.

%>  \brief
%>  This is the [pm.vis.TileHeatmap](@ref TileHeatmap) class for generating
%>  instances of 2-dimensional Heatmap [Tile visualizations](@ref Tile)
%>  based on the relevant MATLAB intrinsic functions.<br>
%>
%>  \see
%>  [pm.vis.Cascade](@ref Cascade)<br>
%>  [pm.vis.Subplot](@ref Subplot)<br>
%>  [pm.vis.Triplex](@ref Triplex)<br>
%>  [pm.vis.Figure](@ref Figure)<br>
%>  [pm.vis.Plot](@ref Plot)<br>
%>  [pm.vis.Tile](@ref Tile)<br>
%>
%>  \final
%>
%>  \author
%>  \FatemehBagheri, May 20 2024, 1:25 PM, NASA Goddard Space Flight Center (GSFC), Washington, D.C.<br>
%>  \AmirShahmoradi, May 16 2016, 9:03 AM, Oden Institute for Computational Engineering and Sciences (ICES), UT Austin<br>
classdef TileHeatmap < pm.vis.Tile
 
    methods(Access = public)
 
        %>  \brief
        %>  Construct and return an object of class [pm.vis.TileHeatmap](@ref TileHeatmap).<br>
        %>
        %>  \details
        %>  This is the constructor of the class [pm.vis.TileHeatmap](@ref TileHeatmap).<br>
        %>
        %>  \param[in]  dfref       :   See the documentation of the corresponding input
        %>                              argument of the class [pm.vis.Subplot](@ref Subplot).<br>
        %>  
        %>  \param[in]  varargin    :
        %>  
        %>                              Any ``property, value`` pair of the parent object.<br>
        %>                              If the property is a ``struct()``, then its value must be given as a cell array,
        %>                              with consecutive elements representing the struct ``property-name, property-value`` pairs.<br>
        %>                              Note that all of these property-value pairs can be also directly set via the
        %>                              parent object attributes, before calling the ``make()`` method.<br>
        %>
        %>  \return
        %>  ``self``                :   An object of [pm.vis.TileHeatmap](@ref TileHeatmap) class.<br>
        %>
        %>  \interface{TileHeatmap}
        %>  \code{.m}
        %>
        %>      t = pm.vis.TileHeatmap(dfref);
        %>      t = pm.vis.TileHeatmap(dfref, varargin);
        %>
        %>  \endcode
        %>
        %>  \note
        %>  The input ``varargin`` can also contain the components
        %>  of the ``subplot`` component of the parent object.<br>
        %>
        %>  \note
        %>  See the documentation of the attributes
        %>  of the superclass [pm.vis.Tile](@ref Tile).<br>
        %>
        %>  \final{TileHeatmap}
        %>
        %>  \author
        %>  \JoshuaOsborne, May 22 2024, 7:21 PM, University of Texas at Arlington<br>
        %>  \FatemehBagheri, May 20 2024, 1:25 PM, NASA Goddard Space Flight Center (GSFC), Washington, D.C.<br>
        %>  \AmirShahmoradi, May 16 2016, 9:03 AM, Oden Institute for Computational Engineering and Sciences (ICES), UT Austin<br>
        function self = TileHeatmap(dfref, varargin)
            if nargin < 1
                dfref = [];
            end
            self = self@pm.vis.Tile(pm.vis.SubplotHeatmap(dfref), varargin{:});
        end
 
    end
 
end