The Loads Kernel Software allows for the calculation of quasi-steady and dynamic maneuver loads, unsteady gust loads in the time and frequency domain as well as dynamic landing loads based on a generic landing gear module.
[1] Voß, A., “Loads Kernel User Guide,” Institut für Aeroelastik, Deutsches Zentrum für Luft- und Raumfahrt, Göttingen, Germany, Technical Report DLR-IB-AE-GO-2020-136, Nov. 2021, https://elib.dlr.de/140268/.
[2] Voß, A., “An Implementation of the Vortex Lattice and the Doublet Lattice Method,” Institut für Aeroelastik, Deutsches Zentrum für Luft- und Raumfahrt, Göttingen, Germany, Technical Report DLR-IB-AE-GO-2020-137, Oktober 2020, https://elib.dlr.de/136536/.
If you use this software for your scientific work, we kindly ask you to include a reference [1,2] in your publications. Thank you!
Install Loads Kernel as a python package with its core dependencies using a package manager (PyPI or Conda):
pip install LoadsKernel
or
conda install -c conda-forge LoadsKernel
Copy and adjust the launch script (launch.py, example located in the scripts folder) to your needs / for your aircraft configuration. Then, launch the python script with:
python launch.py
Alternatively, if ~/.local/bin is in your system PATH, you can use the following commands from the command line:
loads-kernel --job_name jcl_xy --pre True --main True --post True --path_input /path/to/JCLs --path_output /path/to/output
As above, but with access to the code (download and keep the code where it is so that you can explore and modify):
git clone https://github.com/DLR-AE/LoadsKernel.git
cd <local_repo_path>
pip install -e .
To use the graphical tools and other features, optional libraries definded as extras are necessary:
pip install -e .[extras]
or
conda install -c conda-forge loadskernel-extras
Note: Especially with mpi or the graphical libraries, pip frequently fails. In that case, try to install the missing/failing packages using a package manager such as conda, which is the more robust solution.
There are two GUIs to visualize a simulation model (the Model Viewer) and to compare different sets of loads (Loads Compare), which can be started from the command line as well.
model-viewer
loads-compare
There is a growing number of tutorials based on Jupyter notebooks. You can either have a look at the static html tutorials or use the Jupyter notebooks interactively. For the latter, start a jupyter notebook server, which will open a dashboard in your web browser. Then open one of the *.ipynb notebooks from ./doc/tutorials and walk through the tutorials step-by-step.
or
jupyter notebook
This software is developed for scientific applications and is delivered as open source without any liability (BSD 3-Clause, please see LICENSE for details). For every new aircraft, a validation against test data and/or other simulation tools is highly recommended and in the responsibility of the user.
If you use this software for your scientific work, we kindly ask you to include a reference [1,2] in your publications. Thank you!
Note that this is a scientific software for users with a background in aerospace engineering and with a good understanding and experience in aeroelasticity. If you know what you are doing - go ahead and have fun! If you need specific help or assistence, we offer commerical support:
- Development of additional, proprietary features
- Consulting & Training courses
- Service & Support
We are interested in partnerships from both industry and academia, so feel free to contact us ([email protected]).
If you discoverd an obvious bug, please open an issue. In case you already know how to fix it, please provide your feedback via merge requests. For details, please see the instructions on how to provide a contribution or contact [email protected] if you need any assistance with that.
Status of the continuous integration pipelines / workflows:
Master branch
Development branch
In addition to the public regression testing (see above), additional and more comprehensive tests are performed and compared against long standing reference results. This is an internal process and the status of the continuous integration pipelines can only be accessed from within DLR:
Master branch
Development branch
Test coverage
