Peter R.

I can accept it. Its a new file so it cannot break anything. The history is tidy enough for me.

Thank you for making us aware of these recent developments! It indeed seems that it would make sense to replace the code with the improved one. Currently this is not...

Hi Rich, Sorry for taking time. I had a look while doing something else and merged the fix. I had already done the harmonization part so I just picked the...

I was thinking whether it would be more compact to replace: Component: Coil Use W Vector = Logical True Component: W Vector Variable Name = String "CoilCurrent e" with Component:...

Line ~150 in CoilSolver.F90 seems to suggest that if you provide "electrode boundaries" you don't even need Coil End / Coil Start. What if you drop them? "Crappy potentials" seems...

Ok, merged as requested. Great weekend to you too!

Coil Start and Coil End are used by CoilSolver to automatically set the BCs needed to create a coil current. As you can see in CoilSolver_init (line ~137) they are...

So you mean there is a combination of currents such that some are from CoilSolver and some are not? Does the "CoilCurrent e" field look ok in each coil?

This may be a little similar as InterpolateMeshToMesh.F90 -> Ip2DgFieldInElement() The purpose of which is to allow on-the-fly computation of dg fields for postprocessing.

I was going through old issues and looked into this. My recommendation would be to use the Elemental routinies here since the initial field may be more accurate directly on...