Explore Projects

Pharo is a powerful object-oriented programming language widely used in research and industry, as seen here. The graph algorithms library in PharoAI is a crucial resource for developers who work with graph data structures. The current graph algorithms library in PharoAI needs a redesign of APIs and the addition of different algorithms in the library. The goal of this project is to redesign the graph algorithms library in PharoAI by 1. Redesigning the current API using the standard API Practices 2. Incorporating graPharo Layout Algorithms into PharoAI graph algorithms 3. I also plan to incorporate new graph algorithms and layout techniques and Data Structures to improve the library's performance and functionality of current algorithms.

<p>The broad idea is to develop widgets from scratch over the existing DIPY elements, which allow interaction with these elements. These futuristic widgets will be built on VTK directly without using external libraries like Qt or GTK. The idea is to enhance the user experience in a unique way - by bringing interactions closer to the elements themselves.</p>

<p>This project aims to design and implement support for encrypted mailing lists into GNU Mailman using PGP/MIME and GNUPG.</p>

Blender's video sequence editor currently contains a number of "papercuts", or isolated frustrations that can degrade the overall experience and dissuade new users. I intend to implement a wide variety of changes to the video sequencer that I believe will improve UX and promote open-source video editing as a whole, including snapping support for the preview window and marker snapping in the sequencer, options to link or unlink strips, and adding "active" channels to make pasting more intuitive.

<p>The project PyAfipWs under Python Argentina(PyAr) is a library for Developers &amp; tools for accountants and SMEs.PyAfipWs contains Python modules to operate with web services regarding AFIP and other government agencies, mainly related to electronic invoicing, several taxes and traceability.About the project - : The idea is to merge back changes from previous GSoC, convert to UTF-8 &amp; fix encoding issues, add unit tests with upto 85% coverage, convert scripts into python entry points, resolving problems arising in setup.py , support for dbf tables, xml, xls sheets and possibly other libraries, integration &amp; deployment with github actions to upload to pypi automatically and use of pytest VCR for unit test.These are all things that would help in the development of the project.</p>

My project aims to enhance the PyAfipWs project under the Python Argentina (PyAr) organization, focusing on two main objectives: significantly improving test coverage, followed by implementing documentation using Sphinx and refining GitHub Actions workflows. Additionally, if time permits, I aim to build a simulator for key AFIP web services using Python and Flask. Problem Statement: PyAfipWs currently faces dependency conflicts, lacks extensive test coverage, comprehensive documentation, and efficient GitHub Actions workflows. These issues hinder development, reliability, and collaboration within the project. Proposed Solution: Dependency Conflict Resolution: I'll address conflicts with pysimplesoap to ensure seamless integration and operation. Test Coverage Enhancement: Will add comprehensive unit tests for key modules such as wsfev1.py, utils.py, padron.py, and others, aiming for close to 100% coverage. Documentation Implementation: Utilizing Sphinx, I will create detailed usage guides, API references, and contribution guidelines, ensuring clarity and accessibility for developers. GitHub Actions Workflow Improvement: l will also work to enhance workflows by adding linting, type checking, and test automation, along with implementing PR automation for reviewer assignment and auto-merging. Simulator Development (if time permits): A Flask-based simulator mimicking AFIP web service endpoints will be built, facilitating controlled testing environments and streamlining development. Deliverables: Resolve dependency conflicts and initial Pull Requests addressing the issue. Implementing Extensive unit tests for key modules, along with Pull Requests showcasing high test coverage. Completing Sphinx documentation framework integrated with GitHub Actions for automated updates. Enhancing GitHub Actions workflows covering linting, testing, and PR automation, reflected in Pull Requests.

<p>Mission Support System is a flight planning software which a researcher can use to analyze predicted atmospheric data, and plan a flight-path with 3D way-points. The software in the present state allows editing by a single user per flight-path. To share this work, one has to export the work as a <code>$name.ftml</code> file and send it to other researchers for further planning. This back and forth communication not only consumes a lot of human efforts and time, but also can be frustrating when the number of researchers involved in a project is bigger, say &gt;=3.</p> <p>I propose a solution to this problem, the development of <code>Mscollab</code> which stands for "Mission Support Collaboration". <code>Mscollab</code> server would facilitate <em>real-time</em>, <em>collaborated</em> editing of flight-paths by <em>authorized</em> users. By design, it will also provide a chat facility for the users who are collaborating on the project. Its UI would be a part of <code>msui</code>, the core User Interface module of <code>mss</code>. It would additionally provide insights about temporal changes related to waypoints and the users who created them, for analytics purpose. <code>Mscollab-server</code> will be a standalone server built with Python, Flask, and python-socketio.</p>

