EPR Converter (e2a)

The Bruker spectrometers output data by default in the Bruker BES3T format, which whilst being perfectly usable is not recognisable by most operating as standard.

This script was originally written for the benefit of the project students in the lab who wanted to plot their cw EPR data in Excel without going to the trouble of learning how to use MATLAB. Or for going back to the spectrometer and trying to export their data in ASCII format.

Instead, they can call e2a (EPR spectrum “2” ASCII), they are presented with a standard “Open file” window to select the file.  A message box then asks whether they want the converted file put into the same folder or somewhere else, which if selected presents a standard “Save as” window to save elsewhere.

By default files are saved as standard comma seperated value files (*.csv) which are directly readable by Excel / OpenOffice / etc

More advanced users can specify delimiters and other file extensions, for example:

1
E2A = ('path/to/file.DTA',' ', '.txt')

Takes the file file.DTA and converts it to file.txt where values are separated with a space rather than the standard comma

Syntax

1
2
3
4
5
6
E2A
E2A ('path/to/file.DTA')
E2A (delimiter)
E2A ('path/to/file.DTA',delimiter)
E2A ('path/to/file.DTA',delimiter, extension)
E2A ('path/to/file.DTA',delimiter, extension, interval)

Inputs

input1      - The path to a file input2      - Delimiter is the separator in the file , for comma, for space, \t for tab, etc input3      - Extension is the file format to output eg .csv , .txt, .dat, etc input4      - Desired magnetic field interval eg 0.2 to use interpolation to give data points every 0.2 Gauss

 Outputs

output      - a file by default a common separated value file (.csv)

 Example

1
E2A

Standard use, a graphical user interface to select file to convert and where to put it

1
E2A = ('/path/to/file.DTA',' ','.txt')

Take the file file.DTA and convert it to file.txt where values are separated with a space rather than the standard comma


Available for download here This script also requires BrukerRead to run


This page previously appeared on morganbye.net[^1][^2][^3]

[^1:] http://morganbye.net/epr-converter-e2a [^2:] http://morganbye.net/eprtoolbox/epr-converter-e2a) [^3:] http://morganbye.net/uncategorized/2012/02/epr-converter-e2a

What distinguishes you from other developers?

I've built data pipelines across 3 continents at petabyte scales, for over 15 years. But the data doesn't matter if we don't solve the human problems first - an AI solution that nobody uses is worthless.

Are the robots going to kill us all?

Not any time soon. At least not in the way that you've got imagined thanks to the Terminator movies. Sure somebody with a DARPA grant is always going to strap a knife/gun/flamethrower on the side of a robot - but just like in Dr.Who - right now, that robot will struggle to even get out of the room, let alone up some stairs.

But AI is going to steal my job, right?

A year ago, the whole world was convinced that AI was going to steal their job. Now, the reality is that most people are thinking 'I wish this POC at work would go a bit faster to scan these PDFs'.

When am I going to get my self-driving car?

Humans are complicated. If we invented driving today - there's NO WAY IN HELL we'd let humans do it. They get distracted. They text their friends. They drink. They make mistakes. But the reality is, all of our streets, cities (and even legal systems) have been built around these limitations. It would be surprisingly easy to build self-driving cars if there were no humans on the road. But today no one wants to take liability. If a self-driving company kills someone, who's responsible? The manufacturer? The insurance company? The software developer?