Nigella Lawson. Author of numerous cookery books. Star of a quite watchable cookery show, which tends not to be difficult stuff.
Rather than writing about her, I thought I’d just post some pictures of this morning’s bakery – pear and ginger muffins, from “Nigella Express”, a favourite in our house.
If Nigella, or her publisher, object to me showing this one example recipe, will they please tell me?
To save time this morning, I did the preparation last night.The bowl contains flour, sugars, baking powder, and ground ginger. The jug was in the fridge all night, and contains vegetable oil, yoghourt and kefir (instead of sour cream), honey, and two large eggs.
Muffin cases onto baking tray. The oven is already pre-heating by this point.
Pour the jug into the bowl, peel and chop the pears.
Mix it all together, and spoon the result into the muffin cases.
Sprinkle brown sugar on top, and put them in the oven for 20 minutes. You may have noticed that I annotate recipe books. It’s a good way to remember little details that make things work even better when you use the recipe again.
Hmmm, not too shabby! Thanks to doing the preparation the night before, I was able to do this even without having a coffee first. They do go rather well with coffee, for breakfast.
Sometimes, I just don’t feel like cooking a formal “meat and two veg” dinner. So we have what we call “bits”. Here we have stuffed vine leaves from a tin, a selection of charcuterie from Tesco, a few bits of artichoke, and four dips. The orange coloured one is made from our home-grown carrots, with yoghourt in the middle. Then there’s hummus with dukkah sprinkled on it, a beetroot dip I think I invented, with pine nuts on it, and (probably) an aubergine dip.
Clearly, what’s missing is bread and wine. See below…
Well, we ran out of the last bacon I made, a while ago. Even worse, Mrs Walrus bought some shop bacon, which we know just isn’t as good as the home made kind. You might suppose making bacon is difficult. You might even suppose it’s something to do with an old, vulgar joke, but that’s up to you. How come I know how to do it, then? Simple. I stand on the shoulders of giants…
How?
Well, I had to nip out to the shops, as I had no mozarella, and it is Pizza Saturday. After that, I nipped into the butcher’s shop near the supermarket. (I would have given you a link to Deri Page, St Clears, but I don’t do links to Facebook pages.) There were only a couple of people waiting, and I enjoyed the conversations about their relatives who never eat minced beef, and make that two kilos, please, and what on earth is going on in Laugharne? Then I bought a nice bit of pork belly, complete with skin and ribs.
I used my favourite Sabatier boning knife to separate the ribs from the belly, trying not to cut too close, because when you’re eating ribs off the barbecue, it’s best if there’s a good amount of meat on them. I left the skin on, other bacon makers remove it now. That might give them a quicker cure, but I like the choice of whether to fry the bacon with or without it.
Of course, the remaining meat and skin were too big to fit in my plastic brining box, so I cut them in half.
The cure I used is mostly cooking salt, with some dark brown sugar mixed in, and this time, about half a teaspoonful of ground white pepper. Some of it gets rubbed fairly firmly into the meat, while the rest is kept handy to use as the curing proceeds in the fridge, which is usually about two weeks. I look at it daily, draining the liquid from the box, and checking that no mould is trying to establish itself. If it does, I wipe it off with vinegar soaked kitchen towel. It never comes back from that!
I used to put far more cure than this on at first, but it really doesn’t need that much, and you can end up with bacon that’s too salty.
There are actually two plastic boxes in the picture, the inner one has holes in it for the liquid that emerges from the pork to drain down into. It’s tipped out daily, more cure is added as necessary, and the meat gets turned over. If anyone knows a proper word for that liquid, please enlighten me!
End of part one…
Part the Second
I have washed the cure off, patted the meat dry, and put it back in the fridge, propped up on chopsticks to dry out for a week or so. Then I’ll smoke it. There will be pictures.
Part Three
A day ago, I set up the ProQ smoker, filled with oak sawdust, in its specially optimised smoke chamber (it’s a galvanised dustbin from B&Q), hung the bacon up, and started the sawdust smouldering. I don’t mess with little candles to light it, a blast from my blow-torch does the trick. It burns for about twelve hours. Today, I went and got the smoked bacon. I’ll be slicing it tomorrow, and vacuum packing the results, before freezing them. I may also have a bacon sandwich.
And, finally…
I have a bacon slicer. It’s not a very good one, but it’s better than my previous one, which was Chinese, and had internal gears moulded roughly from steelmaker’s slag, or possibly something worse. The gears wore out within weeks. Anyway, I’ve sliced the bacon into a range of rashers, rough chunks, and indescribable bits and pieces. They will all taste lovely. And, in order to store portions without continuing to make everything smell like smoked bacon (I’m not saying that’s a bad thing), I have used this lovely little vacuum packing machine.
The UK somehow seems just to trundle along, with things mostly getting worse for everyone, all the time. There are occasional little bursts of progress, but they soon get eroded away. It’s odd, though, because we change our government from time to time. Yet things just head in the same inevitable downward spiral.
Way back, before the Industrial Revolution, we were ruled by Kings, Nobles, and the filthy rich. Kings were descendants of the guy who was best at intimidating or murdering his opponents, and the people knew it was best to do as they were told, if they didn’t want Mr Sword to meet them violently.
After the Industrial Revolution, the Kings and their chums were joined by the successful industrialists, who set themselves up as the landed gentry. There was a Parliament that made laws, and you could be in it if you had lots of money, or were a lord. Most people weren’t allowed to take part in the voting to select who was in this very wealthy clique.
Now these people felt certain that it was their place to rule over us, because they were rich and important. They made sure Parliament did what they wanted.
But there were these dreadful progressive types, who felt things ought to be more democratic, and the number of people allowed to vote for the government kept increasing. The ruling class didn’t like that. So they made sure they could influence whatever government got itself elected, using money, rather than Mr Sword, and Mr Gun.
And people were fooled into thinking this was a democracy. It’s not.
Whoever was in Parliament, the ruling class already had them under their thumbs in advance, and continued to run things for their own benefit.
Nowadays, this continues. The ruling class make donations to politicians of the major parties, in the certainty that the policies they like will be put in place by the politicians they own. And this is why Keir Starmer is continuing the policies of Rishi Sunak. It’s also why, no matter what policies the Labour Party Conference decides upon, the leadership just does what the ruling class wants done.
And this has been going on for hundreds of years, and it is going to be very difficult to change it, even though the people hugely outnumber the ruling class, because there will always be greedy people willing to sell us out for a bit of luxury for themselves.
The world should have blinkenlights on its computer systems. That’s a given.
I wrote a couple of things. One was a Python program that pinged the four machines forming the cluster, and displayed a red or green light on a UnicornHD HAT to show their status. It worked very nicely. Then I wrote Python code to form part of any program that would be run in parallel on the cluster, which would send a signal saying whether each core was busy or not. It worked nicely, and I now had a row of 16 LEDs, in red or green, so I could see what was going on. It was very pretty.
Unfortunately, as it worked by sending a file by FTP every time a processor core changed between running and idle, it created a very effective Denial of Service attack on our network. Oops.
Now that I have thought about it more carefully, I shall be constructing a much better monitoring system, which will be based on sockets. I’ve been avoiding learning how to use them for far too long, anyway…
Later:
I tried at least umpteen example programs using sockets, and the connections were all rejected, and I couldn’t work out how to fix that. Suggestions, anyone?
Using a Python program to query the cluster computers took nearly six seconds to look at the 16 cores, hardly blinkenlights… A quick hack of a bash script, astonishingly, took almost as long. Back to trying to get sockets to work, then…
Working sockets tutorial!
At last, I found a socket programming example that worked, here!
I wanted to give Zan a tiny donation, but sadly his GoFundMe page seems defunct, and possibly the message I tried to send him also failed…
Sadly, I was then unable to work out how to accept multiple connections from the cluster computers.
Threading sockets programs!
There’s another set of client-server demos on GitHub, here, that I tested with Marvin and two of the Oysters, to confirm that it can do what I want. I can hoik code from those while retaining the program logic, and maybe get all four Oysters to send their status to Marvin, for him to display. I am not at all bothered that I am writing control system code for the cluster, instead of getting round to some fun applications of parallelism
I now have a GUI program that runs on Marvin, which takes a program developed on Marvin, deploys it on the four Pi’s that make up the oyster cluster, then uses mpirun to run it in parallel on 16 cores, with the results appearing on Marvin.
I’m just testing my Raspberry Pi cluster, to see if I have sorted out the setup properly this time. Finding the primes up to 10,000 with one core, and then sixteen cores, followed by using 16 cores to find primes up to 100,000 gave these results…
pi@oyster0:~ $ mpirun -hostfile myhostfile -np 1 python3 Programs/prime.py 10000 Find all primes up to: 10000 Nodes: 1 Time elapsed: 4.34 seconds pi@oyster0:~ $ mpirun -hostfile myhostfile -np 16 python3 Programs/prime.py 10000 Find all primes up to: 10000 Nodes: 16 Time elapsed: 0.34 seconds pi@oyster0:~ $ mpirun -hostfile myhostfile -np 16 python3 Programs/prime.py 100000 Find all primes up to: 100000 Nodes: 16 Time elapsed: 23.78 seconds
So, it is all working as it should now. Next step is to add blinkenlights on the supervising machine, Marvin, which has a UnicornHD HAT. After that, I want to get my GUI based supervisor working.
This leaves far too little time to flog stuff on eBay! I shall have to write a program to do that…
Update:
I ran it for the primes under a million, and it was disturbingly slow. I’d hope for something less than ten times as long as for a hundred thousand, but no!
pi@oyster0:~ $ mpirun -hostfile myhostfile -np 16 python3 Programs/prime.py 1000000 Find all primes up to: 1000000 Nodes: 16 Time elapsed: 2279.37 seconds
Almost ten minutes. I’m assuming things ended up swapping memory in and out, or Python doesn’t handle big integers very well. It’s not a problem, but it is one of the reasons I want blinkenlights…
For a while, I have been turning the camera on the Pi in the greenhouse on and off manually. By that I mean…
Connecting to the Pi using VNC
Opening the /var/tmp directory in the file manager
Creating a file called blind to switch the camera off, or
Deleting/renaming the blind file to switch the camera on
Disconnecting from the Pi
That’s clearly a huge faff, so I decided I’d finally make a GUI based program to do the job, using guizero. Other GUI libraries were either immensely complex or mysteriously impossible to install. I looked at a couple of example programs, and cobbled this together…
My Raspberry Pi cluster, named “Oyster” because of something to do with the Walrus and the Carpenter, had been out of commission for months, so I eventually got to work and tried to set it up from scratch, as an alternative to checking everything over and over again, and failing to find anything wrong. Oyster used to look like this, but the Pi 3s in Lego compatible cases ran too hot.
At first, I attempted to use my only Pi 4, “Marvin”, as the control machine for the four Pi 3s in Oyster, but I got something wrong in the setup, and it didn’t work. I had been thinking 20 cores would obviously be better than 16, but suspected the two different user names in use might be causing the problem. It probably wasn’t, as I now think the ssh communication for the cluster is done anonymously. Possibly. Anyway, I changed my mind about 20 cores, when I thought about the other tasks Marvin runs, and how I didn’t want them slowed down. Sixteen will do. Unless I get some more Pi 3s and add them to the cluster…
Anyway, I went through all the setup described in Ashwin Pajankar’s e-book* about Raspberry Pi “supercomputers”, again. Twice. I found some online guides, and checked the setup with those, too. I could run programs on the four cores of oyster0, but not on the other three Pis. Eventually, I spotted that I had forgotten to create the file “known-hosts” on the controlling Pi. The message passing software, python3-mpi4py, would probably have told me this, if I had run it in verbose mode, but I didn’t. Still, it now works, and I have a sixteen core Pi cluster running.
I have added a program, running on Marvin, that lights up LEDs to show the state of the Pis in the cluster, and intend to add further blinkenlights to show the activity of each of the sixteen cores.
# Program to monitor status of Oyster cluster, displaying up/down indication.
#import os
import time
import subprocess as sp
machines = ["oyster0", "oyster1", "oyster2", "oyster3"]
while True:
for i in range(len(machines)):
machine = machines[i]
state = sp.call(['ping', '-c', '1', machine], stdout=sp.DEVNULL)
if state == 0:
colour = "0 200 0" # Green means UP
else:
colour = "200 0 0" # Red means DOWN
row = "12 "
if machine == "oyster0":
column = "0 "
elif machine == "oyster1":
column = "4 "
elif machine == "oyster2":
column = "8 "
elif machine == "oyster3":
column = "12 "
message = "set_pixel " + row + column + colour
fp = open("/home/chris/ftp/files/blinkenlights" + machine, 'w')
fp.write(message)
fp.close()
time.sleep(1)
This code sends a text file to my Unicorn HD server program, which enables more than one program to write to its 256 LEDs, without messing up each other’s displays.
My plans for further development include improving my set of framework code for running parallel programs on the cluster, and more (or possibly less) importantly, to send messages to Marvin for the blinkenlights.
[* I haven’t included a link to AP’s e-book, because it’s easy to find online, and he is charging far too much for it, while others are giving us the same information free.]
It all started when I read a news item saying RealVNC was going to change its terms and conditions unilaterally, so that home users would be limited to connecting to three computers. I was using it to view and control anything up to fifteen computers.
Panic set in. I began to research other free VNC implementations. Then it was pointed out to me that it was only remote access over the internet that would be affected. I hadn’t been doing that at all. It seemed all the Pi’s on my network would be unaffected. To ensure things would not get changed, I set RealVNC to NOT update automatically on all of them.
During my researches, I heard that a Pi running Wayland instead of X-Windows could be remotely accessed just like VNC, using rpi-connect, and decided that would be interesting to do, anyway. So I needed to update a machine to run the Bookworm version of RaspberryPi OS, which does use Wayland. I have only one Pi 4 at present, and did the thing they tell you never to do – I attempted an in-place upgrade. It ever so nearly worked. But it wouldn’t run rpi-connect. So, I pulled the Pi to bits, took its SSD off the Waveshare adapter it uses, and burned a fresh copy of Bookworm. Once it was all re-assembled, the Pi booted up normally, and rpi-connect was usable. Well, there was the small matter of going online and associating the Pi, whose name is Marvin, with my RaspberryPi ID. Which I have.
Here is a screenshot of my Linux Mint box, with VNC Connect at the top left, a VNC session into the street camera at the bottom left, another remote session on a Pi, at the middle left, and a remote session on Marvin…
Ideas for the next step…
Firstly, it seemed like a good idea to verify that I did indeed have remote access. I turned off wi-fi on my phone, and used Chrome to access the Raspberry Pi sign in page, which was fine. And on connecting to Marvin, I got this…
So, remote access definitely works. I don’t think I will be using my phone for the job, but one of my tablets, or even the Chromebook should work just fine.
The next thing was to write something to enable Marvin to monitor WeatherPi, which has an occasional problem with its greenhouse temperature sensor, that results in the weather monitoring and upload program crashing. I used the Python Paramiko library, and made a program (cobbled together from earlier versions) that checks the weather station every five minutes. If the machine itself is down, it sends a message to my phone, using Pushover. If the machine is up, it checks whether the weather program is running, and attempts to restart it otherwise. I added starting this program to the other programs Marvin runs at startup, which is done by this bash script –
Somewhere online, while I was trying to get the remote monitoring to work, I found a way to make a python program keep going. Using a bash shell script to run the program like this means that if the program does stop, it will immediately be run again, until the terminal it was run in is closed.
while : ; do
now=$(date)
echo $now >> restart.log
python3 /home/pi/program-to-run.py
sleep 10
done
This does not work with programs using Pi cameras, when the camera crashes. I wonder if there is a camera resetting utility available, as rebooting is not possible inside this script! I wonder if libcamera can do a reset of the camera? Must have a look…