octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

odepkg: odeset profile tests


From: Jacopo Corno
Subject: odepkg: odeset profile tests
Date: Tue, 02 Dec 2014 11:14:00 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Dear Carlo, dear Roberto,

here are the results of the execution time of tests I run after the c implementation of the levenshtein comparison introduced by Roberto.

TEST ODESET WITH LEVENSHTEIN STRING COMPARISON

TEST 1: set many options with exact naming
TEST 2: set only one option with exact naming
TEST 3: set many options with many typos
TEST 4: set only one option with small typo

-------------------------------------------------------------------------------------------
| TEST | levenshtein.m | levenshtein.cc | odeset old version |
-------------------------------------------------------------------------------------------
| 1 | 0.819225 | 0.066781 | 0.004404 | | 2 | 0.030761 | 0.015593 | 0.006332 | | 3 | 0.876063 | 0.062384 | (error) | | 4 | 0.037888 | 0.017068 | (error) |
-------------------------------------------------------------------------------------------


Best regards,
Jacopo


On 28/11/2014 09:56, Carlo De Falco wrote:
On 27 Nov 2014, at 16:40, Jacopo Corno <address@hidden> wrote:

the performance of ode45 on it's own should not change with or without 
levenshtein. Only odeset calls it when setting the options before launching the 
solver.

J
OK, so rather than different simulations, on each row use a different set of 
options:

test 1: set many options with exact naming
test 2: set only one option with exact naming
test 3: set many options with many typos
test 4: set only one option with completely wrong name
test 5: set only one option with small typo

c.

--

Jacopo Corno M.Sc.
Technische Universität Darmstadt
Graduate School of Computational Engineering
Dolivostraße 15
64293 Darmstadt / Germany

Office: S4|10-232
Phone: +49 6151 16 - 76877
Email: address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]