When loading an animated SOP Scalar Field in the dynamics, you need to switch Set Always for:

1. Use SOP Dimensions
2. SOP Path
3. Time

Attributes must be of the same bit depth. If 16-bit float is used to save disk space, then you need to cast them back to 32-bit float after loading the caches. Otherwise, problems may arise. For example, object merge branches with 16- and 32-bit attributes in some cases can break all attributes on the geometry.

The pcfilter function sometimes may not understand the point.distance argument. Perhaps this is due to cases where there are no primitives.
Use the filter by the position of the point cloud.

The name and path attributes are not used by packeds. All necessary information is stored in intrinsic attributes.

Channel ranges are specified in seconds by default in CHOP nodes. If we are used to working with frames, then we must not forget to change Units from Seconds to Frames in the Common tab.

When using VEX Volume Procedural, you need to export all the necessary data for the render, including the velocity field.

When writing a condition for disabling a parameter using the Ordered menu, only tokens work in comparison:

{ absorbType == gather }

If the renderable parameter is disabled, then the node is still cooked. And object properties can be read from the VEX shader.

Getting coordinates under the cursor in the network view:

pos = hou.ui.paneUnderCursor().currentTab().cursorPosition()

The pintoanimation attribute only turns on the effect of target geometry on the object. The object must have the targetP attribute, otherwise it just takes P:

When 1, the point is hard constrained to the target animation (e.g., targetP). When zero, the point is unconstrained.
http://www.sidefx.com/docs/houdini/nodes/dop/finiteelementsolver.html#target-attributes