Mailman 3 January 2022 - SfePy

Material Parameters of Individual Nodes
by derj...＠web.de April 12, 2022

April 12, 2022

Hello! It's a great tool you built there! I'd like to use it for some kind of topology optimisation. Is there an "idiomatic" way to set the material parameters of individual nodes? Thank you very much! JonnyB

3 5

Re: {Disarmed} Re: [sfepy-devel] Recommended solvers for Laplace problem?
by mprof run --python laplace.py Jan. 24, 2022

Jan. 24, 2022

1 0

Re: {Disarmed} Re: [sfepy-devel] Recommended solvers for Laplace problem?
by mprof run --python laplace.py Jan. 24, 2022

Jan. 24, 2022

1 0

State manipulation function moved into Variables (PR #764)
by Robert Cimrman Jan. 18, 2022

Jan. 18, 2022

Hi all, I have just merged PR #764 [1], which has some implications for the interactive problem description files (especially for time-dependent problems), because the imperative API has been revisited. The PR #764 addresses the long standing issue #378 [2] which caused a number of subtle bugs. The main changed are listed below, for more see the PR page. I recommend looking at [3], [4], [5] - do not hesitate to ask in case of problems. [1] https://github.com/sfepy/sfepy/pull/764 [2] https://github.com/sfepy/sfepy/issues/378 [3] https://sfepy.org/doc-devel/examples/diffusion-time_poisson_interactive.html [4] https://sfepy.org/doc-devel/examples/linear_elasticity-its2D_interactive.ht… [5] https://sfepy.org/doc-devel/primer.html#running-sfepy-in-interactive-mode Description of the changes: Old (replaced) API: - State instance holds a global DOF vector that contains as contiguous sub-vectors (slices) the data of the unknown (state) variables from the Variables container. - Possible to set DOF vector to a variable without changing the DOF vector in the State instance that contains the variable. -> Prone to hard-to-debug bugs (#378) - Inconsistent naming of functions (historical code evolution). New API: - No State, only Variables. - Once Variables.init_state() is called, the state variables are locked - cannot use variable.set_data() directly. - Problem.solve() and other functions that worked/returned State instance return now the Variables instance instead. - Declarative problem description API not affected. - Imperative problem description API changed in a not backward-compatible way due to: - Renamed or removed functions (mostly Variables and related Equations methods and former State methods). - Locking of the state variables. - No need to create State instances (no State class). - Problem.create_state() is now an alias to Problem.get_initial_state(), which sets up initial conditions - those have to be set using Problem.set_ics() before Problem.create_state()/.get_initial_state() are called. - Stationary examples likely affected only in post-processing of results, after calling Problem.solve(). - Time dependent examples need to be adjusted already when dealing with the initial state: calling Problem.get_initial_state() should do the job (provided the conditions are set, see above). Best regards, r.

1 0