I started growing hops at my parents’ home in Chicago in 2008. In the summer of 2011 we moved them to Michigan and I built this trellis:
Now that it’s time for the trellis to find a new home, I’m writing up my design for posterity. Notable aspects include that it can be harvested without ascending a ladder and that the top is mounted on a tree.
Each of the three hop plants (Cascade, Mt. Hood, Centennial) has its own starting frame. It runs up the yellow chain for 5 feet, then starts climbing a line up into the trees:
The frames are a 5 foot tall 4″ x 4″ vertical post with a short 2″ x 4″ crossbar at the bottom and a longer one at the top. The ends of the bottom and top crossbars are connected by chains, allowing the hops to spread laterally as they grow out and up to the top crossbar. The chains are attached to metal eyelets at the top and hammered in with large galvanized staples at the bottom:
From the eyelets on the top crossbar, six synthetic rope lines (two from each base frame) run up to a steel ring hoisted in a tree, where they clip on with carabiners:
A pulley wheel is tied around a fork in the tree, and the ring is on a long synthetic line that runs through this pulley wheel. At harvesting time, the ring can be lowered from the ground, using the pulley, and the carabiners unclipped for transporting the bines to a picking area. Then the carabiners are reattached and the lines are raised again, all without use of a ladder.
The good and the bad
With 7 years of experience, I can comment on how the design worked.
Ease of raising and lowering: not having to climb a ladder is great.
Longevity: the entire system has held up well, including the synthetic lines, which I never took in for the winter. I don’t think jute or a similar natural twine would have lasted. One wood staple came out from a frame, which is an easy fix.
Shallow climbing angle. I should have mounted the ring higher in a tree, kept the lines tighter, or planted the hops closer to the tree. As it was, the bottom of the climbing lines flattened out under the weight of the plant and the hops needed some help to grow in the right direction. Manual training of hop plants is not uncommon, but I think a steeper climb would have avoided this.
Mowing around the trellises was tricky, both around the bases and under the lines. This meant grass and other unwanted vegetation encroached on the hops.
I was afraid I’d get tangled in the lines while sledding in my yard; this never happened, but could have.
Separate from my particular growing setup: I lost interest in growing hops. I’ve stopped training or harvesting them. A fresh hop beer is fun to make, but not worth (to me) the hassle of training and maintaining the bines. And trying to preserve and package hops for use throughout the year is tedious. They won’t stay good as long as professionally-packed hops from the store (I know: in one season before I had kids, I spent hours and hours drying my hops and turning them into plugs). Once the charm of growing them wore off, it made no sense to spend my time on growing instead of buying pounds in bulk.
2018-08-23: kegged. I hadn’t stirred in the leaf hops and they had formed a thick layer on top, with the top half being dry. So the practical impact of the dry-hopping will be less than 4 oz for 5 days.
The cider itself was clean but dull before dry-hopping. To test the idea of dry-hopping, I’d pulled a 1 liter sample and added the equivalent of 4 oz Mosiac per 5 gallons. The result was fascinating, like a white wine with tropical fruit notes.
I’ve become inconsistent with taking final gravities, especially if the batch is many months old or is being stabilized. Here it’s both, and I never measured the FG. Let’s assume it’s 1.000 which would be an ABV of 6.5%.
Quick active fermentation. Racked about 16 gallons into the barrel a few weeks later, reserving one 5 gallon share to drink clean.
One participant in the barrel project wasn’t able to participate this round, so we covered his share by adding a carboy of 2-year-old Quadrupel ale I had lying around. It was too dull and boozy to drink and had become slightly oxidized. This will slightly boost the SRM of the combined beer and the other 90% of the fresh beer should cover up the oxidation notes.
Here’s a function that generates a specified number of unique random IDs, of a certain length, in a reproducible way.
There are many reasons you might want a vector of unique random IDs. In this case, I embed my unique IDs in SurveyMonkey links that I send via mail merge. This way I can control the emailing process, rather than having messages come from SurveyMonkey, but I can still identify the respondents. If you are doing this for the same purpose, note that you first need to enable a custom variable in SurveyMonkey! I call mine a for simplicity.
This function could get stuck in the while-loop if your N exceeds the number of unique permutations of alphanumeric strings of length char_len. There are length(pool) ^ char_len permutations available. Under the default value of char_len = 5, that’s 62^5 combinations or 916,132,832. This should not be a problem for most users.
On reproducible randomization
The ability to set the randomization seed is to aid in reproducing the ID vector. If you’re careful, and using version control, you should be able to retrace what you did even without setting seed. There are downsides to setting the same seed each time too, for instance, if your input list gets shuffled and you’re now assigning already-used codes to different users.
No matter how you use this function, think carefully about how to record and reuse values such that IDs stay consistent over time.
Exporting results for mail merging
Here’s what this might look like in practice if you want to generate these IDs, then merge them into SurveyMonkey links and export for sending in a mail merge. In the example below, I generate both English- and Spanish-language links.
I first created Zingibier, a “grand cru” style spiced Belgian ale, in 2010. With beginner’s luck, it won a gold medal in the 2010 National Homebrew Competition, and the recipe is featured on the American Homebrew Association’s website.
The beer is tough to categorize. It’s a strong (~8%) wheat beer that uses a Belgian Witbier yeast and spices typically associated with the Witbier style: coriander, bitter orange peel, and chamomile. It also packs a prominent ginger note, with the ginger sufficiently cooked as to not contribute heat.
Yesterday I had a nice maker win that felt like validation for time spent building confidence in the basics of electronics.
The situation was dire. The Medela Pump-In-Style breast pump was needed immediately. We found the old pump but couldn’t locate its battery pack or AC/DC adapter. It was late and local stores were closed.
On Amazon.com I found the specs for a replacement Medela adapter: output 9V, 1000 mA. Rummaging in my to-be-recycled electronics pile, I found a 9v 1000mA power adapter from an electric pencil sharpener I’d used as a high school teacher. But its prong was too small for the Medela.
More rummaging turned up an adapter prong that did fit, this from the power adapter to an old Asus RT-N16 router (12V, 1.25 amps). I cut each adapter’s cord in half, stripped the wires, attached them with crimp-on butt end splices – noting that the positive wire on each pair was marked with stripes – and voila! The pump worked and saved the day.
Summary: By building a protected cycle path along North Maple Road between Jackson and Miller, Ann Arbor will fill a glaring gap in its transportation infrastructure and significantly improve the quality of life for its west side residents.
Ann Arbor has a conspicuous hole in its bike map (bike lanes in green). Do you see it?
Okay, there are a few gaps. Like most American cities, Ann Arbor’s biking infrastructure is limited, relying on unprotected bike lanes and sharrows (other cities have gone way beyond this). But for the most part, its major thoroughfares have bike lanes. The biggest exception is North Maple Road:
This is an essential transportation corridor. It connects to major bike lanes at the north (Miller), middle (Dexter), and south (Jackson, South Maple, Stadium). And it would break from a downtown-centric rut of thinking by enabling residents of many west side neighborhoods to bike to essentials (groceries, drugstore, library, shopping, Secretary of State), restaurants and entertainment, and community hubs like the amazing Westgate Library.
But it’s supremely unfriendly to bikes. It’s a 4 lane road with nothing to slow speeding traffic; the speed limit is 35 mph, though travel speeds exceed that. This road is not a destination, it’s a way to get somewhere, including serving as the primary route to highways (I-94 and M-14). Cyclists must “take the lane” for safety (the lanes aren’t wide enough for a car to pass a bike at the legal distance of 5 feet) and risk the abuse that comes with braving a car-centric roadway.
In my last 1,500+ miles of biking in Ann Arbor, I’ve only been yelled at to “get on the sidewalk!” three times. That low count is a credit to local drivers. But all three times have been on Maple between Dexter and Miller, despite this stretch comprising only 1-2% of my biking time.
A relatively easy fix would be to apply a “road diet,” going from four lanes to three, and use the extra space for an unprotected bike lane on each side. This would feel like Miller or Packard: much better than North Maple is now – but still insufficiently “safe-feeling” for the average person to feel welcome.
And it would be quite doable. No major construction needed, just a traffic study, resurfacing, repainting. The lanes along this stretch are never full, and a recent closure of one lane each way (for road work) offered proof-of-concept that a single travel lane in each direction, plus a central turn lane, will be sufficient.
This would be doing the minimum. It would work for me, a dedicated cyclist, but most people – regular residents, from 8 to 80 – do not feel comfortable biking on a road with 40 mph traffic whizzing by, separated by a stripe of paint.
No, we can do better. Look at the picture above, and how much room there is to work with. Four lanes, plus large public access strips of grass on each side, plus the sidewalks.
It’s the perfect place for Ann Arbor’s first cycle track.
NACTO describes a cycle track:
an exclusive bike facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. A cycle track is physically separated from motor traffic and distinct from the sidewalk. Cycle tracks have different forms but all share common elements—they provide space that is intended to be exclusively or primarily used for bicycles, and are separated from motor vehicle travel lanes, parking lanes, and sidewalk
There are lots of configurations, but at a minimum this cycle track would be clearly separate from the street, raised to the level of the sidewalk and adjacent to it, and with clear markings for both walkers and bikers.
There’s great food for thought in what other cities are doing. Sure, some European cities are in another league, but there are American cities innovating, too. In the time I’ve been dreaming about this space, I personally saw inspiration in Chicago:
In both cases, I happened to be walking or busing by and thought: we deserve this, too. This is a bike path that a ‘tween could ride to the library with her friend, or that a senior could take to Plum Market.
One two-way cycle track, or two one-way cycle tracks?
I would like to hear from experts on this. A one-way track in each direction seems cleaner to enter and exit, there’s no need to cross the street. And it seems safer as bikes would be traveling in the direction that cars expect.
But a single two-way track on the east side of the road might work better for the Jackson-Dexter stretch (see below).
Two sections: Dexter-Miller and Jackson-Dexter
The bike infrastructure gap on North Maple spans these two sections of North Maple. Dexter to Miller is simple: road diet that includes a turn lane (northbound cars often stop traffic to turn left into the Alano Club).
Between Jackson and Dexter
The two blocks between Dexter and Jackson are trickier. I’m less certain this could be subject to a road diet, at least not the southernmost block. There is more lateral movement of cars in this stretch, including turning into the Maple Village shopping center.
Here’s the middle of the stretch, looking north:
And the southernmost block might be the hardest for integrating bike infrastructure, given the traffic flow to and from Jackson. But it needs something. Approaching the Maple & Jackson intersection by bike, and navigating it, is a daunting feat (made worse by the fact that the approach is uphill and that cars swoop into the right lane to make turns):
(an electric-assist bike helps here, but that’s for another post)
Here is where I think a single, two-way cycle track could have the advantage. The city owns the land on the east side of Maple between Dexter and Jackson. If it’s not suitable to remove car lanes here, the track could be built along the west side of Vets Park without altering the road. There’s currently a footpath here for walkers and skaters and there’s plenty of room for a cycle track next to that (see the north-facing picture above).
Would a one-way cycle track on each side be feasible here? Perhaps a single-direction track could fit on the west side of Maple along Maple Village, for southbound bike traffic. This would provide the benefit of being on the natural side of the road, and access to Maple Village. Though it’s not a big deal to dismount at Dexter & Maple and continue into the mall on foot, and biking along the mall would be less pleasant than biking along Vets park. And the logistics seem trickier. There’s grass next to the footpath on the west side of the street, but ownership isn’t as clear to me (would eminent domain by on the table?) and the final few feet where the cycle track would pass the Shell station seems unsolvable to me.
The one-way and two-way cycle track options could be blended. For instance, take a one-way cycle track on each side between Miller and Dexter. At the point where southbound bikes would need to cross to their left to join the last stretch of cycle track in Vets Park, a clearly demarcated path could be shown on the pavement indicating how to do this via left turn. The bike would make a left turn from the left traffic lane (or from the cycle track, if it had its own turn signal cycle – this is a thing in say, Toronto) and then, instead of continuing east into the city, would make a wider curve onto the sidewalk area and join the cycle track.
This block, an extension of the North Maple Cycle Track discussed above, is also a bike infrastructure gap. And frankly an unpleasant place to travel via any mode: car, bike, foot. It’s often clogged.
If the cycle track is built between Jackson-Miller, attention will then be turned to this stretch, to complete the connection to bike lanes on Stadium and Maple. That would be hugely beneficial. But I don’t have the knowledge to suggest a solution myself. If you have ideas, please comment or write your own post!
Outcomes and feasibility
This post is long enough and others have made the case for the benefits of more biking to a city’s residents, so I won’t do that here. I’ll just note that Ann Arbor would benefit massively terms of health, air quality, environmental impact, social connections, traffic flow (yes, my car-driving friends), and overall happiness. But I will expound on benefits other than the generic ones of increased cycling share.
A calmer traffic flow with more non-motorized travelers would be an improvement for those who live along this stretch, creating a more pleasant atmosphere in their front yards and a safer place for kids and dogs. I’d also like to see the city take on the duty of clearing the cycle track of snow; this could be with a small plow, or using a tractor with a spinning broom, ala Water Hill’s SnowBuddy. With the track elevated next to the sidewalk, this snow removal will be straightforward – and the city can do residents a favor by clearing the adjacent sidewalk while they’re already out brushing. This would increase the perk of living along the cycle track. Construction would be an annoyance, but residents along the cycle track would likely see a bump in their home values as a form of compensation.
While the above benefits would accrue directly to those living along the cycle track, the primary benefit – access to the track – would reach those in many neighborhoods on the west side, on both sides of North Maple. Thousands of people would now find themselves with a comfortable, short bike ride to the essentials.
The cycle track would be good from an equity lens. The city’s premier non-motorized transportation projects are downtown (the proposed cycling improvements on First/Ashley/William) or in wealthier near-downtown neighborhoods like the Old West Side and Water Hill (the “Treeline” urban trail). While all residents and visitors benefit from improvements in downtown, it strengthens the city to have top-notch bike infrastructure outside of the city center. This project would primarily serve middle-class homeowners and renters, as opposed to the Treeline, whose chief beneficiaries would be the more-expensive neighborhoods of the Old West Side.
This project should rank high on the non-motorized transportation list. It compares favorably to the Treeline Trail as actual transportation infrastructure*, while also being a recreation opportunity. Our transportation conversation too often focuses only on getting people in and out of downtown. Downtown is great for restaurants, the Farmer’s Market, the Hands-On Museum – but it’s not where most people live day-to-day life. The North Maple Cycle Track reflects the reality of living on a cul-de-sac in The Crescents and needing parts from the hardware store to fix your sink; living by Hollywood Park and picking up a prescription from Walgreens; a one-car family wanting to attend preschool story time at the library.
How does it happen?
I hope planners and other experts will weigh in, likely with better ideas. I’m an enthusiast but not an expert. A study will be needed to measure car traffic volume. And there are lots of details to figure out.
This is not a small project. It involves pouring concrete to create the cycle track, not just repaving what’s there. So timing-wise, I expect this would be a ways off in the future, perhaps planned to coincide with other necessary construction along this road.
But it’s unquestionable that we must make North Maple Road more accommodating for bikes, opening up access from neighborhoods to the business corridor that is the heart of the west side (stretching from Maple Village to Westgate and then south to Stadium and Maple). We have an opportunity to do better than a buffered bike lane. Let’s show what’s possible and enjoy the city life we deserve.
* the Treeline began life as the Allen Creek Greenway, and its mission of bringing Allen Creek above ground has a significant environmental benefit that should not be dismissed.
A homebrewer friend recently brought a $200 TrailKeg to a club meeting. It is shiny and cool and … a thneed.
Instead, you should use a carbonator cap ($8* as of this writing) and some 1 or 2-liter plastic bottles (free after you drink the seltzer water). While TrailKeg claims superiority over the glass growler, the carbonator-cap-and-PET-bottle (PET = #1 plastic, i.e. a soda bottle) combo delivers in most of the same ways:
Has CO2 input for carbing the beer and keeping/serving it under CO2.
My batch numbers might be mixed up, I may or may not sort that out.
Brewing: brewed March 15th. OG 1.050. Big boilover, long cleanup, but everything went fine on the beer side.
It was an 18 gallon batch, two vessels of pale lager and a third that got an addition to make it a Dark American Lager. To make the dark share, I put a half-pound of crushed Carafa II (or III? See recipe/BCS book) in 2 quarts of hot water, steeped it like a big tea bag til it cooled, then added to fermenter.
Fermentation: fermented in 50F ambient cellar space. Pulled up to 64F for a diacetyl rest around 1.020 gravity, which was 5 days (CCYL lager yeast) and 7 days (single pack pitch of 34/70). Let sit around in 64F for a couple more weeks.
Packaging: kegged the CCYL batch on April 11th, it finished around 1.000 FG for a bit over 6% ABV.
Recipe and batch notes: https://www.brewtoad.com/recipes/light-and-dark-lager-partigyle/brew-logs/153459.