Technical – Being Brunel http://www.beingbrunel.com The Civil Engineering Blog Sat, 20 Aug 2016 15:22:38 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.9 http://www.beingbrunel.com/wp-content/uploads/2016/05/cropped-being-brunel-512-1-50x50.png Technical – Being Brunel http://www.beingbrunel.com 32 32 Sketching For Engineers http://www.beingbrunel.com/sketching-for-engineers/ http://www.beingbrunel.com/sketching-for-engineers/#comments Wed, 08 Jun 2016 11:30:07 +0000 http://www.beingbrunel.com/?p=4319 Being Brunel | The Civil Engineering Blog

Sketching is an amazing thing. It's a great way of communicating an idea to someone, rapidly discovering solutions and testing a design for buildability. It's an underrated skill in the engineering toolbox, and one that is sadly finding itself...Read More

The post Sketching For Engineers appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

Sketching is an amazing thing. It’s a great way of communicating an idea to someone, rapidly discovering solutions and testing a design for buildability. It’s an underrated skill in the engineering toolbox, and one that is sadly finding itself sidelined in our increasingly digital world. Which is a shame.

This week, however, I learned that one of the greatest sketching engineers I’ve ever had the pleasure of working with has released a book. Drawing from an impressive fifty years of expertise (pun completely intended), the fantastic Ron Slade talks us through some of the techniques you can use to improve your pencil skills- in his book about sketching for engineers (and architects).

Having been privy to some of Ron’s beautiful sketches first hand, I’d recommend the book just for a chance to see just how well they can be done. Engineering is art, after all, and a visual celebration of a very distinguished engineer should be an exciting enough proposition on its own- we engineers rarely take the chance to celebrate our achievements.

Sketching as a tool is important, however, and worth the investment. One of my favourite summaries about our digital age is:

The unbearable certainty of BIM. Brian Duguid

Revit models and CAD drawings have their place, but sketching should not be underestimated. A 3D model is almost a mathematical document; cold, hard and precise (if not accurate)- full of details. But a good sketch is an expression– what’s drawn and how it’s drawn can say so much more than a thousand notes ever could. The line weights, the level of detail, even the rubbing-out; it forms a story, an interpretation, outlining a designer’s intent. Any engineer will tell you that finding the precise length of a beam, or distance between bolts, is the boring bit, it’s discovering how a structure can work that’s exciting; and that’s what a sketch is to a drawing.

Aside from the communicative art, sketching forces you to think through a problem. Building up your solution, trying new things- never underestimate how good you are at spotting that some thing’s not right. Yes the computer told you that this connection needs 10 bolts, but as you sketch it out it’ll become obvious that just because you meet the minimum spacing, doesn’t mean than anyone’s going to be able to get a wrench in there… And through that process you discover more solutions- it’s the ultimate in conceptual design because it forces you to address those gaps that your calculations inevitably miss.

Check Out Sketching for Engineers and Architects

The post Sketching For Engineers appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/sketching-for-engineers/feed/ 1
3D Printing: An Introduction http://www.beingbrunel.com/3d-printing-introduction/ http://www.beingbrunel.com/3d-printing-introduction/#respond Fri, 03 Jun 2016 11:30:10 +0000 http://www.beingbrunel.com/?p=4294 Being Brunel | The Civil Engineering Blog

In the future everything will be 3D printed. Or so we are led to believe. Like most of the science fiction-esq technologies I grew up with: robots, hoverboards, traffic lights that play music...Read More

The post 3D Printing: An Introduction appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

In the future everything will be 3D printed. Or so we are led to believe. Like most of the science fiction-esq technologies I grew up with: robots, hoverboards, traffic lights that play music to you– 3D printing is slowly becoming a reality. So we might as well make an attempt to understand it…

I’m going to kick off this series by stating the obvious; however 3D printing has a more specific definition then you might expect. It’s the process of digitally driving the creation of a physical three-dimensional model by “printing” a succession of layers on top of one and another to build depth.

It’s a definition that’s analogous with the way a 2D digital printer works; line upon line of pixels, each one after the other on a page. This analogy extends a little further; as it excludes techniques that achieve similar results like screen printing and stenciling.

