funkySetFields and the time component

joshmccraney · September 13, 2022, 23:58

Can anyone explain how the "funkySetFields time -XX " component of funkySetFields works? Whenever I execute "funkySetFields time -0.2" it initializes the field at 0. What's happening here?

Evidently the solution *SO FAR* is to run your sim up to the desired time, then you must execute "reconstructPar", then you must execute "funkySetFields time -0.2", and then view the mesh in paraFoam via reconstructed mesh. You should see the simulation has changed the field you've specified. HOWEVER, upon running the simulation again in parallel, it's as if it has no memory that we changed fields, and it continues running as normal.

FINAL EDIT: IT WORKS! You must delete all processor* and THEN decomposePar again. You'll lose all memory of times 0-->0.2, but it'll work from 0.2 on out!

joshmccraney · October 18, 2022, 21:28

To reiterate:

1) run sim to desired time. Then reconstructPar (if in parallel).
2) rm -r processor* to clear all processors
3) run funkSetFields with the desired time (must have folder corresponding to that time)
4) decomposePar and execute running

If done correctly, I can confirm the field will be set to what you specify in the funkySetFields dict.

Make sure controlDict runs from latest time.

September 13, 2022, 23:58	funkySetFields and the time component	#1
joshmccraney Senior Member Josh McCraney Join Date: Jun 2018 Posts: 220 Rep Power: 8	Can anyone explain how the "funkySetFields time -XX " component of funkySetFields works? Whenever I execute "funkySetFields time -0.2" it initializes the field at 0. What's happening here? Evidently the solution SO FAR is to run your sim up to the desired time, then you must execute "reconstructPar", then you must execute "funkySetFields time -0.2", and then view the mesh in paraFoam via reconstructed mesh. You should see the simulation has changed the field you've specified. HOWEVER, upon running the simulation again in parallel, it's as if it has no memory that we changed fields, and it continues running as normal. FINAL EDIT: IT WORKS! You must delete all processor* and THEN decomposePar again. You'll lose all memory of times 0-->0.2, but it'll work from 0.2 on out! Last edited by joshmccraney; October 9, 2022 at 22:25.

October 18, 2022, 21:28		#2
joshmccraney Senior Member Josh McCraney Join Date: Jun 2018 Posts: 220 Rep Power: 8	To reiterate: 1) run sim to desired time. Then reconstructPar (if in parallel). 2) rm -r processor* to clear all processors 3) run funkSetFields with the desired time (must have folder corresponding to that time) 4) decomposePar and execute running If done correctly, I can confirm the field will be set to what you specify in the funkySetFields dict. Make sure controlDict runs from latest time.