Hi All,
I have a script that I've written that I turned into an add-in. Things were working great the last time I used it, around Nov. 2023. I'm running it again, and I'm getting a very strange error/mistake that happens when I run it as an add-in, but it doesn't happen when I just run the JSL file on it's own.
So, the script runs some modeling and generates an output window that is supposed to show the results of each tuning run graphically and as a table. The output is supposed to look like this (this was run from the script itself):
The output window is generated from a data table that gathers all the fit statistics from the modeling platform.
So again, the script works great and does everything it's supposed to. When I then make it as a jmpaddin file and install it in JMP, something happens and the code gets confused, and instead of referencing the output table, it goes back to the original data table that contains my Y and X's that I'm using for modeling. As a result, the graph builder portion of the output window is blank and I get an error from JMP that the :Tune Run column doesn't exist (it doesn't in the original data table, but it does in the output data table).
This is the output for the same kind of modeling, but running it as an add-in instead of the JSL -- no graph builder:
And, when going to the Window List in the JMP home window, you can see that for the instance where I ran it as an add-in, it's generated the Bootstrap Forest Results window from the original data table T20-XL. So naturally there is no column :Tune Run in that data table. But, when I run it as the straight JSL, it correctly generates the output window (Bootstrap Forest Results 2) from the Summary Output data table as intended.
This is the error that I get:
And the log report shows the following:
I can't figure out what's going wrong and why the add-in version is trying to work with the original data table instead of the Summary Output data table that it's supposed to. I also don't understand why it would work running it straight from the JSL file, but as an add-in it doesn't work right at all.
Has anyone else come across this issue? If so, how did you correct it, and were you able to figure out how it happened in the first place?
Thanks!,
DS