Similarly 3D printing does not include CNC machines and robot assembly, which although digitally driven that effectively use tools to hune objects. This is why the common term “3D printing”” is more technically known as Additive Manufacturing; the process of manufacturing by continuously adding (not official definition)!

I have come to think of additive manufacturing as the finite element method of creating.

Its strength is that it is generic: it might not always be the best way to do something, but it’s the only way to do anything. You can design any structure using FEA; yes there might be”quicker” ways- simple beam theory and the like. And that’s the same opportunity AM offers; a “general solution” to the making problem.

I’m going to talk about the different printing methods with their advantages and disadvantages, and take a look at the current attempts to bring the fledging technology to construction in later posts. For now I just want to dwell on some of the opportunities 3D Printing offers civil engineering.

The most outlandish is the dream that well simply print our future buildings and infrastructure out in there future. Whilst that sounds a little ambitious, even to me; it outlines the possibilities on offer. The most obvious in that example is the robotised workforce; effectively making our site safer and construction much more controllable and predictable.

3D printing allows you to create advanced geometries with a high precision. This gets architects excited as it opens up previously impossible options to them. However for engineers this means no more deliveries (print components on site), much smaller tolerances less faffing on site- imagine printing rebar cages!

Finally by definition AM has little to no waste; every piece of material used must end up in the structure- or be later removed by another process (i.e. temporary works). For an industry that regularly tops the wastage charts, this is not something to be sneered at.

Of course there are some challenges, and I’ll get round to those as well…

The post 3D Printing: An Introduction appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/3d-printing-introduction/feed/ 0
Python For Engineers: Part 1 http://www.beingbrunel.com/python-engineers-part-1/ http://www.beingbrunel.com/python-engineers-part-1/#comments Sat, 21 May 2016 22:45:42 +0000 http://www.beingbrunel.com/?p=4097 Being Brunel | The Civil Engineering Blog

I don't want to hazard a guess how many times I've complained about the terrible misuse of Excel that I often witness atthe hands of over zealous engineers. However, last time I did this someone kindly pointed out that...Read More

The post Python For Engineers: Part 1 appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

I don’t want to hazard a guess how many times I’ve complained about the terrible misuse of Excel that I often witness at the hands of over-zealous engineers. However, last time I did this someone kindly pointed out that, except for one glancing blow, I’ve never really done much to remedy this first world problem (in fact, if anything I’ve helped contribute to it!).

A prime example of Excel abuse is the fantastic TCC column spreadsheet. So in an attempt to put my money where my mouth is, I’m going to kick off a regular series of posts where I’ll take you, dear reader, through the process of converting this magnificent monstrosity into a Python application.

That’s right, we’re going to do some programming.

n.b. this guide is going to be written like you’re a windoze user without admin rights, however every tool I suggest has an OS X and Linux version.

Step One: Getting Python

I don’t want to dwell too much on the what or why of Python, as, over this series, I’ll be hopefully do a better job of demonstrating this than a paragraph of computer science terminology could ever do. However, you might as well know upfront that it’s a programming language that is favoured for science and engineering applications by academia; and that it’s named after Monty Python.

At the risk of introducing some upfront confusion, but hopefully saving you some pain in the long run, I’m going to recommend that you install Python by using the distribution “Anaconda“. Python is wonderfully diverse and comes in many varied forms and with a whole variety of optional packages. In order to focus on the programming I’m just going to come straight out and tell you to download Anaconda for Python 3.5 for now:

Download Anaconda for Python 3.5

Make sure when you click through the installer that you opt to Add Anaconda to my PATH environment variable and Register Anaconda as my default Python 3.5 unless you know any better.

Programming as we go

For the last part of this introduction I want to get you comfortable with the way python works, so we can just dive straight into writing some more serious code in the next post.

First open up a command prompt and type python and you’ll be dropped into a ‘python prompt’. From this prompt anything you type will be evaluated when you press the enter button. Type 1 + 1 and press enter. Python will respond with 2. Not massively impressive, I know, but you’ve just written and executed some python! Feel free to try a few more calculations, but when you’re ready type quit() to escape.

