Shipwreck


Imperial Japanese Navy oiler Irō under attack on 30 March 1944, Palau, photo by United States Navy
Imperial Japanese Navy oiler Irō under attack on 30 March 1944, Palau, photo by United States Navy

Among gnarled and twisted branches, small fish on display.

During the quiet afternoon, us humans come for play.

Beneath our playground, a dark labyrinthine tomb.

This wouldn’t be our playground, but for your horrific doom.

I do not come for the fun and play anymore, if ever I visit this site.

I just come to watch the daring fish, all fighting the good fight.

A Letter to Mr. Ishikawa


Mr. Tomimatsu Ishikawa
Mr. Tomimatsu Ishikawa

This is Mr. Tomimatsu Ishikawa (2/28/1918 – 7/17/2013), WW2 veteran, fighter for soldier’s rights, and scuba diver.  He served on a fleet oiler, the Irō, during the war and was one of the few survivors when she was sunk by an American air raid as part of Operation Desecrate One.  In his later life, he advocated for the Japanese government to properly recognize and inter the remains of his comrades who had died aboard the Irō.  On March 30, 2004, at the age of 86 years old, Mr. Ishikawa dove 90 feet to the ship’s wreck and performed a memorial ceremony for his friends.  Partly, the reason for this dive was personal.  He wanted to pay respect to his friends.  The other reason for the dive was to generate media attention and broader awareness about the situation of the Irō.

Yoko and Mr. Ishikawa
Yoko and Mr. Ishikawa

The guide who helped him complete his mission was my friend Yoko Higashide.  She was very close to Mr. Ishikawa and regarded him as a grandfather.  Before her meeting Mr. Ishikawa, Yoko had limited knowledge about the shipwrecks of Palau.  She had worked there as a dive guide for two years without knowing that there were any shipwrecks.  It was only when she started working at Fish ‘n’ Fins, an international dive shop, that Yoko started to know about the WW2 history of Palau.  Even as she would lead dives to the wrecks, she always felt bad to be diving on them.  In her words, “It’s like we are playing at a graveyard”.

Me holding my letter to Mr. Ishikawa
Me holding my letter to Mr. Ishikawa

In the summer of 2007, I had the privilege to go diving in Palau.  One of the dives I went on was the Irō.  It was not the first time I had been there, but this time was different because my guide was Yoko.  She explained to me about the ship’s history and told me Mr. Ishikawa’s story.  I was inspired by his determination to return to the Irō, even though it was deep and he was 86 years old.  I asked Yoko if she could help me write a letter in Japanese to Mr. Ishikawa.  I wanted to let him know that I was an American who was moved by his mission to pay respect to his fallen comrades.  You can see my letter to him at the bottom of this blog post.  To my surprise, he wrote me back a long letter.  Although I mailed him again in 2009, that was the end of our correspondence.  For me, though, the one letter was enough.  Our lives were connected from then on.

Mr. Ishikawa praying for his comrades
Mr. Ishikawa praying for his comrades

Now, when I dive on war wrecks I am reflective of the human suffering that led the ships to be where they are.  So I do not consider wreck diving to be a leisurely activity like diving on a reef.  It is a somber activity like visiting a graveyard or the site of an old battle.  It is important to go there to remember our history.  Regarding my experience of writing a letter to Mr. Ishikawa, I think it is a truly great thing that even though Japan and the USA fought bitterly within his lifetime, he still lived to see the day when Yoko and I could be friends and enjoy scuba diving together.  I hope that I can always be a peaceful person and make him smile down from heaven.

Please read Mr. Ishikawa’s story by Yoko.  It is the second link in the Related Media below.

Related Media:

Memorial Video of Mr. Ishikawa

Mr. Ishikawa’s Story by Yoko Higashide

Returning Mr. Ishikawa’s Ashes to the Iro by Yoko Higashide

Daniel’s Letter in English

Daniel’s Letter in Japanese (Typed)

Daniel’s Letter in Japanese (Handwritten)

Mr. Ishikawa’s Reply Letter

Beer Golf


Neon Beer Pong Sign

Introduction:

Beer Golf is a game played with ping pong balls, plastic cups, and beer.  It is played by my friends and I as an alternative to Beer Pong, another popular drinking game that we all enjoy playing.  With Beer Golf, your entire household becomes a golf course where each “hole” is an opportunity to drink.

Necessary Equipment:

A plastic cup

Ping pong balls for all players

A permanent ink marker

Plenty of beer

Number of Players:

Two or more people*

* Update: My friend assures me that the maximum number of players is four.  Not being a golfer, I was unaware of this Pace of Play rule.

