Does BCData for moving mesh surfaces sync with actual mesh motion?

[spdomin]

Make sure that wall_velocity_bc and velocity_bc syncs properly with the actual time value. I think it does, however, someone make sure...

The uqSliding mesh is a good test as it uses wall functions. The following is also an interesting note in the code...

  // copy velocity_bc to velocity np1... (consider not doing this when a wall function is in use)
  CopyFieldAlgorithm *theCopyAlg
    = new CopyFieldAlgorithm(realm_, part,
			     theBcField, &velocityNp1,
			     0, nDim,
			     stk::topology::NODE_RANK);
  bcDataMapAlg_.push_back(theCopyAlg);

[spdomin]

Looks like it may be fine...

Time Step Count: 4 Current Time: 0.008
 dtN: 0.002 dtNm1: 0.002 gammas: 1 -1 0
Realm::process_mesh_motion() the current time is: 0.008    // Look here... same time
 Volume  1.44566e+06 min: 6.9497e-07 max: 568
NonConformal alg will ghost a number of entities: 70
Realm::populate_boundary_data() the current time is: 0.008 // Look here... same time
 Max Courant: 208.041 Max Reynolds: 903728 (realm_1)
   Realm Nonlinear Iteration: 1/1