29.04.2013 Views

TESI DOCTORAL - La Salle

TESI DOCTORAL - La Salle

TESI DOCTORAL - La Salle

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.3. Deterministic hierarchical consensus architectures<br />

f! = 3! = 6, which are identified by an acronym describing the order in which diversity<br />

factors are assigned to stages —for instance, ADR describes the DHCA variant<br />

defined by the ordered list O = {df1 = dfA,df2 = dfD,df3 = dfR}. For a given data<br />

collection, the cardinalities of the representational and dimensional diversity factors<br />

(|dfR| and |dfD|, respectively) are constant, while the cardinality of the algorithmic<br />

diversity factor takes four distinct values |dfA| = {1, 10, 19, 28}, giving rise to the four<br />

diversity scenarios where our proposals are analyzed. Moreover, consensus clustering<br />

has been conducted by means of the seven consensus functions for hard cluster<br />

ensembles described in appendix A.5, which allows evaluating the behaviour of our<br />

proposals under distinct consensus paradigms. In all cases, the real running times<br />

correspond to an average of 10 independent runs of the whole RHCA, in order to<br />

obtain representative real running time values. As described in appendix A.6, all the<br />

experiments have been executed under Matlab 7.0.4 on Pentium 4 3GHz/1 GB RAM<br />

computers.<br />

– How are results presented? Both the real and estimated running times of the<br />

serial and parallel implementations of the DHCA variants are depicted by means of<br />

curves representing their average values.<br />

– Which data sets are employed? For brevity reasons, this section only describes<br />

the results of the experiments conducted on the Zoo data collection. On this data<br />

set, the cardinalities of the representational and dimensional diversity factors are<br />

|dfR| = 5 and |dfD| = 14, respectively. The presentation of the results of these<br />

same experiments on the Iris, Wine, Glass, Ionosphere, WDBC, Balance and MFeat<br />

unimodal data collections is deferred to appendix C.3.<br />

Diversity scenario |df A| =1<br />

Figure 3.10 presents the estimated and real running times of the serial and parallel DHCA<br />

implementations in the lowest diversity scenario corresponding to the use of |dfA| = 1<br />

randomly chosen clustering algorithm for creating a cluster ensemble of size l = 57. The<br />

DHCA variants are identified in the horizontal axis of each chart. Meanwhile, the values<br />

of SERTDHCA and PERTDHCA correspond to an arbitrarily chosen estimation experiment<br />

based on a single consensus run (i.e. c =1).<br />

On one hand, figures 3.10(a) and 3.10(b) present the estimated and real running times<br />

of the serial DHCA implementation (SERTDHCA and SRTDHCA). Notice that SERTDHCA<br />

is a fairly good estimator of the real execution time of the DHCA variants. Moreover, it<br />

successfully predicts the fastest consensus architecture —which is what we are ultimately<br />

interested in. Notice that DRA is the DHCA variant minimizing SRTDHCA, which corresponds<br />

to the decreasing ordering of the diversity factors in terms of their cardinality.<br />

On the other hand, figures 3.10(c) and 3.10(d) depict the estimated and real running<br />

times corresponding to the fully parallel implementation of DHCA (PERTDHCA and<br />

PRTDHCA, respectively). There are two issues worth noting in this case: firstly, notice that<br />

the real execution time of the distinct DHCA variants shows a notably lower dispersion than<br />

in the serial case, which somehow corroborates our conjecture regarding the unimportance<br />

of the diversity factors ordering in parallel DHCA variants. And secondly, it is clear that<br />

PERTDHCA does not perform as accurately as regards the determination of the fastest con-<br />

76

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!