Lemma is an Electromagnetics API
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
Trevor Irons ee7121abcf Clean up of KiHa test il y a 3 ans
.github/workflows Create cmake.yml il y a 3 ans
Anaconda Anaconda Environment il y a 6 ans
CMake More work towards renwed PIP pushes il y a 4 ans
Documentation Updated for TEM1D, including skeleton testing framework. il y a 6 ans
Modules Clean up of KiHa test il y a 3 ans
config Work towards port of FDEM code to C++-11 and improved unit testing. il y a 8 ans
python Fix to copy of README.md for python publish. il y a 4 ans
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. il y a 4 ans
CMakeLists.txt Fix to Boost in CMake to throw error when not found but requested. Also fixed bench kiha test il y a 3 ans
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md il y a 5 ans
CTestConfig.cmake Fix for CTest in versions 3.14 and greater il y a 5 ans
LICENCE More work towards using c++-11, and better documentation. il y a 8 ans
README.md Lemma Github sync il y a 3 ans

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