The PRO initiative for open science

I just signed up to the PRO initiative for open science. This is a way for reviewers to nudge authors towards being more open in their approach to science. The idea is authors should either a) provide their data, analysis scripts, and experimental stimuli when they submit a paper, or b) explain why they can’t. Signatories to the PRO initiative agree to request such materials (if they aren’t already provided) when reviewing manuscripts. If the authors don’t provide the materials (or don’t explain why they can’t—some people may have good reason for keeping aspects of their experiment a secret), the review focusses only on this aspect of the paper. There is no obligation on signatories to examine those materials in data or comment on them; the idea is rather to encourage authors to make these materials available for all readers (not just the reviewers) form the outset. Having said that, there are a number of times I’ve been reviewing papers and wished the authors had made their data available.

Changes

I just imported (manually) my blog posts from blogspot, so this should be up to date. Please excuse broken links introduced in the conversion.

Welcome!

A collection of blog posts and data from the lab of Simon Farrell, now at the University of Western Australia.

This site will be fully updated in the next few weeks.

Getting stuff into Editorial

Editorial is the new text editor on the block that has all the kids talking. Its two main features that set it apart from the other N markdown editors available on the iPad are a) Inline preview of markdown, in a very pretty format, and b) the thing is fully Python scriptable. A compendium of workflows shows all the cool stuff you can do with built in workflow components and Python scripting.

One issue with apps like this is getting docs in there in the first place. Many apps, Editorial included, can access a Dropbox account, and will by default set up their own directory in /Apps/. So one has a choice of manually moving documents to and from that directory, or making one’s entire working directory available to the app. This latter is overkill, so I was looking for an easy way to get stuff into and out of Editorial. The solution is to stick the following bash code into an automator service. When run on a file, it will move that file into the Editorial Dropbox directory, and create a placeholder file with extension “edi” in it’s place. Running the script on the “.edi” file will move the document back to its home (and delete the edi placeholder).

xpath=${1%/*} 
xbase=${1##*/}
xfext=${xbase##*.}
xpref=${xbase%.*}

editorialDir="/Your/Editorial/Dropbox/Directory"

if [ "$xfext" == "edi" ]
then
    echo "here!"
    targName=`less $1`
    mv $editorialDir/$targName $xpath
    rm $1
else
    if [  -a $editorialDir/$xbase ]
    then
        COUNTER=2
        while [  -a $editorialDir/$xpref$COUNTER.$xfext ]; do
            let COUNTER=COUNTER+1
        done
        targName=$xbase$COUNTER.$xfext
    fi
    mv $1 $editorialDir/$targName
    echo "$xpref$COUNTER.$xfext" > $xpath/$xpref.edi
fi

Google Nexus 4

So recently I lost my iPhone 4 on the way back to the office from lunch. Two things of note:

  1. I had location services turned on on the iPhone, and could use the “Find my iPhone” feature to track it down. I managed to work out roughly where it was, to within 20-30 metres or so, but the location kept jumping around, indicating the phone was inside (or inside a drain) and couldn’t use GPS. This turns out to actually not be that helpful—I asked around various shops/businesses (including where I bought lunch) but without having a good idea about the precise building or room, there’s not much you can do. One feature I unfortunately did end up using was the remote wipe; I’ve lost a phone, but don’t have to worry about nefarious use of personal information.

  2. To replace the iPhone—which had been carrying along nicely, no complaints—I bought a Nexus 4. This turns out to be pretty full of features, and nearly half the price of an iPhone 5 (yes, I could have bought an iPhone 4 or 4S, but, y’know…). Some impressions:

    a. The phone itself is pretty solid, and really light compared to previous smartphones I’ve owned. It’s a slippery sucker though, and seems to willitself off tables and armchairs.

    b. I had an Android phone a few years back, and although I thought it was good, it didn’t have the same level of polish as iOS. This version (Jelly Bean) actually looks nice, and I’d forgotten how cool it is to use things like widgets. I totally understand the benefits of Apple’s walled garden, but it’s nice to be able to do your own digging. The one glaring exception is the gmail app—on iOS the recent-ish update to the gmail app is beautiful to look at, and the Android version is just plain old ugly in comparison.

    c. I seemed to encounter the issues with buggy wi-fi that have been bugging others. Wi-fi at work was fine, but the connection at home kept dropping. I came close to just returning the damned phone as I wasn’t able to reliably download apps, but in the end installed a third party app that brought the issue under control.

    d. One new feature in Android is Google Now. This allows you to do voice searches and commands, and also brings up useful information (e.g., appointments, flight details) by intelligently working out when you’ll need them. So far I’ve only ever been told about the weather and upcoming calendar appointments, so I lead a dull life (most plausible) and/or Google needs to mine my data deeper (also plausible, and somewhat disturbing).

    e. I don’t have a constant mobile data connection. Whether this is to do with poor coverage from Virgin or a hardware/software fault I don’t know, but it is something I miss from the iPhone on O2.

comments powered by Disqus