Please use the comment section of this page to report bugs and request new features. If your bug report/feature request is too complicated for a comment, feel free to create a new post and tag me (@EK) and inpRW.
When reporting bugs, please first debug your own code to make sure the problem is not with your script. Bugs will most likely be difficult to solve, so providing specific information is essential. I'll need to know the version of inpRW you are running, any output from inpRW to stdout, and the traceback message (if there is one). In some cases, I might not be able to find the bug unless I have an input file and/or user script which produces the problem, but you don't need to provide those unless I ask for them.
New feature requests should be restricted to those that are of interest to many Abaqus customers. Being able to read input files specified via *INCLUDE is an example of a feature of interest to many Abaqus users (inpRW can already handle this). Being able to automatically generate 3 point bend tests based on particular set names is interesting, but something that should be handled by a user-script.
If you wish to contact me privately, you can send an email to Erik.Kane@3ds.com. Please include "inpRW" in the subject of the email.
My first priority is to write tests for the remainder of inpRW functions. After I've accomplished this task, I can begin to add new features with confidence that I won't break any existing functionality.
The following is a list of important feature enhancements I think inpRW needs:
- Full support for *ASSEMBLY input files
- Report node coordinates accounting for active *SYSTEM
This list will be expanded based on user feedback and my own ideas. It will of course shrink as I deliver on these ideas. Please note that anything on this page is not promised to be implemented, nor is a timeline implied. Rather, these are merely ideas that will be seriously considered for implementation at some point in the future.
