GSoC 25 Project Ideas

[VaibhavUpreti]

This thread is for brainstorming and collecting project ideas for GSoC 2025. Share your suggestions, and let's collaborate to develop innovative ideas! 🚀

[SannidhiNair]

Potential GSoC 2025 Ideas

1. Hardware-in-the-Loop (HIL) Simulation

CircuitVerse could benefit from the ability to interact with real hardware in real-time, allowing users to validate their designs against actual devices.

• Establish a connection between CircuitVerse and microcontrollers (Arduino, ESP32, etc.).
• Implement real-time data exchange between virtual and physical components.
• Provide a collection of HIL-compatible components, such as sensors and actuators.

This feature would bridge the gap between simulation and real-world applications, making CircuitVerse a more powerful educational and prototyping tool.

---

2. Quantum Circuit Simulation

Expanding CircuitVerse to support quantum circuits would open doors for students and researchers interested in quantum computing fundamentals.

• Introduce quantum logic gates like Hadamard, CNOT, and T-gates.
• Develop a backend capable of simulating quantum operations.
• Create an interactive learning module explaining key quantum computing concepts.

By integrating quantum simulation capabilities, CircuitVerse could cater to a growing community exploring the future of computation.

---

3. Automated Test Generation for Circuits

Testing is a critical part of digital design, and automating test case generation could improve CircuitVerse’s usability for students and professionals alike.

• Implement algorithms to automatically generate test vectors for circuit validation.
• Develop a feature to simulate, analyze, and verify circuit behavior against test cases.
• Provide a library of predefined test scenarios to assist in learning and debugging.

Automating test case generation would make CircuitVerse a more effective platform for designing and debugging complex circuits.

[ThatDeparted2061]

Replacing WebAssembly with Web Workers in CircuitVerse

Why Replace WebAssembly with Web Workers?

1. Better Parallel Processing

Web Workers allow true parallel execution of JavaScript code by running in separate threads. WebAssembly, while efficient, still executes synchronously within the JavaScript main thread unless explicitly offloaded.

2. Non-blocking UI for Heavy Circuits

Complex circuit simulations can freeze the UI when processed in the main thread. Web Workers keep the UI responsive by running simulations in the background.

3. Simpler Debugging and Integration

Web Workers use standard JavaScript, making debugging easier compared to WebAssembly, which requires debugging through WASM tools and mappings.

4. Efficient Memory Management

Web Workers use structured cloning to pass data between threads, reducing memory overhead compared to WebAssembly's explicit memory management.

How Web Workers Help Manage Heavy Circuits

1. Offload Simulation Computation

   • The main thread remains responsive while computations run asynchronously in Web Workers.

2. Divide and Conquer for Large Circuits

   • Multiple workers can handle different circuit sections concurrently.

3. Avoid Main Thread Blocking

   • Ensures that UI interactions, such as zooming and selecting components, remain smooth even during complex simulations.

4. Dynamic Load Balancing

   • Assign tasks to different workers based on the circuit’s complexity, improving performance.

Implementation Strategy

1. Create a Web Worker for Simulation Logic

   • Move circuit evaluation and logic propagation to a separate worker.

2. Use Message Passing for Communication

   • Send circuit data from the main thread to the worker and retrieve results asynchronously.

3. Optimize Large Data Transfers

   • Use SharedArrayBuffer or transferable objects to efficiently share large circuit data.

4. Handle Worker Scaling

   • Implement a pool of workers to process multiple circuit components in parallel.

By adopting Web Workers instead of WebAssembly, CircuitVerse can achieve smoother performance, better scalability, and easier maintenance while handling heavy circuits.

[ThatDeparted2061]

@JoshVarga This is my proposal for the problem we discussed

[salmoneatenbybear]

1. Heatmap-Based Real-Time Visualization Tools

• Objective: Develop a feature that renders a dynamic heatmap over complex digital circuits, highlighting nodes or wires that change states (0 ↔ 1) frequently or cause high simulation overhead.
• Approach:
  • Live Signal Tracking: Monitor each net’s switching activity in real time, collecting transition data during simulation steps.
  • Color-Coded Overlay: Translate transition frequency into heatmap colors, providing immediate visual cues for potential bottlenecks or high-activity areas.
  • Technical Considerations:
    • Efficiently sample signals without slowing the simulation.
    • Provide granularity controls for users (e.g., adjust update frequency or heatmap intensity).

---

2. Open Hardware Component Library (Digital-Only)

• Objective: Expand CircuitVerse’s built-in library with common digital components (shift registers, digital sensors, counters, digital I/O expanders, etc.).
• Approach:
  • Pre-Built Modules: Implement standardized blocks modeled on open hardware specs, strictly for digital signals (no analog behavior).
  • Extensible Framework: Allow community-generated modules with pin definitions and logic behavior described in JSON or a similar config format.
  • Datasheet Alignment: Derive logic functionality from open-source datasheets to ensure consistency.

---

3. Circuit Partitioning for Large Designs

• Objective: Automatically and manually split large digital designs into smaller subcircuits for more efficient simulation and organization.
• Approach:
  • Automatic Partitioning: Analyze connectivity and functional groupings to suggest subcircuits (e.g., separate control logic, memory blocks).
  • Manual Partitioning: Let users explicitly define partitions to keep the design structured.
  • Signal Passing Mechanism: Synchronize partitions by assigning boundary pins that handshake data at each simulation step, ensuring consistent timing across partitions.

---

4. Open Hardware Emulation (Digital-Only)

• Objective: Emulate the digital I/O behavior of platforms like Arduino or ESP32, focusing on GPIO and basic digital protocols (I2C, SPI, UART in purely digital form).
• Approach:
  • Platform Abstraction Layer: Provide a core set of digital registers and pin mappings to replicate each platform’s basic I/O functionality.
  • Co-Design Capability: Allow a simplified representation of firmware (e.g., state machines) alongside digital components, simulating how signals would interact in real hardware.
  • Template Projects: Pre-configured circuit templates that mirror the pin layouts and basic boot-up logic of these boards.

