I was just about to post this but you beat my to it. Early morning meeting. Let me know if there are any other tests I can run to help with this.

I don't know if this will help, but when trying to use setFields on a pointScalarField, I get that the field is not supported. Exact error message is:

--> FOAM Warning :
From function setCellField::iNew::operator()(Istream& is)
in file setFields.C at line 156
field type pointScalarFieldValue not currently supported
--> FOAM Warning :
From function setCellField::iNew::operator()(Istream& is)
in file setFields.C at line 156
field type pointMotionUy not currently supported

I don't know if this is simply a syntax error in the setFieldsDict, I've uploaded it and the topoSetDict I used to create the cellSet

In polyMeshClear.C can you try moving the pointMesh::Delete(*this) out of clearGeom() and clearAddressing() and into clearOut()? This will keep the pointMesh around during geometry and topology changes. It solves the refineHexMesh test but needs a bit more testing before I commit it.

2) correct, setFields does not support pointFields. Probably not hard to add. Do you see any use for it?

Thanks, moving the call makes the mapping happen and the pointFields are mapped. The solver proceeeds for quite a few timesteps until the refinement engine performs an unrefinement, which leads to an error similar to the first time around:

I think this may have to do with trying to do two consecutive topology change operations, as the refinement mapping alone seems to have no problems; I checked the created meshes and pointFields are created as they should be.

I don't know if this is still a problem with the polyMesh mapping or if it has to do with the way the dynamicRefine portions of the code do unrefinement. I've attached a complete log of the run.

I've pushed 91aaca36bd39bef47bc74803961d07db1160d99c which in addition to that pointMesh deletion moved to clearOut also uses pointMesh::New to construct a pointMesh. Your sprayDyMFoam now runs past unrefinement - it only maps pointMotionUy once (attached log).

Thanks Mattijs. The mapping is working now. Interesting about the temperature dropping; even though I have some custom libraries that handle that, I wonder if this is related to the timestep shrinking issue; I know that with smaller mesh size with refinement and movement I'll get a smaller timestep, but down to 1e-20 or so seems a bit excessive. Some more tests, when I find anything conclusive I'll report back.

This issue can now be closed; it turns out the refinement operation should be carried out before the movement operation to keep the time step from plummetting. Somehow refining after movement causes the velocity field to increase by a ridiculous amount.

I'm now going to learn how to play with my shiny new toy...thanks for the responsiveness!