<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mkin/vignettes/web_only/saem_benchmarks.html, branch v1.2.10</title>
<subtitle>Fitting kinetic models to chemical degradation data (also on github)</subtitle>
<id>https://erac.jrwb.de/mkin/atom?h=v1.2.10</id>
<link rel='self' href='https://erac.jrwb.de/mkin/atom?h=v1.2.10'/>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/'/>
<updated>2023-02-17T20:50:07Z</updated>
<entry>
<title>Update benchmark results for 7950X</title>
<updated>2023-02-17T20:50:07Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2023-02-17T20:50:07Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=5811ab93d856bb339a35eef2d23266fcb781cbe7'/>
<id>urn:sha1:5811ab93d856bb339a35eef2d23266fcb781cbe7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Finish adapting to upcoming deSolve</title>
<updated>2023-02-17T13:44:29Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2023-02-17T13:44:29Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=d5ff53448c61134c46cc4df9ea88fd86fa376d66'/>
<id>urn:sha1:d5ff53448c61134c46cc4df9ea88fd86fa376d66</id>
<content type='text'>
</content>
</entry>
<entry>
<title>We get about 25% performance gain</title>
<updated>2022-11-16T08:15:36Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2022-11-16T08:15:36Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=51d63256a7b3020ee11931d61b4db97b9ded02c0'/>
<id>urn:sha1:51d63256a7b3020ee11931d61b4db97b9ded02c0</id>
<content type='text'>
with the custom lsoda call, avoiding repeated getNativeSymbolInfo calls.
It's just that we should not be calling foreign functions from different
packages, because the may change without notice. Using
getNativeSymbolInfo for "call_lsoda" avoids the CRAN note, and a similar
call could probably be used for "unlock_solver", avoiding the NOTE in
checks for cran, but we should not do this in a CRAN package.
</content>
</entry>
<entry>
<title>Import saemix for easier profiling, update online docs</title>
<updated>2022-11-15T07:01:52Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2022-11-15T07:01:52Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=679cf716192cdfd91dfd232578cbd4e30d7eac12'/>
<id>urn:sha1:679cf716192cdfd91dfd232578cbd4e30d7eac12</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Start benchmark vignette for saem fits</title>
<updated>2022-11-14T20:05:01Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2022-11-14T20:05:01Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=d6168b0851a52adeaed8099e41a960d79acedae9'/>
<id>urn:sha1:d6168b0851a52adeaed8099e41a960d79acedae9</id>
<content type='text'>
</content>
</entry>
</feed>