Rules:

  • Use the permanent ink marker to mark everyone’s ping pong ball with a name or symbol so it can be distinguished.
  • Fill the plastic cup with beer and choose a starting location for it somewhere in the house.
  • Choose the starting location for players.
  • Choose a par for the cup.  The par shouldn’t be too hard or too easy.  More on this later.
  • Each player takes turns throwing their ball towards the plastic cup.  Both the player’s feet must be behind the resting place of their ball.  The player is allowed to lean forward.  The player is allowed to leap and take jump shots so long as they do not step over the line.  The player is not allowed to brace themselves on furniture or other objects.
  • As with golf, the person who is the furthest away from the cup shoots.
  • The person who wins the cup gets to decide the cup location and par for the next cup.  Players start shooting from the location of the previous cup.

Drinking Rules:

  • The player with the most shots to complete the cup has to drink the beer in the cup.
  • If the player who decided the cup location and par shoots above that par, they automatically lose the cup and have to drink the beer in the cup.  This prevents people from choosing ridiculous hard cup.
  • Everyone who shoots below par gets to assign drinks to other players.  They can assign as many drinks as how far below par they were.  This prevents people from choosing ridiculously easy cups.
  • Everyone has to have a beer in their hand at all times.  Rule breakers have to drink.  The only exception to this rule is if you are playing with the Caddy Rule.

Caddy Rule:

  • If there aren’t enough balls for everyone who wants to play, you can play with the Caddy Rule.  Essentially the loser of the previous cup has to be the caddy for the winner (and is no longer an active player on the next cup).  They are required to hold the beer for the player, fill the cup with beer and place it at the chosen starting location, offer advice to the player, and compliment the player when they make a good shot.

Slightly Euphoric


Om in Lotus from opallueur.tumblr.com
Om in Lotus from opallueur.tumblr.com

I try to use words to encompass meaning. To better describe, I use more words. Sometimes I try to find the one word that would encompass all meaning. What would that word be? OM? Maybe, if I was a Hindu. So here we are again, describing the same uncertainty that a relativist view will always but unfortunately lead to. Yet here in the hopelessness of the problem, perhaps there is an answer. Not so much a “truth” that I can know is right. This answer is a different, more euphoric answer. I know it not. But as I reflect on it, I smile and I write. The moment will be fleeting. For as each blog post begins, surely it ends. My euphoria just like my pain; only temporary. But if I really knew this, I would know a “truth”. And as I said, I bear no truths… only an answer.

Calendoo – a Google Apps Script


Google Apps Script
Google Apps Script

Recently I discovered Google Apps Script, a comprehensive system for automating your Google accessories (Gmail, Drive, Calendar, Tasks, etc.).  It includes a web IDE for writing JavaScript code and easy-to-use API’s for each Google accessory.  When you finish writing your scripts, you can save them to your Google Drive and set up triggers to have them run automatically.  Within a few hours of discovery, I had written my own Google Apps Script, which I will now share with you.

First a little background on the problem I needed to solve.  I use the Google Calendar extensively.  In addition to the regular events I put on my calendar (lunch with friends, doctor appointment, anniversary), I also put reminders for tasks that need to get done.  I realize that Google already has a Tasks list for this very purpose.  Call me crazy but I find it easier to whip out the Calendar app on my phone and insert a new event.  The only problem is that I also procrastinate.  Weeks will go by and the task’s calendar event is still languishing on my Calendar.  At the end of every month, I have to clean up my Calendar and decide which tasks are actually important or not.  The ones that are all have to be moved to the next month.

Enter my new Google Apps Script, Calendoo.  Calendoo looks at yesterday’s calendar events and either advances them into the future, if they’re important, or moves them off the Calendar and into a Tasks list (called TasksFreezer), if they are unwanted.  In order for Calendoo to recognize which events belong where, you simply add a Calendoo symbol in the name of your calendar event.  The Calendoo symbols are as follows:

:. (colon period) = Unimportant event, advance yesterday’s unimportant events to next month.

:! (colon exclamation-point) = Important event, advance yesterday’s important events to today.

:? (colon question-mark) = Semi-important event, advance yesterday’s semi-important events to next week.

:- (colon dash) = Unwanted event, take it off the calendar and put it in the TasksFreezer Tasks list.

:+ (colon plus) = Wanted task, take it off the TasksFreezer Tasks list and put it on the calendar today at noon.

If you want to use the Calendoo script, read on for an explanation of how to set it up.

Google Apps Script: Make a copy
Google Apps Script: Make a copy

1. Import the script into your own Google Drive

