<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">

	<title>Xavablog</title>
	<id>tag:xavier.robin.name,2010-05-28:/en/feed</id>
	<link rel="self" href="http://xavier.robin.name/en/feed" />
	<link rel="alternate" href="http://xavier.robin.name/en/blog"/><!--http://xavier.robin.name/comments for all comments http://xavier.robin.name/comments/path for comments on a specific post, http://xavier.robin.name/tag/(tag) for posts with 'tag'-->
	<updated>2012-02-21T09:27:44.476784000+01:00</updated>
	<sy:updatePeriod>daily</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	<link rel="license" type="application/rdf+xml" href="http://creativecommons.org/licenses/by-sa/3.0/rdf" />

	<icon>http://xavier.robin.name/en/img/favicon.ico</icon>

	<author>
		<name>Xavier Robin</name>
		<uri>http://xavier.robin.name/en/contact</uri>
	</author>
	

	<entry xml:lang="fr" xml:base="http://xavier.robin.name/en/">
		<title type="html">La vie après le pétrole, 7 ans après</title>
		
			<category term="politics" label="Politics" scheme="http://xavier.robin.name/en/tag/politics" />
		
		<link href="http://xavier.robin.name/en/blog/2012/01/28/la-vie-apres-le-petrole-7-ans-apres"/>
		<id>tag:xavier.robin.name,2012-01-28:/blog/2012/01/28/la-vie-apres-le-petrole-7-ans-apres</id>
		<published>2012-01-28T18:43:43+01:00</published>
		<updated>2012-01-28T18:43:43+01:00</updated>
		<content type="html">&lt;p&gt;Il y a près de 7 ans, j'écrivais un article intitulé &lt;a href=&quot;/blog/2005/11/10/la-vie-après-le-pétrole&quot;&gt;La vie après le pétrole&lt;/a&gt;, après la lecture d'un livre du même intitulé.&lt;/p&gt;

&lt;p&gt;7 ans après, que s'est il passé ? Eh bien depuis 2005, la production de pétrole a stagné&amp;nbsp;! C'est en tous cas ce qu'affirme &lt;a href=&quot;http://www.nature.com/nature/journal/v481/n7382/full/481433a.html&quot;&gt;un commentaire dans Nature&lt;/a&gt;, &lt;a href=&quot;http://www.washington.edu/news/articles/commentary-in-nature-can-economy-bear-what-oil-prices-have-in-store&quot; hreflang=&quot;en&quot;&gt;repris par Sandra Hines&lt;/a&gt;. Chiffres à l'appui, on découvre le plateau, la tôle ondulée, les prix qui explosent. &lt;a href=&quot;http://www.lexpress.ch/fr/suisse/petroplus-a-demande-sa-mise-en-faillite-594-377470&quot;&gt;Faillite de Petroplus&lt;/a&gt;, &lt;a href=&quot;http://www.liberation.fr/monde/01012385161-l-europe-impose-un-embargo-petrolier-sans-precedent-a-l-iran&quot;&gt;tensions en Iran&lt;/a&gt;, tous les ingrédients sont réunis pour le plus gros choc pétrolier de l'Histoire, tel que prédit par Jean-Luc Wingert.&lt;/p&gt;

&lt;p&gt;Alors il est vrai que depuis, pas mal de choses ont changé. Les énergies renouvelables ne sont plus une chimère défendue uniquement par les Verts. Nombreux sont ceux qui ont compris que les bénéfices que l'on peut en tirer sont loin d'être uniquement écologiques. Mais le chemin à parcourir pour être totalement indépendant de l'or noir semble encore bien long.&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="en" xml:base="http://xavier.robin.name/en/">
		<title type="html">Switching to Catalyst</title>
		
			<category term="my_site" label="My website" scheme="http://xavier.robin.name/en/tag/my_site" />
		
		<link href="http://xavier.robin.name/en/blog/2012/01/07/switching-to-catalyst"/>
		<id>tag:xavier.robin.name,2012-01-07:/blog/2012/01/07/switching-to-catalyst</id>
		<published>2012-01-07T16:42:10+01:00</published>
		<updated>2012-01-07T16:42:10+01:00</updated>
		<content type="html">&lt;p&gt;It should be rather transparent, but I just switched my website from &lt;a href=&quot;http://xavier.robin.name/blog/2010/06/13/eperl&quot;&gt;ePerl&lt;/a&gt; to &lt;a href=&quot;http://www.catalystframework.org/&quot;&gt;Catalyst&lt;/a&gt;, &lt;a href=&quot;http://xavier.robin.name/blog/2011/01/08/switch-to-catalyst&quot;&gt;as announced before&lt;/a&gt;. The application should be a bit more reliable (less error 500 pages, that is after the initial debugging period).&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="en" xml:base="http://xavier.robin.name/en/">
		<title type="html">pROC 1.5 released</title>
		
			<category term="pROC" label="pROC" scheme="http://xavier.robin.name/en/tag/pROC" />
		
		<link href="http://xavier.robin.name/en/blog/2011/12/12/proc-1.5-released"/>
		<id>tag:xavier.robin.name,2011-12-12:/blog/2011/12/12/proc-1.5-released</id>
		<published>2011-12-12T09:27:08+01:00</published>
		<updated>2011-12-12T09:27:08+01:00</updated>
		<content type="html">
