Great news! The RSS is setting a data analysis challenge this year, sponsored by the Young Statisticians Section and Research Section of the Royal Statistical Society: Details are available on the wordpress website of the Challenge. Registration is open and the Challenge goes live on Tuesday 6 May 2014 for an exciting 6 weeks competition. (A wee bit of an unfortunate timing for those of us considering submitting a paper to NIPS!) Truly terrific, I have been looking for this kind of event to happen for many years (without finding the momentum to set it rolling…) and hope it will generate a lot of exciting activity and replicas in other societies.
Archive for Wordpress
RSS statistical analytics challenge 2014
Posted in Kids, R, Statistics, University life, Wines with tags data challenge, NIPS, Royal Statistical Society, RSS, Wordpress on May 2, 2014 by xi'an2013 in review [by WordPress]
Posted in Uncategorized with tags 2013, Wordpress on December 31, 2013 by xi'anThe WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.
Here’s an excerpt:
The Louvre Museum has 8.5 million visitors per year. This blog was viewed about 250,000 times in 2013. If it were an exhibit at the Louvre Museum, it would take about 11 days for that many people to see it.
oops, no tooltip…!
Posted in pictures with tags ICERM, legends, pictures, title edition, Wordpress on January 29, 2013 by xi'anThanks to Jean-Michel Marin, I have just noticed that the legends I put on my (or others‘) images were not visible as blue boxes hovering over the picture. I checked on wordpress and found the solution: The new title of the downloaded image is not the title of the published image!
The title added in this field does not display as a tooltip (when a mouse is hovered over the image). To add a tooltip title, edit the image after inserting it into the post, and add your tooltip wording to the Title field.
However that means that the older images in the ‘Og (those published since the new version of wordpress was implemented, around the very end of November…) will not be corrected…
please do not like my posts!!!
Posted in pictures with tags blogging, pictures, Wordpress on September 7, 2012 by xi'an
This is a very minor inconvenience with WordPress (or just the blogging world) so do not read any further as it does not matter in the slightest! Indeed, for every post that I write, a few complete strangers tag it with a “like” mention, for which I get a notification. Given that those strangers have their own blog, mostly related to photography, I suspect this is an indirect way to induce more visits to their own site… Even though I do not see how anyone but me is aware of those “like”s…
\verbatim [beamer package]
Posted in R, Statistics, University life with tags Beamer, LaTeX, Le Monde, mathematical puzzle, sourcecode, verbatim, Wordpress on June 12, 2012 by xi'anOnce again working on my slides for the AMSI Lecture 2012 tour, it took me a while to get the following LaTeX code (about the family reunion puzzle) to work:
\begin{frame}[fragile,label=notleM2]
\slidetitle{A family meeting}
\begin{block}{Random switch of couples}
\only<1>{
\begin{itemize}
\item Pick two couples [among the 20 couples] at random with probabilities proportional
to the number of other couples they have not seen\\
{\verb+prob=apply(meet(T)==0,1,sum)+}
\item switch their respective position during one of the 6 courses
\item accept the switch with Metropolis--Hsatings probability\\
{\verb#log(runif(1))<(penalty(old)-penalty(new))/gamma#}
\end{itemize}
}
\only<2>{
\begin{verbatim}
for (t in 1:N){
prop=sample(1:20,2,prob=apply(meet(T)==0,1,sum))
cour=sample(1:6,1)
Tp=T
Tp[prop[1],cour]=T[prop[2],cour]
Tp[prop[2],cour]=T[prop[1],cour]
penatp=penalty(meet(Tp))
if (log(runif(1))<(penat-penatp)/gamma){
T=Tp
penat=penatp}
}
\end{verbatim}
}
\end{block}
\end{frame}
since I was getting error messages of the form
[sourcecode language=”latex” gutter=”false”]
[86] (./simulation.38.vrb) [87] (./simulation.39.vrb
!Illegal parameter number in definition of \beamer@doifinframe.
l
l.12 }
?
[/sourcecode]
Using two frames in a row instead of the “only<2>” version did not help…
Continue reading