<p>Its about moving mercurial to work in Python3. Rather than 2to3 support, it will work on both 2 and 3.</p>

Currently, LPython does not have full implementations of data structures such as list, dict, set. The goal of this project is to improve support for partially implemented data structures, and implementing other data structures, along with useful algorithms. Further, these implementations would be benchmarked with equivalent ones in other language libraries, such as the C++ STL. I plan to cover these: - Add missing list functions - Improve dict by expanding the space of keys and values, and nested dictionaries - Create an implementation of set - Allow passing of data structures as function parameters and return values - Work on ordered and unordered variants of dict and set - Explore improvement of hashing functionality beyond linear-probing and chaining - Work on other data structures such as heap and trie

<p>The proposed project is to create a set of Python based tools for easier and efficient creation of Hypermedia driven REST-APIs.</p> <p>The other part is an application that simulates the movements of a flock of drones that have as objective to detect the presence of fires or abnormal heat spots in a given geographical area using an infrared sensors to demonstrate the capabilities of Hydrus and the Hydra Draft.</p>

<p>For a long time, the modifier system was the main way to procedurally generate and modify 3D data in Blender. While modifiers can be stacked to produce a large variety of results it has limited control over the flow of data. The Geometry Nodes system, introduced in version 2.92 of Blender allows the user to go way beyond these limitations by building complex processing graphs with an advanced attribute system that allows storing data into geometry to be available for later nodes in the graph to operate on. At the time of writing, only a small set of basic functionality is available as nodes. This project will port a selection of functionality from the old modifier system to the new nodes system, taking into account the atomic design, the attributes system, and the variety of geometry types it operates on.</p>

Documentation is not written or updated as much as it should be because the overhead is too great. This project aims on integrating existing tooling to provide an intuitive and accessible process to write and edit documentation. The implementation of this solution can be broken down into two phases: 1. Hotswapping page content for code editor 2. Generating pull requests based on content delta

**Pwndbg** is a debugger extension that enhances the debugging experience. It currently supports only GDB and LLDB on Linux and macOS. This project introduces Windows support for Pwndbg. Initially, only WinDbg will be supported, but a generic interface could enable support for other debuggers (GDB, LLDB, x64dbg, etc.). The goal is to bring Pwndbg enhancements to the WinDbg console — providing a similar experience to using it with GDB or LLDB. End users should be able to access all native WinDbg features while also using Pwndbg commands and context windows. The project leverages WinDbg’s `wdbgexts` or `DbgEng` to interface with Pwndbg. This requires either an RPC client-server protocol or native integration of Pwndbg on Windows. Pwndbg needs to hook into WinDbg states (registers, memory, etc.) and respond to all command calls from WinDbg.

<p>The goal of this project is to finish the implementation of the formal integral approach for generating spectra which was started during last years ESO Summer of Code in Space (SoCiS). The current implementation will be rewritten in C and features that enable the use of this method for popular configuration settings will be added. Lastly the whole method will be integrated fully into tardis by providing configuration options to control it.</p>

<p>Radiation is the transmission of energy in the form of waves or sub-atomic particles.In space missions the major concern is the particle radiation.Energetic particle radiation passing through human body could damage the cells or DNA causing an increased risk for cancer. Especially when out of Earth's magnetic field protection, astronaut's are exposed to ionizing radiation with doses in the range from 50 to 2,000 mSv(milli Sievert). The evidence of cancer risk from ionizing radiation is extensive for radiation doses that are above about 50 mSv. Hence it is important to forecast the radiation events and train crew members to tackle the issue of radiation effectively in simulated environments(Mars city project).</p> <p>The aim of the project is to build a reliable system(Tango server) to :</p> <p>1) Alert crew about the incoming SEP event if the radiation level is above the SWPC set threshold.</p> <p>2) Issue the “all - clear” signal once the event has passed Mars.</p>

<p>The aim of the project is to ease the process of creating a new Lint Bear, addressing the issue of linting files having embedded source code and provide command line interface improvements to existing coala application.</p> <p><a href="http://mr-karan.github.io/2016/08/13/coala-GSoC-2016-Summary.html" target="_blank">http://mr-karan.github.io/2016/08/13/coala-GSoC-2016-Summary.html</a></p>