---

5. Benchmarking and Performance Metrics

• Objective: Introduce a framework to measure simulation performance, helping optimize CircuitVerse for large-scale digital designs.
• Approach:
  • Benchmark Suite: Curate example circuits of increasing complexity to evaluate simulation speed, memory footprint, and event scheduling overhead.
  • Performance Metrics UI: Display real-time stats (cycles per second, memory usage) so users can see how design size or structure impacts performance.
  • Optimization Insights: Identify and log common bottlenecks (e.g., large LUTs, complex combinational paths) and guide users toward more efficient design patterns.

[ThatDeparted2061]

1. Electronic Rule Check (ERC) system

This is an ideation to the 3rd point mentioned Sannidhi

To give user a primary set of tests that can help in finding silly errors, prone to happen in complicated circuits

Some of the rules-

• Open Inputs: No gate or component should have unconnected input pins.
• Short Circuits: Avoid direct connections between power (Vcc) and ground (GND).
• Grounded Output: Ensure the circuit has a proper path to ground for current.
• Voltage and Current Mismatches: Ensure components like LEDs or resistors are correctly rated.
• Clock Signal Conflicts: Ensure there is no conflict in clock signal propagation.
  Integrations -
• Frontend- Provide an option named "Run ERC" to the user, so they can check their circuit.
• Backend: Integrate the ERC module into the simulation process. Before running a simulation, invoke the ElectricalRuleChecker to validate the circuit.

Future Enhancements -

• Real-Time Checking: Instead of a manual "Run ERC" button, implement real-time validation as the user designs the circuit.
• Customizable Rules: Allow advanced users to enable/disable specific rules.
• Educational Messages: Explain why each error occurs and how to fix it.

2. Replacing CodeMirror with Monaco Editor for Verilog in CircuitVerse

Why Switch from CodeMirror to Monaco Editor?

1. Better Support for Large Codebases

Monaco Editor, the same editor used in VS Code, handles large files more efficiently than CodeMirror, reducing lag when working with extensive Verilog code.

2. Rich Language Features

Monaco provides:

• Syntax highlighting tailored for Verilog.
• IntelliSense (code completion, hover tooltips, and error checking).
• Built-in support for code formatting and folding.

3. Improved Performance

Monaco is optimized for performance, leveraging Web Workers to process code in the background, keeping the UI smooth even with complex Verilog projects.

4. Seamless Integration with Modern Tooling

Monaco supports modern development features like:

• Multi-cursor editing.
• Real-time linting and diagnostics.
• Integration with language servers for better error handling and auto-completion.

5. Better Customization Options

Monaco provides:

• Custom themes and syntax rules.
• Keybindings that match VS Code for a familiar experience.
• API support for embedding custom Verilog helpers.

6. Extensive API and Documentation

Microsoft maintains Monaco with comprehensive documentation, making customization and debugging easier compared to CodeMirror.

Implementation Strategy

1. Replace CodeMirror with Monaco in CircuitVerse’s Verilog Editor

   • Modify the existing text editor initialization to use Monaco.

2. Enable Language-Specific Features

   • Integrate a Verilog language server for syntax checking and auto-completion.

3. Optimize Performance

   • Leverage Web Workers for background processing.
   • Configure lazy loading for large files.

4. Improve UI and User Experience

   • Provide an intuitive interface with collapsible code sections.
   • Add customizable themes and keyboard shortcuts.

Switching to Monaco Editor will enhance Verilog editing in CircuitVerse, providing a more robust and user-friendly development experience.

[092vk]

GSOC 2025 Ideas 🚀

1. 🎮 Gamifying CircuitVerse

Making Learning Digital Circuit Design Fun & Interactive! 🚀 through Games

1. 🎮 Digital Circuit Design Games 🧩 :

• This will be similar to Candy Crush where there will be a learning path , where you have to design a digital circuit at each level.
• The game will be structured so that after completing it, the student will have complete knowledge of Digital circuits
• The game will start with small combinational circuits like half adder , encoder ,etc and sequential circuits like counters and memory elements to increasingly difficult boolean implementations.

2. 📊 Leaderboards & Achievements 🏅

• Let the user Flex his skills and Show off 💪
• Leaderboard will be displayed with top circuit designers.
• Users will be rewarded through unique titles and avatars
• Users who win contests and challenges will get badges and titles like "Circuit Maker", "Logic Master", etc

3. 📈 User Stats & Activity Graph

• This will keep students motivated by visualizing their learning journey
• Currently the user dashboard is not interesting and blank
• Display the user stats like leetcode does to encourage the user to maintain his stats and display them on their Linkdin profiles.
• Display user activity graph

2. Expanding the Subcircuit Feature (As a electronics student this is highly needed and recommended )🛠️🔗

As a CircuitVerse user, building complex circuits like a 4-bit processor has been an incredibly frustrating experience. 😩 When working on such large projects, many of us often want to reuse previous circuits we've created or fork some circuits from other users. For example, I might want to reuse an ALU (Arithmetic Logic Unit) that I designed earlier, or even integrate subcircuits I forked from others. But the current process of adding these to my project is a hassle! There’s no simple way to import or integrate them efficiently, and the whole thing feels like a nightmare. 😖

• Idea is to allow the user to import and add their earlier circuits and forked circuits in their current project
• Now the user don't have to waste time designing the same thing again and again
• This encourages the reuse of circuits in other projects
• It saves time

3. Enhancing Simulator & Virtual Labs

Currently the simulator runs every time it gets a clock signal which keeps the simulator running all the time , even when the user does not need it.

