For example, if you make an entry with an x value, but no y value, you get this error. Or, if your values in x do not ascend (0, 1, 3, 2) instead of (0,1,2,3) you may get a similar error.
There will be no programming response to do error checking. It is easier to export all your rel functions to troubleshoot. To export all rel functions, go to Function Panel (on right side), select export rel functions. The export file will go into an “exports” file at the root of your ADSM Workspace, and will be named with the scenario name. The file can then be opened in Excel, but if you identify corrections, they will have to be done back in the application. In fact, to make a correction it may be easiest to make a new rel points file and import instead of tinkering in one that has an error, especially if there is an error in the order and your function has many lines.
When the values in a relational function don't make sense, you get an error something like:
** ERROR:../rel_chart/rel_chart.c:277:REL_new_chart: assertion failed: (n > 0) 0 [main] adsm_simulation 14708 cygwin_exception::open_stackdumpfile: Dumping stack trace to adsm_simulation.exe.stackdump
For example, if you make an entry with an x value, but no y value, you get this error. Or, if your values in x do not ascend (0, 1, 3, 2) instead of (0,1,2,3) you may get a similar error.
There will be no programming response to do error checking. It is easier to export all your rel functions to troubleshoot. To export all rel functions, go to Function Panel (on right side), select export rel functions. The export file will go into an “exports” file at the root of your ADSM Workspace, and will be named with the scenario name. The file can then be opened in Excel, but if you identify corrections, they will have to be done back in the application. In fact, to make a correction it may be easiest to make a new rel points file and import instead of tinkering in one that has an error, especially if there is an error in the order and your function has many lines.