Click on the link at the bottom of this blog post.  The Google Apps Script IDE page should open up showing the Calendoo code.  Click the [File] menu and choose [Make a copy].  The Calendoo script should be downloaded to your own Google Drive.  Access it by going to drive.google.com.  The Calendoo script file should be in your root folder.  Click on it to open it.  At this point, you may have to go through a wizard for installing Google Apps Scripts in Google Drive if this is your first time using them.  The Google Apps Script IDE should open again, this time with the Calendoo script installed in your own Google Drive.

Advanced Google Services Dialog
Advanced Google Services Dialog

2. Set up APIs and Permissions for the script

Next, click on the [Resources] menu and choose [Advanced Google services].  An Advanced Google services dialog will appear.  Next to Tasks API, click the radio button to turn it on.  This allows the code to access Tasks API functionality (used for managing Task lists in your calendar).

Google Developers Console Page
Google Developers Console Page

Now you will need to enable the services.  Click the [Google Developers Console] link at the bottom of the dialog.  The Google Developer Console website should open.  In the list of APIs, click the radio buttons next to Calendar API and Tasks API to turn these services on.  Now close the Google Developers Console page and the Advanced Google services dialog.

Run the processEvents Function
Run the processEvents Function

Back in the Google Apps Script IDE, we need to run a function in the Calendoo script so it can request permissions from you the user (yes, this step is a little strange, I know).  Click on the [Run] menu and choose the [processEvents] function.  A dialog will appear saying, “This app would like to: manage your calendars, manage yours tasks, view your tasks”.  Accept the dialog and it will close.  The Calendoo app is ready for action, we just need to pull the trigger.

3. Set up a trigger for the script

Current Project's Triggers
Current Project’s Triggers

To create a trigger to run the script periodically, click on the [Resources] menu and choose [Current project’s triggers].  A dialog will appear with a link, “No triggers set up. Click here to add one now”.  Click on that link.  The dialog will now show the options for our new trigger.

New Project Trigger
New Project Trigger

Choose to run the processEvents function.  This is the main function that drives the entire Calendoo script.  Make the event Time-driven and set it to run everyday at Midnight to 1am.  This will cause the processEvents function to be executed everyday at midnight, pushing yesterday’s events forward.  Click Save.  The Calendoo script is now completely configured for your Google account.  Hurrah!

I hope you enjoy the Calendoo script.

Click here to view the Calendoo script and use it for your own Google Calendar.

Digitizing Old LEGOmation Movies


Elgato EyeTV Hybrid
Elgato EyeTV Hybrid

I recently got my hands on an Elgato EyeTV Hybrid which lets me connect my MacBook Pro to a VHS player.  After a relatively easy setup, I am now able to play the tapes on the VHS player and save them to the MacBook in a digital format.  Finally, all of my old home videos can be brought into the digital age.  As exciting as this is, it also scares me.  Most of my home videos are completely ridiculous.  I would be embarrassed if the internet bore evidence to what kind of a weird kid I was.

Really though, these videos are already part of the public domain in a limited sense.  That’s because when I was ten years old, my sister, my cousin, and I had our own Public Access TV Show.  For those too young to remember, Public Access was a local TV station in most cities that aired shows created by anyone who wanted to pay for one.  The way it worked was that you would send in your content (on VHS tape) and it would be aired at whatever time slot you had received from the station.  The idea seems almost paleolithic compared to today where anyone can create a YouTube channel and share videos with the entire world in literally a matter of seconds.

Monk and Moo
Monk and Moo

Our TV show was called Monk and Moo.  Monk (short for Monkey) was my cousin.  She was the camera person and director.  My sister was Moo, the lead actress, host, and producer.  My role on the show was as more of an extra, filling in when necessary and doing small sketches (my name didn’t make it to the title of the show either).  My major contributions to Monk and Moo were my animation shorts.  I made several of these kinds of clips where I would use my LEGO’s and do a kind of animation called stop motion animation.  The master of this style is, of course, Ray Harryhausen.

Ray Harryhausen and the Medusa
Ray Harryhausen and the Medusa

The premise of stop motion animation is simple.  First, you place the objects being animated in a position.  Then you film that frame of the scene for a split second and stop the video.  Rinse and repeat.  The result is a jerky but consistent sequence of film where your object appears to move around.  Granted I wasn’t a master of this technique.  Most my videos feature at least one second of footage where you can see my hand placing a LEGO guy because I didn’t correctly stop or start the film.

Another stumbling block I had when doing stop motion animation was that I could only have dialog and music if I left the camera filming.  If I kept the music playing while starting and stopping the film, the result was a choppy garbled mess of a sound track.  Such was the result of my first attempt at LEGO-mation.

Some samples of my LEGO-mation movies are below:

Thoughts and Musings by Daniel Bank