• ⏯️ Play/Pause Button(Highly recommended) : Introduction of play and pause button to stop simulation during build/designing process.
• 🚀 Resource Efficiency: this saves the user resources and makes cv run smooth and faster
• 🤝 Real-time Collaboration:Since during designing the simulator can be turned off , resources are free to be used in things like real-time collaboration which might need high resource.
• Implementing rooms : While applying real time collaboration rooms can be created to restrict large number of users(<50 concurrent users in a room)
• this will allow features like virtual labs where student and teachers can work on same circuit

3. Contests and Challenges

• Improve the contests

---

[091vk]

GSOC 2025 Ideas 🚀

3. Enhancing Simulator & Virtual Lab

Currently the play() function responsible for enabling simulation from engine.js runs at every clock cycle even at times when the user don't want it to run like for example when the user is building the circuit he/she don't need the simulation to run.This consumes the resources.

• ⏯️ Play/Pause Button: the idea is to introduce the play and pause button allowing the User to take control of the simulator
• Resource Efficiency: Since the simulator is not running continuously , this will save user resources and make cv faster and smooth
• 🤝 Real-time CollaborationSince the simulator will not run during designing process , this frees up the resources for features like real-time simulator
• Virtual Labs : Real time collaboration can allow CV to have virtual labs by teachers.

3. **Contests and Challenges **

• Bring weekly contests to production grade
• Introduce ways to add problem statements in contests
• Add automated testbench based testing
• Introduction of challenges for Users
• Displaying of winners and challenges completion as badges and on leader boards

---

[Himanshu-kiran]

Brief GSOC 2025 ideas:

1.Guided Code Tour for CircuitVerse

Description:

Creating graphical guided code tour using the CodeTour extension in VSCode to help new contributors understand the large CircuitVerse codebase, workflows, and features. This detailed CodeTour will make onboarding process of new developers and contributors very easy.

Key Areas:

• Project Setup and Configuration
• Core Architecture and Code Structure
• Simulation part of Circuit Verse
• UI Components and Rendering
• Backend, Database and API Endpoints
• Testing and Debugging
• Contribution Workflow

Goal:

To improve the onboarding process for new contributors, making it easier for them to understand and contribute to CircuitVerse.

2.Develop an Analog Circuit Simulation for Circuitverse

Description:

Extend CircuitVerse to support analog circuit simulation, enabling users to design, simulate, and analyze analog circuits with features like DC analysis, AC analysis, and component modeling.

• Key Areas:

• DC Analysis
• AC analysis and diff plots
• Diff Components models
• and many more

Welcome more ideas

Goal:

I think this will significantly broaden the scope of the uses of CircuitVerse.

[salmoneatenbybear]

More ideas

#5157 ( smartboard friendly circuitverse )

#5208 ( circuit cryptography challenge )

#5287 ( Personal Custom Lib of reusable components ) cc : @092vk ( I think we have similar thoughts here )

#5290 ( Resource usage panel )

#5291 ( FSM diagram )

#5289 ( better snap grid for simulator )

[092vk]

@salmoneatenbybear The idea of FSM(Finite State Machines ) is great . We can't have a great digital circuit simulator without FSM. This will allow CV to be used for advanced digital problems and truly make CV one of its kind digital simulator. As an electronics student, I would love to see this in CV. We can implement state diagrams and state tables.

[Himanshu-kiran]

Can you give bit more clarity about circuit cryptography challenge! Is it something related to circuit contest?

[salmoneatenbybear]

@Himanshu-kiran

So that was just an idea I had, currently the first priority would be to bring weekly contest ( no problem statement, abstract contest where the best circuit wins ) to prod then maybe if maintainers permit we can have a problem statement style contest just like that in coding platforms like codechef.

Cryptography is a domain of contest which is possible out of many others, this was just a possible idea which can be a domain.

[Himanshu-kiran]

@salmoneatenbybear Okay got it.Thnks!

[Jay2006sawant]

GSOC 2025 IDEAS 🚀

1 . Augmented Reality (AR) Circuit Visualization for CircuitVerse

🌟 The Vision: A Living, Breathing Circuit
With AR Circuit Visualization, you could simply scan a QR code with your smartphone or wear an AR headset, and instantly, your circuit springs to life in front of you.
No more zooming in and out of tiny components on a screen—just walk around your circuit, observe signal flows in real-time, and interact with individual elements

Features:
📌 Scan & Load: Users scan a QR code or upload a CircuitVerse file to instantly visualize their circuit in 3D AR.
📌 Real-World Projection: Circuits appear floating in front of the user via smartphone, tablet, or AR headset (HoloLens, Meta Quest, etc.).
📌 360° View & Navigation: Users can walk around, zoom in/out, and rotate the circuit for a spatial understanding of connections.

🌟 The Bottom Line
Augmented Reality transforms circuit simulation from a passive experience into an interactive journey.

---

[Saahi30]

1. QR Code Sharing for Circuits

Objective:

Enable users to quickly share their circuits by generating a QR code, making it easy to add in project reports, presentations, and documentation.

Approach:

• Add a "Share" button that generates a unique QR code linked to the circuit.
• Users can download or embed the QR code in PDFs, slides, or print it.
• When scanned, the QR code opens the circuit in CircuitVerse for viewing and simulation.

---

2. Live Collaborative Circuit Editing (Circuit Jam)

Objective:

Enable multiple users to edit a circuit simultaneously in real time, similar to collaborative document editing platforms. This would help students and teams work together efficiently, improving circuit design workflows.

Approach:

Real-time collaboration can be resource-intensive, but a phased implementation can make it more feasible.

Phase 1: Basic Synchronization Using WebSockets

• Implement WebSockets (using Socket.io or Firebase Realtime Database) for real-time updates.
• Only sync changes when needed, rather than continuously streaming data.
• Use a "last edit" tracking system to reduce redundancy and bandwidth usage.

Phase 2: Peer-to-Peer Communication for Reduced Server Load

• Instead of handling all data through a central server, introduce WebRTC for peer-to-peer (P2P) communication where possible.
• Directly connect users in a shared session, reducing latency and server dependency.

