Rube Goldberg Code

[altenbach]

Ben wrote:

Advanced PID fromthis thread. 

---

Ben, something's wrong with you link... 😞

[Ben]

Thanks Christian.

For the sake of completeness the proper link is here.

Q: What do you think about those fancy graphics in the diagram?

Ben

[tst]

Here's another scary piece of code (from here😞

 

And in case you think this isn't RG code, I'm sure it could be done in a simpler way.

Nice one, Jim. I just hope you don't have to maintain that. 😄

[Ray.R]

tst..

You'd be impressed at how often clients show us code just like that.

Now imagine an immense LV folder full of projects sharing files from all over the place, where there are many VI's that share the exact SAME name and everyone checks in & out of the one & only (unique) repository.  Now to make life more fun, picture the large immense labview folder (labview being the name of the folder) having 14,097 files (most of which are VI's) spread across 1579 folders and taking up 4.91GB on the PC.

Am I allowed to cry?

R

Message Edited by Ray.R on 02-12-2009 02:18 PM

[smercurio_fc]

My eyes! They burn!!!!

[tst]

Our own projects folder had these issues where different projects referenced each other's files and had copies of vi.lib files, etc. At some point I wrote a program which went over all the projects, namespaced the VIs and moved things around so that this situation no longer happened. And we didn't even have SCC at the time.

---

Ray.R wrote:

Now to make life more fun, picture the large immense labview folder (labview being the name of the folder) having 14,097 files (most of which are VI's) spread across 1579 folders and taking up 4.91GB on the PC.

---

I'm not sure I see the problem with this (other than using the wrong capitalization for LabVIEW). Our projects folder is probably not dissimilar in size (especially with Subversion creating duplicates of each file). And it's also inside a single Subversion repository, which makes the repository large, but makes it easier to handle. We could probably separate the projects into separate repositories, but then we'd have to automate some of the Subversion work (e.g. the initial checkout).

[Wayne.C]

Ray.R,

As long as you cry in your beer, who cares?

P.S.  That's like the third username I've seen you use today.  Identity crisis?

[Ray.R]

---

centerbolt wrote:

Ray.R,

As long as you cry in your beer, who cares?  --  I'm off beer for a while..  😞   maybe I'll cheat on the weekend...  The beer is almost a year old.  Aged Stella

P.S.  That's like the third username I've seen you use today.  Identity crisis?  --  Yep.  Someone beat me to "RayR" so I put a period .  Bye bye JLV

---

tst,

Yep..  You've described what the folders look like.  They've evolved since LV6.0.  Imagine the surprise I had when I did a mass compile and was facing all the crosslinking issues.  I'm surprised to read that you have a similar large-scaled folder.  It's the first time I encounter such a mess.  I'm going to write a vi to clean things up. 

R

[tst]

Just to make it clear, it's not a single folder. It's a folder called "Projects" which has subfolders for each client and their projects. The entire projects folder is in a single Subversion repository. In the past, it had problems where different projects used VIs located in other projects and different projects had VIs with the same names, which was the problem the program I mentioned handled.

Hmm, maybe I should finally change my user name as well.

[Ray.R]

Over complicated error clusters (Multiple controls / indicators)

http://forums.ni.com/ni/board/message?board.id=170&message.id=393402