This software started life as an attempt to produce a user-friendly version of some 
direct methods code. As the project developed, we decided that it would be useful to 
add a multislice code since with bulk electron diffraction one can never avoid dynamical 
effects, although in many cases they are not critical (to be specific, if 1s channelling 
dominates). We also decided to adopt a GNU model for the software to try and make it as 
standard, and widely usable as possible, avoiding have different versions for specific 
operating systems. The hope is that in a few years the code becomes something which is 
widely used and maintained by the electron microscopy community as a whole.

It will, of course, be some time before the code reaches this stage. We hope that others 
will be interested in contributing, for instance specific code, suggestions or time to 
test it in different environments.

If you are interested in contributing code, there are some basics that need to be adhered 
to. The code should be something which is generally useful and can be applied to either 
(or both) images and diffraction patterns via a GUI. The code should be standard C, C++ 
or Fortran and should (as a minimum) have been tested with the GNU compilers to make sure 
it does not have incompatible features. It should have a Makefile (configure scripts would 
be better), help information in terms of html files and NOT require an extensive set of 
specialized external libraries to run. (The more external libraries are required, the harder 
it becomes to port it to different computers and to maintain.) You have to be prepared to 
provide source code (a basic GNU point), and help to maintain it.

If you want to contribute, please contact either Laurie Marks or Roar Kilaas. No promises; 
we will do our best. Some possibilities are:

Code to simulate and/or analyze CBED patterns. 

Code to simulate and/or analyze Kikuchi lines. 

Code to index a diffraction pattern. 

Code for different types of image filters, from simple to advanced (e.g. MaxEnt). 

Conversion routines, e.g. to Shelx and other code. 

Testing compilation, for instance using the INTEL compilers. 

Setting up a cvs system. 

Offering to mirror the software. 