Of course, this way of using python has a fairly obvious drawback, the user of your “program” will have to type it all out themselves (which was not unknown in the olden-days). Python allows you to write out all the commands that make up your program in a file, which can then be executed- saving you a having to type everything out every time you want to use it!

I’m going to talk a little bit about where to write code next, but for now just open Notepad and type the following:

print(1 + 1)

I’ll come back to the print() in the next post (although short story long it means that the result of 1 + 1 will be shown). For now save the file as sum.py. Now browse to this new file in the command prompt and type python sum.py. You’ll be rewarded with the number 2. Throughout this series will be writing our code in files and then using the python command to run them.

Programs to Write Code

Programmers have a habit of being weirdly opinionated about the editors you should use to write code. However I think I can say without fear of contradiction that none of them would be sadistic enough to suggest that you should use Notepad. Like with Anaconda, I’m just going to tell you to use Visual Studio Code, unless you think you know better. It’s free, light weight, and known how to colour your Python code so it’s easy to read.

Download Visual Studio Code

There are a lot of more powerful and perhaps more Python centric editors out there (PyCharm being my professional choice), but the majority of them will come with a steeper learning curve, and, for now, I don’t want to teach you how to use a Python editor, but how to do some actual coding.


Now with Python installed and the knowledge of how to literally write some Python we’re armed for part two, coming soon, where we’ll make a start on our TCC spreadsheet replacement.

I already know how to write Python, so this is for all you inquisitive engineers out there- I will answer any questions, either as a comment, by e-mail, or on twitter.

The post Python For Engineers: Part 1 appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/python-engineers-part-1/feed/ 4
Art and Approximation: A Review http://www.beingbrunel.com/art-and-approximation-a-review/ http://www.beingbrunel.com/art-and-approximation-a-review/#comments Thu, 20 Aug 2015 10:26:49 +0000 http://www.beingbrunel.com/?p=3898 Being Brunel | The Civil Engineering Blog

"It's better to be roughly right than precisely wrong"

Attributed to John Maynard Keynes (an economist), few quotes so accurately reflect my experience in design. Throughout my career I've become increasingly technical- I even...Read More

The post Art and Approximation: A Review appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

“It’s better to be roughly right than precisely wrong”

Attributed to John Maynard Keynes (an economist), few quotes so accurately reflect my experience in design. Throughout my career I’ve become increasingly technical- I even sit in a dedicated analysis team! I have a dirty little secret, however; if I can get away with doing something simply by hand, I always will.

The fact is, in these modern times, especially as an under-/graduate, it’s easy to find yourself elbow deep in code clauses and finite element analysis output without a sound understanding of how/if what you’re designing actually works. And while the digitalisation of design is an exciting prospect; computers are fallible, and programmers even more so– garbage in, garbage out.

Hugh Morrison’s “Structural Engineering: Art and Approximation” focuses on what he terms “a visual approach to design”. The book aims to help engineers (and architects) learn how to get a ‘feel’ (lit. approximation) for how a structure should be behaving and the magnitude of forces, etc. that it should be supporting. This really is a key skill, and one I, at least, definitely suffered from never being explicitly taught.

Starting with an appraisal of what it means to structurally engineer something (firmitatis, utilitatis, venustatis), Morrison starts to build his foundations with simply supported beams; increasing complexity of form all the way up to fabric structures and dynamics. You might roll your eyes at having to review simply supported beams; but I wonder how many of you really know that maximum deflection of a cantilever is 10 times that of a simply supported beam, and how you can use that information to validate designs quickly…

What the book does best is walk the line between mathematics/physics and codes. There are no long derivations of formulae; you won’t be told how to Hardy Cross fixed moments, but you will be reminded why. And there are also very few mentions of the codes; “because ASCE says” is not the reason something works structurally- of course, you do have to get it to work the your codes, but that’s not how you design it.

Instead this book focuses on how to engineer structures through art and approximation. You won’t come away with a detailed knowledge of everything, but it’ll at least set you on the track to being able to see if a design is sensible, if your validation method is appropriate and the questions you should be asking your specialists. And in a field as diverse as engineering (the nine pages on fabric structures now represents my sum-total knowledge of them,) that’s a useful thing to have.

