BrainBlitz.org

October 15, 2008

A Study of the Effects of Extenuating Circumstances on the Accuracy of Revision Cloud Drawing

Filed under: CAD — Anthony @ 1:43 am
Revision clouds. There are very few people who can create a nice, shapely revision cloud in AutoCAD on the first attempt. I am not one of them.
 
Revision Cloud Observations

Revision Cloud Observations

  • Print this article!
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • StumbleUpon
  • Yahoo! Bookmarks

September 25, 2008

[Engineering] Office Tidbits

Filed under: CAD — Tags: , — Anthony @ 2:40 pm

 

  • Observation: You  know you’ve been spending too much time on the computer if you spill coffee on your khaki pants, and your first impulse is “CTRL Z.”

 

  • Tip: Using MODEMACRO to mess with coworkers
    Try typing “modemacro” into the AutoCAD command line. You will be prompted to enter a new value. Type something in, and press enter. Now look at the very left side of AutoCAD’s status bar – you should see the text you just entered. This is a great way to confuse people or spread propaganda.

For example, you might put “Give Johnny a Raise” on your Boss’ status bar (consider changing “Johnny” to your own name). Or a sinister message on a coworkers status bar – you know, “I’m watching you” or “d0 y0u f33L 1ucKy?” or something.

If you’re really ambitious, you can write a very simple lisp routine to read a text file from the server when AutoCAD starts up, and insert the contents of that file into the MODEMACRO variable. Now you can set messages on anyone’s computer without having to access it all the time (just once initially).

If you want it to be REAL dynamic – set your lisp routine to redefine a common command (zoom?), such that the file is copied to the status bar, then the original command executes as normal.

 

  • Observation: You know you’re Generation X (or younger) if you open your email, write a carefully thought out message to a colleague and send it, and your colleague answers you a minute later. Verbally. From 12 feet away.

 

  • Definition: “Office Meeting” : A time to fellowship with your coworkers over donuts, listen to stories from the resident Veteran Surveyor, discuss American Idol, or place fantasy football bets.

 

  • Observation: You know you’re working in a Civil firm if you hear phrases such as:
    • “Go ahead and nudge that drywell to the right a bit.”
    • “Beat to fit, paint to match.”
    • “Just pound it in there.”
    • “Architects mess everything up.”

 

  • Observation: You know you’re working in an Architectural firm if:
    • You tell the project manager the building doesn’t fit within the setbacks, and he says: “No problem. Grab that property line there… yes, now drag that grip just a bit to the left… “
    • You tweak property lines because 90-degree angles are beautiful.
    • You spend 80% of your time on important  issues such as tile patterns, the shape of sign lettering, wall colors, etc, and 20% of your time on minor issues such as building dimensions and wall sections.

 

  • Tip: The quickest way to find the Civil section in a large, multi-discipline set of plans is to rapidly flick through it, stopping when your eye catches what appears to be a child’s random scribbles on the page. This will most likely be the Utility Plan.

 

  • Tip: Consider adding this note to any general notes you place on each page: “Revision clouds are not to be physically constructed.” Why? You never know.

 

  • Observation: “The Ghost on the Network”
    It is an all-to-common occurrence for a drafter to leave a drawing pristine and clean (layer states set, zoomed to extents, etc), only to come in the next morning to find what can only be described as a virtual disaster area. Usually unexplained, this phenomena is generally blamed on the “Network Ghost.”

A recent study, however, points the finger elsewhere…The Boss.”I just went in real quick to make a couple of minor edits.”

 

  • Tip: Clandestine Chatting within AutoCAD
    So, lunch break has ended, but the political conversation with your coworker was just getting good and heated. What to do? Create a drawing on the network with a simple mtext message in it. You and said coworker xref the drawing into whatever you’re currently working on. Take turns doing an “Edit XREF in place”, and simply reload when you get the notification that the xref has been modified.
  • Notes:
    • It’s rude and confusing to post more than one message consecutively. You must alternate.
    • It is recommended that you put the mtext object on a non-printing layer. Otherwise you’re just begging for humiliation – when the day comes that your message is inadvertently plotted, and suddenly the whole office knows all about your “secret problem.” Or worse – your emotionally unstable coworker reads all the mean things you said about him.

 

  • Definition: “Rapid Topic Shifting” (RTS’ing)
    RTS’ing is a powerful technique for avoiding trouble with the Office Authorities. It is the practice of shifting seamlessly from any given topic to a work-related topic. For example:

