As a User, I would like to have a tool to more easily understand the lst TRACE information, when debugging TRNSYS simulations.
The most important case is debugging timesteps that fail to converge.
One way of visualizing this, would be a sequence diagram:
https://davidje13.github.io/SequenceDiagram/library.htm
https://github.com/davidje13/SequenceDiagram
In the TRNSYS case, the sequence would show the specific types that are being called, with information about the changing inputs that caused the call to be repeated.
Some tools exist to draw such diagrams.
Some initial projects try to get diagrams directly from code.
Most of these have not been maintained, though.
e.g.: https://github.com/pinetr2e/napkin
As a User, I would like to have a tool to more easily understand the lst TRACE information, when debugging TRNSYS simulations.
The most important case is debugging timesteps that fail to converge.
One way of visualizing this, would be a sequence diagram:
https://davidje13.github.io/SequenceDiagram/library.htm
https://github.com/davidje13/SequenceDiagram
In the TRNSYS case, the sequence would show the specific types that are being called, with information about the changing inputs that caused the call to be repeated.
Some tools exist to draw such diagrams.
Some initial projects try to get diagrams directly from code.
Most of these have not been maintained, though.
e.g.: https://github.com/pinetr2e/napkin