What I also liked about the book, was its gateway nature. There’s quite a few references to other, more detailed, texts on each of the major subjects- so if you find yourself being drawn into the world of tension rings, you will be pointed in the right direction. (n.b. I’d like to take this moment to remind ICE members that you have access to a huge library of engineering books…)

I think this book has a few audiences. I would recommend it to all graduates entering design, it’s a way to get some judgement that normally takes a few years of experience. I’d say it’s a helpful tombe for those entering conceptual design, also, where spending six months doing a detailed study of bridge vibration won’t make anyone happy. And I’d also recommended it for the chartered engineer who has been managing too long and the technicals who could do with a bit of broadening.

Structural Engineering: Art and Approximation

The post Art and Approximation: A Review appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/art-and-approximation-a-review/feed/ 3
Genetic Algorithms for Engineering http://www.beingbrunel.com/genetic-algorithms-for-engineering/ http://www.beingbrunel.com/genetic-algorithms-for-engineering/#comments Fri, 24 Jul 2015 15:30:31 +0000 http://www.beingbrunel.com/?p=3749 Being Brunel | The Civil Engineering Blog

Machine learning is the topic of the hour; so in an attempt to stay relevant I thought I'd join in and share some of my own experience. Genetic algorithms are a 'learning' approach that can be used to find...Read More

The post Genetic Algorithms for Engineering appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

Machine learning is the topic of the hour; so in an attempt to stay relevant I thought I’d join in and share some of my own experience. Genetic algorithms are a ‘learning’ approach that can be used to find the optimum from a problem where there are millions of potential solutions, without having to test them all.

The Life of a GA.

The metaphor is fairly simple, if not incredibly brutal:

Day One: Encoding

It all begins when an uncaring God decides to define a creature chromosome. This chromosome can take many forms, but at its simplest it’s a series of on-off switches representing various states (furriness, pointed ears, fangs, etc.). This is called the encoding stage; the form of the solution is defined.

Day Two: Genesis

Happy with the creature definition, our God randomly creates a large(ish) population of the critters, each with a different chromosome, and puts them in a pen for safe keeping. This is the seed that will be used to start the ball rolling. These individuals (or creatures, in our case) are unlikely to be the solution we were looking for; but that doesn’t matter; they are cheap to create.

Day Three: The Hunger Games

Next, our lovable individuals are all tested against a number of qualifiers (marketability, tendency to turn evil if fed after midnight, etc.) and branded with a score. This is the fitness test, it allows us to rank our current population to find out which are beginning to show the qualities we are looking for in our optimised solution.

Day Four: Rapture

We unleash the velociraptors; only the fittest survive. There’s blood everywhere, and only a small percentage of our population remain- those with the highest fitness ranking. If you believe in nature, these poor, frightened, critters are our best hope to find our solution. Their unfit peers were just taking up memory, representing dead ends on our journey to perfection.

Day Five: The Percy Sledge Chapter

Here’s where it gets weird. We begin to play matchmaker for the remaining traumatised and bewildered creations. But because we don’t want our populace to become so homogeneous that it misses other viable options (becomes trained too early); we blast the new offspring with radiation- randomly mutating their chromosomes. This adds entropy, without which the algorithm can become ‘fixated’ on the first slightly rewarding condition and miss something better.

Day Six: Episode Five

The cycle begins again, ad infinitum (well, almost)- pitting mutant children against their own parents and even grandparents, each successive population is tested, culled and bred. The rules of evolution are clear; the desired (most successful) attributes will start to propagate, and (without variations in the fitness tests), our population will become trained on producing offspring more and more apt at surviving.

Day Seven: The Black Sabbath

Finally the rate of improvement begins to dwindle, and a pair of hands reach out from the sky and pluck out the fittest of the fittest; the creature with the highest ranking- our optimum solution. Looking down at the awed faces of its family and comrades- it is the first to see the bombs drop. Afterwards our perfect creature sits alone on the ledge of the pit- the sole survivor of a brutal algorithm. And the answer our God was looking for.