“Apparently Paula was hitting on Simon again. I don’t know what she sees in him… he’s so rude. Did you hear what he said to that one girl? ‘You should ask your vocal coach for a full refund.’ She started the invert will have to shift down a couple inches though, to maintain minimum slope. It’d probably be easier to just route the whole thing through an easement…”

Simple in theory, the technique requires practice for smooth execution – unless you’re one of those clever, quick-witted folks.

And practice you should. Nothing says “Hey Boss, I am a bad employee. Don’t give me a raise” quite as effectively as going completely silent the moment The Boss walks in.

  • Print this article!
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • StumbleUpon
  • Yahoo! Bookmarks

September 19, 2008

AutoCAD’s Evil F1

Filed under: CAD — Anthony @ 10:41 pm

You’re in the zone. Your vision has tunneled to the screen, and nothing else happening around you even starts to penetrate your consciousness. Your left hand is moving with such fluid grace that the only indication of how much is actually happening is the rapid “clickclickclickclickclick…” of the keys. Your right hand on the mouse – the cursor moving to menu items before the menu has even opened. The only thing slowing YOU down is your 4Ghz dual core, water-cooled CPU.

 Then it happens.

The universe stops expanding.

Our galaxy stops spiraling.

Earth stops dead in it’s tracks.

The sun hides behind a heavy, gray cloud.

The birds outside instantly go silent.

You stare at the screen in horror. In the midst of your finger gymnastics, you slightly miscalculated the position of your finger, and instead of hitting “escape,” you hit “f1.”

And the world froze.

The only break in the eerie silence is the sound of your hard-drive, loading what must be terabytes of data to start up AutoCAD’s Help file.

A second ticks by. The universe is holding it’s breath.

Still the hard-drive whirs away.

Another second. An animal-like rage wells up inside you. The cursor jumps spatistically on the screen as you whip the mouse back and forth, trying desperately to regain control.

Denied.

Another second.

You grimace at the screen, grinding your teeth, kicking the wall underneath the desk.

Finally – the Help window pops up. Before it has even fully displayed, you’ve clicked the close button a dozen times.

A few milliseconds later, AutoCAD is back under your command. But it’s too late. Your drafter’s spirit has been crushed, and you spend the rest of the day hitting “refresh” on your email inbox.

***

Don’t let this happen to you again.

The F1 fix for AutoCAD 2005-
The F1 fix for AutoCAD 2006+

  • Print this article!
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • StumbleUpon
  • Yahoo! Bookmarks

February 6, 2008

AutoCAD and the Current Drafting Paradigm (will the geekdom never cease?)

Filed under: CAD — Tags: , , , — Anthony @ 10:12 pm

Preface: 

I decided to add a new category to the blog for CAD. A year ago, the thought might have nauseated me. But having become self-employed and dependant on the software (as a contract drafter), I’ve come to see it in a new light. It’s no longer something I immerse in for 8 hours a day, $20 bucks an hour. These days, my ability to utilize every function and push the envelope of my particular software (AutoCAD) translates directly into dollar amounts.

 So, as you can imagine, I think about it quite a bit. And amazingly, some of the thoughts actually seem interesting enough to put down in a blog. :D

 AutoCAD and the Current Drafting Paradigm

“Back in the day” – Architects/Civils/Mechanicals/Structurals/Etc obviously drew their plans by hand. I think that was the late Cretaceous period… maybe a little earlier. Regardless, eventually computers came along. I don’t know who came first – but obviously (to drafting geeks), AutoDesk creamed the market. AutoDesk reigns supreme. You can buy a reeeeally nice car for what AutoCAD charges to license a company of say… 10 people, with AutoCAD and a couple add-on packages for each seat.

Sorry, got distracted.

WHEN computers came along, the drafting industry shifted to CAD in a logical, but inefficient way. Instead of utilizing the computer’s data organization capabilities, software firms simply shifted drawing on paper to drawing on a computer. In a way, they probably had no choice. If they (software firms) had radically changed the way companies produced their plans, it would have taken far longer for engineers to adopt/adapt. Whatever the reason, two… three decades later, we still use the software as glorified paper and pencils.

The first problem with this model is that – all of the information in a set of plans is represented graphically. The problem with representing data graphically is that graphic data is not immediately recognizable. It is fuzzy. You can’t look at a sewer pipe sitting there - drawn on the screen - and know “Why, that pipe has an incoming invert of 120.34 and an outgoing invert of 122.43! It’s flowing the wrong way!”  

