1e78e5c2d6
fix vtk-dump: vector fields consider mesh type
...
furthermore:
- new argument: --nativeFieldDumps to dump original FDTD field components for debugging purposes
- show global arguments on startup
2010-09-17 15:34:39 +02:00
c3407c7730
define mesh-type in Processing base class
2010-08-11 18:46:47 +02:00
55ac7137a3
minor documentation updates
2010-07-16 10:41:12 +02:00
f7edb2f1fd
changed openEMS dumps from drawing units to unit of meters
...
the better approach is to create a new class (e.g. Dump)which contains all dump formats (currently vtk and hdf5). This class will then be responsible to choose a dump mode: in drawing units or in meters
2010-07-15 12:58:48 +02:00
e880fa3ee8
Processing: some code cleanups & consistencies
...
Signed-off-by: Thorsten Liebig <Thorsten.Liebig@gmx.de>
2010-06-28 18:27:41 +02:00
610f4e62da
processfields: allow different mesh types for vtk dump, e.g. cylindrical mesh dump
2010-06-02 16:41:26 +02:00
4bda515078
processfields: allow low level access to vtk write methods
2010-05-29 12:17:15 +02:00
10bbb9db79
write interpolation type info to vtk file
2010-05-11 21:03:16 +02:00
5e5a278ac7
new: node interpolated dump in processfields
2010-05-11 20:38:58 +02:00
d16545c776
dump time information to hdf5 file
2010-04-29 19:26:45 +02:00
4fcee4588f
win32 compile fixes
2010-04-28 11:15:59 +02:00
e9cdadb01a
processing functions are now independent of the underlying engine data format
2010-04-25 20:28:00 +02:00
d611e5c8b1
debug: write boxes to vtk-file
2010-04-19 16:09:41 +02:00
b4bc990b0f
define dump precision
2010-04-12 09:38:24 +02:00
52f5764976
Supporting sub-sampled dumps
2010-04-07 12:57:45 +02:00
924f0a6d40
first hdf5-file dump implementation
2010-04-05 20:22:03 +02:00
8dc89ecac2
end Criteria with energy estimate; more engine stats while running
2010-03-15 16:59:37 +01:00
b9a3165aac
Update to vtk-field dumps + material-dump for debugging
2010-03-12 20:39:04 +01:00
73e2b153b6
GPL licensing
2010-03-11 16:47:40 +01:00
f73bf210ed
new ProcessingArray; Processing returns next interval for process()
...
Processing now uses a timestep interval in which Process() will do it's work
and returns the next interval it doesn't need another Process() call
all Processing routines can be put into these array
and it will take care of calling Process() at the right time
2010-03-10 12:15:14 +01:00
d31799e912
default dump not-interpolated
2010-03-09 21:35:57 +01:00
161bdf9c28
Seperate Operator init
2010-03-05 13:53:05 +01:00
ca44334da5
Field dumps (E-field) TD, hard E-source
2010-03-02 14:54:50 +01:00
Thorsten Liebig
Sebastian Held