Sunday, 22 January 2017

Saturday, 21 January 2017

film review: Arrival

The aliens have arrived, in 12 giant mysterious ships dotted around the planet. They are enigmatic, but seem to want to communicate. The Americans enlist the help of academic linguist Louise Banks [Amy Adams] and physicist Ian Donnelly [Jeremy Renner]. They gradually manage to establish communication, but does that important ambiguous word mean “weapon” or “tool”? Louise keeps having flashes of her life with her daughter Hannah, who dies tragically young: these images may hold the key to deciphering the aliens’ intent.

This is a very cerebral film, with a lot of talking about alien language and arguing about alien motives, with a small amount of misguided military action: the CGI goes into making the aliens nicely alien, not into swooping spacecraft and big explosions. The gradual increase in the protagonists’ language knowledge and confidence, and the sheer intellectual slog that involves getting that competence, are conveyed well. This description might make the film sound dull and slow, but the plot moves forward briskly and engrossingly. There’s the obligatory twist, which I am pleased to say I spotted before the reveal, but in truth it wasn’t that much before. It’s one of those interesting twists that might make you want to see the film again, to re-evaluate some of the events.

deciphering alien language

Despite the leading character being a woman, the film only barely passes the Bechdel test: her child is female, and they sometimes talk about things other than the father.

For a film about language and communication, there are a couple of places where that communication is a little opaque. Early on, the military is trying to enlist Louise, and threatening to go to another linguist if she doesn’t agree to their terms. She challenges them to ask the other linguist for the translation of the Sanskrit word for war. When they come back with the answer, it is given inaudibly against an overwhelming background of helicopter blades. I looked it up afterwards; it doesn’t seem to be germane to why they chose her over the other guy. The other communication incident, which is deliberate, is that a turning point in the film has Louise persuade a Chinese general to break off hostilities, by speaking a key sentence to him in Mandarin, and we get no subtitles. It works, even though we don’t know what was said. Again, I looked it up afterwards; the sentence is meaningful, but its content doesn’t actually matter, only that it works. In a sense, these two events seem more profound precisely because I didn’t know exactly what is said.

Overall, I really enjoyed this. It is nice to see people solving problems with their brains rather than with their fists and guns, for a change.




For all my film reviews, see my main website.

Saturday, 14 January 2017

book review: Just One Damned Thing After Another

Jodi Taylor.
Just One Damned Thing After Another.
Accent Press. 2013

Dr Madeleine Maxwell, known as Max to all, is an historian recruited by St Mary’s Institute of Historical Research. St Mary’s have some time travel machines, allowing the historians to go back and observe historically significant events as they happen. This requires nerve, and training. Max has the former in spades; St Mary’s provide the latter. But there’s more at stake than Max realises.

This is a mish-mash of genres, involving history, time-travel, boot-camp training, romance, intrigue, tragedy, and more. It is a mish-mash in a good way, as Max, nobody’s fool and nobody’s patsy, powers her way through increasingly bizarre and traumatic incidents, including serving in a WWI battlefield hospital, dodging dinosaurs and more in the Cretaceous, and visiting the Libray of Alexandria under somewhat trying conditions.

Everyone at St Mary’s is eccentric and weird, but also competent, which is always good to see: competence makes eccentricity funny, rather than annoying. St Mary’s does seem to have a rather small staff for what it does (although significantly more than the Gerry Anderson school of staffing levels). And I never fully understood its original business model: the time travel is a secret, so how do the historians’ observations of past events contribute to currrent knowledge? No matter; by the end Max has come up with a new business model which is much more effective. If the villains let them pursue it. Which of course they won’t.

I initially dipped my toe in this series, buying only the first entry. But before I was half-way through this compulsively readable book, I ordered the next three.




For all my book reviews, see my main website.

Tuesday, 10 January 2017

book review: The Last Dragonslayer

Jasper Fforde.
The Last Dragonslayer.
Hodder & Stoughton. 2010

Magic is gradually fading away in the Ununited Kingdom. And the number of dragons is decreasing. Jennifer Strange, a foundling sold into indentured servitude to a wizarding agency, finds herself in charge when its owner disappears, and is having trouble keeping the wizards employed. When a wizard has a vision that the Last Dragon will be killed by the Last Dragonslayer next week, her troubles are just beginning.

I came to this with high expectations, given how much I have enjoyed the clever craziness of Fforde’s other two series: Thursday Next and Nursery Crimes. I was sadly disappointed. Those other two series have a solid underpinning theme (books, and nursery rhymes, respectively) and the overlaying surreality feeds off these, rocketing off in marvellously unexpected directions. The Last Dragonslayer is all surreality, but with nothing underlying it. That removes nearly all the opportunities for cleverness, replacing it mostly with silliness.

A shame. I’ll leave this series, and wait for the next Thursday Next.



For all my book reviews, see my main website.

Monday, 9 January 2017

The Tale of a New Machine

Just before Christmas, my old desktop PC died.  Well, actually only the main hard drive died, and I managed to limp through the Christmas break on the solid state drive alone.  However, it was 4 years old (my previous machine having died just after Christmas 2012), and the 120 GB SSD was constantly full and in need of management.  So I decided to bite the bullet and get a new machine, despite knowing what it would entail.

I ordered a new machine (Intel i7-6700, 4MHz, 4 cores, 8MB cache; 8GB RAM, 240GB SSD, 1TB HD; Windows 10; external DVD writer) and picked it up late on Wed 4 Jan.

