I have no idea why, but naming the function instance when I create it in FEniCSx solves this problem for me. Perhaps a bug in the FEniCSx software.
Thank you
I have no idea why, but naming the function instance when I create it in FEniCSx solves this problem for me. Perhaps a bug in the FEniCSx software.
Thank you