Python client (high-level functions) for RFEM 6 using Web Services (WS), SOAP and WSDL. Available Python SOAP pkgs can be found on wiki.python.org.
This Python project is focused on opening RFEM 6 to all of our customers, enabling them to interact with RFEM 6 on a much higher level. If you are looking for a tool to help you solve parametric models or optimization tasks, you have come to the right place. This community serves as a support portal and base for all of your future projects. The goal is to create an easily expandable Python library, which communicates instructions to RFEM 6 through WebServices (WS). WS enables access to RFEM 6 either via a local instance or a remote internet connection.
- : folder following the structure of RFEM 6 navigator containing individual types of objects
- : runs after window and initializes suds.Client by connecting to
http://localhost:8081/wsdl
and activating model in RFEM. It also envelops essential global functions. - : definition of enumerations
Dependency check is implemented inside dependencies.py with option to install during execution.
-
๐ Clone this repository (if you have GitHub account) or download actual release
-
โ๏ธ Check if there are no opened dialogues in RFEM and server port range under Options-Web Services corresponds to the one set in initModel
-
๐ Run your script. Inspirations can be found in Examples or UnitTests.
The scripts are intended to be used as templates or examples. Also, they can be used for testing of backward compatibility.
Collection of scripts used to support further development.
The easiest way to enjoy the Client is to install current RFEM package directly to your Python via pip install RFEM
. Especially if no code changes are required.
For complete description of classes and functions visit our .
If you run into problems see our Wiki. We are slowly but surely expanding the solutions to the problems found in the Issues section.
Contributions are always welcome!๐ Please ensure your pull request adheres to the following guidelines:
- Alphabetize your entry.
- Search previous suggestions before making a new one, as yours may be a duplicate.
- Suggested READMEs should be beautiful or stand out in some way.
- Make an individual pull request for each suggestion.
- New categories, or improvements to the existing categorization are welcome.
- Keep descriptions short and simple, but descriptive.
- Start the description with a capital and end with a full stop/period.
- Check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.
- Use the #readme anchor for GitHub READMEs to link them directly