- Posts: 2
SixParameterSolver ouputs different than SAM GUI
- pinkardw
- Topic Author
Less
More
16 Jan 2022 20:28 #10510
by pinkardw
SixParameterSolver ouputs different than SAM GUI was created by pinkardw
Hello,
I am running a trade study on combinations of solar panels and inverters that satisfy a given power requirement. Roughly a hundred of the panel models I want to use are not included in the SAM module database, and I was hoping to use PySAM to create inputs, rather than having to input them all into the GUI using the "CEC Performance Model with User Entered Specifications" menu.
I think the Sixparsolve class is the right one to do this ( nrel-pysam.readthedocs.io/en/master/modules/SixParsolve.html ), but when I input values from a module currently in the SAM database, I get different values than what is displayed on the GUI.
Take the Panasonic panel with model number VBHN340SA17 as an example. When I provide the inputs as user entered specifications, I get matching results (see attached screenshot).
When I input the following code:
I get different numbers:
params_outputs =
Is this expected behavior, or am I doing something wrong?
Thanks,
Warren L. Pinkard
I am running a trade study on combinations of solar panels and inverters that satisfy a given power requirement. Roughly a hundred of the panel models I want to use are not included in the SAM module database, and I was hoping to use PySAM to create inputs, rather than having to input them all into the GUI using the "CEC Performance Model with User Entered Specifications" menu.
I think the Sixparsolve class is the right one to do this ( nrel-pysam.readthedocs.io/en/master/modules/SixParsolve.html ), but when I input values from a module currently in the SAM database, I get different values than what is displayed on the GUI.
Take the Panasonic panel with model number VBHN340SA17 as an example. When I provide the inputs as user entered specifications, I get matching results (see attached screenshot).
When I input the following code:
Code:
from PySAM import SixParsolve as ps
params = ps.new()
params_inputs = {
'Imp':5.7,
'Isc':6.13,
'Nser':96.0,
'Tref':43.8,
'Vmp':59.7,
'Voc':71.3,
'alpha_isc':0.001839,
'beta_voc':-0.17825,
'celltype':'monoSi',
'gamma_pmp':-0.31
}
params.SixParameterSolver.assign(params_inputs)
params.execute()
params_outputs = params.Outputs.export()
params_outputs =
Code:
{'Adj': 3.236505714093858,
'Il': 6.13915732085862,
'Io': 2.8122531288754544e-11,
'Rs': 0.5484510790171748,
'Rsh': 367.1385103052429,
'a': 2.7342109987265566}
Thanks,
Warren L. Pinkard
Attachments:
Please Log in or Create an account to join the conversation.
- pgilman
Less
More
- Posts: 5447
19 Jan 2022 11:48 #10523
by pgilman
Replied by pgilman on topic SixParameterSolver ouputs different than SAM GUI
Hi Warren,
I had to do a bit of digging to sort this out. Thank you for providing the Python script -- that made my job a bit easier.
Anyway, the SAM user interface sets Tref = 25 rather than to Tnoct. If you make that change in your Python code you should get the same results as SAM.
The Tnoct parameter is used for cell temperature calculations when you simulate the PV system with the pvsamv1 module. It is not used when you generate parameters with the 6parsolve module.
Best regards,
Paul.
I had to do a bit of digging to sort this out. Thank you for providing the Python script -- that made my job a bit easier.
Anyway, the SAM user interface sets Tref = 25 rather than to Tnoct. If you make that change in your Python code you should get the same results as SAM.
The Tnoct parameter is used for cell temperature calculations when you simulate the PV system with the pvsamv1 module. It is not used when you generate parameters with the 6parsolve module.
Best regards,
Paul.
Please Log in or Create an account to join the conversation.
- pinkardw
- Topic Author
Less
More
- Posts: 2
19 Jan 2022 23:36 #10524
by pinkardw
Replied by pinkardw on topic SixParameterSolver ouputs different than SAM GUI
That is exactly what I needed, thanks so much Paul!
- Warren
- Warren
Please Log in or Create an account to join the conversation.
Moderators: pgilman