In Civil Engineering

Genetic algorithms are at their best when they are finding the ‘best’ of a vast array of potential solutions, and where there is a clear relationship between changes in attributes and the fitness of the resulting individual. Although the above example is cruel, our creatures are actually fairly lucky- had we set out on a brute force approach (literally trying every permutation) we would have had to slaughter millions of them. By creating small samples and combining the attributes of the fittest, we are likely to converge on the best solution after a few tens of generations.

In civil and structural engineering this approach lends itself to goal seeking and optimisation. For example, in calibrating a material model you can apply a genetic algorithm to converge on the properties that match the test data. Similarly, there is the opportunity to use them to find the optimum design for a given set of rules.

In my (limited) experience, I would suggest

  • Keep your encoding as simple as possible. The clearer the relationship between chromosome change and fitness, the faster you’ll converge on a solution.
  • Your fitness function has to be quick to evaluate. If you find yourself talking about doing a finite element analysis, for example, you need to simplify.
  • Breeding and mutation can be calibrated, but you’ll get the best solutions if the way you combine your chromosomes ‘persists’ what was best in the parents. A common pitfall, for example, is separating two inter-related attributes so that the resulting ‘positive’ is lost.

If you’re intrigued and fancy giving them a go, I would recommend taking a look at DEAP, which is a Python library that provides the mathematical base of the Genetic Algorithm approach; ‘all’ you need to do is provide a way of encoding and measuring the fitness of your problem/solution.

Welcome to the future!

The post Genetic Algorithms for Engineering appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/genetic-algorithms-for-engineering/feed/ 1
Mapping the Eurocodes http://www.beingbrunel.com/mapping-the-eurocodes/ http://www.beingbrunel.com/mapping-the-eurocodes/#comments Thu, 23 Jul 2015 10:01:01 +0000 http://www.beingbrunel.com/?p=3744 Being Brunel | The Civil Engineering Blog

Have you ever wondered why the Eurocodes are so damn annoying to use? I know I have. On my litany of things I hate about the Eurocodes are the way it always feels like you need to get 25 documents together before...Read More

The post Mapping the Eurocodes appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

Have you ever wondered why the Eurocodes are so damn annoying to use? I know I have. On my litany of things I hate about the Eurocodes are the way it always feels like you need to get 25 documents together before you can even begin to design anything. Finally, when bored on the train, I decided to see just how valid my complaints were, and how bad the problem is.

Let me present to you an interactive (click on the preview to browse) network graph mapping the references between the Eurocodes:

eurocode-map-preview

About the Data

For this map a ‘reference’ is an explicit mention of the code number (e.g. EN 1994-1-2). To avoid picking up the introduction that lists all the Eurocodes, I have excluded any references before the “1 General” header. To make the map clearer I have also ignored general ‘family’ references (e.g. mentions of the EN 1994 suite, rather than a specific part). I have also excluded NA references, etc. as it’s complicated enough without adding the non-EN documents you require.

Believe it or not, I didn’t painstakingly comb through every page of the Eurocodes to collect this data. I made a bot to do it. If you want to know how I made this map, you can check out the source code for the data extractor and plot data file builder here: on my GitHub. Unfortunately this means that the four Eurocodes PDFs with, inexplicably, encoded text have been omitted from this map:

  • EN 1995-1-1
  • EN 1993-6
  • EN 1993-1-10
  • EN 1991-1-4

But I never liked them anyway!

So next time you set sail on a voyage through the Eurocodes; don’t forget the map (or set it as your wallpaper!).

The post Mapping the Eurocodes appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/mapping-the-eurocodes/feed/ 8
Engineering On Stack Exchange http://www.beingbrunel.com/engineering-on-stack-exchange/ http://www.beingbrunel.com/engineering-on-stack-exchange/#comments Mon, 02 Mar 2015 13:00:00 +0000 http://www.beingbrunel.com/?p=3396 Being Brunel | The Civil Engineering Blog

It's here! We finally have an Engineering Stack Exchange! It feels a bit like I've been talking about this forever- so it is fantastic to see a community finally form and begin to create something. But now we've got it, we...Read More