I have since been reinstalling my life.  Many of the steps below took some persistent googling to find web instructions on what the problem was, and how to fix it.  Stack Exchange is a godsend!

Wednesday
  • install ZoneAlarm firewall and virus checker
  • connect to the internet
  • use IE to download Chrome
  • download and install Evernote – sync 10,000 notes, over the piece of wet string that is my home internet connection
  • download and install Google Drive – sync 15,000 files (10 GB), over said wet string
  • go to download Adobe Acrobat Reader DC, but discover it is already installed – yay!
  • download and install Notepad++ – now I can edit files
  • restore relevant files from previous machine backup
So endeth the first day.

Thursday
  • download and install MS Office 365 (which I have access to via work)
    • 50 minutes to download.  See "wet string", above
  • download and install MikTeX and TeXnicCenter
  • download and install PaintShopPro X8 (via work)
  • download and install Power PDF (via work)
  • download and install Dropbox (more synching...)
  • download and install HP ScanJet drivers and software
  • download and install Python 2.7 
    • look at installing matplotlib, numpy and scipy – looks complicated, so pause for now
  • download and install 7-zip
So endeth the second day.

Friday
  • download and install Ace Money, my finacial software
    • plugged in the licence number from the original install, and it all works
  • get LaTeX to work...
    • fiddle with TeXnicCenter PDF profile to make it work with Adobe Acrobat Reader DC
    • add a new profile to work with Biber
    • discover the version of biber in MikTeX is incompatible with the version of pdflatex, despite have downloaded them in the same package
    • update MikTeX – except it will only update some parts
    • update MikTeX again – all now works
  • think about Python
    • decide to bite another bullet, and move up to Python 3, having checked that all the modules I use in my various bits of software (book review page generation, solar PV graphs, Trello backup code, etc) have Python 3 versions
    • WinPython apparently comes with matplotlib, numpy and scipy already, and allows both Python 2 and Python 3, so I decide to go for that
    • uninstall the “vanilla” Python 2.7
    • download WinPython 2.7
      • discover it isn’t actually fully supported, in that it doesn’t have matplotlib, numpy or scipy
      • decide not to install these separately, but just go for Python 3
    • download WinPython 3.5
So endeth the third day.

Saturday
  •  install WinPython 3.5
    • use the Control Panel to associate .py files with WinPython 3.5
    • spend a LONG TIME trying to find what the path needs to be set to, to access all the different bits in different places; eventually go for
      • PYDIR =  D:\WinPython\python35\WinPython-64bit-3.5.2.3Qt5\python-3.5.2.amd64
      • PYTHONPATH =  %PYDIR%\Lib\site-packages; %PYDIR%\Lib\site-packages\PyQt4; %PYDIR%; %PYDIR%\DLLs; %PYDIR%\Scripts; %PYDIR%\..\tools; %PYDIR%\..\tools\mingw32\bin; %PYDIR%\..\tools\R\bin\x64; %PYDIR%\..\tools\Julia\bin; %PYDIR%\Tools\scripts
      • add %PYTHONPATH% to system PATH
      • probably a bit over the top, but everything seems to work now
    • convert a couple of small utilities from python 2.7 to 3.5, using 2to3.py, and some hand tweaking
      • which went more easily that I had feared; main hand changes needed were removal of some code to handle Unicode strings...
    • convert the solar PV graphing utility to Python 3
      • some fiddling with csv file handling
      • strange warnings from numpy percentile function – which I will fix when I have time...
  • connect machine to home network
    • this requires updating the hosts file
    • can’t update the hosts file – being used by another process – but which one?
    • grovelling around on the web provides the culprit is ZoneAlarm
      • unlock in ZoneAlarm
      • update file
      • relock
So endeth the fourth day.

Sunday
  • use mklink to recreate a symbolic link between the directory containg book cover images in my development directory, and in my website mirror directory
  • convert my book review webpage software to Python 3
    • main issue is the module to read the MS Access database
    • import pypyodbc module – “almost totally same usage as pyodbc” which I was using originally
    • download/install 32bit Microsoft Access Database Engine 2010 Redistributable
      • doesn’t work
      • apparently it need to be 32bit to match the MS Office, and 64bit to match the Python; hmmm
      • uninstall MS Office 365 32 bit, download and install MS Office 365 64 bit
      • uninstall 32bit Microsoft Access Database Engine 2010 Redistributable
      • download/install 64bit Microsoft Access Database Engine 2010 Redistributable
    • then need to edit the registry to allow it access to certain keys
    • then need to change to file location from bookdb.accdb to .\bookdb.accdb
      • sigh
    • then change every field access from row.Field_Name to row['field_name']
      • all the same functionality, but not necessarily in the same syntax
  • download/install WinMerge
    • to stop small differences in the output of the Python before and after porting...
So endeth the fifth day.

Monday
  • set up a VPN to access work stuff
    • download Pulse Secure app
    • poke the relevant holes in my ZoneAlarm firewall
    • discover from work support what I have to type into the userid box to get it to work – it’s not (just) my userid!
Normality has been restored

So endeth the sixth day.

So on the seventh day, I’ll be able to start working again!

If it wasn’t for the help of Stack Exchange, my home “sys admin”, and work support, this would all have been impossible.  I’m glad it happens only every four years or so...