The Challenge: From Code to Collaborative Science

Every engineer or researcher in renewable energy knows the scenario.

You’ve found an excellent Python package like pvlib — a well-documented, community-maintained library for photovoltaic system modeling.
The physics is sound. The functions are tested. The documentation is thorough.

But then comes the harder part.

• How do you turn this library into a reusable workflow that partners, customers, or colleagues can build upon?
• How do you ensure that when a colleague leaves, their carefully constructed models don’t leave with them?
• How do you share your work with collaborators who may not be Python experts — or who simply want to run the model without debugging import errors?

This is where engicloud.ai transforms modeling workflows.

A Real Example: Solar PV System Modeling

Let’s walk through a concrete example.

A research team wants to model a complete photovoltaic system from solar irradiance hitting the panels, through power generation and all the way to battery storage sizing.

Using pvlib and NumPy, they’ve written the physics.

The Components

1. Solar Irradiance Calculator

tus = pv.location.Location(32.2, -111, 'US/Arizona', 700, 'Tucson')
times = pd.date_range(start=startdate, end=enddate, freq='1min', tz=tus.tz)
cs = tus.get_clearsky(times)
solpos = tus.get_solarposition(times)
poa = pv.irradiance.get_total_irradiance(...)
  

‍This calculates plane-of-array irradiance based on location, time, and panel orientation.

2. Load Profile Calculator

A time-varying electrical load representing household consumption:

• lower at night
• higher in the evening

3. Panel Power Calculator

Converts irradiance into DC and AC power, based on:

• panel efficiency
• panel area
• number of panels
• system losses

4. Battery Sizing Calculator

Analyzes the net power flow to determine:

• required battery capacity
• nominal storage size for self-sufficiency

Each piece is straightforward Python.
Together, they form a complete PV system model.

engicloud.ai Calculators & Projects

Encapsulating Expertise

In engicloud.ai, each of these code blocks becomes a Calculator — a self-contained, reusable Python model with clearly defined inputs and outputs.

The key insight:
👉 The Python code does not change.

pvlib remains the computational engine — but now each piece is:

• Discoverable — searchable in the platform
• Documented — inputs, outputs, and physics are explicit
• Reusable — drag into any new project
• Shareable — publish to your team or the world

Chaining Calculators into Workflows

engicloud’s Project feature allows researchers to chain calculators together visually:

[Solar Irradiance] → [Panel] → [Battery]
                        ↑
               [Load Profile] ─┘
  

‍


The connections are explicit.

A new team member can immediately see:

• what data flows where
• which physical assumptions are made
• where to adjust parameters for sensitivity studies

Benefits

1. Knowledge Retention

“Co-workers or students leave — and take knowledge with them.”

With engicloud:

• Models are stored in the platform, not on individual laptops
• Workflows are visual and documented, not buried in notebooks
• Team members can fork and extend, preserving lineage

2. Reproducibility

Scientific reproducibility requires more than sharing code.

It requires:

• Environment consistency — same library versions
• Input clarity — what parameters were used?
• Workflow transparency — what was the processing chain?

engicloud Calculators capture all of this.
When you share a Project, collaborators get the entire computational environment, not just source files.

3. Building on Expert Work

pvlib is maintained by photovoltaic experts at Sandia National Laboratories and the broader open-source community.
It represents decades of validated solar modeling knowledge.

engicloud doesn’t replace this expertise — it amplifies it:

• Researchers build higher-level workflows on top of pvlib
• Non-experts can use those workflows without mastering pvlib
• The underlying physics remains rigorous and community-validated

4. Collaboration Across Skill Levels

Not everyone in a research group writes Python — and not everyone should have to.

With engicloud’s graphical canvas:

• Python experts build the calculators
• Domain experts assemble workflows and tune parameters
• Stakeholders explore results without touching code

The division of labor emerges naturally.

From Research to Dissemination

Traditional Academic Workflow

1. Write paper
2. Add “code available upon request” or a GitHub link
3. Hope someone can reproduce it
4. Watch citations — but nobody actually runs the model

engicloud Workflow

1. Build the model as interconnected Calculators
2. Publish the Project alongside the paper
3. Readers run the model immediately with their own data
4. Extensions are traceable, forkable, and citeable

This is what living papers should look like.

Technical Integration: Leveraging the Python Ecosystem

‍

“Do I have to rewrite everything?” No.
‍

import numpy as np
import pandas as pd
import pvlib as pv
  

engicloud runs your code with access to:

• NumPy / SciPy for numerical computing
• pandas for time-series handling
• Domain libraries like pvlib, CoolProp, or internal packages

The platform adds structure — not constraints.

What engicloud Adds

A Researcher’s Workflow

Week 1
Import existing pvlib code into Calculators. Define inputs (location, dates, panel specs) and outputs (power curves, battery size).

Week 2
Build a Project. Run sensitivity studies. Collaborators in Germany run the same model with different locations.

Month 2
A new student joins. Instead of “here’s a notebook, good luck,” they explore the Project visually — and understand it in an afternoon.

Month 6
Paper accepted. The Project is published with the manuscript. Three research groups cite it — and extend it.

Year 2
The student graduates. The model lives on.

Conclusion: The Platform for Living Engineering Knowledge

engicloud.ai doesn’t replace Python, pvlib, or deep domain expertise.

It makes that expertise:

• easier to access
• easier to reuse
• easier to extend
• easier to collaborate on

In the age of AI, it’s more important than ever that scientific and engineering knowledge remains executable, not just described.

The photovoltaic example illustrates the vision:

• Expert-created code provides the physics
• Calculators provide structure and reusability
• Projects provide composition and visualization
• The platform provides collaboration and longevity

For researchers: less time fighting environments.
For teams: knowledge that survives personnel changes.
For science: work that can actually be reproduced.

That’s the promise of engicloud.ai — where 100,000 equations define your next discovery.

Ready to transform your research workflow?
Explore engicloud.ai and turn your existing Python models into collaborative, reusable engineering knowledge.