The post Engineering On Stack Exchange appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

It’s here! We finally have an Engineering Stack Exchange!

It feels a bit like I’ve been talking about this forever– so it is fantastic to see a community finally form and begin to create something. But now we’ve got it, we have to use it- and prove that engineering is just as, if not more, important than coffee, home brewing and emacs, so that those masters of Stack Exchange will promote us from beta to fully fledged members…

What is it?

The Engineering Stack Exchange is a question and answer website devoted to that wonderful and diverse field that is engineering. It is built on the simple, but powerful, and well proven Stack Exchange platform, which promotes good quality questions and answers through a comprehensive reputation system (by adding a touch of gamification; making the whole process a rewarding, if not addicting, one).

Why Not X

It’s a sorry thing, but when promoting an idea- there’s often a feeling that the success of one thing must come at the expense of another. The three biggest engineering communities out there, that I know of, are the Eng-Tips forums, twitter and reddit; and I’d say that a Stack Exchange of our very own should squeeze in without too much displacement.

Forums are a place for discussion; responses are displayed chronologically, and, with exception of a touch of moderation, there is no real review of submissions. This is fantastic for emulating conversation, asking opinions and talking through recommendations, but its not great for forming coherent collections of knowledge. The format doesn’t lend itself to clearly pairing questions and accepted answers, or easily measuring the authority of contributors.

Reddit and twitter are aggregators; ways of sharing and discussing content. And they’re great for that; I’ve lost count of the amount of interesting stuff I’ve stumbled upon from both sources. While they do provide a rudimentary way of measuring contributions, they are terrible for persistence; with reddit posts being lost after six months and twitter only just making it on a Google search.

Conversely, Stack Exchange actively discourages discussions and calls for subjective recommendations; instead it requires that everything is either a question or an answer (or a comment when either is in need of suggestions and corrections). This means that when you find a question in Stack Exchange, you find the answer clearly marked- and the community that develops exists solely to provide solutions to problems.

What Do I Have To Do?

In a sentence: Join, ask and answer questions.

However the most important thing is to keep heart and try and get as involved as you can- our presence on Stack Exchange is still in its infancy, and there will be some teething troubles. If you want to do more, you can start curating as an editor or moderator; or get involved with the meta site and help shape how the our exchange develops.

So give it a few months, and engineering will have a brilliant new resource to help make us all better, multidisciplinary, professionals.

Join the Engineering Stack Exchange

The post Engineering On Stack Exchange appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/engineering-on-stack-exchange/feed/ 2
Engineering Stack Exchange http://www.beingbrunel.com/engineering-stack-exchange/ http://www.beingbrunel.com/engineering-stack-exchange/#comments Thu, 11 Sep 2014 11:00:17 +0000 http://www.beingbrunel.com/?p=2951 Being Brunel | The Civil Engineering Blog

Around two years ago I wrote a post rhapsodising on the benefits of Stack Exchange, about how it was the best thing in the world and about how Civil Engineers should totally have a presence there. It finished...Read More

The post Engineering Stack Exchange appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

Around two years ago I wrote a post rhapsodising on the benefits of Stack Exchange, about how it was the best thing in the world and why Civil Engineers should totally have a presence there. It finished with a link to the petition, which needed X amount of signatures to get it off the ground.

Well- it died a horrible death.

It turns out, however, that civils weren’t the only engineering discipline attempting to float this idea. Those few of us who had seen our hopes and dreams of a better future for our metaphorical children banded together on an island of “Engineering”; and like a phoenix from the flames the stack grew to the point where it will now be given a chance…

For those of you who aren’t long term readers or are particularly adverse to following links to previous posts- a Stack Exchange is a Question and Answer site. In fact, for a few disciplines (and software engineering comes to mind here) it is the Question and Answer site.

And why would it be the best thing since sliced bread for Engineers to get their own Stack Exchange?

Well, apart from the amazing potential for knowledge sharing and the growth of a community of people willing to chip-in and answer all those difficult questions- it is also brilliant promotion. It’s hard to imagine anything more accessible than a public site where engineers meet to ask and answer real questions from the profession for those who are curious.

