How omque/riverspider-powershell works
Project type and purpose
• This is a single‐purpose, command-line orchestration tool written in PowerShell (“riverSpider-PowerShell”).
• It automates a multi-step workflow:
• Takes a TTPASM input file (assembly code)
• Submits it to a Google Sheets–based assembler Web App
• Downloads the assembled RAM image
• Launches LogiSim (Java GUI) on local circuit files to simulate the processor
• Captures the execution trace and sends it back to the Web App for human-readable analysis
File structure
Top-level files only—no subdirectories:
• submit.ps1 – the main CLI orchestration script
• secretString.txt – stores your Google Apps Script password
• webapp.url – stores the deployed Web App URL
• test.ttpasm – sample TTPASM program for testing
• logisim310.jar / .circ files (externally acquired)
• LICENSE, README.md
There are no separate frontend/backend directories or microservices – it’s a single PowerShell script that interacts with:
• Local filesystem (configs, circuit files, TTPASM, output)
• External Web App (HTTP requests)
• Local Java process (LogiSim)
README for additional insights
• Specifies prerequisites: Java 8+, PowerShell 7.x
• Outlines a 7-step installation & configuration process (copy circuit files, configure Google Sheet Apps Script, place URL in webapp.url, adjust submit.ps1 constants)
• Describes the workflow and external dependencies (Google Sheets Web App, LogiSim)
Main components & interactions (
A. User Terminal (PowerShell 7.x)
B. submit.ps1 (PowerShell Orchestrator)
C. Local Configuration & Inputs
• secretString.txt (password)
• webapp.url (Web App endpoint)
• test.ttpasm or any .ttpasm file
• Circuit files: alu.circ, processorXXXX.circ, regbank.circ
D. External Service: Google Apps Script Web App
• Exposes REST endpoints to assemble TTPASM and analyze logs
• Backed by a Google Sheet “Assembler”
E. Local Java Process: LogiSim (logisim310.jar)
• Loads the circuit files, runs the RAM image, produces a trace log
F. Output: Analysis in Google Sheet, local console logs
Interactions (data flow):
1. User calls: .\submit.ps1 <program.ttpasm>
2. submit.ps1 reads secretString.txt & webapp.url
3. submit.ps1 POSTs TTPASM code + auth to Web App → receives assembled RAM image
4. submit.ps1 writes RAM image locally
5. submit.ps1 spawns Java: java -jar logisim310.jar -tty RAM_image → generates trace log
6. submit.ps1 POSTs trace log + auth to Web App → receives human-readable analysis
7. submit.ps1 prints final results to console and/or writes to files
Architectural patterns & design principles
• Orchestration / pipeline pattern: a single script coordinates multiple tools and services
• Separation of concerns:
• Config files (secretString.txt, webapp.url) isolated from code
• Core logic in submit.ps1; external dependencies injected via config
• Externalization of business logic: the assembler and analyzer live in a Google Sheet Web App, keeping heavy logic out of PowerShell
– Clear labels: e.g., “submit.ps1 Orchestrator,” “Google Assembler Web App,” “LogiSim (Java)”