Phase 3: Version Control and Conflict Resolution

• Implement a snapshot-based versioning system instead of full history logging to optimize storage and rollback options.
• Introduce a locking mechanism to prevent multiple users from modifying the same component simultaneously, reducing conflicts.
• Provide a basic Undo/Redo system to allow users to revert changes locally before committing them.

Phase 4: Advanced Features (Gradual Scaling)

• Add live cursors with user identifiers to show real-time movement and selections.
• Integrate a comments/chat panel for discussions directly on the circuit board.
• Expand to larger team collaborations by testing resource scalability before full deployment.

This stepwise approach ensures that live collaboration is introduced without overwhelming server resources, making it scalable and cost-efficient.

---

3. AI Chatbot for Circuit Assistance

Objective:

Integrate an AI assistant (such as Gemini or ChatGPT) to provide real-time circuit design support, debugging suggestions, and learning resources.

Approach:

Since AI models require significant resources and are not freely available, full integration is challenging. As an initial workaround:

• Implement a lightweight Electron app that occupies a side panel in the workbench.
• This app will run a default AI chatbot (such as Gemini or ChatGPT) without direct integration.
• Users will log in to their AI account separately, ensuring CircuitVerse does not bear AI model costs.

If a custom AI chatbot is developed later:

• Use Gemini’s free-tier API with 15 requests per minute and 155 daily requests, keeping in mind its constraints.
• Train the chatbot on circuit-related queries, limiting its focus to electrical engineering and simulation troubleshooting.

This ensures that AI-powered assistance is available from the outset while remaining cost-effective and scalable.

---

4. Fault Injection & Debugging Mode

Objective:

Enhance circuit realism by allowing users to simulate real-world failures and debugging challenges.

Approach:

• Introduce a "Fault Injection" toggle, allowing users to manually or randomly introduce component failures.
• Simulate different failure modes such as stuck-at faults, wire breaks, and transistor degradation.
• Implement an error log system that highlights potential points of failure and their effects on circuit behavior.

This feature would be particularly useful in educational environments where students learn about real-world circuit limitations and failure analysis.

[ThatDeparted2061]

Live collaborative circuit has been in the talks but i think you suggestion for its name as Circuit Jam is just impeccable
As far as an AI chatbot is concerned i think that will take up a lot of compute which would affect the processing speed

[Saahi30]

Hi @ThatDeparted2061,thanks for your response,CircuitJam does sound cool right....
plus completely understand that an AI chatbot would require significant compute, which could impact processing speed. That’s why I’m not suggesting a full chatbot but rather prebuilt models running as their own standalone service.
My idea is to have a simple dialog box that opens a small side window or pane within the application, allowing quick and handy interaction with these models—think of it like a hovering window of the ChatGPT website on the workbench.

[ThatDeparted2061]

We cud just add a lot of questions in it for FAQ , or you should try researching about some AI bot with MIT liscence which we can use and is super light !

[Priyanshu1035]

GSOC 2025 IDEAS

1. Practice Questions Section

• Introduce Practice Questions to help users reinforce circuit concepts.
• Include various formats such as:
  • Multiple Choice Questions (MCQs)
  • Circuit Design Challenges
  • Other Interactive Formats
• Implement difficulty levels, timed quizzes, and hints for a more engaging experience.
• This feature will enhance learning for students and educators by providing hands-on practice.
• Similar to Leetcode styled.

2. Revamping the Contest Section if Possible

• Selecting the winner based on votes received for a project is a shallow approach; alternative evaluation methods should be
  considered.
• Introduce a more robust scoring system that includes:
  • Project Complexity & Innovation: Judges can assign scores based on technical depth and creativity.
  • Functionality & Optimization: Ensuring the circuit works efficiently and is well-optimized.
  • Peer & Mentor Reviews: Instead of just votes, have experienced users provide feedback and scoring.
  • Automatic Testing (if feasible): Run circuit simulations to verify correctness and functionality.
• Encourage detailed project documentation, explaining the design choices and problem-solving approach.

[hxrshxz]

@VaibhavUpreti

🚀 Automating E2E Testing for CircuitVerse with Playwright 🚀

🎯 1. What’s the Problem?

Let’s be real—manually testing the CircuitVerse website is tedious and time-consuming. Every time a change is made, someone has to go through different pages, test UI elements, and ensure that features work correctly across multiple browsers and devices. Since CircuitVerse is an interactive platform, breakages can go unnoticed until users report issues. 😅

Here’s what’s happening:

• Silent Breakages: A small UI change might break the simulator, circuit saving, or sharing functionality, and we only find out when users complain. 🐛
• Manual Testing is Slow: Contributors and maintainers spend too much time manually verifying features instead of working on improvements. ⏳
• Cross-Browser & Device Issues: The site might work fine on Chrome but have issues on Safari, Firefox, or mobile devices. 🌐
• Risky Deployments: Without automated tests, every update feels like a gamble. 🎲
• This project aims to solve these problems by automating E2E testing for the CircuitVerse website using Playwright.

🛠️ 2. What Will I Do?

I'll build a testing framework that automatically checks CircuitVerse’s core functionality. Here’s the plan:

✅ Test the essentials:

• Does the homepage and simulator load correctly?

• Can users create, edit, and save circuits?

• Are login, signup, and authentication working properly?

• Does the circuit sharing feature function correctly?

• Do UI elements (buttons, toolbars, modals) behave as expected?

• Test circuit validation (ensuring invalid circuits are flagged properly).

• Add tests for multi-user collaboration features.

• Implement visual regression testing for UI consistency.

• 🎨 Catch UI/UX Issues:
  Capture screenshots and compare them to detect layout or styling changes across updates.
  🌍 Ensure Cross-Browser & Device Compatibility:

• Run tests on Chrome, Firefox, Safari, and mobile browsers.
  🤖 Automate Everything:

• Integrate tests with GitHub Actions to run on every pull request and deployment.
  📚 Help Contributors:

