Mailman 3 October 2023 - SfePy

Fwd: Wanted help in defining Gmsh files regions created in Gmsh itself(No defining as x> or x< like this)
by Robert Cimrman 23 Oct '23

23 Oct '23

Forwarding to ML... -------- Forwarded Message -------- Subject: Wanted help in defining Gmsh files regions created in Gmsh itself(No defining as x> or x< like this) Date: Fri, 20 Oct 2023 17:00:59 +0530 From: Himalaya singh <aayusingh05(a)gmail.com> To: sfepy-owner(a)python.org I am new to this tool, and I have been exploring it for some time. I got some issues related to the microstructure Regions defining problem directly from Gmsh(.msh file) using Sfepy. Actually, I am working on lithium ion batteries(Electrode Microstructure) and I am confused how I can make sfepy to read two different regions directly From Gmsh file (where there are grain and grain boundaries having different properties ). I want some help so my microstructure and created regions will be read by sfepy. Also, if i will create a simple square domain in Gmsh having three different regions as i already defined as physical group region_1, region_2,region_3 in Gmsh. How can I implement codes for these domains? I just want it to read directly from: mesh = Mesh.from_file('Region.msh'). Any lead or help will be highly appreciated Thank you for your help! Himalaya Singh Machine Design Department of Mechanical Engineering, IIT Madras

3 3

Re: Problem(bug) with non-linear terms in library
by Robert Cimrman 20 Oct '23

20 Oct '23

Hi Himalaya Singh, The problem is that the initial T is zero, so having the conductivity equal to 2*T leads to a zero (singular) matrix and nothing can be computed. You seem to be setting the initial conditions correctly, but those are not used if pb.set_solver(nls) (nls = Newton solver) is used - you would need a time-stepping solver instead. Maybe you can just use 2*T+ "a small number" to make the problem regular? r. On 10/14/23 08:14, Himalaya singh wrote: > Hello, sfepy community > > I am new to this tool, and I have been exploring it for some time. I got > some issues related to Nonlinear diffusion's equation problem. > > It was working with 1+2*T**4 as in example however changing the non linear > term to 2*T is not working and tried other functions also. > > As I took 100mm*100mm domain and left boundary I fixed it to 25 degree > celsius(gamma1) and Right boundary(gamma2) as 500 degree celcius. > > Initial condition is taken as 25 degree celcius I took a nonlinear function > as 2T, I tried a lot, however the solution was reaching to infinity, I mean > it was showing (sfepy: linesearch: iter 2, (nan < nan) (new ls: > 1.000000e-01)). > > I attached the file below For Your Reference. > > Any lead or help will be highly appreciated Thank you for your help! > > > Himalaya singh > > Machine Design Department > > IIT Madras >

1 0

Fwd: Problem(bug) with non-linear terms in library
by Robert Cimrman 13 Oct '23

13 Oct '23

Forwarding your message to the mailing list... Hello, Can you send us also the mesh, so that the example can be executed? In jupyter, you can (under File/Download as menus) download the notebook as a Python script and send that script - it is easier for me to run and more light-weight. r. -------- Forwarded Message -------- Subject: Problem(bug) with non-linear terms in library Date: Thu, 12 Oct 2023 15:19:14 +0530 From: Himalaya singh <aayusingh05(a)gmail.com> Hello, sfepy community I am new to this tool, and I have been exploring it for some time. I got some issues related to Nonlinear diffusion's equation problem. As I took 100mm*100mm domain and left boundary I fixed it to 25 degree celsius(gamma1) and Right boundary(gamma2) as 500 degree celcius. Initial condition is taken as 25 degree celcius I took a nonlinear function as 2T, I tried a lot, however the solution was reaching to infinity, I mean it was showing (sfepy: linesearch: iter 2, (nan < nan) (new ls: 1.000000e-01)). I attached the file below For Your Reference. Any lead or help will be highly appreciated Thank you for your help! Himalaya Singh Machine Design Department of Mechanical Engineering, IIT Madras

1 0

sfepy new update 2023.3 (Not able to install in windows)
by Himalaya singh 04 Oct '23

04 Oct '23

Good Evening, My name is Himalaya Singh. I tried multiple times to update as well as to install new version of Sfepy, i didnot succeded. All the time it is showing error. I tried a lot, the same command in sfepy manual. I also look to dependencies and installed but still it was failing multiple times. Any help from your side will be helpful and appericiated. Thanks. Error message: error: subprocess-exited-with-error × Building wheel for sfepy (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Building wheel for sfepy (pyproject.toml) ... error ERROR: Failed building wheel for sfepy Failed to build sfepy ERROR: Could not build wheels for sfepy, which is required to install pyproject.toml-based projects

3 4

Re: Terms are yet not working after updation also
by Robert Cimrman 01 Oct '23

01 Oct '23

Hello, On 9/30/23 10:27, Himalaya singh wrote: > Hello, sfepy community > > I am new to this tool, and I have been exploring it for some time. I got > some issues related to Non-linear poisson's equation problem,How to solve > the Non-linear PDEs problem in sfepy. > > In the previous mail I asked about examples of nonlinear PDEs that I got, > however the terms are not showing defined in the library (from sfepy.terms > import Term), I attached the file below. The terms should be there - are you sure you are using the latest release or git version? However, when I run your example, there is another problem. The equations cannot be created because the functions get_conductivity() etc. are only defined declaratively, and are not passed to the terms. I have noticed that the example `sfepy/examples/diffusion/poisson_nonlinear_material.py` is a bit misleading, because the `functions = ...` declaration has no effect there. I am attaching a slightly modified notebook that works for me. r.

1 0