There are several usability issues with the stochastic simulations page.
1. Weather file in stochastic inputs table is different from file in inputs browser
The weather file variable used in stochastic.cpp is file_name, which is different from solar_resource (current library selection) in the UI. A Location and Resource UI equation sets file_name to solar_resource_file, but solar_resource_file is both calculated and indicator, so it is not shown in the inputs browser.

Solution: On the Location and Resource UI form, clear the Calculated and Indicator check boxes for solar_resource_file, and change the label for solar_resource from "Location" to "Solar resource library current selection".
2. Computed samples do not match output table
In order to get the Computed Samples table to match the output table, the user has to know to click Compute samples before clicking Run simulations. (I wasted a bunch of time comparing outputs to inputs for samples that I generated after running simulations.)
Solution: Show the generated samples table when the user clicks Run simulations. A better solution would be to show samples and outputs in a single table like parametric simulations, see #22.
Additional enhancements and fixes:
There are several usability issues with the stochastic simulations page.
1. Weather file in stochastic inputs table is different from file in inputs browser
The weather file variable used in stochastic.cpp is file_name, which is different from solar_resource (current library selection) in the UI. A Location and Resource UI equation sets file_name to solar_resource_file, but solar_resource_file is both calculated and indicator, so it is not shown in the inputs browser.
Solution: On the Location and Resource UI form, clear the Calculated and Indicator check boxes for solar_resource_file, and change the label for solar_resource from "Location" to "Solar resource library current selection".
2. Computed samples do not match output table
In order to get the Computed Samples table to match the output table, the user has to know to click Compute samples before clicking Run simulations. (I wasted a bunch of time comparing outputs to inputs for samples that I generated after running simulations.)
Solution: Show the generated samples table when the user clicks Run simulations. A better solution would be to show samples and outputs in a single table like parametric simulations, see #22.
Additional enhancements and fixes:
Change "Enable weather file analysis" check box label to "Include normal distribution of weather files based on DNI or GHI".
"Show CDF" button export to a table instead of message box.