george Posted May 8, 2016 Posted May 8, 2016 Hello,I have a PV SOL 6.0 horizon file. I uploaded it in here (your attachment does not allow attaching .hor filetypes).I need to send this file to a person who is using PVsyst (I still haven't asked which version does he have).The problem is there seems to be some tiny difference between PVsyst and PV SOL .hor files.How can I edit my PV SOL .hor file, so that it can be imported into PVsyst?I took a look at your PVsyst v6 help page, and it says that PVsyst 4, in its .hor files used only azimuths from -120 to 120.But with PVsyst 5, the -180 to 180 azimuths are supported, but the number of azimuths has been reduced from 240 in PVsyst to 120 in PVsyst 5. Did I understand this correctly?Can somebody please show me how can I convert my PV SOL .hor file to PVsyst 4 or PVsyst5 >= .hor file?Thank you in advance.
André Mermoud Posted May 10, 2016 Posted May 10, 2016 I don't know the format of the PV*SOL horizon files, but in PVsyst you can simply create a CSV file of (Azimuth, Height) pairs values.See the help for the exact format. Now defining points every degree doesn't make sense. If so, PVsyst will "simplify" the horizon line by eliminating the unnecessary points, in order to get a max. of 120 points.
george Posted May 11, 2016 Author Posted May 11, 2016 Dear Mr. Mermoud,Thank you for the reply.I already took a look at your horizon profile help page, and I am not sure I understand the explanation.The PVsyst 4 used pairs of Azimuth, Height values, where Azimuths started from -120 and went to 120 = making it total of 240 Azimuths?PVsyst 5 and PVsyst 6 use pairs of Azimuth, Height values, where Azimuths start from -180 and go to 180, but with incremental step of 3. So that means: -180, -177, -174 ... , 177, 180.Did I understand that correctly?
André Mermoud Posted May 17, 2016 Posted May 17, 2016 In any version of PVsyst, you can define pairs of (Azimuth, Height) as you like (not necessarily with identical azimuth steps). Usually points spaced by 5-10° (or following the significant points of your horizon) are largely sufficient. For diffuse calculations, you are advised to define the horizon all around the site (azimuth -180 .. 180°). In the version 4, the number of points was limited. Some software gave horizon with 1 point every degree, which is completely useless. In these cases PVsyst reduced the number of points by performing some averages.
george Posted May 17, 2016 Author Posted May 17, 2016 Thank you for the reply André. In the version 4, the number of points was limited. Some software gave horizon with 1 point every degree, which is completely useless. In these cases PVsyst reduced the number of points by performing some averages. Does this mean that in PVsyst version 4, the diffuse radiation calculation was also performed on the horizon with the following azimuth directions: -120 to 120?Or in PVsyst version 4, the diffuse radiation calculations were performed with horizon consisted of -180 to 180 azimuth directions?
george Posted June 3, 2016 Author Posted June 3, 2016 Dear André.Can you please say more on how PVsyst 4,5 and 6 will deal with comment lines (lines which are not Azimuth, Height pairs)?Here is an example of a .hor file: STUTTGART DEU, N48.68, E9.22Altitude: 248 m# Timezone: UTC+01:00-180 46-177 46-174 46-171 46-168 46 Will all versions of PVsyst (versions: 4,5,6) simply ignore the first three lines?Thank you for the reply.
André Mermoud Posted May 27, 2017 Posted May 27, 2017 The reading of custom Horizon files is really very restricted.Only the first line may be a comment. The next lines should be values Azimuth; Height;We have indeed to modernize this reading for allowing a more flexible reading.
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