VelocityInputBCs

Velocity Input Boundary Conditions

We already have infrastructure for BCs which work closely with their Iolets (NonZeroEquilibriumVelcocityFixedDensity) Assuming that we can get the physics right, then we need to make a velocity available to the BC. This should be a velocity average, defined in the Iolet, and a weighting factor for velocity profiles, defined in the BC instance. The weighting factor needs to be a function of an effective radius, defined in the site data. The hard part of this problem, therefore, is adding a new quantity to the data for edge sites, similar to cut distances. This should go through by a straight analogy to cut distances, but will necessitate a non-backward-compatible change to the geometry files.

I accept the majority of this. However as we discussed, this does not require an update to the geometry format. We can include another file (referenced from the config.xml) that gives the extra data needed by the new boundary conditions.

Further, does anything else need to be done about broadcasting the inlet (pressure, flow) data to all concerned tasks?