{"id":695,"date":"2024-07-12T10:41:33","date_gmt":"2024-07-12T10:41:33","guid":{"rendered":"https:\/\/doctor-dark.co.uk\/blog\/?p=695"},"modified":"2024-07-15T10:40:21","modified_gmt":"2024-07-15T10:40:21","slug":"fear-and-loathing-with-mpirun","status":"publish","type":"post","link":"https:\/\/doctor-dark.co.uk\/blog\/fear-and-loathing-with-mpirun\/","title":{"rendered":"Fear and Loathing with mpirun"},"content":{"rendered":"\n

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. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

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…<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

# Program to monitor status of Oyster cluster, displaying up\/down indication.\n#import os\nimport time\nimport subprocess as sp\n\nmachines = [\"oyster0\", \"oyster1\", \"oyster2\", \"oyster3\"]\n\nwhile True:\n    for i in range(len(machines)):\n        machine = machines[i]\n        state  = sp.call(['ping', '-c', '1', machine], stdout=sp.DEVNULL)\n        \n        if state == 0:\n            colour = \"0 200 0\" # Green means UP\n        else:\n            colour = \"200 0 0\" # Red means DOWN \n            \n        row = \"12 \"\n        if machine == \"oyster0\":\n            column = \"0 \"\n        elif machine == \"oyster1\":\n            column = \"4 \"\n        elif machine == \"oyster2\":\n            column = \"8 \"\n        elif machine == \"oyster3\":\n            column = \"12 \"\n    \n        message = \"set_pixel \" + row + column + colour\n        \n        fp = open(\"\/home\/chris\/ftp\/files\/blinkenlights\" + machine, 'w')\n        fp.write(message)\n        fp.close()\n        \n        time.sleep(1)<\/code><\/pre>\n\n\n\n
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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
[* 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.]<\/p>\n","protected":false},"excerpt":{"rendered":"
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 … Continue reading “Fear and Loathing with mpirun”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,7],"tags":[15,13],"class_list":["post-695","post","type-post","status-publish","format-standard","hentry","category-computing","category-raspberry-pi","tag-led","tag-raspberrypi"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/posts\/695","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=695"}],"version-history":[{"count":6,"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/posts\/695\/revisions"}],"predecessor-version":[{"id":704,"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/posts\/695\/revisions\/704"}],"wp:attachment":[{"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=695"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=695"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/doctor-dark.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=695"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}