I'd like to use the pv6parmod module to do some script-based parametric analysis of PV module performance, and I am trying to figure out the best workflow for this. Based on the variable names in the various modules, the logical order seems to be:
1. wfreader
2. irradproc
3. pv6parmod
However, I've not been able to get this workflow to work for me; the irradproc module is failing. Here's my sample code:
/** Configuration **/
// Clear all variables
clear();
// Weather file
var('file_name', 'C:/SAM/2015.1.30/solar_resource/USA CO Denver Centennial [golden - Nrel] (TMY3).csv');
// Model configuration
var('irrad_mode', 0);
var('sky_model', 2);
//var('albedo_const', 0.2);
// Array Configuration
var('track_mode', 0);
var('azimuth', 180);
var('tilt', 10);
/** Calculate POA Irradiance **/
// Read weather data then calculate POA irradiance
run('wfreader');
run('irradproc'); // Fails... why?
Using this, I get the rather cryptic error:
Error: check fail: reason unassigned referenced, with 'irrad_mode!' for: beam time -1.000000
EXEC_FAIL: irradproc
This sounds like an unassigned variable, but the error doesn't say which one, and as far as I can tell all the required variables for irradproc are assigned in the data container. What I am missing?
(Note: I'm testing this with SDKtool on Windows, 64-bit, SDK release 2015-1-30).
Alternative question: is there a better workflow for getting the required irradiance inputs for pv6parmod?
EDIT: I just saw that SAM 2015-06-30 is out, so I downloaded and tried it as well. Same error.