Category Archives: Data import

Bugfix for corrupted configuration files

Having investigated a case where CODE stopped working after importing an older method, we found that a data field contained numbers marked as NAN (= not a number). Up to now we don’t know how this situation can arise – probably it was caused by a failing import of measured data.

The following mechanisms have been implemented to make the software survive this situation (active starting with object generation 5.09):

  • Directly after loading numbers marked as NAN are replaced by zeroes. This check is done for configurations stored with generations lower than 5.09.
  • Starting with object generation 5.09, numbers of data fields are checked for NAN status (and replaced by zeroes if necessary) before they are saved in a configuration file.
  • After each import of measured data the relevant data field is checked for NAN status and eventually corrected.

Batch import using Excel files

If you have used the option to export measured spectra in CODE using Excel format you can now import these spectra in batch mode.

There is a restriction, however: The spectra must be stored in the first worksheet of the Excel document, with the first wavelength in cell A1.

The number of the file format to be used in the batch control sheet is 27.

This feature is available starting with object generation 4.48.

 

No import routine

There is no import routine for my spectra. How can I get my data into the software?

If there is not import routine for your type of spectra, you should check first if your spectrometer system can export the spectra in a format which is recognized by our software. Most spectrometer packages can generate tables of the measured data in ASCII format which can be imported using the ‘xy-format’.

In desperate cases you can ask us to write an import routine for your type of spectra. We can do this if we get a description of the data format, and if it can be done with a reasonable amount of effort.