• Write clear documentation so future contributors can maintain and expand the tests.
  🌟 3. Why Does This Matter?

Here’s how this benefits CircuitVerse and its community:

• Fewer Bugs: Catching issues early improves reliability for users. 🛡️
• Faster Releases: Developers can confidently deploy updates. ⚡
• Better User Experience: Ensures CircuitVerse works smoothly across all browsers and devices. 🌐
• Easier Contributions: New developers can focus on features instead of manually testing. 🧑‍💻
• More Trust: A stable and reliable platform encourages more users to adopt CircuitVerse. 🤝

💪 Why Am I the Right Person for This?

I have experience working with Playwright and have contributed to various organizations, including testing-related PRs. Here are a few examples of my work:

1. Migrated a codebase from Cypress to Playwright (2600+ lines)
2. Fixed Playwright tests for JupyterLab operators
3. Added tests for Python keywords
4. Added tests for expanding cells in JupyterLab
5. Additionally:

• I understand CircuitVerse: I have used the platform and know how crucial it is for learning digital logic. 🛠️
• I’ll keep everyone updated: Regular progress reports and feedback loops will keep this on track. 📢
• I want to help the community: A more reliable CircuitVerse benefits students, educators, and developers alike! 🌟
• ⏳ Expected Time Commitment: (300–350 hours)

Let me know if you'd like me to open a pull request and start integrating Playwright! If you like this idea, consider it for GSoC 2025! 😊 If you’re interested in my work, I’d love to start integrating Playwright right away and continue fully implementing E2E testing during the GSoC period as well. 🚀

[naman9271]

@VaibhavUpreti

🏗️ GSoC 2025 Proposal: Modernizing CircuitVerse\CircuitVerse with TypeScript

📌 Personal Information

Name: Naman Jain
GitHub/Portfolio: My GitHub
Email: My Email
Time Commitment: 275-350 hours

---

🚀 Project Overview

Title: Migrating CircuitVerse from JavaScript to TypeScript for Enhanced Reliability & Developer Experience

Synopsis:
CircuitVerse is an open-source platform for digital circuit simulations. However, its JavaScript-based architecture lacks type safety, leading to runtime bugs, inconsistent documentation, and onboarding challenges. This project proposes a phased migration to TypeScript to improve maintainability, reliability, and developer productivity.

Benefits to the Community:

• Fewer Bugs: TypeScript catches 50%+ of common runtime errors at compile-time.
• Better Developer Experience: Enhanced IntelliSense, autocomplete, and self-updating inline documentation.
• Faster Contributions: Reduced onboarding time for new developers.
• Improved Maintainability: Strongly typed APIs prevent unintended behavior.

---

🔍 Problem Statement

The current JavaScript-based CircuitVerse faces several challenges:

• Runtime Errors: Lack of static type checking leads to unexpected crashes.
• Unclear API Contracts: Complex objects like CircuitElement, Simulation, and Gate have implicit structures.
• Hard-to-Maintain Codebase: JSDoc comments often become outdated.
• Difficult Refactoring: Large-scale changes require manual checks.
• Limited IDE Support: No proper autocompletion for deeply nested objects.

By migrating CircuitVerse to TypeScript, we can address these issues and future-proof the library.

---

🔧 Proposed Solution

Why TypeScript?

TypeScript brings the following advantages:

Feature	JavaScript	TypeScript
Error Detection	Runtime	Compile-Time
Auto-Completion	Limited	Context-Aware
Code Refactoring	Manual Checks	Automated
Onboarding Speed	Slow	Faster (Type Hints)

Key Improvements in CircuitVerse

• Strictly Typed Interfaces for core objects (CircuitElement, Wire, etc.).
• Type-Safe Event Handling with strongly defined callback parameters.
• Migration to TypeScript Modules with ES6+ syntax.
• Automatic Documentation using TypeDoc.
• Refactored API with Minimal any Usage (<5% any in final implementation).

---

📅 Timeline (300-350 hours)

Community Bonding (May 20 - June 17, 2025)

• Get familiar with CircuitVerse’s codebase and maintainers.
• Discuss migration strategy with mentors.
• Identify core modules that need urgent type definitions.

Phase 1: Foundational Setup (June 17 - July 7, 2025) [~50 hours]

• Add tsconfig.json with strict type-checking.
• Convert essential configuration files:
  • webpack.config.js → webpack.config.ts
  • jest.config.js → jest.config.ts
• Set up TypeScript compilation workflow.

Phase 2: Core Module Migration (July 8 - July 28, 2025) [~120 hours]

• Migrate core CircuitVerse modules:
  • CircuitElement
  • Wire
  • Simulation
• Define TypeScript interfaces for event listeners and API responses.
• Replace implicit any types with strict interfaces.
• Validate TypeScript integration with unit tests.

Phase 3: Expanding Type Coverage (July 29 - August 18, 2025) [~100 hours]

• Convert utility functions and smaller modules.
• Improve type safety for API requests and responses.
• Implement stricter TypeScript settings (strictNullChecks, noUncheckedIndexedAccess).
• Conduct performance tests to ensure TypeScript doesn’t introduce regressions.

Phase 4: Final Review & Documentation (August 19 - August 26, 2025) [~50 hours]

• Write TypeScript contribution guidelines for maintainers.
• Generate API documentation using TypeDoc.
• Conduct extensive testing and fix any remaining issues.
• Submit final project report and discuss future steps.

---

📈 Expected Outcomes

✅ Fewer Bugs: Prevent runtime errors through static type checking.
✅ Faster Development: Autocomplete reduces lookup time by ~30%.
✅ Improved Documentation: Type definitions provide self-updating API documentation.
✅ Easier Contributions: Well-defined interfaces reduce onboarding time.

---

🔗 Deliverables

