michael

@solarguru - that is an interesting idea, we will need to try that. We have about 2500 .MET files in our library (we run historical production analysis on many of our sites and each year is a separate MET file), so it would at least tell us if it's a network issue vs. the program itself having to read through each MET file when a project is opened. @MicheleANA - the downside of that is if the remote PC restarts, PVsyst will only run in demo mode once we start it up again.

Brief summary - please figure out a way to allow PVsyst to be run through a remote desktop. I would be willing to pay for a special license for this feature given that my team and i will be working remotely for an unknown period of time. I have a large team so all of our PVsyst files (MET, PAN, SIT, etc) are stored on a network drive so we are all synchronized across users. We all have desktop PC's running PVsyst which was fine until the COVID-19 outbreak prevented us from working in the office. We have installed PVsyst on our laptops but it runs very slowly across the network due to the number of projects in our system. I would like to have the ability to run the full program through remote desktop so I can perform my work efficiently. There are alternative programs which do not have this limitation - but unfortunately PVsyst is the only mainstream program banks and investors will accept.

I have been able to get around this problem by using Print > Adobe PDF instead.

I have noticed that when I import data in the 'PVsyst standard format' (typically after converting SolarAnywhere time series data), if I have a partial year the import leaves the temperatures in the months after the end of the time series as '0' in the .SIT file. In other words, if I import a file spanning 1/1/2000 - 4/20/2019, the monthly temperatures for May through December will be assigned a value of 0 C. Since that is generally not realistic for the areas where I am working, I have to calculate the missing averages manually and replace them in the .SIT file before I can use it. Can this bug be addressed in a future revision of the program? Thank you.

I am working on single-axis (N-S) tracking project where I need to stop the tracker at 12 noon and start it again at 3 PM. Between 12 noon and 3 pm, the tracker should stay at its 12 noon position, and at 3 pm it should move to its 3 pm position and continue as normal for the rest of the day. Is there a way either to simulate this behavior directly, or to get a result using the model outputs and some post-processing? Thanks.