Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance analysis with multiple scenes #512

Open
cdeline opened this issue Apr 24, 2024 · 0 comments
Open

Performance analysis with multiple scenes #512

cdeline opened this issue Apr 24, 2024 · 0 comments
Assignees
Labels
v0_5_0 Include for v0.5.0 release

Comments

@cdeline
Copy link
Contributor

cdeline commented Apr 24, 2024

At the moment, performance is run on the entire RadianceObject, which means that a single module type is passed, even if you have multiple scenes with different module types.

Solution:

  • Make CECModule an optional property of the ModuleObj. When you run calculatePerformance, loop through sceneNums and check for defined CECModule if it’s not passed into calculatePerformance. Default to Prism.
@cdeline cdeline added the v0_5_0 Include for v0.5.0 release label Apr 24, 2024
@cdeline cdeline self-assigned this Apr 24, 2024
@cdeline cdeline mentioned this issue Apr 24, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v0_5_0 Include for v0.5.0 release
Projects
None yet
Development

No branches or pull requests

1 participant