• Fully migrated CircuitVerse codebase to TypeScript.
• Updated documentation with TypeDoc.
• Type-safe event listeners and API interactions.
• Comprehensive test coverage for TypeScript code.
• Contribution guide for TypeScript usage in CircuitVerse.

---

🛠️ Technical Details

• Programming Languages: TypeScript, JavaScript
• Build Tools: Webpack, Babel
• Testing Frameworks: Jest, tsd (for type tests)
• Documentation: TypeDoc, JSDoc

---

🤝 Collaboration & Community Engagement

• Regular updates via CircuitVerse’s GitHub discussions.
• Weekly check-ins with mentors for feedback.
• Writing a blog post on lessons learned from TypeScript migration.

---

👨‍💻 About Me

I am a passionate developer with experience in JavaScript, TypeScript, and open-source contributions. My past work includes migrating JavaScript projects to TypeScript and optimizing build systems for large-scale applications.

---

📌 Why Me?

✅ Experience in TypeScript migrations.
✅ Strong understanding of circuit simulation and educational platforms.
✅ Active open-source contributor.
✅ Committed to delivering high-quality, maintainable code.

---

📢 Final Words

Migrating CircuitVerse to TypeScript will significantly improve its stability, developer experience, and long-term maintainability. I am eager to contribute to CircuitVerse’s ecosystem and make CircuitVerse more robust for future developments. Looking forward to feedback from the community and mentors! 🚀

[Neerajpathak07]

@naman9271 Apparently this discussion was made to discuss upon Project Ideas which could possibly be implemented in GSoC this year.
But Ig you have entered your Proposal for that project which might be derailing the purpose of this thread.
However, you could add how the project is going to change CircuitVerse and what all changes could be done to enhance the User Experience along with handling the bugs along the way.

[rxiddhi]

Purpose: Making CircuitVerse More Beginner-Friendly with AI

I am Riddhi Khera, passionate about making technology more accessible and intuitive, especially in the field of digital design and web development. With experience in web technologies and an interest in AI-driven solutions, I enjoy building tools that simplify complex tasks.
For CircuitVerse, I want to contribute by integrating an AI-powered chatbot that helps users navigate tools easily, debug circuits efficiently, and learn interactively. This will make the platform more beginner-friendly and enhance the overall user experience.
I believe that small yet meaningful improvements can have a big impact, and I’m excited to collaborate and refine this idea further with the community!

How Can This Help CircuitVerse?
An AI-powered chatbot can bridge this gap by providing real-time guidance, tool navigation, and troubleshooting support, making CircuitVerse more user-friendly, efficient, and accessible to both students and professionals.

Objective
To develop an interactive chatbot that assists CircuitVerse users by:
=> Providing step-by-step guidance on using different tools.
=> Helping debug circuits by identifying common errors and suggesting fixes.
=> Offering real-time assistance for circuit design and simulation.
=> Enhancing user experience by making tool navigation seamless.

Key Features
* Smart Tool Navigation:
Users can ask the chatbot how to find and use specific tools instead of manually searching.
Example: "How do I add a multiplexer?" → The bot provides instructions or highlights the option.

* Real-Time Debugging Assistance:
Detects common circuit errors and suggests corrections.
Example: "Your AND gate input is floating. Connect it to a logic level."

* Interactive Learning Support:
Provides explanations of digital circuit concepts.
Suggests tutorials and documentation based on user queries.

* Voice & Text Input:
Allows users to interact with the bot via text or voice commands for better accessibility.

* Personalized Learning Suggestions:
Recommends tutorials, community discussions, and templates based on user needs.

* Integration with the CircuitVerse Community:
Connects users to relevant forum posts, video tutorials, and documentation for deeper learning.

[gitsofaryan]

Real-time Collaborative Circuit Editing for CircuitVerse

Overview

CircuitVerse allows users to design and simulate circuits, but it doesn't support collaborative editing. This project aims to introduce real-time multi-user editing for circuits, similar to how Google Docs allows multiple users to edit documents simultaneously. The plan is to use WebSockets (Socket.io/Firebase) and ActionCable (Rails' WebSocket framework) for quick, low-latency updates. By integrating WebRTC, we can enhance performance by reducing server load through peer-to-peer connections. This feature will improve collaboration for both students and professionals working on circuit designs.

---

Prerequisites

JavaScript : Strong knowledge of modern JavaScript and web development practices.

Real-Time Technologies: Experience with WebSockets (e.g., Socket.io, Firebase) and WebRTC for real-time, peer-to-peer communications.

Ruby on Rails Proficiency: Familiarity with Rails, particularly ActionCable for WebSocket integration.

CircuitVerse Familiarity: Basic understanding of the CircuitVerse platform and its functionalities.

---

Project Expected Timeline (8 Weeks)

Phase	Tasks	Timeframe
Week 1	Study the CircuitVerse architecture and research WebSockets, WebRTC, and ActionCable.	1 week
Week 2-3	Implement real-time synchronization using Socket.io & ActionCable for basic collaboration features.	2 weeks
Week 4	Integrate WebRTC to enable peer-to-peer connections and reduce reliance on servers.	1 week
Week 5	Add version control and conflict resolution tools (snapshot-based versioning, component locking).	1 week
Week 6	Develop Undo/Redo functionality and add features like live cursors and a chat panel.	1 week
Week 7	Optimize for larger teams, address any performance issues, and refine the overall experience.	1 week
Week 8	Conduct final testing, write documentation, and deploy the solution.	1 week

✅ Total Duration: 8 weeks (175 hours)

---

Difficulty

🟠 Medium

---

Expected Mentors

👨‍🏫 Aboobacker MK (GitHub)
👨‍🏫 Vedant Jain (GitHub)

---

PS : #5110 #5111

[091vk]

GSOC ML based Ideas :

1.Semantic Search

What ?

A semantic search system for circuits in CircuitVerse could allow users to describe what they want their circuit to do in natural language, and the system would either:

• 1.Find existing circuits that match the description and performs the functions described by the user or
• 2.Provide step-by-step guidance on how to design the circuit.

