Main Lemma Repository
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Trevor Irons 0b7f2462f4 Merge branch 'master' of https://lemma.codes/LemmaSoftware/Lemma 3 years ago
.github/workflows Create cmake.yml 4 years ago
Anaconda Anaconda Environment 6 years ago
CMake Merge branch 'master' of https://lemma.codes/LemmaSoftware/Lemma 3 years ago
Documentation Updated for TEM1D, including skeleton testing framework. 6 years ago
Modules Merge branch 'master' of https://lemma.codes/LemmaSoftware/Lemma 3 years ago
config Work towards port of FDEM code to C++-11 and improved unit testing. 8 years ago
python Fix to copy of README.md for python publish. 4 years ago
vim Bug fix for Anderson lagged solution which would occasionally result in NaN due to array index overrun in spline. Also work towards grounding points in wire antenna. 4 years ago
CMakeLists.txt Merge branch 'master' of https://lemma.codes/LemmaSoftware/Lemma 3 years ago
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 5 years ago
CTestConfig.cmake Fix for CTest in versions 3.14 and greater 5 years ago
LICENCE More work towards using c++-11, and better documentation. 8 years ago
README.md Lemma Github sync 3 years ago

README.md

About

Lemma is an ElectroMagnetics Modelling API. Lemma is developed in the hopes that it will be helpful for academics, industry, and anyone else interested in geophysical modelling.

  • Written in C++
  • Test driven
  • Flexible
  • Fast
  • Object oriented
  • Python bindings
  • VTK integration

Git

Lemma is hosted on several Git instances. Our main instance runs on Gitea and is at https://lemmasoftware.org. The project is also mirrored on GitHub.

Team

Lemma is and has been developed by several organisations and people, including: University of Utah, Colorado School of Mines, US Geological Survey.

Platforms

Lemma is tested on Linux (Ubuntu & Arch), Mac OSX and Windows (7&10) platforms. If you have used Lemma on something else, please let us know.

Getting involved

  • Testing code
  • Improving documentation