Debugging your simulations

As you work with Ashes it might happen that the simulation does not behave as you expected. In most cases, this is due to the model not being defined correctly and can be solved by modifying your input.
  • If you are prompted with an error message, you can follow the steps described in the message or check the Error messages section
  • You can also check whether another user has had similar issues on our user forum following this link:  https://www.simis.io/Q-and-A. If no one has, please post a question yourself giving as much info as you can about the error:
      - What is the error? Why is what happened not what you expected?
      - What steps did you take in Ashes before the error occurred?
      - What is your use case? What type of results are you trying to obtain with Ashes?
      - Do not hesitate to add screenshots to explain your issue.
If the problems lies in the Dll defining an External controller, you can see how to obtain debugging information in the Debugging the controller section.

If you encounter issues that cannot be solved following the steps previously mentioned, for example errors related to your computer, we can help you fix the problem. Contact us at support@simis.io, explaining in details the steps you followed prior to the error occurring. Please attach the log files produced by Ashes to help us with the debugging. You can find the log files by following the instructions in the Debug log file section.

Note: generally, the fastest way to get your problems sorted with Ashes is
  • First check the user manual 
  • If you don't find the answer, post a question in the forum 
  • If that does not help, contact us at support@simis.io


3.13.1 Crash report
3.13.1.1 Debug log file
3.13.1.2 Actions log file
3.13.1.3 Minidump file
3.13.1.4 Ashes project
3.13.2 Debugging the controller
3.13.3 Error messages
3.13.3.1 Displacement and load residual tolerances were not reached
3.13.3.2 The hub must be higher than half of the turbulent wind field height
3.13.3.3 Ill-conditioned or non-invertible system
3.13.3.4 Duplicated blades
3.13.3.5 One or more parts of the model have errors
3.13.3.6 A rotor moved outside of the boundary of the turbulent wind field
3.13.3.7 The turbulent wind file was not found
3.13.3.8 The spring had a displacement outside the range provided
3.13.3.9 The solver detected infinite numerical values
3.13.3.10 The analysis ran into a numerical problem
3.13.3.11 Damping parameters give unphisical values
3.13.3.12 The controller DLL was not running
3.13.3.13 Induced velocity was larger than relative velocity
3.13.3.14 The Steady BEM did not converge
3.13.3.15 File import
3.13.3.15.1 Unrecognized keywords
3.13.3.15.2 All offsets have to be zero at the root
3.13.3.15.3 The blade name was not found in the database
3.13.3.15.4 Part name not found
3.13.3.15.5 Parameter not used in the context
3.13.3.15.6 Values in table must be strictly increasing
3.13.3.15.7 Not a valid tag parameter
3.13.3.15.8 A tag cannot have a tag that influences placed after it
3.13.3.15.9 The name of the imported support section must be equal to the name of the existing support section
3.13.3.15.10 File for parameter X could not be loaded
3.13.3.15.11 Number of RNAs in the imported file error
3.13.3.15.12 Duplicated sensor
3.13.3.15.13 Part name in the sensor list does not exist
3.13.3.16 Python API errors
3.13.3.16.1 Python script maximum timeout exceeded
3.13.3.16.2 Could not find a Python executable
3.13.3.16.3 The Python script process exited with an error message