Tech Stack & Implementation Plan

• NLU & Query Processing: DeepSeek , or fine-tuned BERT for understanding circuit-related queries.
• Circuit Representation: Vector embeddings or structural embeddings for circuit data .
• Search Engine: FAISS/Milvus/Pinecone for similarity search.
• Backend: Python (FastAPI/Django/Flask) for API handling.
• Frontend: Integrated into CircuitVerse UI for seamless experience.

2.AI-Driven Learning & Tutoring for Personalized Learning :

What ?

The aim of CV is to teach digital design , their are proposals for implementing learning games and paths for users to learn digital designing of circuits. The proposal is to implement :

• 1.Leaning paths or learning games that will include verilog and circuit design
• 2.Anylases for users which area they are weak and creating a personalised path for them to improve
• 3.Ai based tutoring , by adjusting difficulties of games based on user data , and use of ai driven content recommendation
• 4.Other immersive techniques to enchance gamification of CV

[salmoneatenbybear]

RTL Viewer (Register Transfer Level Visualization)

Problem: Users working on complex circuits (e.g., CPUs, ALUs) struggle with abstraction.

Solution: Develop an RTL (Register Transfer Level) visualization mode, which:

• Shows data flow between registers and logic gates.

• Helps users see how signals propagate.

• Useful for advanced topics like pipelining and finite state machines.

Cc : @091vk

[092vk]

Yeah this is a must have👍

[Saahi30]

RTL visualization mode sounds like a great way to simplify complex circuit analysis by showing data flow between registers and logic gates!
This could be super helpful for understanding pipelining and FSMs.

I was also wondering whether real-time visualization could also be an option to add, or would it be too heavy on performance?

[salmoneatenbybear]

MyHDL Export for CircuitVerse

Idea: Add support for exporting CircuitVerse circuits to MyHDL (Python-based HDL), allowing users to simulate digital designs in Python and later convert them to Verilog/VHDL if needed.

Cc : @091vk

Why?

• MyHDL is easier to learn than Verilog, making it great for education.
• Users can test and debug circuits in Python before deploying to FPGA/ASIC.
• Python-based simulation avoids the need for complex toolchains.

Implementation Approach:

1. Modify the export feature to support MyHDL generation.
2. Convert CircuitVerse components (gates, flip-flops, multiplexers, etc.) into equivalent MyHDL code.
3. Allow users to download the generated Python file for simulation.

Example Output:
A simple AND gate in MyHDL could be exported as:

from myhdl import block, always_comb, Signal

@block
def and_gate(a, b, y):
    @always_comb
    def logic():
        y.next = a & b
    return logic

[DarkPheonix12]

🛠️ SPICE-Based Analog & Mixed-Signal (AMS) Simulation Support

🔹 Why?

Currently, CircuitVerse is digital-only. Industry tools like Cadence Virtuoso support analog, digital, and mixed-signal simulations using SPICE models.
Adding SPICE simulation will move CircuitVerse from an educational tool to a professional-grade circuit design platform.

🔹 Implementation Plan

• SPICE Engine Integration: Use Ngspice (open-source) or interface with Xyce for scalable circuit analysis.
• Analog Component Support: Introduce resistors, capacitors, inductors, diodes, and transistors with proper SPICE models.
• Mixed-Signal Simulation: Enable co-simulation between SPICE-based analog components and digital logic.
• Waveform Viewer: A high-resolution, interactive signal plotter (similar to Virtuoso’s Analog Design Environment).

🔹 Impact

✔️ Enables analog & mixed-signal circuit design, making CircuitVerse a competitor to Cadence PSPICE & LTSpice.
✔️ Bridges the gap between academia & industry, as professionals rely heavily on SPICE simulations.
✔️ Opens up FPGA/ASIC prototyping workflows by allowing pre-synthesis verification.

📊 Interactive Graphical Data for Circuit Analysis

🔹 Why?

Currently, CircuitVerse does not provide advanced graphical data visualization for circuit behavior, aside from basic logic simulation outputs.
It primarily focuses on digital circuit simulation, where you can see how signals propagate through logic gates. However, it lacks:

✅ Waveform Graphing (like oscilloscopes in Cadence, ModelSim, or LTSpice)
✅ Voltage/Current Graphs for Analog Components
✅ Timing Analysis (Propagation Delays, Setup/Hold Times)
✅ Signal Integrity Visualization (e.g., glitches, race conditions)

🔹 Potential Feature

To move CircuitVerse toward industry-standard EDA tools, adding graphical data analysis would be a major step. This could include:

• Logic Analyzer View: A real-time waveform viewer for digital circuits (like in ModelSim).
• Voltage/Current Graphs: Useful if CircuitVerse expands to SPICE-based analog/mixed-signal simulation.
• Timing Diagram Generator: Display propagation delay, setup/hold times, and glitches to debug digital circuits.
• Signal Correlation Heatmaps: Helps users analyze dependencies between circuit components.

🔹 Impact

✔️ Provides better circuit debugging by visualizing waveforms, timing, and signal behavior.
✔️ Enhances simulation capabilities, making CircuitVerse more powerful for academic & professional use.
✔️ Bridges the gap between educational tools & professional-grade EDA software.

🚀 Why I Am the Perfect Person for This Contribution

Bringing CircuitVerse closer to industry-standard EDA tools like Cadence isn't just an idea for me—it's a vision I am passionate about.
With my strong technical background, industry experience, and coding expertise, I believe I am uniquely positioned to bring this transformation to life.

🔹 1 Year of Hands-On Cadence Experience

I have one year of experience working with Cadence, which means I understand the professional workflow that real engineers use in VLSI design.
I have worked with circuit simulation, layout design, and timing analysis, giving me first-hand exposure to the features that make industry tools powerful.

🔹 Strong VLSI & Circuit Design Foundation

