-------- Original Message --------
Subject:        Re: Modularity: Evaluate hypothesis in MorphoJ
Date:   Tue, 7 Feb 2012 18:00:37 -0500
From:   Emma Sherratt <[email protected]>
To:     [email protected]



Dear Helmi,

In short, the issue is that you are trying to "enumerate all possible
partitions", which for 49 landmarks is very, very high. Try just
enumerating 1,000 and then 10,000.

Hope that helps,

Emma

****                       __
     (\   .-.   .-.   /_")
      \\_//^\\_//^\\_//
       `"`   `"`   `"`****

Emma Sherratt, PhD.
Post-Doctoral Fellow in Organismic and Evolutionary Biology
and Museum of Comparative Zoology
Harvard University
26 Oxford St.
Cambridge, MA 02138
[email protected] <mailto:[email protected]>

http://sites.google.com/site/esherratt/




On 7 February 2012 16:57, morphmet <[email protected]
<mailto:[email protected]>> wrote:



    -------- Original Message --------
    Subject:        Modularity: Evaluate hypothesis in MorphoJ
    Date:   Fri, 3 Feb 2012 05:28:08 -0500
    From:   hmi hmi <[email protected] <mailto:[email protected]>>
    To:     morphomet morphometrics.org <http://morphometrics.org>
    <[email protected] <mailto:[email protected]>>



    Dear Morphometricans,

    I am trying the modularity: evaluate hypothesis function following the
    user guide in MorphoJ (1.03d and 1.04a) on two separate Windows 7-64bit
    machines (core-i5 8gb ram and core2 quad 8gb ram-both with 4 CPU cores)
    for both 2D and 3D data. Both have the 32-bit java console installed.
    The calculations work well for 2D data (25 landmarks) with few seconds
    lag. The characteristics of the 3D data are:

    49 landmarks (80 specimens) with two partitions, where 18 landmarks are
    placed in the second partition. The contiguous partitions only box
    ticked and full enumeration of partitions selected. The 49 landmarks
    originated from a 200 landmark (80 specimens) morphoJ file.

    After selecting this operation, I notice the total CPU usage of the
javaw.exe*32.exe in the task manager goes up to 25% and stays at 25% for
    one modularity operation. So if I made another modularity test, the CPU
    usage will be 50%. I do not see anything come out in the "Results" and
    "Graphics" tab of MorphoJ. When I move the mouse cursor on MorphoJ, it
    does show MorphoJ busy calculating the data. I left the computer on
    overnight, I see the CPU usage is still 25% with MorphoJ busy with the
    calculations. I've tried different analyis in MorphoJ while waiting for
the modularity test and MorphoJ can work on other data and the output is
    generated after few seconds lag which shows that the software is not
    frozen. However, no analysis done after the modularity test could be
    save as the modularity test itself is not completed. I've also tried
    increasing CPU usage process priority to high and realtime but that did
    not improve the processing time. There does not seem to be any
    difference in the processing time regardless of type of CPU usage. The
    ram usage is not affected and stays about 142 mb.

    Is there something wrong with my data? Does anyone know how to make the
    calculations faster?

    Grateful for the help.

    Regards,
    Helmi Pritam
    University of Dundee


Reply via email to