Skip to content
Snippets Groups Projects
Commit ed2d11b9 authored by Matteo Cicuttin's avatar Matteo Cicuttin
Browse files

Updated changelog & api doc.

parent 2ed2e9e7
No related branches found
No related tags found
No related merge requests found
...@@ -21,3 +21,7 @@ Unavailable features: ...@@ -21,3 +21,7 @@ Unavailable features:
- Improved export to SILO. E, H, and J fields are now exportable as nodal or zonal variables. It is also possible to disable the export of a specific field, see `lua_api.md` (8a831181). - Improved export to SILO. E, H, and J fields are now exportable as nodal or zonal variables. It is also possible to disable the export of a specific field, see `lua_api.md` (8a831181).
- Leapfrog integration on CPU & GPU (e3d95022). - Leapfrog integration on CPU & GPU (e3d95022).
## Version v0.3 (NOT RELEASED YET)
- Volumetric sources on CPU & GPU (2ed2e9e7).
...@@ -68,6 +68,19 @@ The solver expects that the callbacks for materials have 4 parameters: ...@@ -68,6 +68,19 @@ The solver expects that the callbacks for materials have 4 parameters:
- `tag`: the current subdomain tag - `tag`: the current subdomain tag
- `x`, `y` and `z`: the current coordinates at which the material needs to be evaluated. Note that currently the materials are assumed to be piecewise constant and that the material is evaluated in the barycenter of the element. - `x`, `y` and `z`: the current coordinates at which the material needs to be evaluated. Note that currently the materials are assumed to be piecewise constant and that the material is evaluated in the barycenter of the element.
### Volumetric sources
Current sources in volumes can be specified by providing a function that evaluates the current density field in a given subdomain. For example the following code defines a volumetric source in the subdomain with tag `4`:
```
function J_source(tag, x, y, z, t)
local Ex = 0
local Ey = 0
local Ez = math.sin(2*math.pi*freq*t)
return Ex, Ey, Ez
end
sources[4] = J_source
```
### Boundary conditions ### Boundary conditions
Boundary conditions are specified for each surface with tag `tag` via the table `bndconds`. If a surface does not have an entry in `bndconds` it is assumed to be PEC. Boundary conditions are specified for each surface with tag `tag` via the table `bndconds`. If a surface does not have an entry in `bndconds` it is assumed to be PEC.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment