.. E-CAM documentation master file, created by sphinx-quickstart on Thu Sep 15 17:56:17 2016. You can adapt this file completely to your liking, but it should at least contain the root `toctree` directive... _readme_electronic_structure:

* :ref:`search`.. figure:: ./images/wake_nova-rgb.png :figwidth: 25 % :align: leftThis is a collection of the modules that have been created by E-CAM community within the area of Electronic Structure. This documentation is created using ReStructured Text and the git repository for the documentation source files can be found at

public and open to contributions.In the context of E-CAM, the definition of a software module is any piece of software that could be of use to the E-CAM community and that encapsulates some additional functionality, enhanced performance or improved usability for people performing computational simulations in the domain areas of interest to us. This definition is deliberately broader than the traditional concept of a module as defined in the semantics of most high-level programming languages and is intended to capture inter alia workflow scripts, analysis tools and test suites as well as traditional subroutines and functions. Because such E-CAM modules will form a heterogeneous collection we prefer to refer to this as an E-CAM software repository rather than a library (since the word library carries a particular meaning in the programming world). The modules do however share with the traditional computer science definition the concept of hiding the internal workings of a module behind simple and well-defined interfaces. It is probable that in many cases the modules will result from the abstraction and refactoring of useful ideas from existing codes rather than being written entirely de novo.Perhaps more important than exactly what a module is, is how it is written and used. A final E-CAM module adheres to current best-practice programming style conventions, is well documented and comes with either regression or unit tests (and any necessary associated data). E-CAM modules should be written in such a way that they can potentially take advantage of anticipated hardware developments in the near future (and this is one of the training objectives of E-CAM). Extended Software Development Workshops=======================================ESDW Zaragoza 2016------------------The first Electronic Structure ESDW in Zaragoza in June 2016 was the starting point for the modules below... toctree:: :glob: :maxdepth: 1 ./modules/MatrixSwitch/readme ./modules/libOMM/readme ./modules/FDF/readme ./modules/pspio/readme ./modules/escdf/readme ./modules/poke/readme ./modules/sqare-grids-doc/readme ./modules/sqare-ode-doc/readme ./modules/sqare-states-doc/readmeESDW San Sebastian 2016-----------------------The ESDW in San Sebastian in September 2016 was the starting point for the modules below... toctree:: :glob: :maxdepth: 1 ./modules/Symmetry-Adapted-Wannier-Functions/readme ./modules/Wannier90-TB-Interface/readme

Pilot Projects==============One of primary activity of E-CAM is to engage with pilot projects with industrial partners. These projects are conceivedtogether with the partner and typically are to facilitate or improve the scope of computational simulation within thepartner. The related code development for the pilot projects are open source (where the licence of the underlyingsoftware allows this) and are described in the modules associated with the pilot projects.