<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mkin/tests/testthat/test_analytical.R, branch v1.0.3</title>
<subtitle>Fitting kinetic models to chemical degradation data (also on github)</subtitle>
<id>https://erac.jrwb.de/mkin/atom?h=v1.0.3</id>
<link rel='self' href='https://erac.jrwb.de/mkin/atom?h=v1.0.3'/>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/'/>
<updated>2020-05-29T13:03:04Z</updated>
<entry>
<title>Warn if standardized residuals are unlikely normal</title>
<updated>2020-05-29T13:03:04Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2020-05-29T13:03:04Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=510436646b1bdd5b8cfab70be29334bd3cc9c828'/>
<id>urn:sha1:510436646b1bdd5b8cfab70be29334bd3cc9c828</id>
<content type='text'>
This revealed a bug in the data returned in mkinfit$data in the case
of the d_3 algorithm, which also affected the residual plot - the
data from the direct fitting was not returned even if this was
the better method.
</content>
</entry>
<entry>
<title>Address solaris platform dependence revealed on CRAN</title>
<updated>2020-05-12T07:08:59Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2020-05-12T07:08:59Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=b88c0140885808ae7443179fe8137dea3b93994f'/>
<id>urn:sha1:b88c0140885808ae7443179fe8137dea3b93994f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release to CRAN</title>
<updated>2020-05-11T15:47:36Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2020-05-11T15:47:36Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=feca0008dcf662bba5c728096c4e63b923b8979b'/>
<id>urn:sha1:feca0008dcf662bba5c728096c4e63b923b8979b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add analytical solution for DFOP-SFO</title>
<updated>2020-05-11T13:20:53Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2020-05-11T13:00:25Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=6308e7d7898d4f064d321d97d162c6752c22b362'/>
<id>urn:sha1:6308e7d7898d4f064d321d97d162c6752c22b362</id>
<content type='text'>
This is about twice as fast as deSolve compiled in the case of FOCUS D
</content>
</entry>
<entry>
<title>Analytical solutions for all SFO variants</title>
<updated>2020-05-11T11:43:40Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2020-05-11T11:43:40Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=b36ae3d710858ee3ff2907eb2d780e0dff48a4f3'/>
<id>urn:sha1:b36ae3d710858ee3ff2907eb2d780e0dff48a4f3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Avoid the call to merge for analytical solutions</title>
<updated>2020-05-09T19:18:42Z</updated>
<author>
<name>Johannes Ranke</name>
<email>jranke@uni-bremen.de</email>
</author>
<published>2020-05-09T19:18:42Z</published>
<link rel='alternate' type='text/html' href='https://erac.jrwb.de/mkin/commit/?id=efab37957381919c21d874906ce870f4941c760a'/>
<id>urn:sha1:efab37957381919c21d874906ce870f4941c760a</id>
<content type='text'>
This increases performance up to a factor of five!
</content>
</entry>
</feed>
