Discussion Forum

Hi

I believe so, you need to use the definitions variables and define the entities where it applies then enter your equaition.
BUT call it something else as "nz" as "nz" is already the local COMSOl variable name for the z component of the vector normal to a boundary.

You can give it another combinatin such as "Nz" or "my_nz"
Note that COMSOL does not always flag an error if you redefine an internal variable as COMSOl allows the user to change its formulas, but COMSOl assumes the user know what he/she is doing, sometimes it's by mistake, and the results can become funny, or it might go undetected (worse)

--
Good luck
Ivar

Thanks for the replay. Sorry I didn't get you, what is the 'definitions variables'?
I need to assign a 'z' ranging from 0 to 0.5 in 20 steps and 'Nz' will vary for this 20 values. How to assign the value of 'z'?

Hi

Is it this you want ?, I', using X in 2D X,Y but it could also be in Z in 3D. Note in solid x and X are different, use rather upper-case in Solids as this reefers to the actual geometrical position (material frame)

--
Good luck
Ivar

I tried 'Z' as the geometric frame but it says circular variable dependency detected. What can i do?
In my problem, 'Nz' should vary across the Z axis.

Hi

circular variable references is a know issue in numerical simulations, but often tricky to solve, it happens when variables depends on variables that depends ... and so on, and sudenly you loop around.

The trick is to cut the loop by adding a new dependent variable but it all depends on the model and the loop you have, far from trivial to say anything more

--
Good luck
Ivar

Thanks for your replay. It'd be helpful if an example is given. And I'll upload my file next time.

I've tried like the pics. But it says out of memory. Im really in a great trouble.
what should I do with it now?
Thanks in advance.

Hi

well first I do not see why you define NZ, you can use directly "z" no ?

then if it is for a periodic index variation, probably you should check your offsets and the formula should read something like ...sin(2*pi*(z-Z0)/0.5[um])) with a Z0 defined per domain, as I see that this material property is applied to many elements.
Finally in wave and optics you need a very fine mesh, which means that you need a lot of RAM (mesh density < 1/5 of the wavelength IN THE MATERIAL (do not forget "n" the index effect!)
One way is if your model is symmetric, you might be aple to use a 2D-axi, but sometimes with some types of polarized light the axisymmetry is not respected

Have you tried to see how the index varies, if it is correctly entered ? The easiest is to select the "dependent variables" sub node in the solver sub-tree and do a right click "compute to current/here" This will load in all initial conditions, you can then use the Results section to visualise the initial values, such as index variations, initial fields etc

--
Good luck
Ivar