Open Source Ecology - User contributions [en]

Team Wikispeed

2013-10-20T14:08:39Z

Andrewed: /* Wikispeed Tenents */ Corrected spelling of tenet

==TED talk:==
<html><iframe width="560" height="315" src="https://www.youtube.com/embed//x8jdx-lf2Dw" frameborder="0" allowfullscreen></iframe></html>

=Team Wikispeed=
[http://www.wikispeed.com/ Wikispeed] is a team of volunteers that formed around the work of [http://www.linkedin.com/profile/view?id=4583874&authType=NAME_SEARCH&authToken=y3gN&locale=en_US&srchid=f5fc9cc6-0258-4503-b0b3-92382aac28b1-0&srchindex=1&srchtotal=1&goback=%2Efps_PBCK_joe+justice+wikispeed_*1_*1_*1_*1_*1_*1_*2_*1_Y_*1_*1_*1_false_1_R_*1_*51_*1_*51_true_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2&pvs=ps&trk=pp_profile_name_link Joe Justice] as he competed in the [http://www.progressiveautoxprize.org/teams/wikispeed Progressive Insurance Automotive X-Prize]. His greatest innovation was applying [http://en.wikipedia.org/wiki/Scrum_(development) lean/agile/SCRUM] software program management to hardware, specifically the iterative design of a 100+ mpg passenger vehicle.

The dramatic success of Team Wikispeed's activities pretty much demands listening to what Joe has to say.

For clarity, and because I wasn't clear on this point until I researched it, it is important to point out that Team Wikispeed was eliminated in the first round of on-location testing at the X-Prize competition. "Without even bothering to look at the finite element analysis and computational fluid dynamics Justice had brought as proof of his design’s validity, the inspector rejected the car outright. Justice felt like he’d been slapped in the face. “It was like fireworks going off in my cheeks,” he says. “This is something I’ve had a whole lot of design input into, and this one person is saying, ‘This isn’t good enough.’...Rather than spending hours pulling apart the SGT01 to get to the suspension, the team simply unbolted the body, removed the suspension module, and began fabricating a new one. They got it done, too, just in time. The only problem was that as they finished, minutes before the deadline, Justice and another team member cut a wire in the electrical system. The car wouldn’t start, and Wikispeed’s run for the X Prize was done. They finished in a tie for 10th in their division." [http://www.seattlemet.com/issues/archives/articles/wikispeeds-100-mpg-car-january-2011/3/ article]

===General===
* First functional prototype built in 3 months.
* Existing manufacturing processes are slow to change because they're exceptionally expensive to change.
** Major manufacturers typically operate on 10-25 year design cycles.
* Wikispeed uses 7-day design cycles.
* Iterated a process that brought the cost/time of a full structural carbon fiber car body down from $36,000/3 months to $800/3 days.
* Went from 1 guy in his garage to 100+ volunteers, in 8 countries, and a production-ready car in 6 months.

===Specific===
* Modularity.
** Every system in the car can be separated from every other system as quickly and easily as changing a tire.
* Test-based.
** The customer-value standard, and the test for it, is designed BEFORE the solution is designed.
* Use less stuff.
** The parts for the frame of the car can be built with stock 4" aluminum tube, an $80 band saw, and a used-kit-built CNC milling machine.
** Reduce costs in tooling, machinery and complexity wherever possible. This allows for improvements to be incorporated into the design immediately because there are so few sunk costs.
* Distributed, collaborative teams.
** Use free online tools.
* Morale for velocity.
** It's not additive or subtractive, it's a multiplier.
* Work in pairs.
** Put a newbie with a pro and the newbie learns AS the job gets done. This eliminates time devoted to training. The pro gets help, the newbie gets hands-on experience.
** Also eliminates the need for most types of documentation.
* Visualize workflow to eliminate any time spent not creatively solving problems.

==Keynote American Council of Engineering Companies==
<html><iframe width="560" height="315" src="https://www.youtube.com/embed//I3HXw0Ruz9M" frameborder="0" allowfullscreen></iframe></html>

==Summary: Scrum Gathering in Seattle==
<html><iframe width="560" height="315" src="https://www.youtube.com/embed//pjempylJy1w" frameborder="0" allowfullscreen></iframe></html>

This is a summary of the talk:
===History===
* Initial Goal: build the lightest chassis.
* Share on the blog
** asked silly and nerdy questions
* passes technical deliverables for the [http://www.xprize.org/ X prize].
** became finalist to compete with 136 cars, most of them funded by millions of dollars
** iterating the car at the race track, inspired a higher driver of a team competing against WikiSpeed to spend a lot of time hanging out with the Team.
** got 10th place.
** Received several tens of thousands of dollars in road legal certification and testing.
** Press
* Team grew: 56 members in 6 countries.

===Learned===

* Contract-first Design: by Modules.
** Suspension - changed for 10 minutes - adjustable in caster, tow?, camber, wheel-base and track, individually per wheel.
** Interior in the race car version - aluminum bathtub that lifts out. The 4-seat interior for the contest can be easily exchanged with the 2-seat interior for testing.
** Engine - at the back of the car. The entire Power Train, with its transmission, fuel tank and cooling system can be rolled out in the time it takes to change a tire while it is running. This let us have one engine on the test bench being evaluated and another engine in the car doing testing, bring the car, switch the engines, test the other one - able to develop and test engines independently of each other.
** Chassis - all other modules connect to. Side, front, front impact. Peak stress. Our entire car absorbs the weight. 5 star crash rating equivalence.
** Car Body - cut foam with CNC machine from a CAD design, sand it, (70 volunteers in 6 countries in multiple locations)
*** from Structural Carbon Fiber (normally used in airspace and exotic automobiles) was really expensive, but the material itself wasn't expensive, but the knowledge how to use it was. So Joe Justice went to composite school for few weeks and then they built the carbon fiber body for $800 in 3 days (body would cost $36,000 in 3 months time with traditional manufacturing techniques).
* Went to [http://www.naias.com/ North American International Auto Show] - put WikiSpeed on the main floor between Ford and Chevrolet. Met the creator of the car body, Rob Mohrbacher of http://mohrcomposites.com from [http://en.wikipedia.org/wiki/Germantown,_Montgomery_County,_Maryland Germantown, Maryland].

===How - Agile and Scrum===

* Weekly stand-up meetings
* prioritized backlogs
* and demos

====Tools====
* FreeConferenceCall - for stand-up meeting
** What I did, what I will do, what is blocking me
* Skype free
* Google Groups - up-to-date daily, pictures, updates, backlog from a Google Doc
* Google Docs - documents collaboration
** Trust the Team. It is versioned - who changed, what when. Can be reverted.
* Avoid planning more than 2 weeks out - we learn so fast that things change what we will do next
* Facebook and LinkedIn for team and public status updates.
** don't repeat information sharing.
* DropBox and SkyDrive for sharing large files
* Youtube to share videos
* Scrumy - online project management tool loosely based on Scrum.
* Linoit.com - for backlog http://linoit.com
* LibreCAD - open source CAD for Windows, Apple, Linux
* Email Lists
** Always Reply All to approximate being in a Scrum room. Allows distributed team to skim emails and be appraised of the current state of the project.<ref>http://futureofprojectmanagement.com/2011/12/02/joe-justice-built-a-100mpg-car-using-principles-of-agile-lean-and-scrum-how-did-he-do-it/</ref>

====Principles - What worked well====
* By minimizing cost of making change we innovate quickly. Changes in team members, changes in goals, changes in machinery, changes materials.
* By loosely coupling modules, we make changes in parallel.
** E.g. split the car into its component modules. Have people working on the suspension system, drive train, emission system, headlights, electronic control mechanism, all in parallel.
** Modularity: Interior module, Chassis, Pedal Plate, Front Crush Structure, Suspension Module, Engine, Transmission, Fuel System, Emission System, Fuel Injection System, Breaking system.
** When we started designing the car, we didn't know how the chassis would end up being like, we didn't know what type of drive train, type of suspension, we will be using. So what we wanted to do is to reduce the cost to make change between those parts. So we architect a contract - the way these modules will talk to each other and hold together in a structural way and the way they communicate.
* By working collaboratively and in shared space we unblock quickly.
** E.g. every time we had a blocking issues the team was able to bulldoze it that same day. Pairing and Swarming worked very well.
* By first automating test we quickly know if we improved. (Test-driven manufacturing)
** Example
*** 100mpg on a highway cycle
*** etc.
** When changes came we quickly knew whether we moved entirely forward, or moved forward on a few fronts, but actually backed on to other fronts. So we had to quickly kill work that would have been actually damaging and thus we were moving forward very fast.
* Test our success criteria - everyone cared about the metrics!
* Team morale (motivation) is a multiplier for velocity.
** Make sure people are never or rarely frustrated and that they get to share successes. Celebrating every iteration.
* Team trust is empowering
** Question access restrictions on documents, avoid group subjugation. Empowerment keeps velocity high.
* Single Backlog - all prioritized tasks are visible and in one place

====Modular Inventory====
* Whenever possible tools are visually next to their consumables.
* Fewest possible categories always inside of each other (See everything from where you stand)
* Minimize time spent doing anything but creative problem solving.
** E.g. - So it’s not just less meetings, less paperwork, but in our case it is that we have a transparent bin that has screw drivers. And every screw driver is in there. There is not a screw driver anywhere else. If someone needs a screwdriver, it’s at a central location not more than twenty steps away. And it’s a clear bin so that they can see if what they need is inside before they even get there. In fact they can see what’s in there across the room and it is labeled. In software teams we would do the same thing with templates, we would do the same thing with test driven development, we would do the same thing with class naming and interface design, so people understand what goes with what. (See references)

====From Software====
* Agile - reduse cost to make change and iterative development
* Test-Driven Design - tester and manufacturing
* XP - pairing and swarming
* [http://en.wikipedia.org/wiki/Scrum_(development) Scrum] - almost everything. Clearly defined roles and responsibilities.
* OOP - clearly defined modules, classes and interfaces
* [http://en.wikipedia.org/wiki/Kanban_(development) Kanban] - work in progress limits, not to overload people.
* Contract First Development - Define precise and verifiable component interface specifications.

====Wikispeed Future Developments====
* Making a family car
* Developing a truck

=Wikispeed Tenets=

* If I give money, time, cookies or supplies to WIKISPEED, and WIKISPEED is profitable, WIKISPEED will pay me back the value of what I put in plus interest commensurable with their level of success. I can choose not to accept repayment, but WIKISPEED will make reasonable attempts. This is based on value, not quantity (in hours, pounds, dollars, or word count).
* If I give money, time, cookies or supplies to WIKISPEED, I have no claim on WIKISPEED or its decisions or what it does with my resources after I give them. Other than tenant 1 above.
* If I share my best thoughts and work with WIKISPEED, WIKISPEED can use them at no cost, and I retain rights to re-use or protect my ideas unless I opt to bequeath them to WIKISPEED or the Public Domain.

=Wikispeed Principles=

* Equitable Distribution of Wealth.
* Avoid profit from waste (e.g. buying a competitor to shut them down). Grow profit based on visible value.
* If we focus on profit over value to customers, we will obtain neither. If we focus on visible customer value over profit, we will profit.
* Use less stuff (Lean) wherever responsible.
* Make decisions at the last responsible moment, this is when we know the most. but be careful not to wait until it is no-longer responsible. We never make a decision before we have to just to "get it out of the way."
* Start with the minimum useful solution (porters on roller-skates over a mail-chute), then iterate aggressively to improve visible value and efficient sustainability of the solution.
* Morale is a multiplier for velocity.
* We trade estimated future states for knowing the most about our current situation and make changes quickly (Agility).
* Trust our team. this avoids a culture of CYA, which slows down innovation and kills morale. e.g. a company which spends $6 million on intranet security allowing employees to not see documents above their salary level to avoid leaking potentially libelous documents, instead of $6 million having interns and attorneys aggressively helping all levels of the org identify documents that are potentially libelous, which are usually a sign of unethical action, coach them on how to rectify those situations ASAP as a company with help from all levels of the company).
* Replace a document with a conversation. Instead of writing a specification document, have a white boarding conversation in a room where as many other team members as possible can over-hear. Take pictures of the white board when you are done and email the team. Documents have a maintenance cost.
* Produce self-documenting work- a car with a navigation that teaches you how to use it instead of a manual. Can you imagine if Internet Explorer still shipped with a manual? We expect it to be self explanatory. Documents are a hidden expense, requiring editing and re-write to match the current version.
* Try not to do something alone, pair with another team member whenever responsible. This aids in knowledge transfer and avoids requirements for documentation.

=References=

*CNN on Management a la Wikispeed - [http://management.fortune.cnn.com/2012/06/18/how-companies-ought-to-train-their-staffers/]
*[http://agileinc.wordpress.com/on-the-road-3/sglon/]
*[http://futureofprojectmanagement.com/2011/12/02/joe-justice-built-a-100mpg-car-using-principles-of-agile-lean-and-scrum-how-did-he-do-it/]
{{Reflist}}
[[Category:Wikispeed]]
[[Category:Open Source Automobile]]

Hexayurt construction

2009-05-28T18:09:34Z

Andrewed: /* Hexayurt Review */

==Introduction==

This article is intended to provide a detailed description of the construction of the hexayurt so that the successes can be replicated and the few mistakes can be avoided.

The design applied at Factor E Farm as the Paul Newman Center for Temporary Housing (kind of kidding... Rob, call it what you like) was a perfect hexagon with 6' walls, 10' peak, and 14' foot width. It will comfortably house 3-4 people and should last about 10 years, given precautions taken. It is a tension structure, so that the building itself will give it structural support.

Rob, who has a history and family background in building construction, was quite skeptical of the structural integrity of the building. It proved to be excellent, and come together better than was thought.

==Step 1: Materials==

Materials aquired were 14? 4x8 OSB boards
100' of metal flashing (about 5-6" wide, and of substantial thickness)
about 18 2x4s (for the roof, they dont need to be anything too fancy, we used salvaged wood that was fairly thin)
Lots of screws (we used drywall, though we would encourage stainless steel)
Paint
Tar (dont need too much)
Gravel (for the foundation)
Vinyl steal material (this was an extra precaution)

==Step 2:Painting and Tarring, Site Prep and Foundation==

'''Painting and Tarring'''

The next step was to paint and tar the OSB boards. All of the OSB boards were painted on all edges, as OSB's weakness is moisture on the ends, which causes it to swell and rot. The paint applied on the edges, corners and such 3 inches in to the board should quell this.

Additionally, Tar was applied to the bottom edge of 6 of the OSB boards, about 4 inches in, so that high water would be deterred from any prolonged exposure to the boards.

'''Site Prep and Foundation'''

We used open engineered technology for site prep! but any rototiller will do. We used the lifetrac with open rototiller to break up the soil, then we went through, measured everything out, ensured there was more than enough space for the walls, then pulled out roots, broke up clumps, and leveled it out with the rakes, and in the process stomped it down with our boots. We used a 2x4 and level to ensure the grade was correct.

Then, we dumped gravel at the assumed edges of the structure, measured it out, and then tamped it down at about 5-6 in wide by 3 in thick, leaving space for a door.

Also, make sure to clear the area from any meddling chickens. (Richard: One of them left a little gift for me on the ground that my hand discovered while making the wall panels)

==Step 3: Cutting==

After the paint and tar dries, the next step is to start cutting the boards.
Because we decided on 6' walls instead of 8', we were able to eliminate 3 OSB boards from the materials list and cut 3 in half for the topmost board.

-So, cut 3 OSB boards in half, making them 2'x8'.

-Cut 6 OSB boards in half diagonally, corner to corner for the pinweel roof (take extra precaution to ensure that these are straight and true, as they will ensure that the roof comes together well in the end. Also, if you are using foiled boards, cut them in half in opposite ways, so as to provide all foil on top)

-Cut 12 2x4s to have a long edge and a short edge, at a 30 degree angle, so that they can be linked together inside horizontally and form the hexagon with the walls

-Cut flashing strips into 6 8' strips and 6 6' strips for the walls, then additionally 6 more 8' strips for the roof

-Using a hammer punch, punch along roof strips and wall strips all along the edge, about 2-3cm in from the edge, making double punches near the ends. For the vertical wall strips, make sure that they are more dense. 2 people can set up a process doing this and have it done very quickly. Make sure to wear gloves as the flashing has sharp edges!!! (richard: i learned this the hard way. twice...)

For speed, have one small team cutting and punching flashing while another team draws and cuts board.

==Step 4: Panel Construction==

'''Wall Panels'''

With tar side down, attach 4'x8' OSB boards to 2'x4' boards, using the 2x4 with the long edge against the boards. Ensure that they are all flush, and that the 2x4 is evenly attached to both boards!

After this, attach flashing strip to one edge (left or right, doesnt matter, just keep it consistent throughout).

A trick Rob discovered with the flashing, to keep it flush as possible with the board, is to use the screw gun at an angle, pointing away towards the loose flashing end. It doesnt need to be an extreme angle, just enough to pull it taught when the head goes in.

Then, attach the flashing and the topmost 2x4 to the top of the 2'x4' OSB board. Leave a consistent space between the top of the 2x4 and the top of the OSB board (we left about 1/4 in). This makes placing the roof much easier and safer.

When attaching any of the flashing, ensure that you are placing less than half (more like a third) of the width of the flashing on the 1st board. This will ensure a good amount will be left to attach to the other board, whether roof or wall, given that the angle between will take up some of that width.

'''Roof Panels'''

Make a triangle with the panel pieces, screwing them into the 2x4 underneath evenly. Ensure that all is flush and that the bottom edge of the 2x4 is far enough away from the bottom edge of the panel to ensure that it wont get in the way when raising the roof. These 2x4s do not need to attach to the rest of the frame, as the roof is self supporting.

Then, like the wall panels, attach flashing consistently on one side, leaving width space for angle and attachment.

==External Links==

[http://www.appropedia.org/Hexayurt http://www.appropedia.org/Hexayurt] - Appropedia site on the hexayurt, tons of info.

[http://www.appropedia.org/Hexayurt_playa_checklist http://www.appropedia.org/Hexayurt_playa_checklist] - More specifically, assembly instructions for the one Vinay built on the playa at burning man. Lots of options for construction now!

=Hexayurt Review=
[[User:Jeremy|Jeremy]] 10:12, 13 February 2009 (PST)
I tried living in the hexayurt for a little while, here are my thoughts. It was in November 2008. Weather was cold but not much rain or snow yet. Yurt was quite sturdy and kept the wind and water out, but was cold inside. Before Bob left we put the 55 gal. drum stove in and cut a hole in the side for the flue that had two bends. The stove was and is a difficulty, hard to light and very smoky. I slept on the futon mattress we had on the dirt floor of the yurt at the time. The floor was still kind of damp, I guess it was built when the ground was not entirely dry or water had gotten under the walls underground. In the morning it seemed very damp inside the yurt, which I think was from the damp ground. I don't know how it would be if it had a good stove.

Nick took over the yurt when he came here. We moved the stove and had the flue go straight up to have a better thermal draw. With the stove going the yurt is pretty warm, but the door needs to be opened a lot to let the smoke out. It doesn't have insulation so it cools off quickly without a fire constantly going. The drum stove either burns out quickly and leaves the yurt cold in the morning or burns extremely hot and smoky all night making the yurt almost too hot and smoky to stay in. A good stove might leave it still pretty cold in the morning but it could be fired up easily and the temperature regulated better. Smoke still seems like a problem to me, even with a good stove in the cordwood hut.
[Image:Hexayurt.JPG]

--[[User:Vinay Gupta|Vinay Gupta]] 16:05, 13 February 2009 (PST)
Ah, yes, I'm not surprised than an uninsulated plywood structure was cold in winter. The Hexayurt geometry does not have decisive advantages in heat retention over other building shapes.

--[[User:Andrewed|Andrewed]] 04:19, 26 May 2009 (UTC)
Your results are perfectly consistent with any use of an uninsulated structure on exposed dirt in winter in Missouri, with a poorly functioning stove. Even 1" styrofoam boards on the ceiling, 1/2" styrofoam boards on the walls, and a plastic tarp on the floor would have helped you immensely. Also, the use of a rocket stove from Aprovecho in Oregon (plans available from them) or the very cheap [http://www.woodgas-stove.com woodgas stove] that Vinay recommends on his website would have kept you warm without the extreme hassle with smoke and complicated chimneys that you suffered. Better luck this winter?
[[Category:Housing]]

User:Andrewed

2009-05-26T04:21:04Z

Andrewed: Created page with 'Andrew Durham philosopher darknessconjecture.wordpress.com'

Andrew Durham
philosopher
darknessconjecture.wordpress.com

Hexayurt construction

2009-05-26T04:19:52Z

Andrewed: /* Hexayurt Review */

==Introduction==

This article is intended to provide a detailed description of the construction of the hexayurt so that the successes can be replicated and the few mistakes can be avoided.

The design applied at Factor E Farm as the Paul Newman Center for Temporary Housing (kind of kidding... Rob, call it what you like) was a perfect hexagon with 6' walls, 10' peak, and 14' foot width. It will comfortably house 3-4 people and should last about 10 years, given precautions taken. It is a tension structure, so that the building itself will give it structural support.

Rob, who has a history and family background in building construction, was quite skeptical of the structural integrity of the building. It proved to be excellent, and come together better than was thought.

==Step 1: Materials==

Materials aquired were 14? 4x8 OSB boards
100' of metal flashing (about 5-6" wide, and of substantial thickness)
about 18 2x4s (for the roof, they dont need to be anything too fancy, we used salvaged wood that was fairly thin)
Lots of screws (we used drywall, though we would encourage stainless steel)
Paint
Tar (dont need too much)
Gravel (for the foundation)
Vinyl steal material (this was an extra precaution)

==Step 2:Painting and Tarring, Site Prep and Foundation==

'''Painting and Tarring'''

The next step was to paint and tar the OSB boards. All of the OSB boards were painted on all edges, as OSB's weakness is moisture on the ends, which causes it to swell and rot. The paint applied on the edges, corners and such 3 inches in to the board should quell this.

Additionally, Tar was applied to the bottom edge of 6 of the OSB boards, about 4 inches in, so that high water would be deterred from any prolonged exposure to the boards.

'''Site Prep and Foundation'''

We used open engineered technology for site prep! but any rototiller will do. We used the lifetrac with open rototiller to break up the soil, then we went through, measured everything out, ensured there was more than enough space for the walls, then pulled out roots, broke up clumps, and leveled it out with the rakes, and in the process stomped it down with our boots. We used a 2x4 and level to ensure the grade was correct.

Then, we dumped gravel at the assumed edges of the structure, measured it out, and then tamped it down at about 5-6 in wide by 3 in thick, leaving space for a door.

Also, make sure to clear the area from any meddling chickens. (Richard: One of them left a little gift for me on the ground that my hand discovered while making the wall panels)

==Step 3: Cutting==

After the paint and tar dries, the next step is to start cutting the boards.
Because we decided on 6' walls instead of 8', we were able to eliminate 3 OSB boards from the materials list and cut 3 in half for the topmost board.

-So, cut 3 OSB boards in half, making them 2'x8'.

-Cut 6 OSB boards in half diagonally, corner to corner for the pinweel roof (take extra precaution to ensure that these are straight and true, as they will ensure that the roof comes together well in the end. Also, if you are using foiled boards, cut them in half in opposite ways, so as to provide all foil on top)

-Cut 12 2x4s to have a long edge and a short edge, at a 30 degree angle, so that they can be linked together inside horizontally and form the hexagon with the walls

-Cut flashing strips into 6 8' strips and 6 6' strips for the walls, then additionally 6 more 8' strips for the roof

-Using a hammer punch, punch along roof strips and wall strips all along the edge, about 2-3cm in from the edge, making double punches near the ends. For the vertical wall strips, make sure that they are more dense. 2 people can set up a process doing this and have it done very quickly. Make sure to wear gloves as the flashing has sharp edges!!! (richard: i learned this the hard way. twice...)

For speed, have one small team cutting and punching flashing while another team draws and cuts board.

==Step 4: Panel Construction==

'''Wall Panels'''

With tar side down, attach 4'x8' OSB boards to 2'x4' boards, using the 2x4 with the long edge against the boards. Ensure that they are all flush, and that the 2x4 is evenly attached to both boards!

After this, attach flashing strip to one edge (left or right, doesnt matter, just keep it consistent throughout).

A trick Rob discovered with the flashing, to keep it flush as possible with the board, is to use the screw gun at an angle, pointing away towards the loose flashing end. It doesnt need to be an extreme angle, just enough to pull it taught when the head goes in.

Then, attach the flashing and the topmost 2x4 to the top of the 2'x4' OSB board. Leave a consistent space between the top of the 2x4 and the top of the OSB board (we left about 1/4 in). This makes placing the roof much easier and safer.

When attaching any of the flashing, ensure that you are placing less than half (more like a third) of the width of the flashing on the 1st board. This will ensure a good amount will be left to attach to the other board, whether roof or wall, given that the angle between will take up some of that width.

'''Roof Panels'''

Make a triangle with the panel pieces, screwing them into the 2x4 underneath evenly. Ensure that all is flush and that the bottom edge of the 2x4 is far enough away from the bottom edge of the panel to ensure that it wont get in the way when raising the roof. These 2x4s do not need to attach to the rest of the frame, as the roof is self supporting.

Then, like the wall panels, attach flashing consistently on one side, leaving width space for angle and attachment.

==External Links==

[http://www.appropedia.org/Hexayurt http://www.appropedia.org/Hexayurt] - Appropedia site on the hexayurt, tons of info.

[http://www.appropedia.org/Hexayurt_playa_checklist http://www.appropedia.org/Hexayurt_playa_checklist] - More specifically, assembly instructions for the one Vinay built on the playa at burning man. Lots of options for construction now!

=Hexayurt Review=
[[User:Jeremy|Jeremy]] 10:12, 13 February 2009 (PST)
I tried living in the hexayurt for a little while, here are my thoughts. It was in November 2008. Weather was cold but not much rain or snow yet. Yurt was quite sturdy and kept the wind and water out, but was cold inside. Before Bob left we put the 55 gal. drum stove in and cut a hole in the side for the flue that had two bends. The stove was and is a difficulty, hard to light and very smoky. I slept on the futon mattress we had on the dirt floor of the yurt at the time. The floor was still kind of damp, I guess it was built when the ground was not entirely dry or water had gotten under the walls underground. In the morning it seemed very damp inside the yurt, which I think was from the damp ground. I don't know how it would be if it had a good stove.

Nick took over the yurt when he came here. We moved the stove and had the flue go straight up to have a better thermal draw. With the stove going the yurt is pretty warm, but the door needs to be opened a lot to let the smoke out. It doesn't have insulation so it cools off quickly without a fire constantly going. The drum stove either burns out quickly and leaves the yurt cold in the morning or burns extremely hot and smoky all night making the yurt almost too hot and smoky to stay in. A good stove might leave it still pretty cold in the morning but it could be fired up easily and the temperature regulated better. Smoke still seems like a problem to me, even with a good stove in the cordwood hut.
[Image:Hexayurt.JPG]
--[[User:Vinay Gupta|Vinay Gupta]] 16:05, 13 February 2009 (PST)
Ah, yes, I'm not surprised than an uninsulated plywood structure was cold in winter. The Hexayurt geometry does not have decisive advantages in heat retention over other building shapes.
--[[User:Andrewed|Andrewed]] 04:19, 26 May 2009 (UTC)
Your results are perfectly consistent with any use of an uninsulated structure on exposed dirt in winter in Missouri, with a poorly functioning stove. Even 1" styrofoam boards on the ceiling, 1/2" styrofoam boards on the walls, and a plastic tarp on the floor would have helped you immensely. Also, the use of a rocket stove from Aprovecho in Oregon (plans available from them) or the very cheap [http://www.woodgas-stove.com woodgas stove] that Vinay recommends on his website would have kept you warm without the extreme hassle with smoke and complicated chimneys that you suffered. Better luck this winter?
[[Category:Housing]]