OK! Good luck with this... see output for a few modes. Thanks for all the help!

Now.. I have Yet Another Problem... gah. Back to the electrostatic problem with Dirichlet BCs. 

This is what I'd love:

Build a .geo file with various points, lines and surfaces. 

In the geo file specify that certain lines are tagged with a specific ID.

In the problem description set up boundary conditions by specifying the value of the potential on all the nodes that are located on those lines.

Is there any way to do that? Everything I've tried so far as failed. I'm trying something like:

...
// many lines skipped...

Line(17) = {9, 8};
Line(18) = {10, 11};
Line(19) = {11, 12};
Line(20) = {12, 9};
Line(21) = {12, 8};
Line(22) = {12, 13};

Line Loop(1) = {1, 2, 3, 4};
Line Loop(2) = {5,6,7,-3};
Line Loop(3) = {14,-6,-9};
Line Loop(5) = {11,12,13,-8};
Line Loop(6) = {-13, -21, 22, -14};
Line Loop(8) = {-17, -20, 21};
Line Loop(9) = {18, 19, 20, -16};

Plane Surface(1) = {1};
Plane Surface(2) = {2};
Plane Surface(3) = {3};
Plane Surface(5) = {5};
Plane Surface(6) = {6};
Plane Surface(8) = {8};
Plane Surface(9) = {9};

Physical Surface(7) = {1,2,3,5,6,8,9};

Physical Line(1) = {7,4};
Physical Line(2) = {5,9,8};
Physical Line(3) = {12,17,16};
Physical Line(4) = {19};
Physical Line(5) = {1};

I'm thinking that by making "Physical Lines" I can refer to them in the problem description by id. Is that right?

Anyway.. when I include these in the .geo file I get:

dfr-slusher:sfepy steve$ python simple.py es-test.py
sfepy: left over: ['verbose', '__builtins__', 'get_r_dependence', '__doc__', '__name__', 'Newregions', 'data_dir', 'nm', '__package__', '_filename', '__file__']
sfepy: reading mesh (/Users/steve/Development/sfepy/tmp/es-lens.vtk)...
sfepy: ...done in 0.04 s
Traceback (most recent call last):
  File "simple.py", line 129, in <module>
    main()
  File "simple.py", line 122, in main
    app = PDESolverApp(conf, options, output_prefix)
  File "/Users/steve/Development/sfepy/sfepy/applications/pde_solver_app.py", line 304, in __init__
    **kwargs)
  File "/Users/steve/Development/sfepy/sfepy/fem/problemDef.py", line 82, in from_conf
    domain = Domain(mesh.name, mesh)
  File "/Users/steve/Development/sfepy/sfepy/fem/domain.py", line 194, in __init__
    gel = GeometryElement(desc)
  File "/Users/steve/Development/sfepy/sfepy/fem/geometry_element.py", line 132, in __init__
    gd = geometry_data[name]
KeyError: '2_2'

I tried a post-mortem debug.. and indeed 'desc' is '2_2', but there is no matching key in geometry_data. ;-(

If this is documented, I missed it somehow. Any hints?

thanks!
-steve


On Thursday, June 7, 2012 8:01:52 AM UTC-6, steve wrote:
Hi Robert,


On Thursday, June 7, 2012 4:39:02 AM UTC-6, Robert Cimrman wrote:
On 06/07/2012 07:09 AM, steve wrote:

> The trick was:
>
>      ebc_1 = {'name':'dummy', 'region':'Surface', 'dofs':{}}

or, literally, just:

ebcs = {}

Dang.. you're right. I thought *sure* I tried that and failed. 

- the short syntax form... :)


There might be some spurios effects due to mesh. What happens if you refine? 

Demonstrates my ignorance... not sure what that means.... I'll look it up.

-steve