Chris Deline

generate module and scene image when running modelchain

1

if modelchain is called from GUI, it should generate a sample image of the module and the scene for debug purposes.

Side branch should be created to allow for automatic shading calculation. What's currently in development can be brought over to here.

Currently can't scan on more than 1 module in a 1-axis tracked simulation. This can be accomplished with multiple AnalysisObjs attached to a trackerDict entry.

Allow removal of entries from module.json

1

Right now module.json is growing and not easy to pare down. We should have functions that let you interact with this data file.

makeScene needs a sceneDict passed to it

1

Optional update: To better align with OOP best practices, it would be better if makeScene had kwarg inputs rather than only allowing sceneDict to be passed. SceneObj would have multiple...

Input Files: Allow NSRDB (SAM), PVGist, and others through PVLib iotools

6

NSRDB no longer provides TMY files - their file is in SAM csv output. Include capability to read this in. (Silvana has the code already - just include it as...

Update example gallery thumbnails in readthedocs

Once we decide to deprecate python 3.7 support, we can reopen pull request #425 without any negative consequences. In the meantime, this is just here as a reminder.

Multi scene objs

4

Allow multiple scene objects to be tracked at the same time by the RadianceObj. This is accomplished by running makeScene multiple times, each one appends a new SceneObj to RadianceObj.scenes...

At the moment addPiles is a function in the SceneObj. It works for fixed-tilt systems. But a top-level function in RadianceObj is needed to loop through entries in TrackerDict to...