&lt;p&gt;pROC's steady progression goes on with version 1.5. It is avalable for R only. S+ users will need to wait for the upcoming 1.6 release which will introduce power / sample size computations.&lt;/p&gt;

&lt;p&gt;This version introduces four new notable features:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;#pROC_1.5_variance_covariance&quot;&gt;Variance and covariance&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;#pROC_1.5_logcondens&quot;&gt;Univariate Log-Concave Density Estimation smoothing&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;#pROC_1.5_plot&quot;&gt;Improvements to the plotting function&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;#pROC_1.5_coords&quot;&gt;New return values in coords&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;pROC_1.5_variance_covariance&quot;&gt;Variance and covariance&lt;/h2&gt;

&lt;p&gt;It is now possible to compute the variance of a ROC curve, and the covariance of two paired ROC curves.&lt;/p&gt;
&lt;pre&gt;library(pROC)
data(aSAH)
rocobj &amp;lt;- roc(aSAH$outcome, aSAH$s100b)

var(roc1)
var(roc2)
cov(roc1, roc2)&lt;/pre&gt;

&lt;p&gt;Two methods are available: bootstrap, DeLong&lt;sup&gt;&lt;a href=&quot;#ref_delong_note&quot; id=&quot;ref_delong_text&quot; name=&quot;ref_delong_text&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;. The bootstrap is the most versatile method. DeLong is faster but works for full AUC only. For more details, see &lt;code&gt;?var.roc&lt;/code&gt; and &lt;code&gt;?cov.roc&lt;/code&gt;.&lt;/p&gt;


