You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As pointed out by @jan-janssen , we have to make a decision how to handle this here. I'd vote as well for the 2-container solution, one still called "continuum", containing damask and another one containing fenics, which we could simply call "fenics".
I opened this issue to keep track of this. I can take care of it after my easter-vacation.
The text was updated successfully, but these errors were encountered:
After discussion in our last infrastructure meeting, we agreed that we only support fenics marginally from now on (this means: there may be conflicts if a user trys to install both fenics and damask side-by-side). For this repository this means
we will dropfenics support, because fenics is not actually maintained anymore
in pyiron_continuum we first focus on improving the damask integration
then we will integrate another FEM package based on this issue
Directly resulting task from this:
Remove any fenics-related notebooks, tests, a.s.o. from the continuum image.
The issue is also discussed here. pyiron/pyiron_continuum#262 (review) .
As pointed out by @jan-janssen , we have to make a decision how to handle this here. I'd vote as well for the 2-container solution, one still called "continuum", containing
damask
and another one containingfenics
, which we could simply call "fenics".I opened this issue to keep track of this. I can take care of it after my easter-vacation.
The text was updated successfully, but these errors were encountered: