Corbin, Le mer. 20 avr. 2022 à 19:10, Corbin Foucart <[email protected]> a écrit :
> > I'm hesitant to propose a change, as doing so may break the build process > for other people using different Python binding configurations. I'm also by > no means a CMake expert :-) However, if it's a safe assumption that anyone > using the bindings is using Python3, sure. > Python2 reached end-of-life two years ago, I think it's fair to require Python3. > As for what type of bindings, I was planing on writing some for the > mesh-refinement indicators and executing mesh refinement. Most of the > bindings I'm planning to write would be specific to solvers I've developed > on top of deal ii, but some of the functionality might be useful to the > community. The idea is to drive the adaptive refinement of a solver with a > Python code that has access to machine learning libraries such as PyTorch. > That sounds very interesting. Note that you can already flag a cell for refinement and then execute the refinement (see here <https://github.com/dealii/dealii/blob/master/contrib/python-bindings/notebooks/tutorial-1.ipynb> ) Best, Bruno -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/CAGVt9eN5S-qNrPYSnGxUu55GZ5uEDAa6wtJ%3DJqYaYDfmfPMh9A%40mail.gmail.com.