VLSI design wasn’t just a subject in my curriculum—it was something I dove deep into.
I have a solid grasp of digital logic, analog circuits, and mixed-signal design, making me well-equipped to understand both the theoretical and practical aspects of EDA tools.

🔹 Expert in Coding & Logic Building

My strong programming skills allow me to implement complex simulations and graphical analysis tools efficiently.
I am comfortable working with data structures, algorithms, and backend/frontend development, meaning I can design, optimize, and integrate the proposed features seamlessly.

🔹 Problem-Solver with a Vision

I don't just write code—I solve real problems.
I have an eye for optimization, a passion for debugging, and a mindset that focuses on building scalable and efficient solutions.
My ability to analyze workflows and identify missing industry-standard features makes me an asset to this project.

🔹 Enthusiastic Contributor & Team Player

I love open-source development, collaborating with teams, and contributing to projects that make a real impact.
I thrive in fast-paced, innovative environments and am always eager to learn, adapt, and push boundaries to make technology better.

[092vk]

Analog and mixed signal is not supported by CV , so connecting or generating netlist for Spice is not useful .

[DarkPheonix12]

Okay, if we are not extending in that direction that would not be appropriate.
But what about enhancing the graphical output of circuit like Cadence does?

[salmoneatenbybear]

We can continue the idea from previous GSOC

Weekly contest sprint to prod

We focus on assimilation of weekly contest into circuitverse pour efforts into making it a regular and thriving thing. Think of making it better and more enriched...

Cc : @Asrani-Aman @tachyons @vedant-jain03 @VaibhavUpreti @Arnabdaz

Stem issue : #4956

Current progress : #5322

[Asrani-Aman]

Yes @salmoneatenbybear we have included this in the GSoC2025 project list

[Himanshu-kiran]

@Asrani-Aman How can we see GSOC25 all projects list?

[salmoneatenbybear]

Instantiate Visual Regression testing with Percy.

Using config made in : #5266

[Himanshu-kiran]

Image to digital circuit using AI/ML (object detection models , OCR etc)
=>Image means converting our notebook handwritten circuit into digital one.

[Himanshu-kiran]

@salmoneatenbybear No, I don't have datasets for training. I was hoping someone might gather dataset. And, I posted this for other as I have only fundamental knowledge of traditional models.

[salmoneatenbybear]

This is a very complex problem to solve, it's tough to build even simple English handwriting recognition models. This would be a really hard model to build... I have some experience in this domain

[salmoneatenbybear]

Also I searched kaggle. No such datasets available... Making one would be a time intensive task...

[092vk]

Also it becomes difficult to identify when drawn with hand , some people make the curve of or gate not that curve , it looks like and gate only . We would need a highly accurate model for that , also issue of lighting.

[Himanshu-kiran]

Yes that would be really difficult.

[DarkPheonix12]

Interactive Waveform Viewer & Logic Analyzer

🔹 Why?
Currently, CircuitVerse only provides basic truth table and logic visualization, but real engineers use waveform analysis to debug circuits. Adding an interactive logic analyzer will make CircuitVerse much more powerful.

🔹 Proposed Features:
✅ Waveform Graphing – Show real-time digital signals (like ModelSim & Verilog Simulators).
✅ Edge Detection – Highlight rising/falling edges for better debugging.
✅ Bus Signal Grouping – Combine multiple signals (e.g., address/data buses).
✅ Triggering & Markers – Allow users to set conditions for capturing specific events.

🔹 Impact:
✔ Makes circuit debugging more intuitive.
✔ Prepares students for FPGA/ASIC workflows.
✔ Moves CircuitVerse closer to professional simulation tools.

[salmoneatenbybear]

#5397

CC : @Asrani-Aman @tachyons @gr455 @Arnabdaz

I think we can include this in project 1 for adding testbench support for the Output components.

[Devika-A029]

Hi everyone! I'm a second-year Applied Electronics and Instrumentation student with a strong interest in embedded systems and microcontrollers. I would love to propose a project idea for GSoC 2025:

Project Title: Embedded Systems Simulation Framework (Digital-Only)

Objective: Develop a web-based simulation framework that allows users to test microcontroller code without physical hardware. It will focus on GPIO, digital communication protocols (I2C, SPI, UART), and simple peripherals like LEDs and buttons.

Approach:

Implement virtual microcontrollers (ATmega328, ESP32, etc.)
Provide digital peripherals for interaction
Support debugging of embedded C/C++ code
Web-based execution using WebAssembly
This will help students and developers prototype and debug embedded applications more easily. I'd love to hear your thoughts and suggestions!

[855princekumar]

Hi everyone,

The idea of integrating comprehensive IoT simulation into CircuitVerse is highly valuable. Coming from an IoT and embedded systems background, I see enormous potential in providing learners and educators the tools to visually simulate and interactively explore real-world IoT scenarios within the CircuitVerse platform. This approach could significantly enhance hands-on learning and bridge theoretical concepts with practical application. I'd love to discuss this further and hear your thoughts!

[Vivek-1102]

Whats up guys Vivek here and i am hear to be a part of the Gsoc 25

[its-pratyushpandey]

These are fantastic ideas! The HIL simulation and quantum circuit support could truly expand CircuitVerse's educational reach. Also, shifting to Web Workers for parallelism sounds like a smart move for performance and scalability. Excited to see how these evolve for GSoC 2025! 🚀

[Aditya30ag]

@Devika-A029 - Your "Embedded Systems Simulation Framework" proposal is excellent and aligns well with CircuitVerse's educational mission. The focus on digital-only simulation with virtual microcontrollers (ATmega328, ESP32) and WebAssembly execution could make embedded systems learning more accessible. This would be particularly valuable for students who don't have access to physical hardware.

[Aditya30ag]

@855princekumar - Your insights on IoT simulation integration are spot-on. The potential to bridge theoretical concepts with practical application through visual simulation could significantly enhance the learning experience. Your background in IoT and embedded systems would be valuable for this type of project.