You can set velocity attribute to the surface and convert it to a vector field with fluid source.

I haven't test it but you can animate one or more pieces on both side pulling apart and import it into dop as an rbd packed animated static object. Then you keep the rest of the pieces as active objects and glued to the animated pieces.

Not sure if I understand it right but you can drive the particles by creating a vector field with the surface, then drive the particles with sopvectorfield and fieldforce in dop.

I am working on a personal project for my demo reel which involves fracturing a house. To get the wood fracture I have to scale it down in one axis, fracture it and scale it back. In my model, the wood frame consist of a large number of pieces orienting at different directions. In order to have the right fracture I have to scale them all in different direction. This procedural automatically orient, scale and fractures wood pieces in the right direction.

The concept:

1. for each pieces in the model, find out the face with the largest area.
   
2. store the normal of the face and store the longest edge as the up vector
   
3. move the piece to origin
   
4. rotate the pieces so that normal points towards +y axis and up towards +x axis
   
5. scale down in x axis and fracture
   
6. restore the rotation and transformation
   

I think the procedure is working in most cases if the pieces are not fuse together. I am looking for critiques, improvement and new feature ideas!

My display toggle worked again for some reason, it completely disable the calculation inside the node. Great answer though

I am working on a character rig with some heavy procedural geometry constrained to the control. I am looking for a way to stop the calculation of geometry node like “vdb from polygon” from running when I am animating the controls. I tried turning off the display attribute in the Render tab but it's still running even though it's not shown in the viewport.

It was working when I use blast @uv==0.7382 to isolate the points but not "if(@uv==0.7382)" in attribute wrangle. Anyone know the reason behind this?

Great Answers! Thanks everyone

Sometimes when I type a value into a field, like 2, it turns into 2.000000000001. I understand there is a limit to the number of digits in floating point number but I am just typing an number without any calculations. I am curious about reason behind this.

The only time I found this a problem was when I was trying to find out points with certain u value “0.7382”, which was shown on the geometry spreadsheet. I was just using an “if” statement to check if the value was exactly equals to “0.7382” but it returns nothing. I later suspected that there were some digits hidden behind it so I multiplied it by 10000 then converted it to integer for comparison and it worked. Does anyone got a better way to compare values?