Quantcast
Channel: COMSOL Forums: Auxiliary problem on different domain
Viewing all articles
Browse latest Browse all 4

Re: Auxiliary problem on different domain

$
0
0
Dear Anastasia,

I found some issues in your model that need to be revised. The issues emerge partly from handling problems; therefor I suggest that you take a look at the model library with many different examples and step-by-step instructions.

Let's start with your first component:

I am unsure if u and u2 is the same magnitude. If that is the case I would rather delete the second application mode in comp1 and in case of convergence problems use the predefined smoothed step function for the initial value. It seems that you tried to re-implement this function under Global Definitions>Analytic. If you right-click Global Definitions you will see Functions>Step which would be the recommended way to model this.

The functional "integrate" is not defined. You can find the integration operators by right-clicking the Definitions-node in Component 1 and adding Component Couplings>Integration.

When coupling between different dimensions and components you have to make the variable globally known to all components and make sure that the values are mapped in the right way (which 2D-domain is mapped where as a surface in 3D) - the program cannot decide this for you ;-)
Coupling entities with the same dimension between model components of different dimension (here: from 3D-edge to 2D boundary, from 2D-domain to 3D-surface) can be defined via Component Couplings>Linear Extrusion. Instead of using u2, you will then use e.g. comp1.linext2(u2) in your dialog.

Please use also the context-sensitive Dynamic Help (the question mark at the upper right corner). It will describe in detail the functionality of each dialog window and its options.

In general it is a good idea to simplify the whole task by breaking up the different components and checking them separately. I suggest that you first fix the 2D-part. Just disable the 3D-part in the solver-node and check the corresponding error messages for component 1.

Hope that helps - good luck!

Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles



Latest Images