But we’re not safe yet: Before Engineering is granted space on the Stack Exchange, we need to prove that there really is a big enough community out there to kick-off by asking and answering questions and maintain activity during the crucial early stages of the site’s life.

And that’s where you can help. I’m not asking you to devote your life to engineering (especially because you probably already have), but to register your commitment to actually use the site when it enters the beta stage. Let’s face it- who wouldn’t want to?

It’s really easy, just click this button:

Stack Exchange Q&A site proposal: Engineering

The post Engineering Stack Exchange appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/engineering-stack-exchange/feed/ 7
Influencing The Next Eurocodes http://www.beingbrunel.com/influencing-next-eurocodes/ http://www.beingbrunel.com/influencing-next-eurocodes/#respond Tue, 22 Jul 2014 11:06:19 +0000 http://www.beingbrunel.com/?p=2630 Being Brunel | The Civil Engineering Blog

It's funny to think that the Eurocodes, which were so cutting-edge when I was at University that I was barely taught about them, actually begun life 12 years before I was born. It's even...Read More

The post Influencing The Next Eurocodes appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

It’s funny to think that the Eurocodes, which were so cutting-edge when I was at University that I was barely taught about them, actually begun life 12 years before I was born. It’s even stranger when you consider that the second generation will be here in less than six years. It is this next edition, and the huge opportunity we have to influence it now, which I want to bring to your attention.

There are a few things that have already been pencilled in for the next generation. We’ll be able to officially design in Glass, FRP and use membrane structures. We’ll also be able to assess existing structures, and verify the robustness and climate change effects of our designs. On a more structurally specific view, improvement and additions to guidance for bearings, expansion joints, integral and cable-stayed bridges, fatigue, axial loading in composite sections and foot bridge vibration is also planned.

The most important goal for this iteration is to make the Eurocodes easier to use. Aside from a continuing commitment to authors of supporting documentation and training courses, the steering committee will also look for ways to improve clarity and make the documents quicker to navigate. On a technical note this includes distributing the XML versions of the codes; potentially allowing for ‘smarter’ digital versions.

As part of this process the BSI is doing something that (in my experience, at least) is unprecedented: It is actually asking engineers to tell them what they think of the Eurocodes, and how they can be improved. Obviously foreseeing a landslide of “I hate them and everything that changes“, they have limited responses to a pro-forma of six questions:

  • Do any clauses require editorial or technical correction?
  • Which clauses would benefit from improvements in clarity?
  • Where should the scope of the EN be extended?
  • Where could the EN be shortened?
  • Are there any clauses whose application leads to uneconomic construction?
  • Are there any clauses whose application necessitates excessive design effort?

The BSI have given engineers until the 15th of August to provide feedback as part of the Eurocodes 2014 Systemic Reviews, and I urge anyone who has ever complained or lost hours bewildered using this suite (lit. everyone) to chip-in now and make a difference:

Click Here to Influence the Next Generation of Eurocodes.

The post Influencing The Next Eurocodes appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/influencing-next-eurocodes/feed/ 0
Maths In The Head http://www.beingbrunel.com/maths-head/ http://www.beingbrunel.com/maths-head/#comments Sun, 13 Jul 2014 21:21:08 +0000 http://www.beingbrunel.com/?p=2624 Being Brunel | The Civil Engineering Blog

It turns out there is one thing that everyone knows about engineers: We Do Maths. I've lost count of the amount of times friends have simply deferred any arthritic to my good-self because "you're an...Read More

The post Maths In The Head appeared first on Being Brunel.

]]>
Being Brunel | The Civil Engineering Blog

It turns out there is one thing that everyone knows about engineers: We Do Maths. I’ve lost count of the amount of times friends have simply deferred any arithmetic to my good-self because “you’re an engineer- you do maths“; dividing bills, working out petrol costs and calculating quantities- my apparent skills have no end. It’s got to the point where my somewhat-taller-half no longer actually does any maths, he just wonders out loud any arithmetic he requires the answer to and then stares meaningfully at me until I answer.

