<p>The two parameters affecting the running time of prepare is the population size, and whether PREPARE is run on monogamous or polygamous mode. Most of the running time is spent on reconstructing the fifth generation.</p
<p>A series of optimizations are compared in which the number of calculations (and thus the total ti...
<p><i>Perm</i> indicates the number of permutations per gene.</p><p>Timings for 4 different executio...
We ran the runserosim function 100 times and report the mean run times under various simulation sett...
<p>Time performance of our implementation of the hit–and–run on genome scale networks. On an Intel d...
<p>Multi-core CPU version ran on 16 CPU threads running on 16 CPU cores.</p><p>Running time (in seco...
<p>Multi-core CPU version ran on 16 CPU threads running on 16 CPU cores.</p><p>Running time (in seco...
<p>Note: The running time is given in seconds. The running time of the Maslov rewiring represents th...
<p>Run time (in seconds, on a single core of an Intel i7 processor) for typical single runs for each...
Speedup factor and total processing time for performing all-to-all MCPSC with increasing number of t...
<p>Based on the elapsed wall clock time (<b>A</b>, in hours) and the total CPU utilization (<b>B</b>...
<p>Runtimes in CPU hours for generation of 100 designs using RECON, both by fixed backbone (FBB) and...
<p>Time consumption of Multifind, LocARNATE+RNAz and RNAz on 100 Rfam alignments and 100 yeast align...
<p>Average time taken to compute the likelihood for a household of size . Other parameters , and as...
<p>The plots show the CPU time (Intel Xeon E5-1620 with 3.70GHZ) for running the Net-RSTQ algorithm ...
<p>Computational time is depicted as a function of genome size when setting the sample size to 50, a...
<p>A series of optimizations are compared in which the number of calculations (and thus the total ti...
<p><i>Perm</i> indicates the number of permutations per gene.</p><p>Timings for 4 different executio...
We ran the runserosim function 100 times and report the mean run times under various simulation sett...
<p>Time performance of our implementation of the hit–and–run on genome scale networks. On an Intel d...
<p>Multi-core CPU version ran on 16 CPU threads running on 16 CPU cores.</p><p>Running time (in seco...
<p>Multi-core CPU version ran on 16 CPU threads running on 16 CPU cores.</p><p>Running time (in seco...
<p>Note: The running time is given in seconds. The running time of the Maslov rewiring represents th...
<p>Run time (in seconds, on a single core of an Intel i7 processor) for typical single runs for each...
Speedup factor and total processing time for performing all-to-all MCPSC with increasing number of t...
<p>Based on the elapsed wall clock time (<b>A</b>, in hours) and the total CPU utilization (<b>B</b>...
<p>Runtimes in CPU hours for generation of 100 designs using RECON, both by fixed backbone (FBB) and...
<p>Time consumption of Multifind, LocARNATE+RNAz and RNAz on 100 Rfam alignments and 100 yeast align...
<p>Average time taken to compute the likelihood for a household of size . Other parameters , and as...
<p>The plots show the CPU time (Intel Xeon E5-1620 with 3.70GHZ) for running the Net-RSTQ algorithm ...
<p>Computational time is depicted as a function of genome size when setting the sample size to 50, a...
<p>A series of optimizations are compared in which the number of calculations (and thus the total ti...
<p><i>Perm</i> indicates the number of permutations per gene.</p><p>Timings for 4 different executio...
We ran the runserosim function 100 times and report the mean run times under various simulation sett...
DOI
Add to ORKG