[Plugin] CleanUp
-
I think about this too from time to time. And one of the problems is that it might be easy enough if all components were inserted with the same rotation, but it gets tricky if all components are rotated differently.
To help compare, you could take all edges from comp1 and compare its length against all edge lengths in comp 2. They should have all the same amount, of the same lengths if they are possibly the same component. That would help determine if you should continue comparing the two components.
Also, you could compensate for components that are the same, with different scale factors by the same idea. Get all edge lengths for each. Then take each comps shorteest edge, and scale it up to be the length of the other comps smallest edge. Get that scale factor, and scale all edges the same. THen compare to see if the newly scaled lengths all equal the target component's edge lengths. And voi-la, theres a way to test for scale differences.
Just some ideas while they were still in my mind.
Chris
-
I was thinking of taking the source object and start of with an entity, compare it and it's connected faces and edges (length and angle betweens) and then iterate through the target object and look for matches. Once a match is found, iterate to next entity in the source and see if it compares to any of the potential next entities in the target.
...too complicated...?
-
I think something like that is what you would end up having to do, but I was imagining you could cut out a lot of groups by first testing them with whay I was suggesting. If for example, you have 100 groups. And you don't know if they are possibly same components or not, you could test them based on their entity number.
All groups with the same amount of entities, then get tested together for the same amount of edges, same amount of faces. Those that still have matching numbers move on to the next round of comparisons. Maybe we are down to 10 that have the same amount of entities, same number of edges and faces.
Then compare those 10 based on all edge lengths. If their edge lengths don't match up, maybe try adjusting the scale using them method I outlined. Then if by chance you end up with any components that match entity.length, and edge amounts, and face amounts, and their edge lengths all match, then maybe you have a good chance of them being the same component.
Then at that point, I was thinking you could look for any edge length that only has 1 identical edge length match in the other group. Then you have a starting point for aligning axes, using the identical edges. Just take one component and transform it to its one edge would be aligned to the other edge. Then you could compare all their point3d positions and see if they all are the same.
Of course, that would all be done with temporary groups or proxy Point3d objects or something.. The original group would need to remain unaffected. But I think you could identify groups that appeared to be identical based on entity counts, edge lengths, etc. Then take those and try to aligned them, you could then just test their points against eachother. And if their points are identical, you've got a match!
That is how I would forsee it happening. What I like about this method is that there is no looping through the model looking for angles. Just compare point positions.
Just a thought,
Chris
-
wanna connect to my notepadd++ and work on it? PM me
Chris
-
That's be cool - to make some real use of that Np++ feature! But I'm off to bed. Should have been there least an hour ago.
How many hours behind GMT are you?
-
+8 I think. I am still at work - 16:50 here.
Chris
-
You mean -8 .
A full workday in difference. Could be tricky to try this outside the weekends... -
Ahh yes, -8. Yeah, I normally catch you when you wake up and I'ts like midnight here. Or in the middle of the day for me and its the middle of the night for you. So maybe this weekend we'll try it.
Actualyl though, I already most ofthe code. I got the part that sorts all entities and makes an arrayof all the groups to compare. Now you can just finish up everything after that
Chris
-
I'll connect it to my magic 8-ball.
-
Kind of very useful this plugin ; i ve tried it on version 6 and it s pretty good (if u re setting well the variable debug).
So,thank you!Take care!
Elisei
-
guys, that new idea of the 'convert groups to components' plugin sounds exciting. I wanted such a script ever since i first importet my first model from 3Ds...
can't wait to see some first results -
@ely862me said:
Kind of very useful this plugin ; i ve tried it on version 6 and it s pretty good (if u re setting well the variable debug).
So,thank you!Take care!
Elisei
Regardless of the variable, you will run into a Sketchup bug where it's impossible to delete some edges, even if they are 100% planar.
-
Brilliant Plugin ThomThom!!! Perfect!!!
-
You can download this plugin from the first post in this thread, there should be a link somewhere in the post or sometimes towards the bottom of the post. You dont need to have a pro license to use plugins.
-
Yes - download link is in the first post. In this, and most others on this forum, it's at the bottom of the first post.
-
Thankyou! i got it and got it working
-
this cleanup routine is simply outrageous!
Yesterday I ran the intersect with modelroutine, hoping to get rid of 3 redundant duplicate planes that each face of an imported model had been blessed with I finally stopped SU after 4 hours of trying to due that job. the SU file had grown to 600,000k in the task manager window. Your Cleanup routine on the other hand was almost instant.
Well Done!
-
just cleaned up an imported model (from 3Ds Max).
cleaned up edges: 62.700
remaining edges: 84.300your plugin rocks, thomthom
-
ThomThom, ran this plugin on a file today - it actually took it a surprising long time to clean the file!
So I opened Outliner and find that there are 920 uniquecomponents in the file. It was obviously imported from OBJ file into SketchUp because each component is called "OBJ_29" etc.
So, if your Cleanup routine had an option "Convert All Unique Components to Groups" that would be great.
It's a fairly simple model, shouldn't really be more than a 1 or 2Mb file if it was build properly in SketchUp... but it's a 29Mb file!
I have tried selecting all the unique components and exploding them but SU appears to be chugging along quite some time on it, and I am unsure if it's completely frozen, or just working hard and ignoring me.
The absolute best for AutoCAD files would be one that said "Convert Identical Groups to be Identical Components"... wished for that many times when you have 50 columns that are all the same, but each is a unique "group" from ACAD.
-
@fletch said:
So, if your Cleanup routine had an option "Convert All Unique Components to Groups" that would be great.
It's a fairly simple model, shouldn't really be more than a 1 or 2Mb file if it was build properly in SketchUp... but it's a 29Mb file!
Converting the components to groups won't make the file any smaller. Internally, Groups and Components are pretty much the same.
@fletch said:
I have tried selecting all the unique components and exploding them but SU appears to be chugging along quite some time on it, and I am unsure if it's completely frozen, or just working hard and ignoring me.
Yea, exploding large amount of geometry makes SU crawl to a halt.
@fletch said:
The absolute best for AutoCAD files would be one that said "Convert Identical Groups to be Identical Components"... wished for that many times when you have 50 columns that are all the same, but each is a unique "group" from ACAD.
Why is the blocks unique in AutoCAD in the first place? Blocks are imported fine into SU as components. This is really more a matter how the ACAD drawing is made.
Mind you - I've also wanted a function to merge similar groups/components. When importing from Revit you often get windows that should be the same component as different components, but with different axis orientation.@fletch said:
So, if your Cleanup routine had an option "Convert All Unique Components to Groups" that would be great.
This could in theory be done easily. Except that there seem to be a bug in the SU API that makes the creating of groups some times crash SU.
Advertisement