<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Georgia Stavropoulou on Medium]]></title>
        <description><![CDATA[Stories by Georgia Stavropoulou on Medium]]></description>
        <link>https://medium.com/@georgia_60137?source=rss-12349b67a236------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fCti1nXevB9NKuYZ.</url>
            <title>Stories by Georgia Stavropoulou on Medium</title>
            <link>https://medium.com/@georgia_60137?source=rss-12349b67a236------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:16:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@georgia_60137/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Use border-image CSS Property for Non-Symmetrical Images]]></title>
            <link>https://medium.com/d-e-weblog/how-to-use-border-image-css-property-for-non-symmetrical-images-1b80b89b2e5a?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b80b89b2e5a</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[styling]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[image-borders]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 13:49:32 GMT</pubDate>
            <atom:updated>2019-05-03T08:08:03.518Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a website as a non-developer is pretty hard. The latest bump on our road was the millimeter lines of our mockup for <a href="https://rosalind.xyz/">Rosalind’s site</a> and how to code them.</p><h3>1. The easy way</h3><p>The easiest way we came up with was the background image. We simply exported the lines from the <a href="https://inkscape.org/">Inkscape</a> file as a .png for the y-axis. And this is the snippet:</p><pre><br>body{<br> background-image: url(https://medium.com/%E2%80%98images/leftborder.png%E2%80%99);<br> background-position: left top;<br> background-repeat: repeat-y;<br>}<br></pre><p>It’s self-explanatory, but if you have any questions feel free to ask. We would repeat this process for the x-axis, but this didn’t seem right. <a href="https://qwazix.com/">Michael</a> was at unease. We already had a big background image and we added lightheartedly two more. Moreover the two background-images approach had an unsolvable overlap. It felt like this would backfire any time soon. We dropped it.</p><h3>2. The kludge</h3><p>A few minutes in <a href="http://stackoverflow.com/">stack overflow</a> and the hacky approach popped up. It included an extra <em>&lt;div&gt;</em> in the html document before any other element in the <em>&lt;body&gt;</em> with <em>class=”mil”</em>. The <em>&lt;div&gt;</em> needed extra styling to hold our lines. Here it is:</p><pre><br>.mil{<br> width: 100%;<br> height: 200px;<br> margin-left: 260px;<br> background: blue;<br> background-image: url(https://medium.com/%E2%80%98images/topborder.png%E2%80%99);<br> background-repeat: repeat-x;<br>}</pre><p>The color is blue, so we could see what we were doing. Y-axis was next. But now we had a bunch of new actual elements, the code was messy and everything in the website went 200px down and this had to be corrected, and, well, this was not the solution.</p><p>We took a break and revisited later with a fresh eye. And coffee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*49_dNJ-fgmdcJyA7VcNlbA.png" /><figcaption>Joe the CEO.</figcaption></figure><h3>3. The optimal way</h3><h4>I. Image first</h4><p>The millimeter image was initially an <em>svg</em> image created in Inkscape. We decided to make sure the vectors aligned exactly to pixels in order to avoid aliasing problems (for example equal-thickness lines not showing as having equal thickness on-screen. See the section Antialiasing and Raytracing of <a href="http://paulbourke.net/miscellaneous/raytracing/">(this article</a> for more info). We opened a new Inkscape file clicked on <strong>View &gt; Page Grid</strong>, so that a pixel grid was visible. We also set pixel to be the general display unit of the Document and the custom size. The page has width 112px and height 126px. We made this match the final size in browser (virtual) pixels we wanted to show it so that we would spend less time in size calculations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nqc_kVCUcfQ_MjmcW_j_TA.png" /><figcaption>Inkscape settings.</figcaption></figure><p>With the Rectangle tool we drew millimeter lines with 2px width, both horizontally and vertically, as depicted below. We were very meticulous with the space left right after the last two lines, exactly 12px; the same space is left among all the other lines. We avoided the Bezier tool, because it snapped to the middle of the line of the grid and gave us half a pixel as a leftover. All these helped us to create an image, for which we knew and could calculate any required measurements in pixels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ErZzoSdaVlnefqmkxiEp1A.png" /><figcaption>The millimeter lines.</figcaption></figure><p>BUT when we exported the image, we went at the Export PNG Image tab and at the <strong>Page &gt; Image size</strong> we doubled it (again in px), so width became 224px and height 252px actual image pixels.</p><p>We were set for perfection.</p><h4><a href="https://www.quirksmode.org/blog/archives/2010/04/a_pixel_is_not.html">II. A pixel is not a pixel is not a pixel</a></h4><p>Why we decided to export*2? Well because most modern browsers render everything double-sized up (or more). Naturally a designer opts in for maximum quality of their website in every device. And with this choice the millimeter image would keep its quality, in any scale up to 2:1.</p><p>If you would like to make sure you maintain absolute sharpness in 3:1 screens like those of QHD smartphones you can export in 288dpi in Inkscape (3x), or even more. Keep in mind however that size can quadruple each time you double sizes, depending on your graphic.</p><p>All the above allowed us to use the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/border-image">border-image CSS property</a> for the body of the document. Here’s our snippet:</p><pre><br>body{<br> border-image-source: url(https://medium.com/%E2%80%98images/borderimage.png%E2%80%99);<br> border-image-slice: 140 0 0 84;<br> border-image-width: 70px 0 0 42px;<br> border-image-repeat: round;<br> width: max-content;<br> margin: 0;<br>}</pre><pre>main{<br> margin-left: 60px;<br>}<br></pre><p>Let’s elaborate a bit more on that.</p><ul><li><strong>border-image-source</strong></li></ul><p>That was an easy one. We simply put the url; in our case it was a short url, because the CSS document and the images subfolder are in the same folder named public_html. How tidy and mighty we are! :P</p><ul><li><strong>border-image-slice: 140 0 0 84;</strong></li></ul><p>These are the the numbers for top, right, left and bottom parts that we need to slice. Notice no <em>px</em> designation .We picked these numbers by breaking down this diagram <a href="https://mdn.mozillademos.org/files/3814/border-image-slice.png">here</a>. This gray area that our slicing shades is going to be the pinpointed part of our image and the right and bottom leftovers are the repeating units that eventually will build the border. These numbers are in actual pixels (i.e. doubled in our case). The cool about that is you can triple, quadruple etc, depending on how technology advances!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52zrPHNXg3pu4snW6Bt4AA.png" /><figcaption>This is the starting point that won’t move.</figcaption></figure><ul><li><strong>border-image-width: 70px 0 0 42px;</strong></li></ul><p>Note here that regardless the fact that we doubled up our pixels to export, CSS needs to be set in the original (virtual) pixels of our Inkscape lines, hence 70px and 42px are the correct values and not 140px and 84px. The needed width from top to bottom equals with 70px (that is our measuring unit regarding our original image, plus we need to have our border image appearing only on our left), 0 for right and bottom because we have no border image appearing there and 42px from left to right, since that’s the maximum width of our original vertical millimeter lines.</p><ul><li><strong>border-image-outset</strong></li></ul><p>We omitted this CSS property, because the initial value of 0 was working just fine for us.</p><ul><li><strong>border-image-repeat: round;</strong></li></ul><p>We tried all the other options but round tiled the lines nicely, without visible distortions of the image, errors, bugs or extra pixels. We also tried various versions in Inkscape with more lines drawn, but the latest version was the most optimal. As such less distortion appeared when the image repeated itself.</p><p>For this case study margin of the body had to be set in 0, so no gap was left between the browser window and the lines.</p><ul><li><strong>border-style: solid;</strong></li></ul><p>But the image was not displayed on Chrome. We did a bit online research which involved, guess what, <a href="https://stackoverflow.com/questions/25479713/css-border-image-not-working-in-chrome">stackoverflow</a> and <a href="https://www.chromestatus.com/feature/5542503914668032">chrome platform status</a> and we solved this by adding an extra line of code in the stylesheet. With a solid border-style our millimeter lines were working on Chrome just fine.</p><p>To quote the chrome platform status website,</p><blockquote>Blink will begin to require a border style in order to paint border images. This has always been required by the spec, but has not been enforced. In order to not be affected by this change, add e.g. ‘border-style:solid’ where border-image is used.</blockquote><ul><li><strong>width: max-content;</strong></li></ul><p>And last but not least, this was a real brain teaser, the width had to be equal to max-content. The width of our <em>&lt;body&gt;</em> element by default equals the width of the viewport. Our Rosalind image was larger, exceeding the viewport width by far. Naturally the border image ended where the viewport ended. Although <a href="https://brutalist-web.design/">brutalism</a> guides our web design choices and we were tempted to leave it like this, in the end we had to go with width: max-content; to fill the gap between each border entirely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jaVCwKTwKEdkCkGU_01VfQ.png" /><figcaption>Without width: max-content; the lines stop, even tough the image does not.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jJ0X5wWibttbAujEU7SQ5A.png" /><figcaption>With width: max-content; the lines go on till the end of the scroll bars.</figcaption></figure><p>We’d love to have your comments! What do you think of the border-image property? Have you ever used it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b80b89b2e5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/how-to-use-border-image-css-property-for-non-symmetrical-images-1b80b89b2e5a">How to Use border-image CSS Property for Non-Symmetrical Images</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing dx-punch]]></title>
            <link>https://medium.com/d-e-weblog/introducing-dx-punch-6bdbf2355a9f?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bdbf2355a9f</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[civil-engineering]]></category>
            <category><![CDATA[punching-shear]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[eurocode]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 08 Mar 2019 12:01:11 GMT</pubDate>
            <atom:updated>2019-03-08T12:22:23.567Z</atom:updated>
            <content:encoded><![CDATA[<h4>An open-source python package for punching-shear design with Eurocode</h4><p>Since July 2018, we have been working on developing software for the structural design of concrete slabs and footings in punching shear.</p><p>The were two main objectives put forward at the conceptual stage:</p><ol><li>To make an open-source software module.</li><li>To provide an extensive coverage of technical use-cases.</li></ol><p>A few months later, after extensive testing, and the baptism by fire in the design of a running structural project, we are pleased to announce the release of version <strong>1.0.0</strong> of the package <strong>dx-punch</strong>, written in Python.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vDTQKpLdm-JQnlulTocuuA.png" /><figcaption>The design checks on the raft slab of the <strong>Metro Hotel.</strong></figcaption></figure><p>The reason for opening the source-code is simple: <em>Anyone can use it, anyone can contribute</em>.</p><p>Building a community of open-source engineering software may accommodate collaboration in the field, advance the quality of existing solutions, and bring engineering practice up-to-speed with the organizational and technical status of the digital era.</p><h3>A short walk through the implementation</h3><p>The goal of punching-shear design is to ensure that the shear-stress capacity of a slab or footing satisfies the respective demand due to the direct act of column forces. Imagine a piece of cardboard, and a pencil standing on that piece of cardboard. Also imagine a program that checks whether the pencil will punch the cardboard if we put a given load on the pencil. dx-punch does exactly that check but for a slab and a column instead of a cardboard box and a pencil.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0Pd4iH8agQ11OZeR2DmDg.jpeg" /><figcaption>A pencil on a cardboard (or for that matter, a cardboard on several pencils) doesn’t work that much differently from a column on a slab.</figcaption></figure><p>This proves to be a problem of rather geometric nature: the design quantities depend heavily on the geometry of the column relative to the slab.</p><p>Hence the program has been built on top of existing python libraries that support geometric operations and vector manipulation, such as <em>mathutils</em> from blender and <em>matplotlib</em>. As we say in the open-source world we’re standing on the shoulders of giants. This means that we are not trying to reinvent things that others already did quite well.</p><p>dx-punch is the top package on a stack of python packages, all developed in this context separately to increase the modularity of the solution. The resulting hierarchy is the following:</p><ul><li><a href="https://pypi.org/project/dx-punch/">dx-punch</a></li><li><a href="https://pypi.org/project/dx-eurocode/">dx-eurocode</a></li><li><a href="https://pypi.org/project/dx-base/">dx-base</a></li><li><a href="https://pypi.org/project/dx-utilities/">dx-utilities</a></li></ul><p>Each package has a different scope, specializing from top to the bottom.</p><p>At the higher level, dx-punch supports the following features, with reference to <strong>Eurocode 2</strong>:</p><ol><li><strong>Evaluation of basic control perimeters (§6.4.2, Eurocode 2):</strong></li></ol><ul><li>Support for columns of arbitrary polygonal shape.</li><li>Support for drop panels. Drop panels are thicker parts of the slab over columns (like ancient column capitals) that help the slab bear the punching force. They are usually used when additional reinforcement bars are not enough to control the punching shear. .</li><li>Automatic classification of columns into <em>internal</em>, <em>edge</em>, and <em>corner</em>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*-NATno0dernGq3PwbT2saA.png" /><figcaption>This sketch shows automatic classification of the columns and the areas of the slab that punching shear is affecting in each case (control perimeters).</figcaption></figure><p><strong>2. Evaluation of design shear stress for bi-axial eccentricity of all classes of columns, using three methods:</strong></p><ul><li>Analytical via numerical evaluation of the perimeter modulus W1 (6.40, Eurocode 2) in both directions.</li><li>Approximate through Eq. (6.43, Eurocode 2).</li><li>Simplified through §6.4.3(6), Eurocode 2.</li></ul><p><strong>3. Design checks according to §6.4.4, Eurocode 2:</strong></p><ul><li>Support for declaration of soil-pressure on raft-slabs (lowest basement slabs, that is):</li></ul><p>&gt; Uniform<br>&gt; Discrete pressure field</p><p><strong>4. Evaluation of a code-compliant shear-cage layout according to provisions of §6.4.5, Eurocode 2.</strong></p><p>Furthermore, dx-punch provides nice sketches of the slab in question using matplotlib and outputs the results in tabular reports through pandas. The programming interface also allows programmatic access to these visualization and reporting utilities.</p><h4>Not yet supported:</h4><ul><li>Slab openings near the columns (near enough to intrude into the control perimeters) [§6.4.2(3)].</li><li>Favorable effect of in-plane normal stresses in Eq. (6.47).</li><li>Evaluation of radial layout of shear reinforcement (Fig. 6.22A).</li></ul><h4>How to use it or contribute?</h4><p>Have a look at the page <a href="https://gitlab.com/d-e/dx-punch">where the source code lives</a>.</p><p>You can also read the documentation to see all the functions and them in your own code.</p><p>Full documentation <a href="https://d-e.gitlab.io/dx-punch/">here</a>.</p><h3>A short example</h3><p>Let’s try to solve a slab together, step by step. You will need to edit some files that look like code, but don’t worry, it’s not that scary and we’ll guide you all the way through.</p><p>The easiest way to try out dx-punch is by using <a href="https://mybinder.org/">binder</a>. Visit this <a href="https://mybinder.org/v2/gl/d-e%2Fdx-punch/master?filepath=notebooks%2Fdesign_example.ipynb">link</a> to start up a temporary instance.</p><p>When your instance launches you should see the following screen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Da_kKLYMQFUfc_Obc_nlrg.png" /></figure><p><strong>A bit about what we are seeing here</strong></p><p>The first block of code sets up a few things. These are needed for our program to perform its calculations. You can see that it uses <em>matplotlib</em>, <em>dx_punch</em> and other libraries.</p><p>Right about the middle of the page you can see a plan view of our slab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*gyQpKV6LgW__x2ULC53rVA.png" /><figcaption>The slab before our modifications.</figcaption></figure><p>The slab and columns are described in the second box named <strong>A tentative input data structure</strong>. Scroll up a little to see it.</p><p>See those numbers in green? These are the input values. If you want to change for example the thickness of the slab just edit the thickness variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*TD19wOKBLAjns_hR6nCmpA.gif" /><figcaption>Editing slab thickness.</figcaption></figure><p>Then you can see the parameters of the materials used as well as the slab reinforcement bars.</p><p>Following are the columns on the slab: if you want to add another column just add a new column section as follows: copy the part between the curly brackets (including the brackets) and edit the various values (most notably the origin).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*szWRDXHTvaZv5NNtlRTkNg.gif" /><figcaption>Adding a new column in dx-punch.</figcaption></figure><p>See? Piece of cake.</p><blockquote>Notice that matching brackets go green when you click on them. Also do not forget to add a comma between the two columns.</blockquote><p>Now it’s time to run the program again. Click in the second box (where you added the new column) and press ⏯ Run in the toolbar above. You will notice that the focus will shift one box below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*IFT-q1K96vo-2bc5Re-gYQ.gif" /><figcaption>Running a jupyter cell.</figcaption></figure><p>Repeat this until you reach the cell with the slab plan. Click on <strong>Run</strong> again and you will see the new column we added displayed below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*MUbF8U7uFKix3wYnMnHyUw.gif" /><figcaption>New column appears.</figcaption></figure><p>Now the plan view of our slab looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*qH329F9Pskgzi0jjvTokeA.png" /><figcaption>Slab with the new column.</figcaption></figure><p>Hit <strong>Run</strong> one last time and you will get the results of the calculation printed just below. The results for Column 1 look like this:</p><pre>==&gt; Column 1:<br> -&gt; Column “C9432”:<br> — Results:<br> * Position: corner<br> * Geometry:<br> + Centroid:<br> — x [m]: 0.125<br> — y [m]: 11.325<br> + Bounding box:<br> — bx [mm]: 250.0<br> — by [mm]: 250.0<br> * Effective depth [mm]: 280.0<br> * Tensile Reinforcement:<br> + Effective tensile region:<br> — bx [mm]: 1090.0<br> — by [mm]: 1090.0<br> — Centroid (offset):<br> * dx [mm]: 420.0<br> * dy [mm]: -420.0<br> + x-axis: T10@200 + T10@200<br> + y-axis: T10@200 + T10@200<br> + ρx: 0.0028<br> + ρy: 0.0028<br> + ρl: 0.0028<br> * Design:<br> + Perimeter u0:<br> — Most adverse loadcase:<br> * name: LC0<br> * Ved [kN]: 111.0<br> * Mex [kN.m]: 25.0<br> * Mey [kN.m]: 22.0<br> * ex [mm]: -198.2<br> * ey [mm]: 225.2<br> — β: 2.919<br> — ved [kPa]: 2314.4<br> — vrd [kPa]: 5280.0<br> — DCR (ved/vrd): 0.438<br> + Perimeter u1:<br> — Most adverse loadcase:<br> * name: LC0<br> * Ved [kN]: 111.0<br> * Mex [kN.m]: 25.0<br> * Mey [kN.m]: 22.0<br> * ex [mm]: -198.2<br> * ey [mm]: 225.2<br> — β: 1.407<br> — ved [kPa]: 404.3<br> — vrd [kPa]: 480.5<br> — DCR (ved/vrd): 0.841</pre><p>This approach means that you can easily solve many slabs by just editing the numbers and using copy and paste. However a graphical user interface is in the works, at least for a single column. Unfortunately we can’t promise if and when it will be ready. For now you can create your own jupyter notebooks in binder using the example above as a template. You can even make them pretty enough to be presented as reports. You can find more information on how to do all that in the help menu.</p><p><a href="https://eurocodes.jrc.ec.europa.eu/showpage.php?id=132">Our references:</a></p><ul><li><a href="https://eurocodes.jrc.ec.europa.eu/showpage.php?id=132">Eurocode 2</a></li><li><a href="https://matplotlib.org/index.html">matplotlib</a></li><li><a href="https://pypi.org/project/dx-utilities/">pandas</a></li><li><a href="https://medium.com/d-e-weblog/al-matar-hotel-support-works-e05f17cd2d4b">Metro Hotel</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bdbf2355a9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/introducing-dx-punch-6bdbf2355a9f">Introducing dx-punch</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building our Own 3D Printer from Scratch]]></title>
            <link>https://medium.com/d-e-weblog/building-our-own-3d-printer-from-scratch-d9dfe2f53d08?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9dfe2f53d08</guid>
            <category><![CDATA[rosalind]]></category>
            <category><![CDATA[reprap]]></category>
            <category><![CDATA[3d-printer]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[3d-printing]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 22 Feb 2019 14:36:20 GMT</pubDate>
            <atom:updated>2019-04-01T08:39:50.153Z</atom:updated>
            <content:encoded><![CDATA[<h4>and what the project of recreating it aspires</h4><p>Back in 2014 my colleague <a href="https://qwazix.com/">Michael</a> decided to buy a 3D printer. During his online research, the <a href="https://reprap.org/">RepRap project</a> popped up. Everything around this project was very interesting and engaging and led to his first order. Mono Mendel from a company called <em>RepRapPro</em> meant to be his first 3D Printer. It came in a box with instructions on how to assemble the parts.</p><p>After printing a great variety of objects, both of his own design and others’ posted online (for free use of course), Michael knew all the pros and cons of his Mendel. His first impulse was to improve it. But the restless creator inside him wanted to take over and do more fun stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwB5TVIL-tzqAYtHKQId8g.jpeg" /><figcaption>Rosalind printing <a href="https://www.thingiverse.com/thing:600550">Aria</a>, a free model that <a href="https://www.thingiverse.com/loubie/about">loubie</a> created. Isn’t she fearsome?</figcaption></figure><h3>Building Rosalind</h3><p>So he decided to built his own 3D Printer. But before the actual build, he had to decide what ideas and values this new project would embrace.</p><ul><li>Being <strong>COREX–Y</strong> was the very first one. This means that the printing head moves left–right and front–back, instead of left–right and up–down. CoreXY is a linear motion system easy on the processor, so regular 8bit controllers such as Arduino MEGA wouldn’t struggle, keeping the cost down. This allows greater printing speeds and also it leaves the window open for a conversion of our 3D printer to a CNC machine in the future.</li><li><strong>Open source</strong> was of great significance, since we have been using FOSS projects for years here in the office and contribute to the community in any way we can. Thinking community–wise is closer to our belief system. Sharing our improvements and welcoming others to contribute promotes open collaboration and diversity, thus enriching the design process in an interesting and sustainable way. Also, whatever we learnt about 3D printing is because of other people sharing it freely and we want to give back.</li><li>The third thing we wanted was the new printer to be <strong>parametric</strong>. This would ease–in any modifications. It also ensured that in the future we could build a bigger or a smaller 3D Printer, without doing the paperwork all over again.</li><li>Being for the most part <strong>printable</strong> was the last but important consideration. This would make Mendel of great use. And even if we didn’t have Mendel, there are many 3D Printer owners in the community, who would happily help us with our needed prints. We were ready. This also makes it easy for you to create your own Rosalind with off the shelf parts and a friendly neighborhood 3D printer.</li></ul><h3>We set out to build Rosalind</h3><p>Why Rosalind you ask? Well because of the RepRap tradition of naming the 3D Printers after famous biologists. She is even able to print herself!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-C3OcRt5zZJ0ujXsQImOGA.jpeg" /><figcaption>Can you pinpoint where Rosalind is?</figcaption></figure><h3>A year later…</h3><p>…and this brings us to today, we felt like broadening this project. We aimed to build a new Rosalind from scratch. This time we added two more requirements: the requirement of being reproducible (the first Rosalind is one of a kind, many hacks were used there) and the requirement of a full documentation.</p><h3>What are our goals with Rosalind no2</h3><p>In the beginning of the process we asked ourselves a few questions to help us draw the guidelines that would keep us on track.</p><ol><li>Do we want to keep the characteristics that Rosalind already has?</li><li>How can we fund this project sustainably?</li><li>What new nuances does she aspire to?</li></ol><blockquote>The first question was an easy one. All four parameters were still important to us.</blockquote><p>Especially remaining open source in a constantly growing entrepreneurial world. Focusing a lot on the community and on spreading the knowledge of 3D printing is deeply connected with our approach on trying to find out how things work, instead of the <em>it just works</em> mentality.</p><p>This is an open source project from early on, created by an active member of the open source community, who wants to continue with contributions for the community and vice versa. <em>Create an open chat channel</em> was recently crossed off our to do–list. You can join us at #rosalind on irc.freenode.net, where we can engage in our love for 3D printing. We’d love to read about other people’s ideas and concepts, print their designs, help them with prototyping and take into consideration their proposals for improvement.</p><p>A virtual place with pictures from other creators Rosalind’s prints would be awesome!</p><blockquote>The second question needs a lot of work.</blockquote><p>I got to be honest here. For now we only make use of affiliate links to the products we bought to build Rosalind. That’s all. Apart from that we have in mind a couple more baby steps. If our project grows enough and there are people interested in building their own 3D Printer, but not sure what or where to buy their vitamins from, we could pack and ship assembly kits with all the pieces. We could also create special 3D printed items like faux jewelry or home decoration and sell them in a small store at our neighborhood or even online. But we are still far away from that.</p><blockquote>The third question was a bit harder to answer, but we managed to sort out our thoughts.</blockquote><p>Our new 3D Printer needs to feel tinker–friendly, repair–friendly and do–it–yourself friendly. All the way friendly!</p><ul><li><strong>Playfulness</strong> appears to find its place in our agenda. We want people to get the feel of exploring and playfulness that they get from a new game. We want to connect with the inner child of the individual, who wants to explore the world of 3D printing. We do not want it to be just a game with strict instructions. We want it to be an invitation to get on the floor, and follow the steps to create a new game that, yes, we designed, but they are making. Moreover we want to give examples of toys that people can make just for fun!</li><li><strong>Practicality</strong> is another aspect appealing to us. We want to be able to show of things that people can print with their 3D printer that are also practical in their everyday lives. The 3D Printer is not just a machine to create junk. It is also a tool that can be added to people’s lives and maybe occupations. 3D printing can be part of our life if it is easy to use.</li><li><strong>Innovation</strong> in today’s world is key. We want to continuously create new things. Most open source 3D printers (even those created with OpenSCAD) are not parametric enough and minor modifications in size require a lot of work. We set out to create a printer which will be configurable by just editing a few files and maybe, in the short future by selecting things on a website. No, Rosalind doesn’t have any fancy new extruding techniques or multiple materials (at least for now). But we aim for it to be <strong><em>very easily buildable</em></strong>, without any custom parts you can’t print yourself, or purchase off the shelf.</li><li><strong>Eco–friendly</strong> is the last aspect for now. There is a way to make your filament from plastic bottles. This is a great opportunity to recycle, save a bit money on your supplies and print even more! We plan this as our next endeavor, but no promises!</li></ul><h3>So now what?</h3><p>We are in the process of filming a series of <a href="https://www.youtube.com/channel/UCdxG_ejbPIiGv8sVioCvBeA?view_as=subscriber">video tutorials</a> to help you build of your very own Rosalind and introduce as many new people to the 3D universe as possible. Of course we learn as well through this process, as we gain more experience on the matter. Oh, and we have lots of fun. Along with the videos we are completing the documentation step by step.</p><p>More updates to come! Stay tuned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Te5s1qz7g_ZyJg2qZWvF6w.jpeg" /><figcaption><a href="https://www.youtube.com/watch?v=QT0tcetAYUg">Vitamins!</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9dfe2f53d08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/building-our-own-3d-printer-from-scratch-d9dfe2f53d08">Building our Own 3D Printer from Scratch</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart Cities]]></title>
            <link>https://medium.com/d-e-weblog/smart-cities-5c61b079940f?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c61b079940f</guid>
            <category><![CDATA[smart-cities]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[privacy-protection]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 08 Feb 2019 13:49:06 GMT</pubDate>
            <atom:updated>2019-02-08T13:49:06.261Z</atom:updated>
            <content:encoded><![CDATA[<h4>the problems they raise and the protection of our data</h4><p>Nowadays everything is ‘smart’. Your phone, your coffee-maker, your jacket. (By the way I live for the moment when I’ll hear someone going like<em> Tell me jacket, is it going to rain today?).</em> Even your dumb toaster. And if it’s not smart, it will soon get to be. The term is not meant only for small objects. The scale gets larger, including whole cities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oY5DeugPhESKH1xtM91M4Q.png" /><figcaption>Smart cities — Constantly connected | Blender and Inkscape</figcaption></figure><h4>Smart city. Or wired city. Or cyberville (ooh that’s cool).</h4><p>There are many terms to describe the concept of a smart city. But what is it actually? It is an urban area that uses technology and data collection. All this information is then used to improve urban life, resources, infrastructure, public services, economics, even planning. <a href="https://en.wikipedia.org/wiki/Information_and_communications_technology">ICT</a> (Information and communication Technology) and <a href="https://en.wikipedia.org/wiki/Internet_of_things">IoT</a> (Internet of Things) connect the citizens and strive for interaction, optimization and efficiency.</p><h4>My city is smart, what about yours?</h4><p>It feels that this could easily take a bad turn though. Let’s say that a city initiates a program to update itself. Some areas get ICT and IoT technology and start improving. And then the municipality runs out of funds. Or it has been decided to upgrade certain areas from the very beginning. What happens to the other areas? Are they territorialized? Do they become the outcasts and slowly get abandoned? Discrimination because of lack of digital advance is more present than ever. Smart cities are in beta right now and they’ll be a long time before the trial and error period is over. Until the official version is released, if of course such a formula is possible, the urban environment needs to be diverse and sustainable, providing equal opportunities and benefits to all areas.</p><h4>Instrumentation intelligence</h4><p>It is one of the major ways that our urban infrastructure becomes smarter. Through instrumentation intelligence the city collects data real-time. Analysis follows and you can even predict events and incidents across the various city districts. This alone clearly arises surveillance issues. Mass surveillance seems deeply rooted in the way a smart city operates. Although cameras, sensors and tracking applications disturb our privacy and reduce urban anonymity, right now they are socially acceptable. No one seems to care that our data footprints are all over the place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RRN_C_ICZRImXVYUlScLDw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/T2b8Q6xQjEc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">chuttersnap</a> on <a href="https://unsplash.com/search/photos/surveillance-cameras?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Let’s talk money</h4><p>One aspect of all this, and perhaps the most significant one, is the economic benefit. A smart city aims not only for happy citizens, but also to breathe new life into the local workforce. How? By turning the city into a hype-full-of-happenings place and thus appealing to young, creative people who excel in technology and want fulfilling daily routines. However this comes with a risk. So far money makes the world go round. Market wants profit, market gets it. All these individuals, either citizens or young newcomers need to be lured and distributed, then spend and fuel the city. The human framework they form needs to run aptly.</p><h4>Human framework</h4><p>As I’ve already mentioned the human framework is the base for all this. The easiest and most efficient way to manage this framework is to know what people like, want and need. And how do you do that? Going through the collected data is tempting and seems inevitable. New technologies are integrated with major government services, without many alternatives given, and that binds the citizens to use them. Also all these activities and happenings run on social media, meeting apps, blogs, constantly stirring up FOMO. This becomes a bit of a cycle, since it creates needs. People will never be off the city grid and in some cases they won’t be able to, even if they wanted so. They will be wired 24/7. Eventually they won’t want to opt out. They are already reluctant to do so.</p><p>As usual, these technological innovations trickle from the top down. This time from a wealthy generation of 1% millennials that live in gentrified parts of the tech cities of the world displacing the native population and compensating for their lack of free time and personal space with myriads of privacy invading gadgets. They perceive these gadgets as providing them with mostly positive values and life quality.</p><p>This is easy however if you are a cis white male working in tech and renting a thousand dollar loft in bay area. What are the effects on immigrants, workers, the elderly?</p><h4>What could be done then?</h4><p>If there’s an answer to all this, it lies in the way that we approach smart cities and not in the technology itself.</p><p>Of course technology will be implemented to <em>smartify</em> a city, it’s naive to expect the opposite. Delegating this task to corporate interests would most likely lead to an attempt to gain power over urban infrastructure and maximize their profit, while technology should be used to impact the local community in a positive manner. Tailored solutions should ensure that every interaction among citizens and their smart city is easily accessible, reliable, and accountable. All urban sectors should have some sort of update to avoid a formation of digital ghettos.</p><p>Furthermore all the multiple data streams should not be analyzed by a single entity, rather than multiple, a mixture of local authority and grassroots groups. The analysis should run in full transparency and even become open source, so everyone could gain knowledge of their data handling. Permitting access to their own personal data in a usable format gives the option for every individual to decide on what they want to share, ensuring transparency and increasing liability. Investing in public awareness on how and why data is collected is also a key point to air out doubts and conspiracy theories. Such example is Barcelona with its <a href="http://opendata-ajuntament.barcelona.cat/en/">Open Data project</a>. Their approach even led to growth in using the smart city applications.</p><p>Participation is very crucial too. Services, applications and platforms could be co-designed by community and government. As a result every aspect of the residential life is included, with social, environmental and cultural being the most important. Test driving and the following up survey is also a good way for citizens to participate in the making of their smart city in a democratic way. They are actively engaged and the decision making process is equally allocated.</p><p>Finally alternatives should exist for all those people who don’t have access to technology or simply don’t want to. We are hardwired to love our high tech phones and use them at all times. 100% digitalizing the areas of our urban life only makes it worse. Screen free hours are essential to our physical and mental health. Our smart cities ought to know that!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7TP0abnDURn5SuYGDq-s0w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/FPt10LXK0cg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">ROBIN WORRALL</a> on <a href="https://unsplash.com/photos/VUyb7WeQ0QA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c61b079940f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/smart-cities-5c61b079940f">Smart Cities</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a concept project with Inkscape]]></title>
            <link>https://medium.com/d-e-weblog/how-to-create-a-concept-project-with-inkscape-7c8047dca59b?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c8047dca59b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[vector-art]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[inkscape]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Tue, 15 Jan 2019 14:16:49 GMT</pubDate>
            <atom:updated>2019-01-15T14:16:49.943Z</atom:updated>
            <content:encoded><![CDATA[<h4>beginner friendly</h4><p>Concept projects are the best! And the worst. Mostly because the lengths you should go are always pretty vague. How much work is enough to present your ideas for a space or a building? And how do you define the checkpoint where you should stop? No one really knows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*wNheoz5_TLCut1Z90jVFxw.png" /><figcaption>Initial plot drawing.</figcaption></figure><p>When this landed on my desk I got very anxious. A plot at Ikaria and the owner’s vision for a multipurpose space for the summer. A restaurant, a coffee shop, a small theater and a couple of other activities, mostly appealing to tourists and visitors. The input was a <em>.dwg</em> file with a few altitude measurements here and there, coordinates and photos depicting the surroundings. <em>What am I supposed to do with this information?</em> I wondered and kept avoiding the task for a few days. My brain did a lot of back-end work until I felt ready to actually do something. Let’s go.</p><h4>1. Get to know the requirements</h4><p>Fortunately our client was pretty clear about the uses he desired to accommodate. All I had to do here was to decide the best way to depict this. Since I only had a plan of the plot, I decided to go with that. I would create a plan view, almost from scratch. I also did some research on the uses and the building regulations to have a more complete overview.</p><h4><strong>2. Create a background</strong></h4><p>I went with maps that I could find online. Using the coordinates I managed to pinpoint the location. I took a screenshot of the spot. And that’s all for this step.</p><h4><strong>3. GIMP time</strong></h4><p>Because I didn’t like the colors and all those details, I imported the image in the <a href="https://www.gimp.org/">GIMP</a> and played around with the saturation. I also dragged the image <em>curves</em> to darken some areas and highlight others. Last modification was to go to <em>Filters</em> &gt; <em>Artistic</em> &gt; <em>Oilify…</em> This blended the colors a bit and blurred the image to the point that it resembled an oil painting. This is the result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDMGBtdoiZyP2tTlNKi-TQ.png" /><figcaption>Before and after.</figcaption></figure><h4>4. Contour lines</h4><p>That was the hardest part. I couldn’t find a way to create the contour lines. I searched and searched and this <a href="http://contourmapcreator.urgr8.ch/">site</a> popped up. I zoomed in and found our plot, left-clicked twice on two different points. This led to a rectangle area that covered the plot between two pins. The only parameters I filled in were the number of levels, the level of interval and the units (m). Finally, I clicked <em>get data</em>. Contour lines appeared on the map. Victory! I scrolled down and there was this option <em>Save Contour Map as an SVG file</em> in bold. Hit <em>Download SVG file</em> and I was good to go. In order to make sure that this site was legit even at a basic level, I got the data for another area as well, that I already had a contour lines <em>.dwg</em>. Very roughly they matched. (Yay! \o/)</p><h4>5. Inkscape</h4><p>I opened the <em>.svg</em> file with <a href="https://inkscape.org/">Inkscape</a> and I imported the screenshot as well (it’s important to use links in files that usually tend to get very large. This harms portability a bit but makes it much easier to work with files). The contours were on top. I thought I was done.</p><blockquote>Wrong.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1dgAyhC6uLN7KGETvJpzOg.png" /><figcaption>Combined files.</figcaption></figure><p>I didn’t like it. The background seemed irrelevant, it didn’t match well, it felt strange. I tried to fix it, tweak it, customize it. It did not look good. Period.</p><p>So I decided to re-draw all the lines using the <em>Bezier</em> tool. I moved the initial contour lines on a different layer, lowered the opacity and locked it to avoid mistakes. It helped me to trace some contour lines and adjust them according to what the satellite image depicted. It was time consuming and hard. When I was done, I crosschecked the result with the altitudes the <em>.dwg</em> provided. It far improved, don’t you think?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFa8POcr0STz5BtbjUa-2Q.png" /><figcaption>Final contour lines.</figcaption></figure><h4>6. Concept design</h4><p>Now that I had a decent background I moved to some user scenarios to sort out our visitor audience. Families, couples and friends. Harming as few trees as possible was high on our agenda. How do you make it friendly to all these people, while respecting the natural environment?</p><p>The best way to approach this was through a mental UX design. Simply put, I tried to imagine what I’d like to experience as a visitor there. What I meet first? Where am I directed to go? This helped me with the placing of our buildings in the landscape and the routes that connected them. Our main access point was on the northern side. I placed open air parking lots there and proposed an afforestation, because there was no previous tree cover there. Paths and walkways would follow the natural course of the terrain. Buildings and trees were placed parallel to the contour lines of landscape, following and enhancing it.</p><p>All these were created in Inkscape, using basic rectangles and squares. The <em>bezier</em> tool became my best friend for more complex shapes. Playing around with the colors and the opacity was the part I enjoyed the most.</p><h4>7. The trees</h4><p>Trees were a chapter of their own. To create one of those I layered four things:</p><ul><li><strong>an outline</strong></li></ul><p><em>Bezier</em> tool helped me to create it. I then edited the path with the <em>Node editor</em> to match my preferences and picked a dark green color.</p><ul><li><strong>a green circular area</strong></li></ul><p>I duplicated the outline and node edited to roughly follow it. I used a flat green fill and lowered the opacity.</p><ul><li><strong>a shadow</strong></li></ul><p>I duplicated the outline again. I moved it diagonally, towards the upper right corner of the page in a 45deg angle. I deleted some of the nodes and edited the remaining ones that osculated the outline to overlap perfectly. I used a linear gradient fill from gray to fully transparent, lowered the opacity and blurred it. I saved the file (thankfully nothing happened, I had to save earlier).</p><ul><li><strong>images with tree top views</strong></li></ul><p>To add some extra detail to the trees I found two <em>.jpgs</em> I liked and imported them. Scale them to fit the outline and the general structure of the foliage. Oh, and lower the opacity.</p><p>Then I grouped all the elements and duplicated my tree four times. I placed the trees wherever I wanted (here in a diagonal row). To avoid a tile-like outcome, I edited each tree separately. Feel free to rotate, scale up or down, distort a bit, flip, change the opacity, lower or raise the selection. Nature is about diversity after all!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEm9Wgb9JGiE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEm9Wgb9JGiE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEm9Wgb9JGiE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c58ca85bb049c1ee2055dd9a8707f74/href">https://medium.com/media/2c58ca85bb049c1ee2055dd9a8707f74/href</a></iframe><h4>8. Final touches</h4><ul><li><strong>zoom in.</strong></li></ul><p>I needed a zoomed in depiction to the area, where the restaurant was in order to show how the tables were placed on the different levels. A simple circle with no fill did the trick. It worked as a magnifying tool on the left. I made it more vibrant to separate it in an even more discrete way.</p><ul><li><strong>text</strong></li></ul><p>Below the zoom-in area I created a semi-transparent rectangle and wrote a few things about the project. Try to avoid too technical terminology. Prefer simple explanations that appeal to anyone. Keep it short and sweet, it is easier to understand.</p><ul><li><strong>pictures</strong></li></ul><p>I decided that a plan drawing and a text box alone wouldn’t communicate the atmosphere I had in mind. Some good photos would capture better the vibe. I downloaded a few suitable pictures from <a href="https://unsplash.com/">Unsplash</a> for free and placed them on the right side of the layout. My little mood board already elevated the aesthetics.</p><h4>9. Done!</h4><p>This is the final result. What do you think?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*inJ3w6yGA90bgYi6mMJ-FA.png" /><figcaption>Final plan.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c8047dca59b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/how-to-create-a-concept-project-with-inkscape-7c8047dca59b">How to create a concept project with Inkscape</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Merry Christmas!]]></title>
            <link>https://medium.com/d-e-weblog/merry-christmas-572863e73724?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/572863e73724</guid>
            <category><![CDATA[new-year]]></category>
            <category><![CDATA[comics]]></category>
            <category><![CDATA[joe-and-redeye]]></category>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[christmas]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 21 Dec 2018 11:42:16 GMT</pubDate>
            <atom:updated>2018-12-21T11:42:16.397Z</atom:updated>
            <content:encoded><![CDATA[<h4>And a happy New Year.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wPkLdr6AuWr9SvWtesEccQ.png" /><figcaption>Joe and Redeye, our coffee cups wish you well.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=572863e73724" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/merry-christmas-572863e73724">Merry Christmas!</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drafting through the decades series]]></title>
            <link>https://medium.com/d-e-weblog/drafting-through-the-decades-series-ef7277da2eb?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef7277da2eb</guid>
            <category><![CDATA[civil-engineering]]></category>
            <category><![CDATA[3d-printing]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[bim]]></category>
            <category><![CDATA[drafting]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Mon, 17 Dec 2018 13:32:51 GMT</pubDate>
            <atom:updated>2018-12-17T13:32:51.452Z</atom:updated>
            <content:encoded><![CDATA[<p>And we are back! In the last part of our series, we want to pay our respects to the CAD software that we use and reflect on what the future holds and what we envision as a sustainable solution for smart drafting software.</p><h4>Part 5: In the aftermath of CADs</h4><p>Computer-aided design improved continuously. In a few years it moved from a hard-to-use tool to being the official way of working. It became well established in every engineering office that wanted to work on projects with up-to-date quality and values. Especially AutoCAD, first released in 1983 for the IBM PC, marked up a milestone in 2D computer drafting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ysezCIabyh4FVUpFrcv18Q.png" /><figcaption>Screenshot of AutoCAD 12 showing one of our old projects and our very own DomusCAD extension!</figcaption></figure><h4>Our first…</h4><p>…was AutoCAD 12, released on 1992. We used it on DOS on a 386DX clocked at 33Mhz. If you installed everything it would take 10 of the 60 megabytes of the hard disk, and that was a lot of space at the time. Despite the complexities involved in fitting it in our workflow it was a great change of tremendous help, especially as demands increased.</p><p>Back in the day, software released every few years. Each new version was an actual experience and you had the time to incorporate any changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*4YgwgTg5ZVGKb4nlhqIsHw.gif" /><figcaption>AutoCAD r14 real-time pan and zoom. The project shown is Vodafone HQ in Cairo.</figcaption></figure><p>Five years but only two releases later, the improvement of AutoCAD was staggering. R14 was a mainstay of computer aided design. It even had real-time pan and zoom. Before that, the pan tool used to re-draw the design to the new coordinates you specified instead of moving it around smoothly like nowadays. R2000 had layouts. From then and during the last 18 years little has changed.</p><h4>The attack of the clones</h4><p>AutoCAD was not the only one though. The stagnation of CAD features among the versions and the exorbitant prices Autodesk was charging, led to the appearance of a multitude of clones. All this started when Softdesk created a secret AutoCAD clone in order to defend against potential competition by Autodesk. Autodesk acquired Softdesk but was not allowed to acquire IntelliCAD (the clone) due to fair competition rules. The source was sold to Visio, which was then acquired by Microsoft. Microsoft however did not pursue the AutoCAD clone business. In the meantime, another entity was formed that continued to license IntelliCAD code to multiple sublicensees who each develop their own branch.</p><p>However, all this tumult is nothing more than what CADs are from they very beginning; lines on a virtual paper. This needs to change.</p><h4>Smart software</h4><p>Software needs to be smart. Even though the word smart gets attached to almost anything nowadays, especially technology, it doesn’t always hit the spot. Building software for example is not there yet. Hopefully we don’t need to build it from scratch, just add sparks for innovation.</p><h4>BIM (Building Information Modeling)</h4><p>Communicating, cooperating and reviewing in an interactive visual environment goes a step further with Building information modeling. BIM is a 3D model-based process of working. Files are networked and shared to support decision-making in real time regarding almost any building asset. An engineering team is enabled to co-author the project at hand and coordinate everything during its life cycle until completion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6yMx85jLkV0ZfkdCw6WA9w.jpeg" /><figcaption>BIM ecosystem (image from the web)</figcaption></figure><p>Building models should move on from plain objects to entities with attributes. Right now, we draw virtual lines of all the construction elements. But the software knows nothing about that. It cannot tell the difference between a slab and a column. As far as the software is concerned these are mere digital depictions. As a result, any modification must be done manually. For example, a bigger beam section means that you need to scale up all the beams manually. If we’re talking about evolution, the software should be able to understand and perform a beam scaling with a simple command such as <em>scale up the beams by 0.2</em> and adjust everything, like the reinforcing bars, the column section, the concrete mixture ratio etc.</p><p>Objects need to move on to entities as well. If we draw a desk the software needs to know the concept of the desk. Hence scaling down the work surface shouldn’t result in thin desk legs unable to support themselves. When calculating the structural loads, the software would include the desk in the imposed loads.</p><p>Another task that should be done automatically due to entities is the tendering, both the itemization of the construction supplies and labor and their cost.</p><p>All these would improve the cooperation among the engineers as well. Let’s say that the architect wants to move a column but the new point is where electrical installations are. The software warns him, optimizes and proposes a new point. Consequently the electrical engineer avoids this problem. Thus the difficulty of collaborating with multiple partners is reduced.</p><p>The nature of an entity-smart software would give a real edge over traditional CAD design and its limited solutions.</p><h4>Libre software and open standards</h4><p>Up until now most engineering software has been proprietary, with minor exceptions. The industry-standard <em>.dwg</em> is not only proprietary but a closed standard that was never intended by its creator, <em>Autodesk</em>, to be used for sharing drawings (that is what <em>.dxf</em> files are for). IntelliCAD creators reverse-engineered it and created a rival proprietary piece of code that reads and writes <em>.dwg</em> files.</p><p>Thus it is almost impossible to create Libre CAD software to rival <em>AutoCAD</em> and it’s clones today. (The GNU project has been trying with <a href="https://www.gnu.org/software/libredwg/">LibreDWG</a> which actually had another release recently, but it still ways behind.)</p><p>IFC is fortunately an open standard and thus support can be legally and easily added to Free Software projects. There are already open source libraries that read and write IFC files and work for supporting it in <a href="https://www.freecadweb.org/">FreeCAD</a> is <a href="https://yorik.uncreated.net/guestblog.php?2018=510">underway</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c756KncBxqwxYhHa2VFIUQ.jpeg" /><figcaption>Image from <a href="https://yorik.uncreated.net/guestblog.php?2018=510">Yorik’s Coffee Corner</a> blog</figcaption></figure><p>Thus we hope that there will soon be a way to solve our engineering problems using exclusively next-generation libre software.</p><h4>Version control</h4><p>Extensively used in software engineering, version control systems records the life of a file. Additionally, by using project management tools revolving around versioning, you can have a complete documentation during every project, revert to a past state, set milestones, allocate responsibilities, track project activity. And that’s just the tip of the iceberg. For a better overview <a href="https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control">this article</a> could be very helpful.</p><p>Our need for constant improvement, led us to integrate git to our working processes. It proved to be a major challenge, as any other digital transformation effort, and we are still struggling to find how to use the most out of it (local repositories, remote repositories and all that jazz). But we believe that is a very useful and powerful tool for us engineers.</p><p>It is the future, and we are not looking back!</p><h4>OpenSCAD 3D modeling</h4><p>Last but definitely not least is OpenSCAD. OpenSCAD is a free, open-source and script-only based modeler for creating solid 3D objects. It plays well with version control and allows the creation of fully parametric designs hence the model can be adjusted simply by configuring the parameters and modifying the variables. At the moment it is mostly used to design 3D printed parts and fixtures. However, we strongly believe that eventually it will influence the engineering world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N97V-4yDpu6SQxlPOUwWdw.png" /><figcaption>Rosalind, our 3D printer built in OpenSCAD.</figcaption></figure><p>In the aftermath of CAD what else do you think comes next? What does the future hold? We do not know, but we surely want to keep exploring.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef7277da2eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/drafting-through-the-decades-series-ef7277da2eb">Drafting through the decades series</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drafting through the decades series]]></title>
            <link>https://medium.com/d-e-weblog/drafting-through-the-decades-series-6055e136c835?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/6055e136c835</guid>
            <category><![CDATA[cad]]></category>
            <category><![CDATA[retro-gaming]]></category>
            <category><![CDATA[commodore-64]]></category>
            <category><![CDATA[construction]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 02 Nov 2018 15:00:50 GMT</pubDate>
            <atom:updated>2018-11-02T15:22:40.705Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 4: Hello Technology! aka the Game change</h4><p>As already discussed, hand drafting was well established as the default way for presenting an engineer’s work. Then, the computers kicked in! We all know that computers had been under development since the 1950s, but it was not until the early 1980s that the first commercial CAD software showed up in various industries. This, combined with the introduction of the first IBM PC in 1981, set the stage for extensive adoption of both CAD packages and PCs. Every engineering firm that wanted to be innovative and ahead of the rest had to have (and know how to use) one.</p><h4>Commodore 64 and PC10 — Our first “partners”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7DVwGPmzCAFjc0mjm1mlA.png" /><figcaption>Our Commodore64! We managed to set it up today and it still works!!</figcaption></figure><p>The first computer that we bought was Commodore 64, a basic machine (meaning that it ran on BASIC) that we connected to a TV. The second was a Commodore PC10, equipped with DOS (Disk Operating System for the young people out there) and a 12-inch screen, it would only display in black and green. Just like the Matrix.</p><h4>Structural analysis and design software</h4><p>Structural analysis software ran on that PC. Our first one was DOMUS, a software package based on the 1959 building regulation. It was a piece of software written by <a href="https://www.linkedin.com/in/sotos-demetriou-64260b24/">Sotos Demetriou</a> and fairly customized to operate according to the Greek regulation mentioned above. It had a plain text environment and could run plane frame structural analysis. That means that the engineer designed every important plane section. The sections included the major construction elements, columns, beams and slabs. Nodes’ coordinates and bearing loads had to be specified. Additional data and information about each frame, like dimensions, were necessary, in order for the analysis to run. Each analysis required several hours to complete and sometimes the entire night. If a mistake popped up you had to run the analysis again. And perhaps again. And again. There were times that the same analysis ran for several nights straight until the desired results were reached.</p><p>After running the analysis the engineer had to print out the results for regulatory submission. That meant that a printer was connected to their workstation. Ours was a dot-matrix printer connected to the PC10. The exact model was <em>Star NL-10</em>. The walls in our old office space still echo the sound of that printer, working 24/7 to finish the printing of the analysis.</p><p>After DOMUS, we created DomusII, which required a more evolved PC to run. We decided to expand our computer task force with a PC equipped with the intel 80386 processor and a 16-color display.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCocwcn9Z4shvKvDKTSFKw.png" /><figcaption>Left: Display of our construction software. Right: Printout of DomusII column analysis.</figcaption></figure><h4>How the regulation affected the situation</h4><p>In the mid 1980s the way buildings were being analyzed structurally changed completely. The 1959 regulation was construction-centered, meaning that the way a building was designed and analyzed focused mainly on the building remaining intact when bearing the heaviest load or at least make it through with the least damage. Small column sections and huge beam sections prevailed the engineer’s design.</p><p>Increased seismic activity led to the release of new regulations that shifted the focus from buildings to people. It was very important to guarantee people’s safety, especially in case of an earthquake. As a result, the engineer had to make sure that the damage in a building would become visible as soon as possible, so that the residents would have enough time to evacuate. Typical column sections got larger and typical beam sections smaller. The requirements in reinforcement bars changed as well. On top of this, the regulation made space frame structural analysis mandatory. Inevitably, all the engineers had to buy a PC workstation to keep their office up-to-date with the technological advance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnIISNdQviUnCfxCzS9gnA.jpeg" /><figcaption>Λερναία and Διαμαντορύχος were two games that we developed and ran on Commodore64 (all work and no play…).</figcaption></figure><h4>The in-between</h4><p>Hand drafting and computer-aided design overlapped for a period of time. The transition from the ‘pen and paper’ safe place to the uncharted new worlds of ‘mouse and screen’ took time, as all major changes do. During this time both our design and construction approach changed. Computers created a fertile environment for new ideas and a variety of construction solutions that overflew the engineers’ minds and influenced the evolution of their work. This process went on until everything was molded into its final form and our new identity emerged on how we did things from then on. Meaning, computers were here to stay and it was up to the engineers to figure out how they would best incorporate this amazing piece of technology into their daily working routine.</p><p>Keep up with us to find out more about this innovative period as we’ll go in more depth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*HHrKJKKd9Dbz2pf2MPdzaw.jpeg" /><figcaption>AutoCAD12 was the first release that we used in the office (downloaded image).</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6055e136c835" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/drafting-through-the-decades-series-6055e136c835">Drafting through the decades series</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drafting through the decades series]]></title>
            <link>https://medium.com/d-e-weblog/drafting-through-the-decades-series-87d1415715c8?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/87d1415715c8</guid>
            <category><![CDATA[print-white]]></category>
            <category><![CDATA[blue-line]]></category>
            <category><![CDATA[drawing]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[copy]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Fri, 19 Oct 2018 13:52:38 GMT</pubDate>
            <atom:updated>2018-10-19T13:52:38.418Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 3: Copy cat</h4><p>After <a href="https://medium.com/d-e-weblog/drafting-through-the-decades-series-954a98757302">inking</a> for the first drawing was done, the engineer of the past could lay back, relax and enjoy a cup of coffee. A big chunk of the work had just been completed.</p><p>But what about the rest of the drawings?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eqIU4qKufMAoC8Rt0PpWhA.png" /><figcaption>The original and the copy. The designs date back to 1992.</figcaption></figure><p>This is where reprography would way in. Reprography is the process of reproducing an original design, commonly referred to as the ‘master’. This technique was a common practice among engineers, and had gone through various methods like blueprints, whiteprints and photocopying.</p><p>Blueprints are the most recognizable type of reprography. They have been around since the mid-1800s, and the term _blueprint_ is still being used, in an informal manner, to refer to any kind for (floor) plan.</p><p>We do have a long history in engineering, but it doesn’t go that far back. In case you are interested in learning more about blueprints, you can start by reading <a href="https://en.wikipedia.org/wiki/Blueprint">this</a>.</p><p>The earliest copying method we had the chance to use were whiteprints.</p><h4>Whiteprints</h4><p>Also known as blue-lines. They were actually dye-based prints on an off-white background. Cost-efficient, simpler to reproduce and using fewer toxic chemicals than the blueprints, whiteprints prevailed the engineering world quite quickly. Blue was the most popular linecolor but we mostly used sepia, a dark brownish hue.</p><h4>The master, the diazo and the fumes</h4><p>As we’ve already mentioned, the master was drawn on tracing paper, a.k.a. the translucent medium. But in order to produce color you also needed the diazo paper, a commercialized paper coated with a mixture of diazonium salt (a light sensitive chemical) and azo dye (a colorless chemical), which, when combined, produced color.<br>You had to adjust the intensity of the UV exposure light and the speed of the diazo duplicator to get the desirable outcome.</p><p>Both sheets were fed into the machine. In the first chamber the two sheets were exposed to UV light. The exposure phase left you with white areas on the copy wherever there was no lines on the master. Of course the light could not penetrate the lines. This actually brings in mind how the layer masks work in software like Photoshop. During the second phase only the diazo paper went through the machine. Fumes of ammonium hydroxide created the chemical reaction that developed the lines. That distinct scent of ammonia is something that every engineer recalls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n7HS8EuSD5kmSWrrf59Hhg.jpeg" /><figcaption>Detail from the same design. Doesn’t it look amazing?</figcaption></figure><p>We used to have a duplication room of our own. A low-volume copying machine was there, so that we could create copies whenever needed. It was a Technodiazo by Neolt, equipped with filters that neutralized some of the ammonia scent (or so the manufacturer claimed). Still though; it vividly permeated the air. I do not think that that scent can be erased from our nasal memory, no matter how many years will pass.</p><h4>Taking care of the copies</h4><p>The copy unfortunately was not permanent. Within weeks or months it faded away, depending on the amount of the light exposure it underwent. Unless you wanted to lose the design, you really needed to take good care of your copies and store them in the dark. Most of our copies were stored in rolls in the dark and rarely reviewed so we managed to still have some copies that are quite legible!</p><h4>Document control</h4><p>Of course changes occurred during a project. Each office had colors of favor the engineers used to markup the various modifications on the copy. Contrasting colors were the top choice because they just made things easier. The standardized color scheme was recorded for reference purposes. After the modifications were finished, the document was crosschecked. The master was modified to include the changes made on the copy. New blue-lines were then printed and this process went on like this until the project was complete.</p><p>In our office, yellow, red and blue were the colors of choice for our document review and control. Yellow was used to trace all the correct parts of the whiteprint. Red was for errors, notes, optimizations, alterations to be made, proposals or second thoughts. Following that step, the engineer in charge of addressing the findings, erased the red lines and fixed the problem areas using a blue pencil. If the red marks were too many, the workload was split in half between two engineers.<br>We actually still use these three colors while reviewing our printed designs. I guess some habits do die hard (if not at all).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MDgyA_Tjz5xrxCJwnf8vJA.png" /><figcaption>Red, yellow, blue pencils. Our revision tools.</figcaption></figure><h4>What’s next?</h4><p>Technology moved forward really fast in the 1980s and 1990s. It is no surprise that computers dynamically got in the engineering game during the 1980s. Wanna learn more? Find out in our next article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87d1415715c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/drafting-through-the-decades-series-87d1415715c8">Drafting through the decades series</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drafting through the decades series]]></title>
            <link>https://medium.com/d-e-weblog/drafting-through-the-decades-series-954a98757302?source=rss-12349b67a236------2</link>
            <guid isPermaLink="false">https://medium.com/p/954a98757302</guid>
            <category><![CDATA[inking]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[rapidograph]]></category>
            <category><![CDATA[hand-drafting]]></category>
            <dc:creator><![CDATA[Georgia Stavropoulou]]></dc:creator>
            <pubDate>Mon, 08 Oct 2018 11:39:17 GMT</pubDate>
            <atom:updated>2018-10-18T17:40:50.863Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 2: Inking and other tales</h4><p>In the first part of these series, we discussed <a href="https://medium.com/d-e-weblog/drafting-through-the-decades-series-da89ead229d0">hand-drafting</a>. Before we enter the computer and CAD era, we thought that inking is a technique that deserves mentioning since it was widely used and actually set-up the way lines and plot styles are still depicted in CAD software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x2yvBhjl58wkxIeR3b52fw.jpeg" /><figcaption>Inking one of our designs in the 1990s</figcaption></figure><h4>A short story on rapidographs</h4><p>Technical pens were a major part of the hand drafting experience. In our office we refer to them as rapidographs, even though most of them were actually isographs. Rapidograph is actually a trademarked name by rOtring and it was the prototypical technical pen of its age in 1953; well established long before we entered the engineering game.</p><p>Grabbing your rapidographs meant you had gone through the whole design process. Your project was ready to go formal.</p><p>Every engineer had a basic set of various nib sizes in order to ink draft the drawing with lines of consistent width. Every width actually held semiotic information for the drawing. Can you name one line width and its purpose? For example I used a 0.6mm nib for concrete sections and 0.1mm for projection lines.</p><h4>The challenges</h4><p>Inking had its challenges. The rapidograph should be held vertically for the ink to flow. Right angles were tricky. Well, all angles as a mater of fact. You should not go all the way with your rapidograph; stopping 0.1mm before two lines met, did the work. Otherwise, your angle ended up with a blot of ink rather being sharp and crisp. Triangles had to be used on their bevelled edge to avoid bleeding. Alas, no amount of effort could fix that.</p><p>Each nib came with its own stylus, which consisted of many pieces. The coolest part was that you got to dismantle your rapidographs, mainly for maintenance reasons. Dismantling and reassembling felt quite similar to dismantling and cleaning your weapon, with a dash of adventure to the procedure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BEj3CAEInV3fADvtLMzXgQ.jpeg" /><figcaption>A selection of our favorite, now decommissioned, rapidographs</figcaption></figure><p>Replacing the ink cartridge was a small project on its own. You had to be extra careful with the nib and protect it during the ink replacement. I recall tapping the remaining ink out of the nib on a tissue paper and then wiping it off. Sometimes I would let tap water run through the nib, but I’m not quite sure whether that was legit or not.</p><p>There was a time when I took a break from drafting for a couple of weeks. The ink dried out. To remove it I had to let the nibs soak into rubbing alcohol, and then carefully clean them. At the end of the day they were saved, and that taught me that tools may be objects, but they also have a mind of their own.</p><h4>The paper</h4><p>Of course you needed paper to draft on. Tracing paper was your first, and probably your only, choice. It was a translucent thick paper, suitable for rapidographs. There was no neat way to erase an ink mistake. A scrape tool was used (I had a razor blade) but inevitably that would scratch off a bit of the paper surface along with the ink, no matter how gentle the scratch.</p><p>After a few hours and a lot of patience, the drawings were ready. Finally! But wait a minute… Were the engineers in need of one and only drawing? What happened when we needed multiple copies? Needless to say we could not possibly hand draft the same plan six or seven times.</p><p>The answer to this little riddle comes in our next article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=954a98757302" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/drafting-through-the-decades-series-954a98757302">Drafting through the decades series</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>