RT @MMBDTP: ‘Investigating the mechanisms of action of intracellular anaerobic pathogens on human host cancer cell metabolic networks (BREWER_U23MMB)’ with @danbrewer and Professor Colin Cooper. #mmbdtp23 https://t.co/oFhBFmtCaP https://t.co/vpCnq6Sv89


from Twitter https://twitter.com/danbrewer

Comments

Post a Comment

Popular posts from this blog

Nationwide statement to QIF Format

Nationwide recently closed down the ability to get OFX statement files. These files were used to get transaction information into Microsoft Money and many other bits of accounting software. You can read more about it at the BetterOnlineBanking.co.uk website. I needed to find a way round this so that I could continue using Gnucash without resorting to typing everything in. Looking around I notices that the QIF format was pretty simple and so I have written two scripts: A Nationwide credit card statement to QIF converter A Nationwide flexaccount statement to QIF converter They are tested to work on both OS X and Linux and have zero requirements. Lets hope that Nationwide sort themselves out and produce a better way to do this. Usage Download the full statement in csv format from Nationwide Download the relevant script into the same directory Make the script executable: chmod +x NWCreditcsv2qif.sh Create the QIF file: ./NWCreditcsv2qif.sh NWCreditOct2009.csv > NWCreditOct2009.qif...
Read more

Interrupting R processes in Ubuntu

Image
Interrupting R processes in Ubuntu : " Pressing Ctrl+C should work in the terminal. If that doesn't work, open another terminal console and type ps aux | grep R kill -s INT PID The first line allows you to discover the PID number of your particular R instance, which is then used in the second line. In the second line above, INT may be replaced by HUP in some cases. The above methods set up an alert-thing to tell the program to stop. When the computations are done externally of R, it can't be executed before the external codes checks back with R. If the external code doesn't do this regularly or at all, killing the entire program is the only way out. If none of the above work, this is probably what has happened and it may be a good idea to let the package author know about the problem... "
Read more