SolarNode Filter Simulator

The SolarNode Filter Simulator is a web application for designing and testing SolarNode Datum Filter configurations without a SolarNode:

• build a filter chain on a canvas, starting from the main filter chain on the Datum Queue, including nested chains
• configure each filter with the same settings SolarNode provides
• run sample datum through the chain, and see how each filter transformed them
• see the route each datum took through the filters, drawn on the canvas
• download the execution flow as a stand-alone HTML report
• export the configuration as a SolarNode settings CSV file, or import an existing one
• save the whole simulation, with its inputs, to a file to share it or open it in another browser

The simulator runs the real SolarNode filter code, from the SolarNode bundles published to Maven Central, so filters behave the same as they do on a node.

Note

The simulator is in early development. See PLAN.md for the roadmap.

Running

The simulator is a single application that serves its web UI over HTTP. Once it is running, visit the URL it prints in a desktop web browser. The native executable listens on port 2008 by default, and the JVM build (bootRun) on port 8080.

To run from source with Java 25:

./gradlew :solarnode-filter-sim-app:bootRun

To run the native executable (see README-Developers.md for how to build it):

./app/build/native/nativeCompile/sn-filter-sim

Once started, it prints a message with its URL:

SolarNode Filter Simulator (0.1.1) started, visit
http://localhost:2008

Pass --server.port=8081 (or set the SERVER_PORT environment variable) to use a different port. The native executable listens only on the local machine (127.0.0.1); pass --server.address=0.0.0.0 to accept connections from other machines. It logs only warnings and errors; pass --logging.level.root=info for the full log.

External commands

The POA Calculator (pvlib) filter runs an external command, normally the ghi-to-poa script of the SolarNodeOS sn-pvlib package, to calculate POA irradiance. The simulator runs a command only when its full path is in the Allowed Commands list, on the Environment tab of the inputs. Allow only programs you trust, as they run on the computer running the simulator. A list of commands to allow in every simulation can also be set when starting the simulator, with --sim.commands.allowed=/path/to/command,/another/command.