I am still in Munich supporting the one-week Forge accelerator workshop, returning back to Switzerland by train tonight.
For ecological reasons, I prefer to avoid flying whenever I possibly can.
Lots of exciting development is going on here, and we are making great progress.
I have another important detail to report from the the RTC Revit Technology Conference Europe in Porto last week, and other little titbits to share as well:
As I mentioned in the notes from the Revit API discussion panel, one of the topics we touched upon was how to edit and continue, aka debug without restart or live development, i.e., enable the full cycle of debugging an add-in, discovering an error, editing the code to fix it, and continuing debugging in the same Revit model without being forced to terminate and restart Revit and reload the project.
This is not immediately achievable, because if you use the Visual Studio debugger to launch Revit, it will lock the DLL that you are debugging, and you will not be able to edit it.
The standard suggestion to work around this that I made in the past is to convert your add-in code to a macro for debugging, and then convert it back again when done.
Various other suggestions have been made (and are listed in The Building Coder topic group 5.49 mentioned above) to enable reloading the add-in without converting the code to a macro, e.g., by loading it from an in-memory byte stream instead of a file.
Michael Porskær of Orbicon A/S pointed out that he uses a much simpler and more direct method by running Revit.exe in normal standalone mode instead of launching it from the Visual Studio debugger, attaching the debugger to the Revit.exe process, and using the AddInManager provided with the Revit SDK to load the add-in.
Here are the exact steps:
Michael published the 52-second video DebugCommandWithoutRestartRevit showing these steps live:
Thank you very much, Michael, for documenting and sharing this!
I am very glad that Sander Obdeijn of Itannex is here participating in the Munich Forge accelerator.
He has extremely deep Revit experience, both in the user interface and API.
He uses the approach described above to debug his Revit add-ins and pointed out a handy tool to make it yet more efficient:
You can use the Resurrect Visual Studio extension (source on GitHub) to automatically re-attach the debugger to previously debugged processes with one single click.
I answered a lot of repetitive questions in the last couple of weeks and months – not to mention years and decades.
That led me to realise recently that I am pretty sure that at least 10-20% of my work could be automated.
The tasks that seem most easy to address are responses to simple questions on getting started raised in email messages and discussion forum threads.
I would need tools to:
After a couple of months of training, I think the system should be able to:
Initially, I would expect it to rate all probabilities at zero percent.
At that point, I should be able to start training it.
Some of the auomatically generated reponses I would classify as acceptable and use as is.
Others (or all?) might need some tweaking, and could also be used after slight improvement.
Same might be way off, of course.
Training would begin.
Who knows, maybe I am already much further, and the text you read here now was AI generated?
Check out these other AI, CAD and communication related items:
Design Graph provides a new way to explore your 3D design data using shape-based machine learning to recognize and understand parts, assemblies and entire designs. It learns to identify the relationships between all parts within and across all of your designs, irrespective of whether cross-references exist. It learns to interpret designs in terms of those parts and provides a way to navigate your data using simple text search, learned categories of parts, shape similarity, usage patterns and even smart filters for part numbers, materials and other properties.
Microsoft announced progress and a historic achievement reaching human parity in conversational speech recognition.
Matt Taylor pointed out the interesting report on an artificial intelligence course creating an AI teaching assistant.
The students didn’t even know their TA was a computer.
The key phrase for me is that "... the number of questions increases if you have more students, but the number of different questions doesn’t really go up ... the same questions [are repeated] over and over again."
That is exactly what I have been noting more and more in my work recently, and what spawned my interest in this.
"The students ... studying artificial intelligence ... were unknowingly interacting with it... The goal is to have the virtual teaching assistant answer 40 percent of all questions by the end of year."
Thank you very much, Matt, for pointing out this perfect example of what I am after!
On a completely different topic...
I went to a nice little open floor dance event last Sunday evening immediately after my arrival here in Munich, in the Mohr-Villa Kulturzentrum, organised by Juliana Barrett.
I only mention it to point out (and as a note to self) that she was using a portable sound system with pretty good loudpseakers, the HK Audio Lucas Nano 600.
A picture from my last morning walk to the office across the Isar:
