Schedules - combining different categories
Thank you!
what i want to do is transfer information from an area schedule to a room schedule:
The first picture shows the area schedule with values for a Parameter called BGF.
The second picture shows the room schedule (only totals per floor) where i would like to show the BGF areas from the area schedule.
That looks like it works now because i created a room parameter called BGF and put the values from the area schedule manually in one of the rooms - which is wrong for 2 reasons: the BGF (gross room area) is obviously not the area of only one room. Second, I would like the parameter to be filled automatically...
Any idea how to solve that?
Thanks a lot!!
Accepted solution
Hi there!
thank you for the reply. Yes that definitely helped!
My question now is.... I tried to opn the file here but Dynamo is showing
"Error opneing corrupted file c:-----the name of the file...."
Question1 why is it not opening it?
Questions2
I opened another Dynamo file on linking the filled regions to schedule
I am not sure how to link certain filled region (and not ALL filled region) to set up a schedule
How can I do it?
Here I attach the dynamo file and the tutorial i followed was this one
https://www.youtube.com/watch?v=kd53-ofHCgY
Que. #1 - 95% sure this is occurring because you are attempting to open the dynamo in Dynamo version 1.
The dynamo file I attached for Fabiana must be opened with Dynamo version 2.0 or later.
Que. #2 - To identify only certain filled regions, you will want to filter out all the non-applicable elements by
a certain parameter value. To do that, you would employ the same dynamo blocks/nodes that were used to
filter out filled regions from all detail items (blocks in red, using data from the block in orange instead of
the "All Elements of Category" node).
Although, from what I can gather at this point, you're trying to use the dynamo in a use case that is very
much different from Fabiana's use case... and as a result, neither the dynamo you have provided, nor the
dynamo I made will work in your case without some substantial modification. Also, If you're just trying
to schedule filled regions, I would suggest dropping dynamo altogether and simply using the built-in
schedules. You should be able to pick out filled regions from a Detail Items schedule using the
"Family & Type" field.
However, if you are attempting to do something more advanced, Dynamo does have a semi-steep
learning curve and you will not learn everything you need from me, especially while on the
Revit Architecture forum.
You can use this website to learn more about how to use Dynamo:
And you should try to aim your Dynamo questions at this forum instead of the Revit Architecture forum:
*You'll get a lot more of your questions answered that way*
Accepted solution
@Anonymous
Yes! That would simply be a modification of the dynamos we've been throwing around so far. If you'd like to give it a try on your own, I can answer questions.
@Everyone
I'm currently working on a Revit addin to allow anyone to easily combine schedules from different categories.
If ya'll would like to help me test it out that would be greatly appreciated. If so, just stay tuned, I'll most likely post about it on this thread.
@Anonymous Sure! First off... You've gotten yourself into a bit of a pickle because A. Dictionaries can be a bit tricky to use, so I just avoid them and stick to lists & B. just knowing that you're using dictionaries doesn't clear up all the issues because the dictionaries that Dynamo uses (through the blocks... outside of the Python node) are different from the standard dictionaries used within Python.
Okay, this'll be a bit of a roller coaster, so hold on tight!
1. Dynamo Error ('iteration over non-sequence of type Dictionary')
The following error is indicating that you can't "Iterate" over a Dictionary :
And it's pointing to line 11 of the code.
And this is a perfect example of why I don't like dictionaries. For one, they can't be looped over because they have no intrinsic 'order'... there's no 'first' or 'last' item... so a loop can't iterate over a dictionary. A dictionary is really just a jumble of items we'll call pairs that have no idea how they relate to each other... no intrinsic association... no indexes. Each pair just has a key(string) that's connected with a value(integer, double... etc.) and you can ask the dictionary to get you a particular value in a pair... but ONLY if you already know the key that you're looking for.
So i'd suggest avoiding dictionaries if you can, but we'll make them work for now.
2. Dealing with the mismatch between Level counts for Areas/Rooms
From what I've gathered from your question, your core issue is that there may be rooms for levels 1-4 (for example) but only areas for levels 1-3... and the dynamo would freak out because there isn't a perfect 1-to-1 correspondence between the Room levels & Area levels. Well, one simple solution to this problem is to simply feed one list of dictionary keys into both "Dictionary.ByKeyValues" nodes (preferably from the list with less keys)... that way they should have matching keys.
In this example, we feed the keys for the Area dictionary into the Room ".ByKeyValues" node... so all pairs in the Rooms dictionary that weren't ALSO in the Area dictionary were dropped. Sort of a filter...
3. Finding a way to loop through these dictionaries and do our arithmetic
So, like I mentioned before, dictionary values can only be found if you already know the key you're looking for... so we'll feed in the same unique keys list from the smaller Areas dictionary that we used to filter the Rooms dictionary just above.
Now, I've made the following modifications to your code... Green = additions & Orange/Yellow = changes:
- First change (lines 7-8) I didn't highlight, but I removed the "UnwrapElement()" calls from the input. Leaving them doesn't hurt, but it also doesn't help. There's nothing for it to do so it just does nothing. It can only convert Revit element types from what Dynamo can interpret to what python can interpret... so it does nothing with a dictionary.
- Next, (line 9) I specified the list of unique keys that we KNOW appear in both the Areas dict and the Rooms dict as "levelKeys"... because those are they keys we will be searching for within the two dictionaries.
- Next, (line 13) I modified the loop to loop over the list of keys('levels') instead of the dictionary which it couldn't do anyways.
- (line 15-16) I added variables that would serve as the total calculated areas per level... one for the Rooms and one for the Areas.
- (line 18) I modified the object which the loop iterates over... making the loop iterate over a list of all the know values that correspond with the 'LevelKey' variable within the 'dicrooms' dictionary. As I mentioned earlier about how Dynamo dictionaries are different from Python dictionaries.... this means that they have their own special way of pulling values matching a given key out of them. Those special ways of extracting values are badly documented online, but they are documented here: https://primer.dynamobim.org/09_Dictionaries/9-3_Code-Block-Uses.html
The last image on that page shows a list of methods and properties you can call (methods and properties are essentially anything that requires following the object with a period like "dictionary.Count"). So, that documentation states graphically and very loosely that we should use ".ValueAtKey(key)" to get the values in the dictionary that are found on a specific level.
- (line 19) Has two modifications... one to finally unwrap the Revit element and convert it from Dynamo form to Python room. This time it WILL have an effect because it's the actual room object itself rather than the dictionary containing the room objects. The second change is from ".Double()" to ".AsDouble()" as the Revit Parameter Object requires you to call it's '.AsDouble()' method to return a floating point value. Here are the docs for it: https://www.revitapidocs.com/2018.2/c0343d88-ea6f-f718-2828-7970c15e4a9e.htm
- (lines 20-24) Simply a repeat of the above few lines of code but running over the Areas instead of the rooms and adding each one's total to the running totals in lines 15-16.
- (lines 26-27) Finally find the difference between the total Room area and the total Area area for this specific floor and add the result to a running list of floor area differences at line 11.
4. Interpreting the Results
Now, if you were to run this dynamo, all you would see out of your Python Script node is a list of numbers. I'm guessing you also want to see what levels those numbers correspond to as well, so we can simply add another node after the python script that pairs each item in the list with each LevelKey that we sent into the Python Node like so:
And now we get a list of area differences per floor that we can easily interpret:
The modified dynamo is attached to this reply, and if you have any questions, feel free to ask.
Brilliant! Thank you SO MUCH! It helped a lot and I also learned a lot!!!
I just would like to change the output a little bit, it is not quite exactly what I need yet.
I would like to paste the summ of the room areas by floor in an area Parameter called "Dynamo NRF" on the same Floor.
I changed the python node a Little bit, divided the total room area by the number of Areas in the same Floor and combined the two lists. What I would like to do now, (I imagine Dynamo nodes would be enough?) is paste the value of index 0 in the Elements contained in index 1, 2 in 3, 4 in 5
Thanks again!
Accepted solution
@Anonymous Okay, cool! I think I understand now.
So you're trying to map the calculated values from each level back into the Areas that made up that level. Like This???
So they'll appear in an Area schedule without going blank from conflicts when you deselect "itemize every instance".
If that's what you're trying to accomplish, then yes, that can be done with the dynamo nodes (as well as within the python code)... although it will require some modification to the structure of our data either way. I don't have a ton of time at the moment, so here's the summary.
The main issue is that... to make use of the built-in dynamo node "Element.SetParameterByName" you need to have a perfectly parallel list of area elements along side a list of the values you wish to set for each of those elements. So you'll have to re-map the relationship between your values and elements. I made the following changes to your code:
These code changes will result in two lists (gesamt and ids) with perfectly equal lengths.... and the value from index n of 'gesamt' should correspond directly to the area object at index n in the 'ids' list. The gesamt list will contain a bunch of repeated values, but that's good... as long as both lists have the same length. Then you can simply feed in both lists to the 'SetParameter' dynamo node... and internally it will loop through both of them in parallel. Here I used the "GetItemAtIndex" node to separate out the two lists when they exit the python script node... because putting a comma to separate them like I did causes the two separate lists to be combined into a list of two lists. These nodes then re-separate the lists:
I've also attached your original dynamo that I modified.
By the way, I was not able to verify that this worked perfectly because your model is obviously a bit different than the one I'm using and I didn't go to the lengths of recreating your parameters. If I were you I would double check the area calculations the dynamo is doing by hand... at least once or twice. There may have been arithmetic errors along the way that still need to be ironed out or you may need to convert between units before saving the values into a parameter. Just something I typically do to double check my work.