&lt;h2 id=&quot;pROC_1.5_logcondens&quot;&gt;Univariate Log-Concave Density Estimation smoothing&lt;/h2&gt;
&lt;p&gt;Until now, three methods were available to smooth a ROC curve: &lt;code&gt;binormal&lt;/code&gt;, &lt;code&gt;density&lt;/code&gt; and &lt;code&gt;fitdistr&lt;/code&gt; (to fit a distribution with &lt;a href=&quot;http://cran.r-project.org/web/packages/MASS/&quot;&gt;MASS&lt;/a&gt;). Now, two new methods are available: &lt;code&gt;logcondens&lt;/code&gt; and &lt;code&gt;logcondens.smooth&lt;/code&gt;. They are based on Duembgen and Rufibach (2011)&lt;sup&gt;&lt;a href=&quot;#ref_duembgen_note&quot; id=&quot;ref_duembgen_text&quot; name=&quot;ref_duembgen_text&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;. You first need to install the &lt;a href=&quot;http://cran.r-project.org/web/packages/logcondens/&quot;&gt;logcondens&lt;/a&gt; package:&lt;/p&gt;

&lt;pre&gt;install.packages(&quot;logcondens&quot;)&lt;/pre&gt;

&lt;p&gt;It doesn't need to be loaded.&lt;/p&gt;

&lt;pre&gt;plot(rocobj)
rs &amp;lt;- smooth(rocobj, method=&quot;binormal&quot;)
plot(rs, add=TRUE, col=&quot;green&quot;)
rs2 &amp;lt;- smooth(rocobj, method=&quot;density&quot;)
plot(rs2, add=TRUE, col=&quot;blue&quot;)
rs3 &amp;lt;- smooth(rocobj, method=&quot;fitdistr&quot;, density=&quot;lognormal&quot;)
plot(rs3, add=TRUE, col=&quot;magenta&quot;)
rs4 &amp;lt;- smooth(rocobj, method=&quot;logcondens&quot;)
plot(rs4, add=TRUE, col=&quot;brown&quot;)
rs5 &amp;lt;- smooth(rocobj, method=&quot;logcondens.smooth&quot;)
plot(rs5, add=TRUE, col=&quot;orange&quot;)
legend(&quot;bottomright&quot;, legend=c(&quot;Empirical&quot;, &quot;Binormal&quot;, &quot;Density&quot;, &quot;Log-normal&quot;,
                               &quot;Log-concave density&quot;, &quot;Smoothed log-concave density&quot;),
       col=c(&quot;black&quot;, &quot;green&quot;, &quot;blue&quot;, &quot;magenta&quot;, &quot;brown&quot;, &quot;orange&quot;), lwd=2)
&lt;/pre&gt; 
 

&lt;h2 id=&quot;pROC_1.5_plot&quot;&gt;Improvements to the plotting function&lt;/h2&gt;

&lt;p&gt;Several users have been bothered by the fact than in pROC (R version), the sensitivity is plotted as decreasing specificity. Most other software plot increasing 1 – specificity on the X axis. The reason is purely historical: only few statistical software can plot an axis in decreasing direction. For instance S+ cannot do it, and pROC's ROC curve are plotted as 1 – specificity there. However it makes absolutely no difference on the ROC curve itself. As it was possible, I decided plot the modern version on R rather than stick to obsolete conventions.&lt;/p&gt;

&lt;p&gt;For those who are disturbed and prefer to stick to obsolete conventions, pROC 1.5 comes with a way to plot increasing 1 – specificity in the R version with the &lt;code&gt;legacy.axes&lt;/code&gt; argument.&lt;/p&gt;

&lt;pre&gt;plot(rocobj, legacy.axes=TRUE)&lt;/pre&gt;

&lt;p&gt;Note that it makes no difference to the coordinates of the plot, and if you want to add some text you still have to think in the &quot;new&quot; way. Consequently, the following will always be plotted to the top left corner of the curve, whatever &lt;code&gt;legacy.axes&lt;/code&gt; you specified:&lt;/p&gt;
&lt;pre&gt;text(1, 1, auc(rocobj), adj=c(0, 1))&lt;/pre&gt;

&lt;h2 id=&quot;pROC_1.5_coords&quot;&gt;New return values in coords&lt;/h2&gt; 


&lt;p&gt;The &lt;code&gt;ret&lt;/code&gt;argument of the &lt;code&gt;coords&lt;/code&gt; function now accepts several new values:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&quot;accuracy&quot;: (sensivity + specificity) / 2&lt;/li&gt;
	&lt;li&gt;&quot;tn&quot;: true positives count&lt;/li&gt;
	&lt;li&gt;&quot;tp&quot;: true negatives count&lt;/li&gt;
	&lt;li&gt;&quot;fn&quot;: false negtives count (positive observations classified as negative by &lt;code&gt;predictor&lt;/code&gt;)&lt;/li&gt;
	&lt;li&gt;&quot;fp&quot;: false positives count (negative observations classified as positive by &lt;code&gt;predictor&lt;/code&gt;)&lt;/li&gt;
	&lt;li&gt;&quot;npv&quot;: negative predictive value, or tn / (tn + fn)&lt;/li&gt;
	&lt;li&gt;&quot;ppv&quot;: positive predictive value, or tp / (tp + fp)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In addition, sensitivity, specificity, npv and ppv can be prefixed with &lt;code&gt;1-&lt;/code&gt; in order to get the opposite value. Finally two additional values are recognized:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&quot;npe&quot;: converted to 1-npv&lt;/li&gt;
	&lt;li&gt;&quot;ppe&quot;: converted to 1-ppv&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here is an example. We take the best threshold of the ROC curve &lt;code&gt;rocobj&lt;/code&gt; and display all the parameters of this threshold:&lt;/p&gt; 


&lt;pre&gt;coords(rocobj, &quot;best&quot;, ret=c(&quot;threshold&quot;, &quot;specificity&quot;, &quot;sensitivity&quot;, &quot;accuracy&quot;, &quot;tn&quot;, &quot;tp&quot;, &quot;fn&quot;, &quot;fp&quot;, &quot;npv&quot;, &quot;ppv&quot;, &quot;1-specificity&quot;, &quot;1-sensitivity&quot;, &quot;1-npv&quot;, &quot;1-ppv&quot;))&lt;/pre&gt;

&lt;p&gt;Coords also accepts a new argument: &lt;code&gt;drop&lt;/code&gt; to control the dimension of the return value. If &lt;code&gt;drop&lt;/code&gt; is &lt;code&gt;FALSE&lt;/code&gt;, a matrix will always be returned, even if it contains only one column. This is especially useful to make scripts more reliable.&lt;/p&gt;


&lt;h2&gt;Conclusion&lt;/h2&gt;

&lt;p&gt;Here is the full change log:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;New &lt;code&gt;cov&lt;/code&gt; and &lt;code&gt;var&lt;/code&gt; functions&lt;/li&gt;
	&lt;li&gt;&lt;code&gt;coords&lt;/code&gt; accepts new &lt;code&gt;ret&lt;/code&gt; values: &quot;accuracy&quot;, &quot;tn&quot;, &quot;tp&quot;, &quot;fn&quot;, &quot;fp&quot;, &quot;npv&quot;, &quot;ppv&quot;, &quot;1-specificity&quot;, &quot;1-sensitivity&quot;, &quot;1-npv&quot;, &quot;1-ppv&quot;, &quot;npe&quot; and &quot;ppe&quot;&lt;/li&gt;
	&lt;li&gt;New &lt;code&gt;legacy.axes&lt;/code&gt; argument to &lt;code&gt;plot&lt;/code&gt; 1-specificity rather than specificity&lt;/li&gt;
	&lt;li&gt;New &lt;code&gt;axes&lt;/code&gt; argument to turn off the plotting of the axis&lt;/li&gt;
	&lt;li&gt;New &lt;code&gt;logcondens&lt;/code&gt; and &lt;code&gt;logcondens.smooth&lt;/code&gt; (Univariate Log-Concave Density Estimation) smoothing methods&lt;/li&gt;
	&lt;li&gt;New function &lt;code&gt;has.partial.auc&lt;/code&gt; to determine if an AUC is full or partial&lt;/li&gt;
	&lt;li&gt;New argument &lt;code&gt;drop&lt;/code&gt; for &lt;code&gt;coords&lt;/code&gt;&lt;/li&gt;
	&lt;li&gt;&lt;code&gt;auc&lt;/code&gt; and &lt;code&gt;multiclass.auc&lt;/code&gt; objects now also have secondary class &lt;code&gt;numeric&lt;/code&gt;&lt;/li&gt;
	&lt;li&gt;Updated load call&lt;/li&gt;
	&lt;li&gt;Delong's CI reversed in ROC curves with &lt;code&gt;direction=&quot;&amp;gt;&quot;&lt;/code&gt;&lt;/li&gt;
	&lt;li&gt;Delong's CI AUC returned values &amp;gt; 1 or &amp;lt; 0 in some rare cases&lt;/li&gt;
	&lt;li&gt;Minor improvements in documentation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;As usual, you can find the new version &lt;a href=&quot;http://web.expasy.org/pROC/&quot;&gt;on ExPASy&lt;/a&gt; and  &lt;a href=&quot;http://cran.r-project.org/web/packages/pROC&quot;&gt;on the CRAN&lt;/a&gt;. To update, type &lt;code&gt;update.packages()&lt;/code&gt; or &lt;code&gt;install.packages(&quot;pROC&quot;)&lt;/code&gt; if you want to update pROC only.&lt;/p&gt; 

&lt;ul class=&quot;notes&quot;&gt;

&lt;li&gt;&lt;a href=&quot;#ref_delong_text&quot; id=&quot;ref_delong_note&quot; name=&quot;ref_delong_note&quot;&gt;1.&lt;/a&gt; Elisabeth R. DeLong, David M. DeLong and Daniel L. Clarke-Pearson (1988) “Comparing the areas under two or more correlated receiver operating characteristic curves: a nonparametric approach”. &lt;i&gt;Biometrics&lt;/i&gt; &lt;b&gt;44&lt;/b&gt;, 837–845.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#ref_duembgen_text&quot; id=&quot;ref_duembgen_note&quot; name=&quot;ref_duembgen_note&quot;&gt;2.&lt;/a&gt; Lutz Duembgen, Kaspar Rufibach (2011) “logcondens: Computations
     Related to Univariate Log-Concave Density Estimation”. &lt;i&gt;Journal
     of Statistical Software&lt;/i&gt;, &lt;b&gt;39&lt;/b&gt;, 1–28. URL: &lt;a href=&quot;http://jstatsoft.org/v39/i06&quot;&gt;jstatsoft.org/v39/i06&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

</content>
		</entry>

	<entry xml:lang="fr" xml:base="http://xavier.robin.name/en/">
		<title type="html">Un puzzle en HTML 5</title>
		
			<category term="internet" label="Internet" scheme="http://xavier.robin.name/en/tag/internet" />
		
		<link href="http://xavier.robin.name/en/blog/2011/11/20/un-puzzle-en-html-5"/>
		<id>tag:xavier.robin.name,2011-11-20:/blog/2011/11/20/un-puzzle-en-html-5</id>
		<published>2011-11-20T17:23:58+01:00</published>
		<updated>2011-11-20T17:23:58+01:00</updated>
		<content type="html">&lt;p&gt;Incroyable ce qu'on peut faire avec HTML 5. Jérémie Patonnier présente un &lt;a href=&quot;http://jeremie.patonnier.net/experiences/svg/inline/puzzle.html&quot;&gt;puzzle vidéo&lt;/a&gt;. Tout simplement bluffant !&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/files/blog/2011/11/20/puzzle_video.png&quot; alt=&quot;Capture d'écran du puzzle&quot;&gt;&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="en" xml:base="http://xavier.robin.name/en/">
		<title type="html">Invitations to Careers 2.0</title>
		
			<category term="internet" label="Internet" scheme="http://xavier.robin.name/en/tag/internet" />
		
		<link href="http://xavier.robin.name/en/blog/2011/11/19/invitations-to-careers-2.0"/>
		<id>tag:xavier.robin.name,2011-11-19:/blog/2011/11/19/invitations-to-careers-2.0</id>
		<published>2011-11-19T21:08:46+01:00</published>
		<updated>2011-11-19T21:08:46+01:00</updated>
		<content type="html">&lt;p&gt;I was invited to fill a profile on &lt;a href=&quot;http://careers.stackoverflow.com/&quot;&gt;Careers 2.0&lt;/a&gt;. I received a bunch of invitations, if you want one &lt;a href=&quot;/contact&quot;&gt;contact me&lt;/a&gt; with your CV (as a link, or use the given email address) and I'll send you one.&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="en" xml:base="http://xavier.robin.name/en/">
		<title type="html">Thoughts about the S+ GUI</title>
		
			<category term="pROC" label="pROC" scheme="http://xavier.robin.name/en/tag/pROC" />
		
		<link href="http://xavier.robin.name/en/blog/2011/11/19/thoughts-about-the-splus-gui"/>
		<id>tag:xavier.robin.name,2011-11-19:/blog/2011/11/19/thoughts-about-the-splus-gui</id>
		<published>2011-11-19T19:37:29+01:00</published>
		<updated>2011-11-19T19:37:29+01:00</updated>
		<content type="html">&lt;p&gt;For more than a year and a half, I have been releasing pROC version in two flavors: R and S+. The S+ version has a great advantage (or disadvantage for some) over R: it has a GUI, a graphical user interface. This is especially useful for users who do not want to learn programming R and who prefer a clic-and-point interface.&lt;/p&gt;

&lt;p&gt;However, this dual-version comes with a cost. Here are some thoughts about it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I have to maintain two different version. Fortunately R and S+ are similar enough that most code works in both environments. There are a few inconsistencies, especially the way the variables are scoped (&lt;a href=&quot;http://cran.r-project.org/doc/contrib/Fox-Companion/appendix-scope.pdf&quot;&gt;see this document by John Fox for more details&lt;/a&gt;). I need to be careful when &lt;code&gt;sapply&lt;/code&gt;ing: any variable accessed inside the function must be passed as argument in S+. Functions such as &lt;code&gt;try&lt;/code&gt; and &lt;code&gt;eval&lt;/code&gt; also behave quite differently. Overall, good tests in the examples section of the documentation are crucial to detect potential errors.&lt;/li&gt;

&lt;li&gt;The only exception is the &lt;code&gt;plot&lt;/code&gt; function. Graphics have huge differences between R and S+. Any modification of &lt;code&gt;plot&lt;/code&gt; is really difficult.&lt;/li&gt;

&lt;li&gt;S+ is much slower than R. Bootstrap operations take much longer to complete. Even DeLong computations, which are nearly instant in R, take a noticeable time to complete in S+.&lt;/li&gt;

&lt;li&gt;Specifically about the GUI now, writing S+ GUI code is awfully painful. For example there is little control over the placement of the buttons. The sample size window I'm currently developing is really ugly, and there is nothing I can do to improve it. The events are quite unpredictable, especially when the user rolls-back a window it is often in a broken status.&lt;/li&gt;

&lt;li&gt;The previous point stems from the lack documentation of the S+ GUI. It comes with a minimal introduction, that is just enough to start. But there are far too many undocumented features I had to discover myself by guessing-and-error. For instance, how to catch a user roll-back? I still haven't found how to cancel an analysis when I detect an error in the user's submission, or how to handle colors properly. For a professional-grade software, this lack of documentation is unexpected, to say the least.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So, would I start a new project with a GUI in S+? Probably not. I would first investigate the R integration plugin of SPSS. There are also some GUI for R, such as &lt;a href=&quot;http://socserv.mcmaster.ca/jfox/Misc/Rcmdr/&quot;&gt;Rcmdr&lt;/a&gt;. I can't tell if they are a manageable option, as I have never tested it. Another option would be to create a web interface, but R doesn't have CGI and it would require interfacing with another language such as perl. Anyway, I would not recommend anybody to start an S+ GUI project.&lt;/p&gt;

&lt;p&gt;What to expect of pROC in the future? Let me say I don't expect to stop its development soon. The version 1.5 of pROC, which will be released very soon, has a new sample size computation function, and a dedicated window in S+. In the long term (&gt; 1 year) however, the situation might change. I will leave the University of Geneva in just over a year; will I still have access to S+? This problem is typical from proprietary software and its licensing. I won't pay for it, and I don't know if TIBCO provides licenses for application developers.&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="fr" xml:base="http://xavier.robin.name/en/">
		<title type="html">Qui dirige vraiment le monde ?</title>
		
			<category term="politics" label="Politics" scheme="http://xavier.robin.name/en/tag/politics" />
		
		<link href="http://xavier.robin.name/en/blog/2011/11/17/qui-dirige-vraiment-le-monde"/>
		<id>tag:xavier.robin.name,2011-11-17:/blog/2011/11/17/qui-dirige-vraiment-le-monde</id>
		<published>2011-11-17T09:58:07+01:00</published>
		<updated>2011-11-17T09:58:07+01:00</updated>
		<content type="html">
&lt;p&gt;Dans une interview donnée à la BBC le 26 septembre dernier, Alessio Rastani déclare que &lt;a href=&quot;http://www.bbc.co.uk/news/business-15059135&quot; hreflang=&quot;en&quot;&gt;ce ne sont pas les gouvernements qui dirigent le monde, mais Goldman Sachs&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;L'analyste dit aussi que les plans de sauvetages ne changeront rien et ne l'intéressent pas. Ce qui l'intéresse, c'est comment gagner de l'argent. Il rêve depuis des années d'avoir une telle récession – pour gagner de l'argent. Aussi inquiétant que cela puisse paraître, sa prédiction vient de se réaliser. Avec &lt;a href=&quot;//fr.wikipedia.org/wiki/Mario_Monti&gt;Mario Monti et &lt;/a href=&quot;//fr.wikipedia.org/wiki/Louk%C3%A1s_Papad%C3%ADmos&quot;&gt;Loukás Papadímos&lt;/a&gt;, la banque dirige maintenant l'Europe.&lt;/p&gt;

&lt;p&gt;Alessio Rastani fait également une deuxième prédiction : dans 12 mois, les capitaux de milions de personnes vont disparaître. Voilà qui devient intéressant.&lt;/p&gt;

&lt;iframe width=&quot;560&quot; height=&quot;315&quot; src=&quot;http://www.youtube.com/embed/kpg76VjTa58&quot; frameborder=&quot;0&quot;&gt;&lt;/iframe&gt;</content>
		</entry>

	<entry xml:lang="fr" xml:base="http://xavier.robin.name/en/">
		<title type="html">Dernière date binaire</title>
		
			<category term="computers" label="Computers" scheme="http://xavier.robin.name/en/tag/computers" />
		
			<category term="humour" label="Fun" scheme="http://xavier.robin.name/en/tag/humour" />
		
		<link href="http://xavier.robin.name/en/blog/2011/11/11/derniere-date-binaire"/>
		<id>tag:xavier.robin.name,2011-11-11:/blog/2011/11/11/derniere-date-binaire</id>
		<published>2011-11-11T11:11:11+01:00</published>
		<updated>2011-11-11T11:11:11+01:00</updated>
		<content type="html">&lt;p&gt;Nous sommes le 11.11.11. Dans quelques instants il sera 11:11:11. La dernière date binaire (qui s'écrit uniquement avec des 0 et des 1) avant un bon bout de temps (un peu moins de 89 ans, 88 ans, 50 jours, 12 heures, 48 minutes et 49 secondes pour être précis).&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="en" xml:base="http://xavier.robin.name/en/">
		<title type="html">pROC now on GitHub</title>
		
			<category term="pROC" label="pROC" scheme="http://xavier.robin.name/en/tag/pROC" />
		
		<link href="http://xavier.robin.name/en/blog/2011/09/13/proc-now-on-github"/>
		<id>tag:xavier.robin.name,2011-09-13:/blog/2011/09/13/proc-now-on-github</id>
		<published>2011-09-13T12:19:38+02:00</published>
		<updated>2011-09-13T12:19:38+02:00</updated>
		<content type="html">&lt;p&gt;You can now &lt;a href=&quot;https://github.com/xrobin/pROC&quot;&gt;follow pROC development on GitHub&lt;/a&gt;!&lt;/p&gt;

&lt;p&gt;Among the upcoming features: sample size computation, variance and covariance functions, and much more… stay tuned!&lt;/p&gt;</content>
		</entry>

	<entry xml:lang="en" xml:base="http://xavier.robin.name/en/">
		<title type="html">pROC 1.4.4 released</title>
		
			<category term="pROC" label="pROC" scheme="http://xavier.robin.name/en/tag/pROC" />
		
		<link href="http://xavier.robin.name/en/blog/2011/08/10/proc-1.4.4-released"/>
		<id>tag:xavier.robin.name,2011-08-10:/blog/2011/08/10/proc-1.4.4-released</id>
		<published>2011-08-10T09:22:57+02:00</published>
		<updated>2011-08-10T09:22:57+02:00</updated>
		<content type="html">&lt;p&gt;I just released pROC version 1.4.4.&lt;/p&gt;

&lt;p&gt;This version fixes a critical bug in the computation of one-tailed ROC tests p values. Please update to this version if you perform one-tailed tests.&lt;/p&gt;
 
&lt;pre&gt;library(pROC)
data(aSAH)
rocs100 &lt;- roc(aSAH$outcome, aSAH$s100)
rocwfns &lt;- roc(aSAH$outcome, aSAH$wfns)
roc.test(rocs100, rocwfns, alternative=&quot;greater&quot;)
roc.test(rocs100, rocwfns, alternative=&quot;less&quot;)&lt;/pre&gt;

&lt;p&gt;Thanks to Lisa Koch for pointing out the problem.&lt;/p&gt;

&lt;p&gt;Here is the full change log:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Fixed alternative for one-tailed tests.&lt;/li&gt;
	&lt;li&gt;Removed COPYING file to fix a warning in r-devel.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;As usual, you can find the new version &lt;a href=&quot;http://web.expasy.org/pROC/&quot;&gt;on ExPASy&lt;/a&gt; and  &lt;a href=&quot;http://cran.r-project.org/web/packages/pROC&quot;&gt;on the CRAN&lt;/a&gt;. To update, type &lt;code&gt;update.packages()&lt;/code&gt; or &lt;code&gt;install.packages(&quot;pROC&quot;)&lt;/code&gt; if you want to update pROC only.&lt;/p&gt;</content>
		</entry>


</feed>
