Modification Tracking with Dynamo

Modification tracking in a Revit model is a recurrent topic. It’s always very time consuming to compare different versions of the same model, and to figure out what’s new, what was deleted,  and what has changed.

A little online research pointed me, as often, to a post from Jeremy Tammik on the building coder. In his post, he describes two approaches to the problem. One of these aproaches is to compare “snapshots” of models. His work inspired me to create a couple of dynamo nodes and workflows to facilitate the fastidious task of modification tracking!

The goal was to create an easy way to figure out what modifications occured between two versions of the same model and to offer an easy way to visualize those modifications. I will first introduce the set of nodes I came up with then I’ll develop about how they can be used in three separate workflows.

modificationtracker-nodes
Modification Tracking nodes, Data-Shapes Package

1. The Nodes:

1.1 ModificationTracker.ModelComparison: This node is the first step of the modification tracking. It takes 3 inputs :

  • DocumentA : Current document by default.
  • DocumentB : The document you want to compare DocumentA against.
  • Categories : List of categories you want the ModificationTracker to take into account

The code of this node uses the elements’ GUIDs to determine whether they are existing, new or deleted. It will return a report of the modifications and lists of the existing, new and deleted elements. The ExistingElements Data output is the data you’ll need to initiate the geometry and metadata comparisons between DocumentA and DocumentB.

comparison

1.2 ModificationTracker.GeometryChanges: This node compares meshed approximations of the geometry of elements that exist in both DocumentA and DocumentB. It will then output the elements with the same geometry and those with a modified geometry in separate lists.

geomchange

Here are the definitions I used to get the geometry “Snapshots”:


#Copyright (c) mostafa el ayoubi , 2016
#Data-Shapes http://www.data-shapes.net , elayoubi.mostafa@gmail.com
#This code was inspired by Jeremy Tammik @Jeremytammik
def flatten(container):
for i in container:
if isinstance(i, (list,tuple)):
for j in flatten(i):
yield j
else:
yield i
def tostring(x):
return x.ToString()
def getgeomlist(x):
return list(x.get_Geometry(Options()))
def getvertices(x):
#getting geometryelements as list
geomelems = getgeomlist(x)
#getting nested instance geometry for all geometry instances
while any('GeometryInstance' in g for g in map(tostring,geomelems)):
for index,i in enumerate(geomelems):
if 'GeometryInstance' in i.ToString():
geomelems[index] = i.GetInstanceGeometry()
else:
continue
geomelems = list(flatten(geomelems))[0]
#getting all faces, keeping meshes
faces = []
for i in geomelems:
if 'Solid' in i.ToString():
faces.append(list(i.Faces))
elif 'Mesh' in i.ToString():
faces.append(i)
else:
continue
faces = list(flatten(faces))
#getting all meshes
meshes = []
for f in faces:
if 'Mesh' in f.ToString():
meshes.append(f)
else:
meshes.append(f.Triangulate())
#getting all vertices
vertexlist = []
for m in meshes:
vertexlist.append(list(m.Vertices))
vertexlist = list(flatten(vertexlist))
#creating sorted vertex string representation of object for comparison with other indice of element
vertexstr = ', '.join(sorted(set(map(tostring,vertexlist))))
return vertexstr

view raw

ModificationTracker – getvertices

hosted with ❤ by GitHub

1.3 ModificationTracker.ParameterChanges: This node compares string “Snapshots” of the parameters of the elements that exist in both DocumentA and DocumentB. Like the GeometryChanges node, it will return changed and unchanged elements in separate lists.

paramchanges

Here is the definition I used to get the parameter values “Snapshots”:


#Copyright (c) mostafa el ayoubi , 2016
#Data-Shapes http://www.data-shapes.net , elayoubi.mostafa@gmail.com
#This code was inspired by Jeremy Tammik @Jeremytammik
def parametersnapshot(x):
parameters = x.Parameters
paramnames = [p.Definition.Name for p in parameters]
#Sorting is important because the parameters are queried in random order.
#We need to make sure the snapshots are ordered in the same way so we can compare them.
sortedindex = sorted(range(len(paramnames)), key = lambda k : paramnames[k])
sortedparameters = [paramnames[i] for i in sortedindex]
paramvalues = []
for p in parameters:
if p.AsString() != None:
paramvalues.append(p.AsString())
else :
paramvalues.append(p.AsValueString())
sortedvalues = [paramvalues[i] for i in sortedindex]
return ', '.join(['%s : %s' % (param,value) for param,value in zip(sortedparameters,sortedvalues)])

view raw

ModificationTracker – parametersnapshot

hosted with ❤ by GitHub

1.4 ModificationTracker.AllChanges: This node compares both the geometry and the parameters of the elements that exist in two versions of the same model:

allchanges

2. The Workflows