You have to measure it, label it, add notes, dimensions, etc. So you’ve got a label on the pipe – Nooooooooooooo! Duplicate information! Duplicate information is the evil of any data-driven system. It wastes memory and time, and when it comes to updating… I’m going to estimate that 80% of the errors I see on plans result from some piece of information being missed during an update - caught on pages C3.5 and C7.8, but whoops… someone missed it on page C9.39.

“How is the information duplicated” you ask? Well, you’ve got your line – which has an exact length, and (assuming it was done in 3D) exact invert elevations. The rest of the data can be derived from that. But you’ve also got your label – a textual representation of the same data.

Here and there the software attempts to keep that data in sync. For example, in AutoCAD, dimensions can maintain association. Move the line, and the dim comes with it, automagically updating. Civil3D actually takes the concept much further. Tweak an alignment, and entire profiles update in real time.

But overall, the system is still massively graphically oriented. AutoDesk’s work (and others, I’m sure) represents a combination of two paradigms – a compromise between the old system and the alternative system. A necessary compromise, no doubt. Even with Civil3D’s familiar environment, it’s still been slow to take off.

Those stubborn engineers.

So what IS the alternative system?

As usual, AutoDesk has taken the most prominent stab at it. It’s called building information modeling (BIM) in the architectural context, and AutoDesk’s Revit apparently takes a non-graphical approach to developing plans. I haven’t played with it yet… but, whether Revit or some other system, the industry is movin’ that way, so we’re all going to jump on the bandwagon sooner or later.

AutoDesk aside (THEY’RE EVERYWHERE!!!1111), what is BIM?

1. It’s the way things should  be.

2. It’s fundamental premise is:
Plan data must be represented in cold, hard form that is not open to fuzzy interpretation, and relationships between the data must be defined. That means – you should be able to represent an entire design in a relational database, where the data is in unforgivingly well defined form, and relationships between various elements of that data are defined and rigidly adhered to. The important part – the graphics must be derived from the data, not the vice-versa.

That’s a mouthful – so here’s an example.

Say you have a square building in plan view. You grab a corner of the building via a grip, just like in AutoCAD, and give it a stretch, lengthening one of the walls. The way things are usually done now, this will simply stretch that one corner of the building, and obviously, your square now has two corners that are no longer 90 degree angles. The way it would be handled in  a BIM system:

You’d stretch that wall. The graphical representation of the object would communicate with the underlying database: “my length has increased by 10′”. The database would update that value. Next, the database would go through all of the relationships connected to that wall. It would find that a relationship has been defined by the designer, that the opposite wall is to be the same length as the current wall. It would update the length of the opposing wall to be the same as the stretched wall.

But wait! That’s not the end! This is just plan view. Because of our no-duplication rule, all associated elevations, sections and details are all referencing the same data. So you stretch that one wall – and WHAM! The entire plan-set updates itself. Perfectly. No errors. Not even on lonley page C9.39.

Sweet. So what’s the point of this article?

Whether due to affordability, stubborn engineering minds, (reasonable) caution in adopting new technologies, or inter-industry file compatibility issues, BIM (or… I dunno… how about SIM – “site information modeling” for civils) is proving slow to take hold. HOWEVER! Partial solutions are available, and can be incorporated directly into existing systems. At least in AutoCAD, which, at this point, is all I can talk about from personal experience.

The most basic support, which has been around for pretty much ever, is external references – aka xref’s. These are simply live links between multiple files. Update the design file, and all sheets that reference the design file will update. For the most part, xref’s are horribly abused, used inappropriately, used without well thought-out schemes, etc. But used properly, they can play a huge part in minimizing data duplication.

Also basic is – viewports, and the associated layer control provided per viewport. The downside of viewports is the scale/text size complexities they introduce. Those complexities can mitigated with excruciatingly well organized text styles and … erm… a large brain.

More advanced, an exciting introduction to AutoCAD is dynamic blocks and attribute extraction. Dynamic blocks allow you create parametric “smart” objects, and attribute extraction allows you to view information embedded in blocks (traditional or dynamic) in a myriad of ways. A simple example of the power of these two combined can be seen in the keynote system download(opens in a new window) on this site. Not included in that example is the Dynamic Block’s ability to be data-driven via a small, self-contained database-like function called a “lookup table.”

Advanced to the point of near-inaccessibility (and used by probably 1% of the industry), you have database links and VBA support, which together can do amazing things… as long as you have a true geek on your team to write some custom software.

Anyway, I would like to do some “Best Practice” articles on xrefs, file organization, etc. But since I never finish things that I start, or  follow up when I say I want to do something, who knows?

Check back in a week.

  • Print this article!
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • StumbleUpon
  • Yahoo! Bookmarks

Powered by WordPress