Let's look at two serious choices that we are facing – one more serious than the other:
To Dynamo or Not to Dynamo
I explained some aspects of getting started with the Revit API and Dynamo programming, as well as the choice between working with Dynamo versus the pure Revit API, in the Revit API discussion forum thread on Dynamo:
Question: I am completely new to Dynamo.
Is there a way to generate different plate sizes in Revit using a
.txt file with Dynamo?
txt files with all the information needed to generate steel frames.
Before buying Revit, I would like to know if
txt data can be uploaded into Revit and used to generate 3D models (maybe by using Dynamo).
Answer: Welcome to the Revit API!
Yes, what you describe is possible in Revit.
However, please note that this discussion forum is dedicated to programming Revit using the standard .NET Revit API.
If you specifically want to implement your solution using Dynamo, the best place to discuss it is probably in the Dynamo discussion forum.
If you want to work with the standard .NET Revit API, please read the Revit API getting started material first and work through the DevTV and My first Revit plugin tutorials.
Response: Thank you. Can I ask you one more question?
Is standard .NET Revit API better than Dynamo to import text data into Revit to auto generate steel frames? I have a 3rd party program that designs custom steel frames. The data files have everything needed to generate a 3D model. I don't know Dynamo or standard .NET Revit API so I will be starting from scratch. I know just enough Revit to be dangerous. I really appreciate your advice!
Answer: Dynamo is a wrapper around the standard Revit API; search these articles for 'dynamo' and 'wrapper':
- RTC Revit API Panel, Idea Station, Edit and Continue
- Dynamo, Symbol vs Type and Exporter Exception
- Zero Touch Node Wrapper and Load from Stream
- 11 Years and Revit API Docs Full Text Search
- TBC Samples 2023 and the New Structural API
Dynamo also adds some functionality of its own, e.g., its own geometry library.
For your purposes, I think both would work well.
For learning purposes, I would suggest starting step by step with different areas:
- Revit end-user interface, optimal workflow and best practices
- Programming basics, e.g., a non-Revit-related Python tutorial
- .NET programming basics, e.g., a non-Revit-related C# tutorial
- Revit API basics, e.g., the My First Revit Plug-in video tutorial
- A Dynamo tutorial
The first is vital. You need that to understand and solve your Revit task. Only after understanding it from a UI point of view will you be able to address it effectively from the API side of things.
Learning a little bit of Python is highly recommended. It is the most didactical language there is, and learning basic programming with it is fun and easy.
.NET is the foundation of the Revit API, so you need some understanding of that.
You need to understand the architecture of the Revit API to get an add-in implemented, loaded and running.
You can quickly dive into Dynamo and then compare to see what you prefer:
- Python versus C#
- Pure Revit API versus Dynamo
Rereading your question, I think that the most important step for you first of all is the first one: research the exact manual steps required in the user interface to read the available text data and generate your steel framing in Revit from that. I assume that the text data specifies the steel framing cross-section in some way, either by using predefined profile definitions or specifying the exact geometry of the cross-section. So, how can that data be transformed into Revit to define an appropriate steel framing element type? Once you have the profiles and element types defined, I guess placing the steel framing is simply a matter of reading the beam, column and framing element start and end point and placing straight segments. Finally, your text data may be specifying how the elements are connected and joined. That may be very complex. All of this is probably non-trivial to achieve in the UI. You need to know the exact UI approach, best practices and detailed execution steps before you can start thinking about programming it.
The pure Revit API will give you the greatest flexibility. The Dynamo framework may possibly offer predefined existing libraries and packages that you can use, and you may find it easier to learn. That is a question of taste.
But first things first: what do you have, what do you need, and how to achieve it optimally in the UI, applying best practices?
Home Planet at Great Risk
Our one and only home planet is at great risk and requires immediate radical action if we wish it to continue sustaining life and human civilisation in the manner we are accustomed to.
This fact is expressed very clearly and with as much hope as we can possibly muster by Sir David Attenborough presenting Breaking Boundaries – the Science of Our Planet, a 10-minute preview of a Netflix documentary:
Breaking Boundaries tells the story of the most important scientific discovery of our time – that humanity has pushed Earth beyond the boundaries that have kept Earth stable for 10,000 years, since the dawn of civilization. The 75-minute film takes the audience on a journey of discovery of planetary thresholds we must not exceed, not just for the stability of our planet, but for the future of humanity. It offers up the solutions we can and must put in place now if we are to protect Earth’s life support systems.
The boundaries he talks about are the nine planet boundaries identified by the Stockholm Resilience Centre. It presents the film in more detail in its research news: New Netflix documentary brings the planetary boundaries to the world.
Here are some of the comments on the YouTube preview that stood out for me:
- This was frightening but gives hope. So much waste and for what? Our planet and life are amazing.
- Just imagine a civilization that dreamed up 52 different flavors of ice cream, and the atomic bomb – being so lazy, it could NOT SAVE ITSELF from a looming, self-made extinction level event. The Age of Stupid is upon us, and David Attenborough is sounding the alarm.
- It's great that people are starting to understand some of the details of the climate and ecological crisis. It should also be known that governments around the world have known the risks for a very long time, and most have chosen to do next to nothing, knowingly submitting the next generations to unimaginable suffering. We cannot rely on these political systems to do what is necessary. It is time for ordinary people to work together and demand a better future. I believe our best bet is to join Extinction Rebellion and act as if the truth is real
- There's a huge disconnect between our understanding of planetary boundaries and our current lifestyles. We admire what he does and says, but who is actually willing to stop flying? To cut their holiday driving? To simplify their lifestyle? To buy less stuff? We're just not getting it, are we – we're all waiting for someone else to do something. What will we say to our kids, a couple of decades hence – when it's too late? The responsible thing would be to get political and demand change NOW – even if it hurts.
Scott Sheppard explains several other aspects and points out detailed research results in each of the critical areas in his article explaining how Autodesk software can help address the nine planetary boundaries; I quote from there:
Data sources for the charts:
- Stockholm Resilience Centre
- Our World in Data: Annual CO2 Emissions
- Our World in Data: Outdoor Air Pollution
"Save the Planet" is a misnomer. Whether the result of human activity or natural long-term planetary cycles, planet change will not destroy the planet, but it might make it inhospitable to humans. The Earth is our home. If you stopped paying your electric bill, didn't repair your air conditioner, or got the water turned off to your home, your house would still stand and not crumble, but you wouldn't want to live there. So regardless of the cause of planetary change, we must take care of the Earth as our home. "Save the People" appears to be a more apt slogan.
The Stockholm Resilience Centre is an international research center on resilience and sustainability science. The center is a joint initiative between Stockholm University and the Beijer Institute of Ecological Economics at The Royal Swedish Academy of Sciences. The center believes in the importance of reconnecting humanity to the biosphere. People must stop considering nature as something separate from society because people and nature are indeed intertwined in social-ecological systems. The development of places and things can no longer be done without an increased understanding of nature's role in humanity's own survival and well-being. [stockholmresilience.org]
One of the tenets of the Stockholm Resilience Centre is a set of nine planetary boundaries:
- Ozone – stratospheric ozone depletion
- Biodiversity – biosphere integrity
- Pollution – novel entities (e.g., organic pollutants, radioactive materials, nanomaterials, microplastics)
- Temperature – overall planetary warming from climate change
- Ocean – ocean acidification
- Freshwater – freshwater use
- Forests – land system change
- Plants – biogeochemical flows
- Clouds – atmospheric aerosol loading
The theory behind these boundaries is that if we allow the Earth to cross enough of them, there is no turning back. The Earth will no longer be a hospitable place for us. Though the nine planetary boundaries were established in 2009, there have been some recent articles (in the last few months alone) related to them:
At Autodesk, we are inspired by the prospect of a better world designed and made for all. Our mission is to empower innovators with design and make technology so they can achieve the new possible. To do that, we deliver customers intuitive, powerful, and accessible technology that provides automation and insight for their design and make processes, enabling them to achieve better outcomes for their products, their businesses, and the world. Everyone's definition of "better" may differ, but hopefully, everyone can agree that it includes "hospitable."
Respecting boundaries is alive in the lab.
Many thanks to Scott for raising the issue and permission to quote your text!