(Late) Spring Cleaning

[snowyweston]

I've been stealing time away from the insanity of two jobs going full guns to do a bit of housekeeping (in anticipation of the next wave once these are drop-kicked out the door) and aside from consolidating all of our system family and component family content files into one, (itself child-linked in under our template proper)

I've been having a bit of a pan-content go at making sure that said content is ready to receive a beasting by Dynamo (come the time).

In particular, I'm talking shared parameters.

But I've a Klingon on my otherwise pristine file - with one SP listing on the LHS 'pick fields' of the schedule builder, but no placed instances have it (at least if I filter said multi-category* schedule by Parameter Exists) - how is that even possible?
*no this particular SP was never applied to system families - and I've checked them just in case


So then my suspicion lay with sub-nested families in the placed instances in project. Shared (children) would show in schedule (no other filters in place) - so it can't be them. So then the culprit MUST be an unshared .rfa that some how got the SP....

How the hell does one even start going about digging for that in a file of over 4000 families? :crazy:




BTW:
I've dipped a toe into Dynamo hoping it would have a means to dig into unplaced content - but a quick go using the "Parameter Exists" node from Clockwork points out that Dynamo, like Revit's schedules, appears 'only' interested in what's in the model space, not model. :banghead:

[Twiceroadsfool]

You do a save as and start deleting the parent families in groups.

Before doing that you REMOVE the parameter from the schedule fields. Then after deleting 30 families via the PB, you go see if it's still an AVAILABLE field in the schedule.

When it isn't, you know it's a nested in one of those thirty.

I have to do this all the time, believe it or not. It goes pretty quickly.

Sent from my Phablet. Please excuse typos... and bad ideas.

Aaron Maller
Director
Parallax Team, Inc.

[jmk]

I recently came across a shared parameter that appeared in the create schedule dialog, but not in the project parameter list. I couldn't add it into the project parameters (already in the project) but also didn't appear in the family. The family components weren't shared.

I ended up writing a quick dynamo script to purge that parameter (requires clockwork & steam nodes)

[snowyweston]

I have to do this all the time, believe it or not. It goes pretty quickly.

Groups and schedules had all been expunged anyway, (I'm moving it all around as a stripped link that'll bind once all is squeaky clean) - so yeah, that's how Friday is looking...

[snowyweston]

I ended up writing a quick dynamo script to purge that parameter (requires clockwork & steam nodes)

Got Clockwork but will have to fetch Steam* tomorrow to see if this might assist, cheers!


*been trying to avoid layering too many packages into my learning.

[Twiceroadsfool]

Making a single multi cat schedule to use the method above doesn't do any damage, lol.

But Dynamo is definitely a better way to track it down.

Clockwork, steam, rhythm, and bumblebee are my "can't live withouts" in Dynamo.

Sent from my Phablet. Please excuse typos... and bad ideas.

Aaron Maller
Director
Parallax Team, Inc.

[cellophane]

But Dynamo is definitely a better way to track it down.

Clockwork, steam, rhythm, and bumblebee are my "can't live withouts" in Dynamo.

The only issue with using any of the packages is that updates can break graphs without leaving a clear fix in-place, especially if you are only a part-time Dynamo newbie like me

[Dave Jones]

Clockwork, steam, rhythm, and bumblebee are my "can't live with outs"

you are one ***** dude

wait, what? you can't say k_i_n_k_y here? WTF

[Twiceroadsfool]

The only issue with using any of the packages is that updates can break graphs without leaving a clear fix in-place, especially if you are only a part-time Dynamo newbie like me

Dude I'm more of a newbie at it than you are. But the packaged do so much, it's hard to function with them. If you aren't using packages then you're basically writing custom python, and at that point you might as well write in the API.

Sent from my Phablet. Please excuse typos... and bad ideas.

Aaron Maller
Director
Parallax Team, Inc.