Philip Cardiff

> @solids4foam @philipcardiff Do you have any further ideas? It is strange that there are issues when solids4foam is compiled without Eigen; @raynoldtan was the solids4foam installation cleaned (i.e. Allwclean)...

> * [ ] Rename `forceFieldName` to `nameForce`. In the code, this is actually called `nameSolidForce`. Is this really specific to solids? @solids4foam I guess this should not be specific...

FYI, I also have this issue on my M3 Mac. I am not sure of the cause of the problem, but I suspect it is related to linking to libPstream...

The `_ompi_mpi_byte` should be given in `libmpi.dylib`, e.g. we can see this with `nm`: ``` >> nm -g $(mpicc --showme:link | sed -e 's/.*-L\([^ ]*\).*/\1/')/libmpi.dylib | c++filt | grep "_ompi_mpi_byte"...

Problem solved: your solution [here](https://github.com/mrklein/openfoam-os-x/issues/76#issuecomment-1653457396) works. That is, in `$WM_DIR/rules/darwin64Clang/c++ ` and `$WM_DIR/rules/darwin64Clang/c`, replace `x86_64` with `arm64`. Then, clean (`wcleanPlatform`) and re-build OpenFOAM. However, this leads to an error when...

I suspect another reason for the difference with `openfoam-openfoam` is that the 1st-order `Euler` ddt and d2dt schemes are used (solids4foam uses the 2nd-order `backward` scheme). You could try switching...

Ah, OK, yes, we added a d2dt2 `backward` option in solids4foam. In that case, using a smaller deltaT would improve the OpenFOAM predictions, if that is an option (probably also...

Thanks @mrklein for this excellent resource. As a by the way (broadly related to this issue), OpenFOAM.com versions (e.g. v2312) no longer need patches for macOS; however, your guide is...

> @philipcardiff Thank you for the comment. So, the solution would be to remove mention of custom tap and to change formula name to simple `scotch` (guess, we can remove...

> Updated wiki. Do you think it OK now? This looks good to me.