<p>Collision detection is essential in a game engine. It is the reason you go bonkers playing Flappy Bird. However, it would be difficult and expensive to represent each object using its exact geometry, so a better idea would be to put those objects in bounding volumes or CollisionSolids. These CollisionSolids are mathematically defined, so by using "some math", a collision system would be able to detect their intersections with each other.</p> <p>Currently, Panda3D is missing 3 collision tests: parabola into box, parabola into inverse sphere, box into capsule. Here are some use cases that we've probably seen before:</p> <p>1) An Angry Bird hitting a box (parabola into box)</p> <p>2) Protecting the audience from a football in a spherical stadium (parabola into inverse sphere)</p> <p>3) Some box object hitting a player (box into capsule)</p> <p>My first goal would be to add these collision tests.</p> <p>My second goal would be to add another CollisionSolid named CollisionHeightfield. The idea is that we can represent heightfields using a grayscale image, with lighter (taller) and darker (lower) pixels. We can use this concept to efficiently deal with collisions in uneven terrain.</p>

<p>Provides a single clean interface to the different representations of 3D rotations (matrices, Euler angles, quaternions). Also supports many useful algorithms such as SLERP, uniform random sampling, and solutions to Wahba's problem</p>

The idea here is to provide both runtime support (preferably using the SymEngine library to provide the computation, as it is fast and robust) and compile time support (in ASR) to implement Symbolic Algorithms in LPython. The runtime operation could use the SymEngine library for LLVM, C and C++ backends. For Python backend, we can simply use SymPy itself. The algorithms would be implemented in the ASR code, which would make them independent of any specific frontend. Any frontend that uses the ASR code could then make use of the symbolic algorithms without having to reimplement them. LPython, in this case, would not implement the symbolic algorithms themselves, but would instead parse the syntax used by the SymPy library, which already has a rich set of symbolic algorithms, and use the ASR representation of these expressions to perform various operations. This would allow LPython to have powerful symbolic manipulation capabilities without having to reinvent the wheel.

<p>Currently, EOS delivers icons via a set of well-documented methods, which chiefly include EOS-Icons Package, CDN, or direct download of icons in SVG/PNG formats. This project will be based on developing an npm package that can deliver EOS Icons to its users as an independent component library and create a unified central system that will enable EOS to deliver its icons to various frameworks (e.g. React, Vue and Angular) independently. This npm package will be as lightweight as possible in order to reduce the load put on the browser (using the tree shaking approach), which will result in providing a much smoother workflow to the users. Creating a package of EOS Icons for React, Vue, and Angular frameworks will go a long way in having a more consistent user experience as well as boost capability to accommodate users who migrate from one framework to another.</p>

<p>I will be working on adding a new functionality to FURY which shall enable users to visualise various types of proteins via different representations like Richardson aka Ribbon diagrams and molecular surface diagrams. As a part of my stretch goals, I’d like to expand protein representations via other representations including -</p> <ul> <li>Stick</li> <li>Ball and stick</li> <li>Wire</li> <li>Pipes and Planks</li> <li>Sphere</li> </ul>

<p>The project aims to develop an interactive Heads up Display (HUD) on the OCULUS RIFT for the V-ERAS Simulation. Once the interactive semi-transparent interface is implemented on the existing V-ERAS simulation environment it should display data from the Habitat Monitoring Client. The Habitat Monitoring Client GUI is already in place. It can interface with any general Tango Device Server. A portion of the project will aim at making the HUD highly interactive and recognize touchless hand and body gestures through Leap Motion Controller.</p>

Currently, the CVE-BIN-TOOL supports basic VEX triage functionality but lacks user-friendly tools for editing, validating, and managing VEX data. VEX’s JSON-based structure, while machine-readable, it is error-prone for manual human interaction, which often leads to invalid files or incomplete triage information. This project aims to bridge this gap by working on cve-bin-tool’s VEX capabilities through these three key pillars: 1. Interactive HTML Reports: Embedding JavaScript-based editing interfaces to enable offline-compatible VEX triage with real-time validation. 2. CLI Automation: Developing tools for validation, guided generation, and archival of VEX files to minimize manual effort. 3. Standardized Maintenance: Integrating the lib4vex library to unify support for CSAF, OpenVEX, and CycloneDX formats while ensuring schema compliance. By simplifying VEX workflows, the project will allow developers to manage vulnerability context effectively, reduce their errors, and align with evolving security standards.