v1.0.1

• Minor (but very important) fix to the example script so that it now runs by @willGraham01 as in #320.
• Other minor fixes and doc improvements pulled from main.

Full Changelog: v1.0.0...v1.0.1

v1.0.0

A stable, trusted version. Following a few bugfixes and some nice structural refactoring and additions to the documentation.

What's Changed

Noteworthy fixes

• Command line options moved to input file by @willGraham01 in #262
• Update iteratefdtd_matrix: dz/2 offset and system test input/output update by @willGraham01 in #253
• Documentation improvements #230 and #252
• Tracking the MATLAB scripts for test file generation #236
• clang-format by @willGraham01 and @samcunliffe in #222 and #235
• Add citation file. by @samcunliffe in #84
• Adding codecov to the CI by @samcunliffe in #268 and #284

Other minor fixes and refactoring

• Iterator refactor [3/N] by @willGraham01 in #204
• SurfacePhasors class by @willGraham01 in #205
• PRHS into a readable class by @willGraham01 in #206
• Vertex Phasors Class by @willGraham01 in #209
• Output_Matrices class by @willGraham01 in #213
• Iterator class breakdown 2: Now with composition by @willGraham01 in #215
• Update spdlog version to v1.11.0. by @samcunliffe in #228
• Documentation follow-up for #215 plus minor doxygen fixes. by @willGraham01 in #221
• Add to Doxygen pages, and use doxygen as a CI check. by @samcunliffe in #231
• #216 iteratefdtd_matrix: Updates for the main loop by @willGraham01 in #224
• DRY our .github/workflow by @samcunliffe in #234
• Refactor the Main Loop by @willGraham01 in #218
• Add compile_commands.json to .gitignore by @samcunliffe in #251
• Final part of #230: clarity + the flow of information by @samcunliffe in #265
• Track input data generation process in the repo by @willGraham01 in #236
• Link to the template chooser page. by @samcunliffe in #267
• Add coverage build and upload unit-test coverage to codecov.io by @samcunliffe in #268
• Fix badge. by @samcunliffe in #269
• Fix typo in issue template by @willGraham01 in #274
• Fix example script path by @willGraham01 in #273
• Add more tests for the argument parsing. by @samcunliffe in #270
• Track generation for arc_02 and arc_03 by @willGraham01 in #241
• Update catch2 by @samcunliffe in #275
• Typo in README by @samcunliffe in #276
• Add arc_{08,12,13,example_fdtd} to test_regen.py by @willGraham01 in #242
• Add arc_09 and arc_10 to the scope of test_regen.py by @willGraham01 in #243
• Add docstrings to variables by @willGraham01 in #277
• Update run_bscan.m in anticipation of arc_{17,18,19} by @willGraham01 in #245
• A kindof trivial test addition to help debug #279. by @samcunliffe in #283
• Add some configuration to codecov. by @samcunliffe in #284
• Add CI, MATLAB tests, and doxygen build to the merge_group. by @samcunliffe in #288
• Remove (unused) using directive from header. by @samcunliffe in #297
• Introduce a versioning system. by @samcunliffe in #203
• Fallback to v1 if no tag provided (or no git repo) by @samcunliffe in #300

Full Changelog: v0.1.0...v1.0.0

v0.1.0

The addition of the option to toggle bandlimited interpolation, rather than rely on cubic interpolation, to extract field values away from the vertices/spatial grid.

What's Changed

• Introduction of band-limited interpolation schemes by @willGraham01, @samcunliffe, @prmunro.
• Refactoring of the testing framework by @dstansby, @willGraham01.

Users can how specify on the command-line whether tdms should use the cubic interpolation methods (which were the only interpolation methods available in v0.0.1), or the band-limited interpolation methods (detailed below).

Band-limited interpolation has replaced cubic interpolation as the default interpolation method. The -c or --cubic-interpolation flags can be passed to the tdms executable to override this behaviour and force the use of cubic interpolation again.

Band-limited interpolation (BLi)

When a Yee cell has a spatial dimensions of the order of $\lambda/6$, where $\lambda$ is the shortest wavelength of interest, interpolation schemes such as cubic interpolation that only use 4 sample points are suitable. It is often the case however that larger Yee cell dimensions are being used, in which case a BLi scheme (which uses 8 sample points) is required. Much like cubic interpolation, the formula for the interpolated field value when using BLi is a weighted sum of the sample points, although derived from ideas in Fourier analysis as opposed to fitting a polynomial through the provided sample points.

Since BLi requires 8 samples to produce an interpolated value, there are some situations where the executable will be forced to fall back on cubic interpolation if running particularly "thin" simulations (with $<8$ Yee cells in a particular dimension). Interpolation is done on a directional basis, so tdms will always attempt to use BLi if there are $>8$ Yee cells available in a particular dimension even if there are less than this in other dimensions.

Full changelog: https://github.com/UCL/TDMS/commits/v0.1.0

v0.0.1

A verified and well-tested stable version with cubic interpolation.

What's Changed

• Refactoring by @t-young31 in #36 #64 #88
• Adding many tests. by @t-young31, @giordano, @willGraham01, and @samcunliffe
• Bugfix to steady state mode by @prmunro in #94
• [Time-Domain] Interpolation functions for the H-field by @willGraham01 in #74

Full Changelog: https://github.com/UCL/TDMS/commits/v0.0.1