You're reading an old version of this documentation. For up-to-date information, please have a look at v0.5.


A few ideas how to develop the project further, currently a list as a reminder for the main developers themselves, in no particular order, though with a tendency to list more important aspects first:

For version 0.5

  • Implement derived importers for Magnettech files

    • Magnettech stores datasets in individual files, be it individual scans for accumulations or different steps in a series of measurements.

    • At least for goniometer, power, and modulation amplitude sweeps, these should be transformed into single datasets.

    • Requires interpolation of data, as each individual dataset has its own x axis (usually field).

  • Import infofiles in all magnettech importers.

  • Put infofile importer in utils module or elsewhere, to not copy code in every single importer

  • Implement handling of “RT” as temperature value in the infofile.

  • Import and store filter mode from Magnettech data

    • change metadata (done)

    • adapt infofile-importer (in every importer)

  • Magnettech: Choose between raw data and data filtered during measurement.

  • Logging

    • Frequency correction should issue a warning (rather than throwing an exception) if no MW frequency value is contained in dataset (yes, such datasets do exist unfortunately)

  • Reorganise templates for reports, according to the directory layout proposed by aspecd (see for details).

  • Bugfixes

    • Keep step parameter of magnetic field or not?

For later versions

  • Start to (re)implement functionality test-driven.

  • Handling of Magnettech files

    • Renaming to sensible conventions (recursively through directories)

  • Batch processing (via recipes?)

    • Basic preprocessing, plot, export as PNG/PDF, figure caption for dokuwiki


A list of todos, extracted from the code and documentation itself, and only meant as convenience for the main developers. Ideally, this list will be empty at some point.


Assign further metadata. Note that some metadata are entered manually, and therefore, parsing values with units with or without space between value and unit can be quite tricky.

original entry


Does not work properly. Already gives wrong values with simulated data without a hyperfine-coupling. Reimplement with other method…

original entry


Do not rely on dataset from recipe properties but use the dataset from apply_to that is imported into the context. Further deal with (meta)data in the context thus that those are easily usable in a template.

original entry