The slightly worrying thing about this whole situation is that I’ve also lost count of the number of times I’ve witnessed an engineer (myself included) struggle with a trivial calculation, joking: “it’s lucky I don’t do maths for a living…”. Of course, the fact is that the sort of maths engineers use on a daily basis has a habit of being a little more abstract and calculator based than your day-to-day restaurant disagreement. It doesn’t hurt, however, to know a few of the following tricks to make ball-parking easier and maintain the slightly dubious reputation engineers have for “doing maths”.

Double and Halve

People are good with the number two; whether it’s because it’s the first times-table most of us learn, or just because doubling and halving quantities comes naturally to us. By appreciating that we can almost instinctively divide and multiply by two you can substantially improve your mental arithmetic speed; it’s called the double-and-halve trick. When multiplying two numbers just halve the smallest and double the largest until you end up closer to a factor you’re familiar with:

793 \times 24 = 1586 \times 12 = 3172 \times 6 = 6344 \times 3 = 19032

Obviously this trick is at its most effective when you have a number that is a power of two. For those times when life gives you lemons, however, you can still achieve similar speeds by separating out the difficult portion:

123 \times 13 = 123 \times (12 + 1) = 123 \times 12 + 123 = 246 \times 6 + 123 = 492 \times 3 + 123 = 1476 + 123 = 1599

Form the Square

Squaring numbers is a common thing in engineering; probably because of they way we work with physical quantities such as area. This trick is actually the application of a simple rule, and an equation that everyone learns and immediately forgets. For those of you who don’t know it, there is a rule for squaring any number ending in five: form a number using all but the last digit (i.e. 5), multiply that by itself plus one, and then finish it with 25:

35^2 = ( 3 \times 4 ) \; \text{and} \; ( 25 ) = ( 12 ) \; \text{and} \; ( 25 ) = 1225

It even works with decimals, just temporarily remove the point by multiplying though tens:

1.05^2 = \left(\frac{10.5}{10}\right)^2 = \frac{ ( 10 \times 11 ) }{ 100 } \; \text{and} \; ( 25 ) = \frac{110}{100} \; \text{and} \; 25 = 1.1025

Of course, you’d be lucky if you managed to pull off a calculation where you only had to square something ending in a five. However, you are only ever ±5 away from a number ending in 5, and that’s where our GCSE maths equation makes an appearance:

(x + y)^2 = x^2 + 2xy + y^2

Using this little gem, we can split our non-conforming number into something ending in five, and a number between -5 and 5 that we should be able to square in our heads. This allows us to use the ‘ending-in-five’ trick even when the number doesn’t:

39^2 = (35 + 4)^2 = 35^2 + 2 \times 35 \times 4 + 4^2 = (3 \times 4) \; \text{and} \; (25) + 2 \times 70 \times 2 + 16 = (12) \; \text{and} \; (25) + 280 + 16 = 1225 + 296 = 1521

Or, similarly, where you nearest five is greater than the number you’re trying to square:

44^2 = (45 - 1)^2 = 45^2 + 2 \times 45 \times (-1) + (-1) ^2 = (4 \times 5) \; \text{and} \; (25) - 90 + 1 = 2025 - 90 + 1 = 1936

Engineers Aren’t Mathematicians

This final trick isn’t really a trick at all, it is just the recognition that engineers aren’t mathematicians; we operate in uncertainties and precisions. Whilst I can’t calculate the square root of 73 in my head, I know that the answer is between 8 and 9, and is closer to 9; at a guess I’d say [Ed. you’ll have to trust me on this one:] 8.6, which (at 73.96) is good enough the majority of Civil Engineering applications.

By keeping an eye on the degree of accuracy you’re simplifying each stage by, you should be able ensure that you can calculate to a good enough aim for the application you need. You can improve your accuracy by acknowledging that, as an engineer, you’re trained to think conservatively and therefore you will want to normalise your conservatisms by taking geometric means between ranges (see Fermi Estimates for a guide).

It should be noted that being ‘close-enough’ when dealing in bistromathics is, alas, never good enough!

The post Maths In The Head appeared first on Being Brunel.

]]>
http://www.beingbrunel.com/maths-head/feed/ 1