Hello,
I have ran into an issue when running/tracking collisions.
First I run a clash test and mark up the clashes and organize them to be turned into a report. Navisworks automatically saves the data and if the model is updated the issues become resolved.
HOWEVER lets say you review 1st floor mechanical then 2ndfloor mechanical, and you isolate the sets (selection tree items, levels, etc however you break your model up) and hide everything else to make viewing much easier. If you "update all" clash reports and no longer have the 1st floor models selected it updates the 1st floor and says all the clashes are resolved. You can even try to correct this problem and unhide everything and reupdate it. You still loose all of your information you just inputed and the clashes are all appearing again as new. They no longer show that the clash was assigned or any comment that was inputed. This makes it extremely hard to track...
Is this suppose to happen? Is there a fix? Is there a best practice that prevents this?
Thank for visiting our blog.
Unfortunately this is an issue that our development team is working on a fix.
I will add your issue to the existing one but
I understand that this may be an issue, so I am including the following link. It is setup for you to submit feature requests, or feedback, directly to our development team:
http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=1109794
I encourage you to use the feedback link as our Development group is always interested and would like to hear your feedback directly, since you are better suited to state the business case for a feature request.
Hello,
We are running into this issue, is there a proper way to track week by week or meeting by meeting on clashes for each trade and properly track who is decreasing and increasing by looking at a graph of some sort that shows how it is tracking over time?
Thank you.
I like that! Please enlighten us on your workflow and how you create that chart.
Hi! Yes that looks like a nice UI. Something like that would be the most ideal, but to do it for specific clash tests within the same graph if possible (Elec. vs All, Mech vs All, etc.)
Is what you have available to include adding multiple tests?
What you show is nice looking, can you explain how it works?
Thanks!
public static void GetClashTestToCsv(Document doc, string path, bool groupAsSingleClash, bool includeDate, DateTime date) { var documentClash = doc.GetClash(); var clashTests = documentClash.TestsData; using (var writer = new StreamWriter(path)) { writer.WriteLine(includeDate ? "Date\tDisplay name\tTest type\tTolerance\tClash status\tCount" : "Display name\tTest type\tTolerance\tClash status\tCount"); foreach (ClashTest test in clashTests.Tests) { var countByStatus = new Dictionary<string, int>(); var clashResultString = (includeDate ? date.ToShortDateString() + '\t' : "") + test.DisplayName + '\t' + test.TestType + '\t' + Math.Round(test.Tolerance * 0.3048, 3) + '\t'; foreach (var issue in test.Children) { var status = issue is ClashResultGroup ? ((ClashResultGroup) issue).Status.ToString() : ((ClashResult) issue).Status.ToString(); if (issue is ClashResultGroup) { var crg = issue as ClashResultGroup; if (groupAsSingleClash) AddStatus(countByStatus, status); foreach (var cr in crg.Children.Select(issue1 => issue1 as ClashResult)) AddStatus(countByStatus, status); } if (issue is ClashResult) AddStatus(countByStatus, status); } foreach (var status in countByStatus.Keys) { writer.WriteLine(clashResultString + status + '\t' + countByStatus[status]); } } } } private static void AddStatus(Dictionary<string, int> dict, string status) { if (!dict.ContainsKey(status)) dict.Add(status, 1); else dict[status]++; }
I'm not sure if this will help you, but I've created a piece of code which can export all clash tests to a CSV file, which can easily be tracked week by week using MS Excel. Steps (which repeats every week):
1. Running clash detection over the NWF file which refers to the weekly updated NWC files (I'm using Update all command)
2. Exporting CSV file after updating all clash tests
3. Importing CSV file into the MS Excel file
4. Formatting data into a pivot table (which contains all the clash data since the beginning of the project)
5. Grouping data and filtering a chart (from my previous post)
Nope, the code will export a simple CSV file, tab delimited. CSV file can be imported into Excel using a few simple steps (Google for importing TXT/CSV data into Excel). This code is a part of my Navisworks plugin (which I've developed for my own use) and you can use it if you want to write something similar. Complete formatting has been done using standard Excel options. I've attached a video where you can see a workflow.
Whoa this is great. I may be interested in your plugin. What exactly does the plugin do?
Nice work.
Another option would be to do the Clash Report export as XML. This can then be consumed elsewhere using an XML reader, transforming it into HTML or something more suitable for a specific program. An XSLT transform could also be added in the file header to dynamically transform the contents to HTML for direct opening in Excel. Benefit here is it puts the burden of interpreting the data on the consumer rather than the producer (Navisworks).
Has the issue in the OP not been resolved? I'm pretty new to Manage 2018 and have a NWF with several sub-contractor models appended. For clarity, I've been hiding the NWCs that aren't relevant to a particular clash test (say windows vs steel), otherwise the clash view gets lost in a dense, irrelevant mesh of furniture and piping etc. This seems to wreck the trail of crashes I've created when re-running the test. Do you really have to leave *everthing* visible at all times?