Introduction:
inpRW is a collection of Python modules for parsing, modifying, and writing Abaqus input files. It requires Python 3.7+, numpy, and scipy. It can be run independent of any Abaqus pre-processor, or it can be integrated into the Keyword Edit feature of the 3DEXPERIENCE Platform. The primary author is Erik Kane, who is a Dassault Systèmes Simulia Corp. employee.
inpRW should be considered around beta quality. While it has an automated test suite, it is not yet complete, so some areas of the code are not as robustly tested as others. Thus, there will likely be some bugs. There are also some useful features which have not yet been programmed, like full handling of *ASSEMBLY input files, accounting for *SYSTEM when reporting nodal coordinates, and some other features.
inpRW should be considered a plugin. This is not an official DS tool, so the same guarantees and support that go with official DS tools do not apply to inpRW. It is still my intention to further develop inpRW; this will involve correcting bugs and adding new features. Some future updates might need to make changes to the public-facing API which will break existing scripts. I will document when these occur. This will hopefully be a rare occurrence, but if a certain feature would make inpRW significantly better (and the only way to implement that feature is to make an API change), I will likely make that change.
inpRW does not enforce types for most function inputs. The expected type for each function argument is of course documented. While this might lead to function failures if using input types outside of those I considered when programming inpRW, there might also be cases which work which I did not consider.
If you find inpRW useful, I would appreciate if you sent me a message indicating your organization, how many people at your organization are using it, and what this utility allows you to do that you could not before. You can comment here if you wish, or you can send me an email (erik.kane@3ds.com). This feedback is important; I need to know how useful this tool is to end-users to help determine how much I can continue to work on inpRW.
The rest of this post groups various separate posts regarding inpRW.
Informative Posts About inpRW:
This post will contain recording and other posts meant to educate on the usage of inpRW.
inpRW Files:
This post will contain all the files necessary to run inpRW. This will include the Python .whl files necessary to run the tool, the documentation, and a test suite.
*** IMPORTANT ***
Please see this post for an important notice about installing inpRW to the latest public cloud version of 3DEXPERIENCE: inpRW with 3DEXPERIENCE 2024x Hotfix 5.21+
inpRW Updates:
This post consolidate individual update posts. These individual posts will be created when new versions of inpRW are released, and will include a summary of new features, bug fixes, and any API changes that have occurred.
inpRW questions:
You can write comments in this post if you have small questions regarding inpRW. If your question cannot be easily asked in a comment, feel free to create a full Question in this community, including the tag "inpRW"; you should also tag me (@Erik Kane) to ensure a quick response. Please read and search inpRW's documentation before posting questions. Any time I spend answering questions is time I can't spend working on inpRW, so please check the existing documentation first.
inpRW feedback:
This post will allow users to report bugs, request new features, etc. using the comment functionality.