These nodes were created to serve the following workflows (I make use of UI.MultipleInputForm++ and Dynamo Player in order to make them as user friendly  as possible ) :

Important note: The ColorSelection input in the form is only available with revit 2017. You will have to set the color overrides whithin the script if you are using Revit 2016 or a previous version. 

2.1 Visualize geometry changes:

This workflow will prompt the user to select the linked model to compare the current model against, the cotegories to track and the override colors for changed, unchanged, and new elements.

geometrychange
Check Geometry changes between two indices of a same model | download .dyn for Revit2017 | download .dyn for Revit2016 or previous

To test this workflow, I have created a “Dummy” Revit file with some walls and colums, then I moved some of these columns and walls and saved it as a new version. I have tried the workflow on a “real” model with over 2000 elements and the performance was still pretty good.

geomchange-1

2.2 Vizualise parameter value changes:

This workflow works in a very similar way to the previous one except it tracks parameter value modifications instead of geometric modifications.

parameterchange
Check Parameter Value changes between two indices of a same model | download .dyn for Revit2017 | download .dyn for Revit2016 or previous

As a test, I have two versions of a same model where only some text parameter values have been changed on a wall and two columns.

paramchange

2.3 Vizualise geometry and parameter value changes:

This workflow allows to track parameter value changes as well as geometric changes. It creates a form that prompts the user to select the linked file to take into account, the categories, and all the override colors.

allchange
Check All Changes between two indices of a same model | download .dyn for Revit2017 | download .dyn for Revit2016 or previous

all changes.gif

Please let me know if you’re facing any issues with those nodes. I’d be happy to improve them!

