Activity for Giorgio Palma
-
Giorgio Palma posted a comment on discussion Help
Hi Nazalli, the easiest way I can imagine at the moment is to analyse the mesh you are going to use for your calculation and identify the elements for which you want to define a custom impedance. Then, using custombc=1, you can define a set of files for lambda, gamma, f and g in which the desired values are given to each mesh element. In this way each element can have a different value for all the coefficient satisfying your impedance law Z(x,y). This last task could be done manually, or also writing...
-
Hello Max, I made a couple of tests and dug into our commits. The bad news is that you found a bug of acousto2.0. The good news is that it had been already discovered some time ago while we were developing acousto, and it is fixed in the v2.5, which is going to be released very soon. At the moment, a way I can imagine to overcome the issue is to let custombc=2 to write a the bc files with nome=1, and then use custombc=1 with wathever nome. All the best, Giorgio
-
Hello Max, I made a couple of tests and dug into our commits. The bad news is that you found a bug of acousto2.0. The good news is that it had been already discovered some time ago while we were developing acousto, and it is fixed in the v2.5, which is going to be released very soon. At the moment, a way I can imagine to overcome the issue is to let custombc=2 to write a the bc files with nome=1, and then use custombc=1. All the best, Giorgio
-
Hello Max, I made a couple of tests and dug into our commits. The bad news is that you found a bug of acousto2.0. The good news is that it had been already discovered some time ago while we were developing acousto, and it is fixed in the v2.5, which is going to be released very soon. At the moment, you are right, the only way I can imagine to overcome the issue is to write a huge number of bc files and use custombc=1, which is what custombc=2 does automatically. All the best, Giorgio
-
thank you Max for your precious work. I'll investigate this and come back with something as soon as possible!
-
no, at the moment the user is responsible to provide a number of boundary conditions equal to the number of frequencies to evaluate for each bc group (floor0, floor1, ... walls0, walls1, etc. in your case), or to provide a non frequency dependent bc for each group (floor, walls, etc.)
-
Dear Max, I found two problems in the acousto input file: the structures defining the custom bc must be outside of the modsol structure: modsol={ # solver module active=1; [...] } ceil0={ tag = 15; re_lambda = 1.0; im_lambda = 0.0; re_gamma = 0.0; im_gamma = -23.813; # alpha=0.25, f=325Hz }; all the physical tags present in the msh file must be defined in the cfg file: modsol={ # solver module [...] gmshbc=["ceil%d", "floor", "wall"]; (OR gmshbc=["ceil%d", "floor%d", "wall%d"]; depending if you want...
-
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">Dear Max, if you would provide me the input files set you are trying I'll be glad to help you!All the bestGiorgioIl 29 apr 2021 16:08, Max Funk <mf3@users.sourceforge.net> ha scritto:Hello Umberto Iemma, many thanks for your program... I tried to convert the tutorial: Room_Acoustics to the new boundary conditions custombc=2 with the physical tags of the gmsh file. But now I get an error message: 2021-04-29 15:33:56 DEBUG [1/1] modsolinfo->custombc=2...
-
Dear Max, if you would provide me the input files set I'll be glad to help you and solve the problem!
-
Dear Max, if you would provide me the input files set I'll be glad to help you and solve the problem!
1
