a yellow rose came out today
i didn't ask her why
in fact she hadn't much to say
and didn't even try
but though our conversation stalled
we still exchanged a smile
and in the sweetly-scented breeze
nodded for a while
a yellow rose came out today
i didn't ask her why
in fact she hadn't much to say
and didn't even try
but though our conversation stalled
we still exchanged a smile
and in the sweetly-scented breeze
nodded for a while
During our morning chat, Phil referenced Johnny Dangerously's catchphrase, "Once!" and so I asked him what his catchphrase is. He didn't reply immediately, so I helpfully suggested a couple of possibilities like "Aclarity" and "We're not just stotting around, here!"
He replied, "Heels touch ground when Slavs squat around!"
I said that sounded like a pretty weird catchphrase to me, but it turns out to be a reference to some offensive video I hadn't seen before about squatting. This is part of Philip's never ending quest to trick me into watch weird movement videos.
In any case, I subsequently asked Lucy what her catchphrase was and, after a moment of reflection she said, "I dunno." Then she brightened and said, "Hey! Maybe *that's* my catchphrase!"
Five minutes later, she asked me, "Hey, hey! So what's your catchphrase?"
Upon a moment of reflection, having completely forgotten what we were talking about five minutes ago, I said, "I dunno." Then I brightened and said, "Hey! We have the *same* catchphrase!"
I've always loved computer games. When I was young, I got to play arcade games as they first came out. I remember when Pong was first installed in our local pinball parlor. I spent a lot of time in video arcades in high school. When I became an adult professional, I found that many of my colleagues had basically never played such games. And I played relatively few as I worked to establish my career.
When my children were little, I would often identify a game they were playing and play it with them. In part, this was to have a an excuse to do things with them. I often felt like my dad would let me participate in his world (going for a hike, birdwatching, etc.) but was never willing to engage with me about things I was interested in. I wanted to find something they were doing that I could stand. So I played Pokémon with them (they got Red and Blue while I got Pokémon Yellow — with Pikachu!). And the Zelda games. And a variety of others, along the way.
At the same time, I try to set limits. I generally only play one game at a time: I played Ingress until I decided to try Pocket Camp and played that until I switched to Pokémon Go (at the suggestion of a son). My goal is that playing games remains just a small part of my day.
We got a Gamecube as our first video console game when it was relatively new. And one of the first games we got was Animal Crossing. I was immediately charmed by the game: You arrive in a a new town and buy a house with a gigantic loan that you need to pay off by collecting stuff (fruit, then insects, then fossils, then fish, then art) and selling it to earn "Bells" — the currency. The guy who loans you the money (a suave business-tanuki) also runs the store that you buy and sell stuff at. But the game had a variety of creative touches: in particular there was a museum that would accept donations of one of each of everything to put on display. And some fish and insects could only be found at certain times of day, or certain locations on the map. Or certain seasons.
One of the best features was that it appeared to be intentionally designed to have you to play every day, but to play for only a relatively short amount of time. It gave decreasing rewards the longer you played in a particular session. Although you could "grind", you could do most of the stuff that needed to be done for the day in a half hour. You could pick all the weeds, collect all the fruit, etc, and then there just wasn't much to do. But you might want to check back at various times of day to see if different fish or insects were out.
After the GameCube, the kids moved on, and I hadn't played Animal Crossing for years. I never played "New Leaf" which was released for the Nintendo DS (which I didn't have). Two years ago, Nintendo released a mobile game called "Pocket Camp" which I played for a while.
When they announced the newest version in the franchise, New Horizons, I figured I might try it to see what it was like. But I wasn't particularly excited about it. Then the Coronavirus happened.
Animal Crossing has gotten a huge amount of press worldwide as people cast about for something to do during the quarantine. The best article I've read so far is The Quiet Revolution of Animal Crossing which describes the game as a thought experiment about how life could be organized along a different set of values, that maximizes happiness and freedom over profit.
In my five-person household, four of us are playing Animal Crossing together. My younger son, who is the only one who has a switch, was gracious enough to let the rest of us create houses on "his" island. It's been fascinating to me to watch how each of use apprehends and constructs a completely different reality about how to organize their in-game activity.
He was actually pretty unhappy at having to share his island -- and even volunteered to purchase another switch to avoid this fate. But it was too late: there were no longer any available for love or money. As the primary player, he was the one that had to spend money early in the game for any infrastructure and for the animal residents. And for a while, this added to his passive-aggressive relationship with the rest of us. But when he hit it big in the "stalk market," he became a bit less concerned with money.
My older son has been more interested in large-scale engineering projects to facilitate resource extraction: reshaping the landscape to improve the quality of fish and creating separated spaces for large orchards to grow fruit, or constructing giant fields of flowers to generate crosses to get different colors.
My wife, who was an avid player of pocket-camp, is entirely driven by the gamification. There is a second form of currency (Nook Miles) which you earn by accomplishing tasks. She structures her game play to maximize earning Nook Miles, so she generally sells things or buys things, not due to need or interest, but only when the system offers you a reward for doing so.
I think I understand my own perspective best. I approach the game as play. I am not particularly goal oriented, but enjoy moving through the game with serendipity finding things (like fish and insects) and trying improve the aesthetics of myself, my house, and the island. That said, I'm not above using the gamification features to somewhat restructure what I want to do: sometimes I identify things I want to buy and then wait to purchase them until there is a reward.
A brief digression about gamification: as has been amply documented, rewards undermine the potential for developing intrinsic motivation. A good in-game example is photographs. The game sometimes offers a reward for taking a photograph. So you can get the reward for just randomly clicking the button. And that's what my wife's photographs tended to look like. But the game offers a vast array of resources for taking *interesting* photographs. In fact, its pretty clear that the game designers realized that by enabling people to take photographs and share them via social media, they could give the marketing additional reach.
Looking at the pictures posted online, I notice a further division in the kinds of images posted. Some people share the ordinary events of the game: "Ooh! I caught a coelacanth!" Whereas others show some creative project they undertook: a labyrinth of tarantulas or my archaeological site (see below). Those are the only interesting ones, to me. Everyone experiences the ordinary moments of game play. But seeing something uniquely creative, like these wanted posters where Jolly Redd moors his boat.
— san atlantis (@hhanalulu) April 24, 2020
I created a little archaeological site that I'm rather pleased with.
— Steven D. BREWER (@limako) April 24, 2020
Nintendo even set up a place ("Photopia") where you can dress up rooms and characters from your island with all of your furniture and clothes to stage scenes to photograph. I discovered early on that this includes the avatars for other players. There's something deeply unsettling about being able to take another player's character, strip them to their underwear, and then dress them and pose them however you want. I mean, it's not R rated. But it still felt like a violation. (You can find these pictures and more at my Animal Crossing Image Gallery.)
As a further aside, I wish it was easier to get the image files out without posting them to social media. As far as I can tell, the only way to get them out is by removing the MicroSD card and copying the files by hand. I don't really want to give the switch (and anyone who uses it in the household) permission to post as me to social media. That's just not going to happen.
Animal Crossing is like a Rorschach test that causes each player to see different aspects. Some people see Animal Crossing as representing consumerism gone mad: go into more and more debt to expand your house and stick useless stuff in it! At the same time, there's no obligation to do that. The animals live very simply. Players have to opt in to the consumer culture. Nobody makes you take out larger and larger loans -- or even pay off the loans you have. There's no interest. You don't even need to build a house: you can keep just living in a tent, if you want.
I'm also playing as "girl" character which has been interesting. I never took much interest in clothing in the previous games: Your avatar had to wear something, so I'd pick some generic clothes and then basically never change them. As a "girl" however, I have skirts and blouses and sweaters and tights and shoes and am taking great delight in mixing and matching them. I also annoy people by saying things like, "It's not lady-like to run with tools in your hands."
The most difficult aspect, for us, has been reconciling our different perspectives on managing the island. This particularly came to a head when we all got the ability to terraform the island -- to add or remove water features and high ground. Who gets to make those decisions? When should you consult with others? Governance is hard work -- even for a game. We're still struggling with this. We've had a couple of passionate arguments about this, but have been able to work through them so far.
The multiplayer aspects have been particularly interesting to me. One multi-player mechanism is to visit other people's islands or let them visit yours. In this way, you can get things that are rare or not available on your own island. Or, if you're participating in the "stalk market" you can buy or sell turnips at more favorable prices. But there is also a cooperative game-play mode.
While playing, you can "tag in" other players who can share the screen with you while you play. But this means there is the single, shared screen. The camera keeps the main player on screen, but moves to try to keep the second player on screen. If they go too far, they unceremoniously pop back on to the screen. But the loss of sole control of the camera can be pretty frustrating and makes certain activities difficult or impossible without the active collaboration of the second player. For example, you can't reliably see fish to catch them without the connivance of the second player. Having realized this, I've taken this as a challenge, to co-play effectively in a supporting role. It's a unique dimension to game play that I hadn't considered before.
I've had a great time during my Professional Improvement Fellowship working in the All-Campus Makerspace. It's a vibrant community of people working on projects they're passionate about. I enjoyed going in every morning, getting a few hours of work before anyone else arrived, and then breathing in the atmosphere as the place filled up. I've made good progress on my project and learned a huge amount about the topics I'm studying. And it's been fun.
I fear the students didn't quite know what to make of me. I wasn't staff and I wasn't student. I was just kind of there. But they were very welcoming and let me be a peripheral participant. I got to help out, in minor ways, with a dozen or more projects going on in the Makerspace. And they were just starting to discover what a weirdo I am.
On Wednesday, March 11, 2020, it became clear that the University would be taking steps to enable social distancing and the Makerspace made the decision to close operations to give staff Thursday and Friday before spring break to plan and prepare for the changes.I swung by on Wednesday and took home my box of materials and got set up to begin working on my project from home. I had realized, even as the pandemic was in its earliest phases, that working there was probably risky. It's a campus crossroads with students from all over campus coming through. So I had been expecting to step back at some point. It was just a surprise to have it happen so suddenly.
I haven't made much progress since I started working from home. I assume that once the excitement over the pandemic wears off, it will be easier to focus and get stuff done. But I'm really going to miss working in the Makerspace and all the new friends I've made there.
For working with headless Raspberry Pis, I thought it was useful to have the Pi report its address(es) when it boots. Originally I wrote it as a one-liner, but I realized that it was useful to grab the MAC address for debugging porpoises. But to get that, you need to know which interface is active. And this was starting to sound less like a one-liner and more like a script. So I hacked one together in bash.
The script just iterates through the interfaces, checks to see if they're up, and then reports the info back to a script on the server.
#! /bin/bash # rpi phone home script 20200228 sbrewer for i in $(ls -1 /sys/class/net) do #echo "Working on $i interface..." if [ $(cat /sys/class/net/$i/operstate) = "up" ] then echo "Reporting $i interface..." _IP=$(hostname -I) _HW=$(cat /sys/class/net/$i/address) _HN=$(hostname) /usr/bin/wget -O/dev/null -q https://bcrc.bio.umass.edu/pitrack/?hwaddr=$_HW\&pi=$_HN\&ip=$_IP fi done
A staple in Japanese manga and anime are the trappings of shinto practices. Shrines are frequent settings and, although they're rarely discussed directly, you see the architecture, objects, and designs as part of the background. I probably saw a shimenawa first in My Neighbor Totoro, which was perhaps the first anime I really watched. The giant camphor tree is almost a character in the movie and although I saw the shimenawa around it, I didn't know what it was or what it meant.
(image via ecostories)
I also saw a shimenawa in the anime Natsume Yujincho and the Book of Friends. Natsume breaks a shimenawa that releases a dangerous yōkai that ultimately becomes his guardian and tutor. Most recently, I've been reading Nekomusume Michikusa Nikki which includes shrines in the various settings and in which shimenawa feature prominently (if anonymously). There are also end-of-chapter information pages and one of them may have shown shimenawa.
For whatever reason, I realized that I didn't know anything about them, so I googled them. I didn't even know the word when I started, just searching for "japanese shrine tree rope" which helped me find a series of pages about them, including a wikipedia page. And that led me to the wikipedia page for shide. And a number of pages that described how to make them. I resolved to make one for my sakura tree.
In the pictures I had seen, a shimenawa seems to traditionally have a rope, tassels, and shide. So I went out to find the components to make one.
Shimenawa are traditionally made with rice straw, but hemp is also used. I was dubious about finding rice straw in this area. I thought about trying to find raw hemp, as it is increasingly grown in this area. But making rope looked like a lot of complicated work. So, cheating just a bit, I went to the store and found a heavy sisal rope for $1.35/foot and got a dozen feet.
When I got back with the rope, Alisa asked, "Did you measure it first?"
"Guess," I replied. She just smirked. But it turned out that 12 feet was exactly right: just long enough to tie a knot with no extra. OK. Maybe 14 feet would have been better.
For the tassels, I looked online and saw that people often make them with embroidery thread. The bundles of thread are already looped which makes it easy to tie up one end and cut the other to make a pretty tassel. And I considered getting brightly colored thread. But that seemed gaudy and out-of-place given what I had seen online. So I just bought a big ball of thick, jute twine, wrapped it around a large shim (I used an old 18 egg carton) and then tied up one end and cut the other. I also bought a length of thinner hemp string that I used to tie up the tassels -- and the ends of the rope -- and to hang everything.
I also bought a pad of thick drawing paper to make the shide. I had found a page on how to make shide, which explained how to make a series of cuts and then fold the paper up while rotating. It's easy, once you get the hang of it.
I ended up making 8 tassels and 4 shide. Once I had everything in hand, it was simple to tie the rope around the tree and then distribute the tassels and shide at likely spots along the length.
I'm pleased with the results. The total cost in materials was about $30. It took me several hours to purchase everything and then a couple of hours to make the tassels and shide and to hang everything on the tree. But it was a warm winter day with sun and I enjoyed the chance to do something outside and dream of the sakura blossoms to come.
And of course, I had to post a thread on twitter.
made a shimenawa for his beloved sakura tree / faris ŝimenavon por sia amata sakuro https://t.co/GjaW8PSoKr
— Steven D. BREWER (@limako) February 17, 2020
This first time was an experiment. Maybe by next time, I'll be ready to try actually making the rope. Or maybe not. It's fun either way.
Last spring, a faculty member and student met with me to discuss building an instrument and I agreed as a kind of "dry run" as part of the preparation for my new class. It sounds like a relatively simple project: a small, wearable device that collects two temperature readings. After a cursory bit of research, I recommended we try using the Adafruit Feather with BluetoothLE and two Onewire temperature sensors. It sounds simple, but trying to get it to work proved way more complicated than I had imagined.
First, we were hampered by trying to connect to the feather using the Windows laptop the student had. She didn't know anything about using serial ports via USB. And the USB cable she had was power only. And the bluetooth interface on her laptop couldn't do BluetoothLE at all. So everything felt like two steps forward and one step back.
Getting first one and then two temperature sensors working over the Onewire interface was not too bad. But then we confronted the fact that her laptop couldn't do BluetoothLE -- and I realized that even if we could, we would end up wanting a data logger that would remain after she completed her project. So I recommended we get a Raspberry Pi.
I had expected BluetoothLE to be relatively straightforward. Boy was I surprised. There were a few examples that were provided with the Adafruit Feather: we tried the heart-rate monitor example to start with. But it turned out to be not a good fit for what we were trying to do. It turned out that the implementation is tied to proprietary protocols and there were complicated twists at every level. The heart rate monitor example uses a predefined set of characteristics that are not readily generalizable. After struggling with it for a long time I was on the point of giving up.
After much experimentation, I decided that a generic uart connection would make more sense. But there were a bunch of tricks to getting it to work at all. It turned out I couldn't connect to the device without first doing a "scan" with the adaptor. The python bindings that came from Adafruit didn't work. Eventually, I found pygatt -- a different set of python libraries that (by using a deprecated set of connection tools) I could get to connect more-or-less reliably, and receive data. But it could only send text, so I multiplied the float by 100, rounded to an integer, transmitted the integer as CSV, parsed the CSV with python, and divided by 100, before rebuilding CSV together with a time stamp.
It reminded me a bit of the Galileos I worked with a couple of years ago. https://blog.bierfaristo.com/content/galileo-wrap As an expert, I could work with them and ultimately get them to roll-over and bark. But it wasn't something that I would expect a novice to be able to take on and get anywhere with.
Overall, the experience was very useful to me for the kinds of projects I'm hoping students will do. And I learned a bunch of useful tricks for working with these tools, although there are still a number of hurdles to overcome.
When I was working with pis on the wired network, the technical staff would configure them with a static ip, which made them easy to contact when running in headless mode. But the Makerspace doesn't have wired eithernet and, even when it will, it will probably use the campus services, which generally do dynamic addressing. So I'd like a Pi to report what address it's on to a central location so I can track it. I've adapted some PHP code on the server side to receive and report these data.
You need to set the hostname on the pi and then I've crafted this one-line liner to add to rc.local that, if the network is configured, will report it's IP address.
/usr/bin/wget -O/dev/null -q https://bcrc.bio.umass.edu/pitrack/?pi=`hostname`\&ip=$_IP
Just add inside the test that prints the IP address and done.
I had a good conversation with Tom over weekend about my thinking for my new course. We talked about the structure of the course, using the Software Carpentry lesson template for approaching the technical training aspect, and how the experience I've had helping students manage projects in the writing class will probably be apropos in this class.
"How are you going to have students manage their manuscripts?" Tom asked.
Years ago, I had showed Tom how to get started with LaTeX which he used to great effect in graduate school. He had suggested I use it with the students in my writing class, but I had declined, since I felt the learning curve would be too steep. But this class is different: I'm going to be pressing students to learn to use the command line, to write code, and to manage their projects using git. Building their thesis using LaTeX just seems like a natural extension at that point.
Tom pointed out that CS has a LaTeX template for submitting a thesis to the graduate school. I still need to check with some of the departments (like Math and Astronomy) that are almost certainly already using TeX for honors theses. And it's yet another domain I'll need to spend some time getting back up to speed with. But it's a good idea and should be a lot of fun.
Last spring, I was awarded a Professional Improvement Fellowship which gives me a release from my "regular responsibilities for one semester" to work on the project I had proposed. This is kind of a big deal.
When I arrived at the University, Lo, these many years ago, I was one of relatively few Non-Tenure Track (NTT) faculty. Although, I was hired in at a salary that was competitive with other faculty, there were no promotion opportunities and the conditions for NTT faculty varied widely across the campus. Over the years, we've made huge strides at the bargining table through patient negotiation. In the last contract, we secured a one-semester leave for Senior Lecturers to work on a significant academic project. The first time I applied, I did not receive one, but was awarded one the second time around.
During the fall, in free moments here and there, I began laying the groundwork for my leave. I applied and received some travel money to attend meetings during my professional leave and I submitted a proposal to the Honors College to have my course project fast-tracked for approval as an honors seminar. This proposal was also approved and I have now submitted the official paperwork for the course approval process. And it has cleared the first level of approval. Here's the course description:
In this two 4-credit course sequence, students will build instruments using open science hardware and collect data that bears on a research question. In the first semester, students will explore case studies about creating/deploying instruments combined with hands-on activities to develop technical skills for instrument development. Each technical lesson and activity, modeled on the Software Carpentry curriculum, will lead students through two instrumentation platforms (Raspberry Pi and Arduino) and how to collect, log, and analyze data from analog and digital sensors. Students will post brief weekly "Research Notes". By the end of the first semester, students will have (1) drafted a proposal for a research project and (2) developed a functional prototype of the instrument. During the second semester, students will use Agile project management techniques to collaboratively build, test, and deploy finished versions of their instruments and conduct iterative rounds of calibration and data collection to assemble a data set that bears on their research question. By the end of the course, students will complete an individual thesis using data collected with their instrument and create an "instructable", supplemented with imagery or video, that describes their instrument, how it works, and how to make one.
Now the real work begins.