47 thoughts on “Modification Tracking with Dynamo”

  1. These look very useful. I assume the intent is that Document B would be an “archived” copy of the same model saved earlier? I envision comparing two linked mechanical models – an older version that I used to coordinate electrical connections and the current linked version. Since I work directly in neither they would both be linked. Can’t wait to give them a try.

    Liked by 1 person

    Reply

    1. Hi Scott,
      yes that’s right. “Indice” might not be the propper term in english. But the idea is exaclty what you describe.
      Also, while the nodes will give you the lists of changed/unchanged elements between two linked models, you won’t be able to override their color in a view. To my noweledge, this can only be done with the current model. I would be very happy if someone proves me wrong about this! 🙂
      I’d be very interested to know how they work for you.

      Like

      Reply

      1. Hi Mostafa,

        I use both Revit 2016 and 2017 and was trying your “Model checker all workflows” graph (un-modified) in 2016 and received a “dereferencing a non pointer” error at the Element.OverrideColorInView node.

        I created two detached mechanical models, modified one and linked the unmodified one into the “new” version and ran the graph within the new version of the model.

        Thoughts?

        Thanks much,

        Scott

        Like

    2. This is due to something that was pointed out by Cesare Caoduro today . The ColorSelectionDialog is not exposed in 2016. I updated the package today to handle that exception. You should be able to use the script with no problem in Revit 2017, but you won’t be able to have the color selection buttons on the form with Revit 2016. Also, is your Revit language english?

      Like

      Reply

      1. Hi Mostafa,
        Awesome work!
        I’m using Revit 2017 and I’m still experiencing this issue even though I downloaded your package update from today. I received a “dereferencing a non pointer” error at the Element.OverrideColorInView node.
        Cheers! Thank you so much for your work!
        Brice

        Liked by 1 person

  2. Pingback: Weekly Roundup – 2016.52 & Post 200! | The BIMsider
  4. Pingback: Model Change Tracking with Dynamo - Revit news

      1. Thanks for the response! Not sure OOTB colo.ByRGB node is? Is it from a package?

        Would it work with the color picker from rhythm of John Pierson for earlier versions?

        Also from a revit perspective GUID is rather unstable with different versions, Would i have to change any script to switch to element ID?

        Once again you are bringing cutting edge stuff to the masses thanks a lot Mostafa!!

        Liked by 1 person

      2. I have tried clockworks nodes which are the one you use but no effect 😦

        What can I feed to the geometry colour change codeblock?

        I ll do later a post on the forum

        Liked by 1 person

      3. Rather randomly I got it to work. Sorry for overflowing your comments, but i find it extremely intresting.

        Anyway Ican add deleted elements as well in the geometry workflow?

        thanks

        John

        Liked by 1 person

    2. Hi John, thanks for you comments
      if the deleted elements are in the linked file, you won’t be able to override their graphics. As far as I now, this cannot be done through the Revit API. Glad you got the colors to work. John Piersons ColorPicker works with the same method I used so you wont be able to use in a version of revit older than 2017. What you can use though is the color picker from UI++ package . Don’t hesistate to ask on the forum if you need help !

      Like

      Reply

  6. My name is Lewis Kent I am a BIM manager at a Large Contractor and this is the perfect tool for me, will save me and my company alot of time and cost. I am a new to Dynamo could you please advise me how to go about getting this up and running tutorials etc i will need to get myself up to speed and become able to create manipulate this script to my projects.

    I thank you in advance for even creating this any further assistance will be humbly received.

    Liked by 1 person

    Reply

    1. Hi Lewis,
      thanks for your comment, saving people time and money is exactly the purpose of that kind of work 🙂 Very glad you think it can do that for you.
      The wrokflows I described in the article are pretty much ready to use, you can download the .dyn file (pick the right one according to the version of revit you’re using) and open it with dynamo1.2 and you should be able to use it as described. If you face any issue I’d be happy to help, just ask on the dynamo forum.

      Like

      Reply

  7. Hi Mostafa,
    Wow! Good idea, good implementation. Discoverd this tool just this week. Up to now, I hit one snag; the ModificationTracker.AllChanges tool does not seem to recognize an added parameter. Am I correct in assuming that for still-existing elements, it only checks parameter values for parameters that existed in the families in the original file?
    Still, the .ModelComparison does the heavy lifting, I think I can take it from there.
    Thanks!

    Liked by 1 person

    Reply

    1. Hi Ekko Nap,
      thanks for your comment. You’re correct if a parameter is added the nodes will consider that the parameters have changes, even if all the existing parameters are the same. I will try and find a way to handle thoses cases better. Thanks for the feedback!

      Like

      Reply

  10. Hi Mustafa, Great job. I’m wondering if is possible also to track location changes with this workflow. at this point is the missing components for this great workflow… is it possible to track a change of location of a components that has been moved?
    Thanks for your work

    Liked by 1 person

    Reply

      1. Yes, i’m experiencing some troubles, with some columns placed at grids crosses. When you move one of them, the columns records a different value on the “Column Location” Parameter. So the nodes records a change in parameters but not on the location. There is any open tread on the Dynamo forum where i can post some screenshots, or in any other place on the web.

        Liked by 1 person

  11. Hi Mustafa,

    Thank you, I am a BIM Team Leader and it’s very useful tool for me.

    I just discovered in two days. I have got some issues with the Properties change.
    I can not track the change of some instant parameter of system families (Material of wall, etc…) and some user type parameters (such as material of window frame, etc…) .

    In the other hand, I have Solibri to track the change of IFC models. However, the feature to track the modification inside Revit is very great.
    We have tried to make an add-in to track all changes inside Revit and your work with Dynamo is uesful reference for us to do that.

    Hope we can share the ideas and knowledge.

    Thank you again.

    Liked by 1 person

    Reply

  14. Hi Mostafa, I’m using your script ( check geometry only ) in revit 2016 and i can’t get teh UI menu to come up when i run dynamo.

    Any idea why this might be happening.

    Great work by the way and thanks in advance

    Kind regards

    Liked by 1 person

    Reply

    1. Hi! Thanks for your message 🙂
      First of all, make sure you’re using the .dyn for revit 2016. It’s different because Revit 2016 doesn’t support the color selection input of the form. The second thing you can do is right click on each input of the data-chapes nodes and make sure the default values are activated. This only needs to be done once. I should update the downloadable definition and fix that.. 🙂

      Liked by 1 person

      Reply

  15. I cannot seem to recreate the graphs so that they work in REVIT 2018.3. the codeblock after Multipleinputform++ fails as a Get.valueatindex operation failed « index out of range » error.
    Any thoughts?

    Like

    Reply

    1. Please disregard my previous question. I figured out that I had some inputs that needed to be reset..again. I constantly get bit by this one by forgetfulness 🙂
      Thank you for such a great Contribution!!

      Liked by 1 person

      Reply

      2. Dimitar
        I believe the process is to select the placed node on the canvas, then right click to get the options. There is where you can “reset” the node, but I believe it has to have Thrown an error first before that option becomes available as I cannot get it to show on a correctly working node.
        Sorry for such a long delay in the response!

        Like

  16. Hi Mustafa (forgive my spelling),
    This script works well when comparing old and new versions of an equivalent model. However, is there a node modification / script that performs a similar task, only between linked models comparing, say, architectural and structural models? My end goal is to track the same category from each model, compare them, and color/flag them visually if one of them changes / something is added.

    Like

    Reply

  17. I’d like your input on the feasibility of using this workflow to compare two views in the same model. The idea is to compare detail callouts for similarity in order to inform the placement of live vs reference callouts. Thoughts?

    Like

    Reply

      1. Presumably the idea is to find similar locations in a model, referenced against a user indicated location and range (by means of selecting an existing View?), and place a View Reference in certain other Views?
        Or would it be more feasable to compare Views to a user-input original and replace those Views with Reference Views where the Callouts were visible?

        Like

Leave a reply to data|shapes Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.