aquiles viza
04/03/2024, 1:59 AMresults.txt
file and then reopen it with cace
I expect the generated data to be shown but that's not the case.
The data exists if I open the file, but cace
is not able to recognize it.
Also, if I run another test after running the one with multiple simulations, those results will be lost when cace
refresh the new results.Leo Moser
04/03/2024, 4:48 PMaquiles viza
04/03/2024, 4:53 PMtestbench
or results
.Tim Edwards
04/03/2024, 5:55 PMTim Edwards
04/03/2024, 6:29 PMstatus: done
entries in results
. The status: done
is normally associated with plots. But apparently it fools CACE into thinking the parameter result is a plot, which prevents it from writing the numerical results to the file.
There are multiple issues here; the main one is that the results get lost when "`status`" is present in the results dictionary. But there are other issues, too, such as that the numerical results from the testbenches exist but are inaccessible because the "pass/fail" button isn't created. The button provides access to the testbench data, so the button should be created when "testbenches" data exist rather than when "results" data exist. The results can always be regenerated on demand if needed.
The root cause of this is that any time a plot is made the status: done
entry is created, and then messes up everything. Until we fix this, don't look at any graphs of data for parameters that are not intentionally made to be plots between the time they are simulated and the time that the output file is made. Run the simulations, save the resulting file, then look at plots.
We'll get this fixed ASAP.aquiles viza
04/03/2024, 8:03 PMTim Edwards
04/03/2024, 8:04 PMaquiles viza
04/03/2024, 8:20 PMcace
.Leo Moser
04/04/2024, 6:28 AMaquiles viza
04/04/2024, 3:48 PM