20 July 2012

213. Another earthquake (ca 4.3) felt in Melbourne, 20th July 2012

This one (4.3) didn't last as long as the last one, or maybe it was because I was in a busy chinese restaurant in Glen Waverley. Basically felt like sitting on a wooden floor with someone walking across it rapidly. That was at 19.11 (7.11 pm) 20/7/2012.

According to the GA:
Near Moe, Vic. Magnitude: 4.3 (ML) Depth: 0 km Tsunamigenic: Not available 
Date and Time UTC: 20 July 2012 @ 09:11:31 Sydney Time: 20 July 2012 @ 19:11:31 (AEST) 
Location Coordinates: -38.282, 146.164 
Solution status Last updated: 20 July 2012 @ 19:23:11 (AEST) Solution finalised: No Source: AUST 

Would say duration about 5 seconds. My wife didn't feel it, and it seems like few others did, as the noise in the restaurant didn't die down at all.

Not much of an experience in the SE Melbourne suburbs this time, and I don't think it will generate much media excitement this time.

IF YOU FELT IT, REPORT IT:
 http://www.ga.gov.au/earthquakes/staticPageController.do?page=felt-earthquake

The Australian GA didn't crash this time. Look here for good ol' local details about the 'quake:
http://www.ga.gov.au/earthquakes/getQuakeDetails.do?quakeId=3237322



But here's what's out there so far:

http://news.ninemsn.com.au/national/8502657/earthquake-reportedly-shakes-melbourne

http://www.theage.com.au/victoria/second-earthquake-shakes-melbourne-20120720-22fo6.html

This blog claims to have pictures from mayhem in a supermarket from this latest earthquake:
http://www.dirtydazz.com/wow-im-sure-we-just-had-another-earth-tremor-quake-in-melbourne-711pm-20-july/

That's 2 earthquakes in Melbourne in the past month -- and the last one was on the 19th of June, a day and a month ago.

From USGS:
13 km (8 miles) SW of Moe, Australia
21 km (13 miles) W of Morwell, Australia
34 km (21 miles) W of Traralgon, Australia
77 km (47 miles) ESE of Cranbourne, Australia


212. TmoleX client on Debian

Based on what Andreas Klamt has said about COSMO vs COSMO-RS I figured it might be worth taking a look at Turbomole. Turbomole is not GPLd, so whether it's a viable approach depends on whether you have a university paying for a license on your behalf. Luckily, I do, and APAC also has it on their HPC clusters.

As always, turbomole may or may not be for you -- the basis set nomenclature is definitely different from the Pople one. I'm only half-heartedly shopping around among different computational packages, but my guides may benefit someone.

The client is free and can be downloaded from here:
http://www.cosmologic.de/index.php?cosId=3016&crId=3

put TmoleXClient33_Linux64.sh in your ~/tmp
launch it by doing
sh TmoleXClient33_Linux64.sh

I don't like the idea of littering my system folders with symmlinks when you can fire up your PATH instead.
If you want to install in /opt, make sur eyou've already created /opt/COSMO and chown:ed it

Once all that's done you can do
echo 'export PATH=$PATH:/opt/COSMO/bin' >> ~/.bashrc
source ~/.bashrc

Start the binary by typing
TmoleX


211. Putting a 'Hold' on Gnome

Update 05/08/2012: The Mint people may have their own reasons for forking various GNOME components, but it seems that the removal of features in Nautilus was a direct reason for the creation of Nemo: http://www.webupd8.org/2012/08/nemo-linux-mint-team-forks-nautilus.html


There are a lot of things which are yet to come to Gnome. It's becoming increasingly clear that the Gnome people are going to push their ideas on the distros using Gnome regardless of whether the changes make sense or not. My main issue is still the destruction of gnome-screenshot, but it's clear that there are other things afoot that will make many of us unhappy. See e.g. nautilus

Actually, GNOME 3 is mostly fine. It's the removal of functionality from some of the GNOME applications which bothers me the most.

Going to KDE, XFCE, Xmonad, LXDE etc. won't bring me back gnome-screenshot. When it comes to Evolution, Epiphany etc. there are plenty of good alternatives. But Shutter etc. don't cut it when it comes to replacing gnome-screenshot. Nautilus, to me, is a good file manager and I prefer it to e.g. dolphin, thunar etc. for various reasons (dolphin because it's QT, thunar because...I don't even remember. Maybe I should have a look at it again...)

In all fairness, a subsection of the users will not care or maybe even like changes that I hate. Change isn't bad. Bad changes are bad. Change for the sake of change is bad.

Anyway. A temporary solution is to freeze gnome and not allow upgrades until you are sure that you won't be trading higher version numbers for reduced functionality.

Also, some might like the Mac-like idea of putting menus at the top of the screen, while most people using a desktop-sized screen will be severely unhappy with this (mouse has to travel a lot further). 

I suppose the idea is that you're only using one application per desktop at a time BUT WHY WAS THIS EVER THOUGHT TO BE THE WAY PEOPLE WORK?

Really, designing with non-work uses (chat/browsing) in mind seems a bit counter-productive. Literally.

Wikipedia has a list of the gnome applications which are the things that might get fiddled with. Basically, google for upcoming changes and prevent the heck out of them.

Early warning about stuff about to be changed in GNOME 3.6: 
see e.g. http://www.phoronix.com/scan.php?page=news_item&px=MTEzMzY
empathy
clutter
evolution
mutter
nautilus

Additional stuff to consider freezing
gnome-screenshot
gnome-shell
epiphany-browser
evince

Again, change may be good, but we've been burned before, so better to freeze stuff now, and make deliberate decisions about what changes to allow once they've been tested.

So how to freeze specific packages?
sudo su
echo "empathy hold"|dpkg --set-selections
echo "epiphany-browser hold"|dpkg --set-selections
echo "evince hold"|dpkg --set-selections
echo "gnome-shell hold"|dpkg --set-selections
echo "gnome-screenshot hold"|dpkg --set-selections
echo "mutter hold"|dpkg --set-selections
echo "mutter-common hold"|dpkg --set-selections
echo "nautilus hold"|dpkg --set-selections

Note that this may hold other packages, which list the above packages as dependencies, back as well. Still, better to make informed choices.