unilhexio Posted March 14, 2017 Posted March 14, 2017 I am testing now the calculation for several years, and the results that I got in batch simulation are not the same than I got by changing the year of simulation in "Ageing" tool.In "batch simulation", I have specified Degradation-> year of simulation", and then in the csv batchparams file I have introduce the years I want to simulate, but the Energy Injected into Grid that I obtain after batch simulation is sliglthly higher than the results I got by changing the year of simulation in "Ageing" tool.What can be wrong? Is the batch simulation taking into account the mismatch increase due to degradation?
Bruno Wittmer Posted March 16, 2017 Posted March 16, 2017 Yes, in principle the two should yield identical results. I will check this and post a reply.
Bruno Wittmer Posted March 17, 2017 Posted March 17, 2017 The behavior you are observing might be linked to the flag that controls the mismatch calculation before each simulation.Before a calculation involving ageing, PVsyst will, by default, do a Monte-Carlo calculation of the mismatch factor due to ageing.This leads to slightly different results every time you perform a simulation.You can also force the program to keep the same mismatch factor for each simulation. In the 'Ageing' dialog you need to check 'Keeps calculated Mismatch values'.In this case the mismatch values are kept fixed (also written to file) and the simulation will give always the same results.Keeping mismatch values fixed.
unilhexio Posted March 17, 2017 Author Posted March 17, 2017 The behavior you are observing might be linked to the flag that controls the mismatch calculation before each simulation.Before a calculation involving ageing, PVsyst will, by default, do a Monte-Carlo calculation of the mismatch factor due to ageing.This leads to slightly different results every time you perform a simulation.You can also force the program to keep the same mismatch factor for each simulation. In the 'Ageing' dialog you need to check 'Keeps calculated Mismatch values'.In this case the mismatch values are kept fixed (also written to file) and the simulation will give always the same results.Ident Simulation Simul for Year Comment SIM_1 0 New simulation variant [/i]Is "year 0" the first year of simulation?
unilhexio Posted March 17, 2017 Author Posted March 17, 2017 The case I have tested:The following shows the mismatch parameters as I stablished:http://thumbs.subefotos.com/903bbcd26d5c63a97c436af14ba5ef55o.jpgAnd the following shows the batch parameters I want to change:http://thumbs.subefotos.com/1794a8fcc28eea2017ac310ab5ed44dfo.jpgThe following is the batchparams .csv file as I have defined it:http://thumbs.subefotos.com/5352dce5bd7b9f4ee831c47b18e82404o.jpgAn the following is the Batch results:http://thumbs.subefotos.com/4517935500acbff8e9b6b2cb540d1aa7o.jpgThe following shows the PVsyst simulation results for the second year (stablishing "year 2" in ageing):http://thumbs.subefotos.com/221213437be8550379be53024f03c7c4o.jpgSummarizing:For 2nd year, the PVsyst simulation leads to a PR of 85.1% and 12.081 MWh/yr (12.080.597 kWh/year).For 2nd year (SIM_3) batch calculation leads to a PR of 85.14 and 12.089.130 kWh/year.I am not sure if the right simulation would be SIM_2. In that case batch calculation leads to a PR of 85.4 and 12.126.279 kWh/year.None of the above Batch ressults are matching with what I obtain directly in PVsyst simulation for 2nd year.If I repeat the batch calculation I obtain the same ressults again and again.By the way, the same occurs in every project I do. I don't think it is related with this project, particularly.
unilhexio Posted March 27, 2017 Author Posted March 27, 2017 I would appreciate a response about this issue...
unilhexio Posted April 5, 2017 Author Posted April 5, 2017 It seems I am alone in this discussion, but the ressults from the batch calculation do not match with the results from the final report simulation. There are slight differences (in the order of some kWh) in Energy injected into Grid and I think PVsyst support team should consider this issue.Regards.
unilhexio Posted June 22, 2017 Author Posted June 22, 2017 Dear PVsyst team,Have you revised this issue yet?I don't see that it had been solved in the latest PVsyst version...Regards.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now