Create a rounded tip cone using planar solid for DEVICE

[aalam]

The elements library in FDTD Solutions and MODE solutions allows the users to create a rounded tip cone using the “custom” object. However, if someone is trying to import this structure into DEVICE (CHARGE or HEAT), they can not do it since DEVICE do not support the custom object.

One easy solution to this problem is to use the planar solid object which is available in DEVICE (and also in the optical solvers). The planar solid object can be used to create any arbitrary geometry. In this file (rounded_tip_cone.ldev (5.0 MB)) a structure group has been created that generates a planar solid to create a rounded tip cone. The input parameters to the structure group have been kept almost identical to the FDTD (custom) counterpart.

Here is one more post that shows how a truncated cone can be created using planar solid,

How to draw a (truncated) cone in DEVICE using the 'planar solid' object

The DEVICE solver currently do not have an object library like the optical solvers which can be a limitation if you are trying to add a complex structure in your design, for example a truncated cone. Good news is that by using the planar solid structure, it is very easy to create complex geometries like a truncated cone using the script environment. The planar solid object is a very powerful tool to create arbitrary geometries. Lumerical’s knowledge base has documented the properties of this …

[sara.magdi]

I tried to use the structure in my design. But when I add it I always get the following error while building the geometry:
Mismatch between number of faces when searching for duplicates

Is there a specific reason for getting this error?

[aalam]

Hi. This particular error happens when the solver has trouble connecting one geometry to another (while generating the whole structure before meshing). Often when you have a curved surface touching another curved surface or a planar surface, the solver has this problem. If this is the case in your design then try using some small overlap between geometries that are touching each other.

If you are running a 3D simulation then try switching to “algorithm 2” in the solver properties as shown below:

If none of these work then if you share the file with me, I can take a look at it.

[sara.magdi]

Using Algorithm 2 solved the problem in building the geometry. Thank you.

I have another problem though. At the end of the simulation, the results do not converge. drift/diffusion poisson solver fails to converge according to the log file.

[aalam]

If the solver fails to converge then the first thing to check would be the mesh and the doping profile. Calculate the mesh only and inspect the “grid” dataset. Make sure that the doping in getting applied properly, specially at the surfaces. Next run the simulation for zero bias only. If the simulation runs then start to apply a voltage sweep. If the sweep fails then try again using smaller steps.

For some more suggestions on how to resolve convergence problems, check out this other KX post: overflow-error.

[sara.magdi]

I used the radial constant doping code for the lower part of the nanowire:

How to add a constant radial doping profile in DEVICE

The constant doping object in DEVICE allows users to apply a constant doping to a semiconductor region. This works fine with most structures. However, in some cases the doping profile needs to be radial (e.g. devices with nanotubes or nanopillars). The import doping object in DEVICE can be used in such cases. The users can use the script environment to create a rectangular grid (x, y, z) and then use the script to generate a matrix (N) that keeps an undoped circular core (value = 0) and appli…

when I taper the top of the nanowire as in this file:
https://drive.google.com/a/aucegypt.edu/file/d/0B_ijuqxdABI0VHZUWWxTU2tvOVU/view?usp=sharing

The results start to converge. I tried to make the mesh finer but it still did not work.

[aalam]

The results start to converge

Did you mean to say the results are still not converging? I could not see the file from your google drive as it requires signing in with a google account. Can you upload the file here or is it too big? You can consider uploading the project file and the doping (.mat) file separately if that helps with the size.

[sara.magdi]

Yes Sorry. I meant the results started to "diverge"
The file is still big to upload here even after I remove the doping and the generation.
I uploaded it on dropbox (I think it could be downloaded without signing in)

Sara_Magdi_NW.ldev

[aalam]

Hi Sara. I am sorry but I could not open the file in DEVICE (I was able to download the file without any issues). It looks like that the file might be corrupted. Do you think it got corrupted after the simulation failed? If you have a fresh copy of the file then please share it with me.

Since you were talking about tapering the top of the doping, you might find this post useful:

Creating radial doping profile for a truncated cone

Continuing the discussion from How to add a constant radial doping profile in DEVICE: If the structure has variation along z-axis, i.e. if it is like a truncated cone rather than a cylinder then the doping is no longer uniform along z direction and so to create a radial doping profile for such a structure, we need to define the doping at different cross sections along z. We can divide the 3D profile in N number of slices and calculate the doping profile at each slice in a manner similar to wha…

[sara.magdi]

It actually worked when I adjusted the doping using the script in your last post.
Thanks a lot for your help.

[ahisham]

Hi i have a problem with tunc cone in device when i simulate my design it always gives me that massege error "No area for degenerate"
can any one help