Edit shading data with Solmetric SunEye 210 output file

I’m having trouble figuring out how to use the SunEyeoutput in SAM. In SAM go to System Design/Edit Shading, then try
importing the SunEye ObstructionElevations file. In doing this, SAM automatically enables the third option, “solar azimouth-by-altitude beam
irradiance shading losses” but no imported data is visible. If you import data
under that third option, then you can see some data but it includes some header
rows and also zeros out any solar generation that I simulated prior to editing
shading.
Thanks. 

Hi Dale,

It is possible that the file format SAM is expecting is different from the format of the file you are trying to import. Would you mind attaching an example of the file so I can investigate?

An alternative would be to format the data yourself to match SAM's table.

Best regards,
Paul.

Hi Paul,

I've attached most of the SunEye 210 output files, just so you know what other options might be for shading data. I'll send the rest of them along with the SAM case simulation in the next post. The SunEye 210 output file that seemed to make the most sense to use is the ObstructionElevations file, but there's those first few rows of data that don't seem to work in SAM. The way I can import the file is System Design/Edit Shading/check "Enable solar azimuth-by-altitude beam irradiance shading losses"/import. I've tried editing the ObstructionElevations file to remove the first 11 rows, but whether it's there or not, the SAM simulation results in zero solar energy generation. I noticed that Sam is looking for an input file where 0 degrees is north, 90 is east, 180 is south, and 270 is west, whereas the SunEye 210 output file direction range is -180 through +180, so that might be an issue.

Thanks,
Dale 

Here are the rest of the files.

Hi Dale,

Thank you for sending the files.

There is a bug that affects importing the shading data as an obstruction table that we will fix. See github.com/NREL/SAM/issues/698 .

As a workaround, you can import the hourly data from the Sky01Shading.csv file.

Best regards,
Paul.

Any idea when the bug will be fixed?

In the meantime, the workaround seems to do the job. Thanks a lot!

Dale Lyons