>>> IMPORTANT: Issue and bug reporting guidelines

Next Topic
 
classic Classic list List threaded Threaded
Locked 1 message Options
Reply | Threaded
Open this post in threaded view
|

>>> IMPORTANT: Issue and bug reporting guidelines

Precise Simulation
Administrator
This post was updated on .
  In order to get help efficiently, and to make it easy for people to help you, please try as much as possible to try to follow the steps below.

1) Update to the latest toolbox version

  Before submitting a bug report or a technical issue, please first ensure you have the latest version/build of the toolbox and confirm that the issue can be reproduced on the latest version.

  To find the current version and build number select "About ..." from the "Help" menu in the toolbox GUI, and compare it with the latest release as announced in the News forum topic, website release articles, and toolbox releases page.

2) Search forum, documentation, articles, and FAQ for similar and related issues

  Make sure your issue has not been previously asked and answered in the forum, toolbox user's guide and documentation, frequently asked questions (FAQ), or technical articles.

3) Ensure the issue is reproducible

  The most important thing for diagnosing issues is that to be easy and quickly reproducible. Reduce the model if possible to only include relevant parameters and geometry to reproduce a specific issue.

4) Include relevant information

  In order to get better help, please include enough but not too much relevant information with all issue reports, such as:

4.1) System configuration (Select "System Info ..." from the "Help" menu)

4.2) Model (.fea/.cfd) files and/or (.fes/.m) scripts (share with dropbox/google drive etc. if over a few MB size)

4.3) Steps to reproduce the error/issue

4.4) Error and/or warning messages

4.5) Other relevant information

5) Be respectful and humble, and try help answering questions from other users.