Fetching the latest programs, projects, and workspace data.
Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
Blender currently supports exporting MaterialX within USD, but lacks meaningful support for authoring or executing MaterialX-standard shader graphs natively. This project aims to introduce the MaterialX standard node library into Blender's shader editor as first-class native nodes. A working execution prototype through Cycles' OSL backend will serve as the secondary deliverable, enabling round-trip evaluation of authored graphs during the project timeframe. Adding this feature to Blender will make it easier for 3D assets to interoperate with other DCCs, and will make Cycles a great candidate as the reference renderer for MaterialX.
<ul> <li>Merging of MSUI and MSColab windows for a more intuitive workflow, since both the windows share some core functionalities. My proposal includes,<ul> <li>Redesigning and Implementation of the new UI</li> <li>Migrating MSColab features to the new window</li> <li>Refactoring core-logic</li> <li>New profile page for the users</li> </ul> </li> <li>Design and implementation of new configuration editor. Since MSS uses json files for storing configurations, it requires the user to have a prior knowledge about the json syntax. With the proposed configuration editor the user can solely focus on modifying, adding, deleting configurations.</li> </ul>
<p>The project consists of implementing in Scipy an interior-point method for nonlinear problems. The main goal is to implement a constrained optimization algorithm able to deal with a large (and possibly sparse) problems for which the constrained optimization methods currently implemented in Scipy (namely SLSQP and COBYLA) are largely inappro- priate to deal with. Implement benchmark problems and integrate quasi-Newton (namely BFGS, SR1 and L-BFGS) and finite differences (using graph coloring schemes to deal with sparse structures) approximations to the method are also part of the project.</p>
The project aims to modernize and enhance the functionality and performance of DIPY (Diffusion Imaging in Python), a library for the analysis of diffusion magnetic resonance imaging (dMRI) data. The focus is on making key improvements across several areas to ensure the tool remains a cutting-edge resource for scientific visualization within the Python community. Here's a concise overview: Problem Addressed: The project addresses the need for improved code robustness, performance optimization, and user experience in DIPY. Specific challenges include the current lack of keyword-only arguments in functions, inefficient resource loading, bulky website management, and the need for better documentation and learning resources. Deliverable with approach: 1. Keyword-Only Arguments: Audit and refactor functions to use keyword-only arguments for clearer, more robust code. 2. Lazy Loading: Implement lazy loading to optimize performance by loading resources on-demand. 3. Website Management Improvement: Work with mentors to identify and implement enhancements for easier website management. 4. GitHub Actions Integration: Automate development workflows with GitHub Actions to improve efficiency and reduce errors. 5. Issues and Pull Requests Triage Automation: Enhance and automate the triage process for better project management. 6. Refactoring and Documentation: Refactor DIPY packages for improved readability and maintainability, and enhance docstrings for better documentation. 7. Tutorials Addition: Create new tutorials based on community feedback and identified learning gaps to facilitate user adoption and learning.
This project adds a Sample Sound node that retrieves audio from sound files, and provides their frequency response over time for use in Geometry Nodes. It will primarily be based on Audaspace—Blender's all-purpose audio engine—for its actual functionalities. The following deliverables are expected: 1. Sample Sound node; 2. Sound socket type; 3. Sound input node; 4. Series of examples and documentation.
The project will involve updating the database schema to accommodate EPSS data, adding EPSS data to the database through download in CSV format and parsing it for each CVE, updating database queries to retrieve EPSS data, and updating output reports to include EPSS data. The project will also include adding extra CLI commands to filter EPSS scores and updating documentation and tests to reflect the new changes. Overall, the integration of EPSS will enhance the precision and reliability of the CVE-BIN-TOOL, allowing users to better understand the severity of vulnerabilities and prioritize their remediation efforts. This is an overview of the tasks for this project: Update database schema Add EPSS to the database Update output reports to include EPSS data Add extra CLI commands to filter EPSS scores Update documentation and tests
This proposal aims to enhance CVE-BIN-TOOL by integrating support for different VEX triage functionality. The problem at hand is the limited scope of CVE-BIN-TOOL, which currently lacks extended VEX integration, hindering its ability to provide a holistic risk assessment. The solution involves refactoring the current workflow, implementing support for various VEX formats (such as CSAF, OpenVex, and CycloneDX), establishing linkages between SBOMs and VEX formats, and updating documentation and tests for usability. Through this project, we aim to provide cybersecurity professionals with a comprehensive tool for identifying and mitigating vulnerabilities effectively. The deliverables include a refined workflow, support for multiple VEX formats, documented linkage mechanisms, and updated documentation and tests.
<p>Machine learning datasets are often continuously modified yet there is no efficient way to determine if two datasets are the same. This challenge becomes problematic when the datasets are large (20 GB+) and cannot be easily loaded into memory.</p> <p>This project intends to use Locality Sensitive Hashing (LSH) with the MapReduce paradigm to compare large scale, out of core machine learning datasets.</p>
<p>The main objective of this project is to create such interfaces (by the means of various visualizations of the library) that makes it easier for user to:</p> <ul> <li>Access the required filter curves</li> <li>Calculate the photometry of a star's spectrum under a certain filter set</li> </ul> <p>To achieve this, I propose to develop several adequate visualizations by enabling interactivity and UI controls, such that they serve as <strong>analytical web interfaces</strong> through which user can access what they need in a couple of clicks! These interfaces will be made accessible to the user by integrating them within living Sphinx docs, such that they will be auto generated when building the docs.</p> <p>Besides, I also aim to well document the wsynphot package after integrating the developed interfaces in it, ultimately reshaping the entire package. Hence, user can <em>auto-generate both the filter curves & photometry</em> directly from the docs as per their requirements, by using these responsive interfaces.</p>
<p>Pythran is an ahead of time compiler that takes advantage of SIMD instructions to speed up Python code. Currently, in SciPy, there are many algorithms that are too slow as pure Python and could be accelerated via Pythran. Therefore, this project aims to identify such algorithms and use Pythran to improve their performance. Moreover, there are many function in SciPy don't have benchmarks yet, so writing new benchmarks is also included in this project.</p>
<p>The current Python's development process is very complicated for core developers. When an external contributor uploads a patch for a certain issue, the core developer needs to download the patch and then apply the patch and run the tests manually to make sure it works properly. Also, the core developers review the code on the forked version of Rietveld code review tool which is not being maintained. Once the patch is correct, the changes are committed manually. This is a manual and burdensome process for core developers. On <a href="https://mail.python.org/pipermail/core-workflow/2016-January/000345.html" target="_blank">1st January 2016</a>, Brett Cannon decided to migrate from Mercurial on hg.python.org to Git on GitHub.</p> <p>So, my project is about migrating to Git/Github. I will be working on creating pull requests on Github whenever a patch is submitted on the issue tracker (<a href="https://bugs.python.org" target="_blank">https://bugs.python.org</a>) and integrating various bots to maintain linear history of commits, auto-close of issues, enforce CLA, etc. Towards the end of the GSoC period, I will work on patch-related improvements.</p>
The Goal of this project is to add the functionality to import and export OpenTimelineIO (.otio) files in Blender. OpenTimelineIO is an open-source interchange format and C++ API that represents an editorial cut as a structured, JSON-serialized object graph carrying precise cut information, media references, markers, transitions, and effects across non-linear editors (NLEs). With the ability to import and export .otio files in Blender, the artists would be able to work using different softwares on the same timeline keeping Blender in their production pipeline.
The project aims to significantly enhance the user interface of the Mission Support System (MSS) - MSUI - by implementing a comprehensive set of usability and functionality improvements, tailored to streamline user interaction and optimize the overall user experience. This project will focus on several areas of UI enhancement, which would include : 1. Integrating small user images for personalized login and chat experiences. 2. Implementing real-time visualization of concurrent users working on an operation. 3. Enhancing chat functionality by adding a server message channel.
<p>For the project I propose working on creating a base class for the equations of motion generators in the physics module of the sympy library and add a Newton-Euler equation of motion generator. The benefits of creating a base class for equations of motion generators would include ease of adding additional equations of motion generators and making the code more compact and so speed enhancements and bug fixes will affect all generators simultaneously rather than having to be implemented on a per generator basis. In addition to this work I would also be working on increasing the speed/efficiency of the existing python code for the equations of motion generators since I will already be digging into their base functionality.</p>
This project aims to add enhancements, solve issues and improve the user interface of the Python Software Foundation GSoC Blog platform. Currently, there are several issues listed on the issue tracker of the PSF GSoC Blog. This project aims to solve those issues and improve the usability of the blog platform for admins and students.
<p>This project aims at improving certain existing UV editor tools and also adding some new features to better support workflows involving UDIM textures. Operations such as packing selected UV islands will be improved and new features for grid snapping will be added to the UV Editor.</p>
<p>Today, many fields of computational sciences (Data Science, Data Visualization and even Machine Learning), mathematics, engineering, geology and others make use of matrices. Usually described from tables, it is a central tool used by many programming languages. A tensor is a generalization of vectors and matrices and is easily understood as a multidimensional array. In the PolyMath project (a Pharo project that implements numerous mathematical algorithms), there is already a support for vectors (tensors with rank 1) and matrices (tensors with rank 2), but not general multi-dimensional matrices (aka tensors). The main objective of this project is to extend the existing PolyMath classes to support tensors and related operations.</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>This proposal is based on description of Plyer, one of the sister projects provided by Kivy Organization. The goal of the project will be to extend the support of currently existing APIs for other platforms and provide new stable and platform independent APIs to the users for allowing them to access the features of their desktop and mobile devices.</p>
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>Liquids and smoke are both fluids and share properties. It therefore makes sense to have one single fluid solver in Blender which handles all fluid simulations.</p> <p>In this project I plan to add liquid simulations to the existing Mantaflow (smoke) integration. More specifically, I would like to achieve the same functionality from the Elbeem code base with Mantaflow. Besides smaller Mantaflow specific features, the novel NB FLIP will be implemented as well.</p>
<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>
Pwndbg’s codebase is incosistent and (only partially) structured. The goal of the project, is to "clean" the codebase, by enforcing stricter linting, refactoring code, splitting large files/modules into smaller parts, and adding standardized logging and wrappers. Deliverables: cleaner structure, improved readability, reusable utilities, and documented conventions
<p>This project is aimed to provide a fixed point compiler backend for the <code>fixbv</code> type defined in <a href="http://dev.myhdl.org/meps/mep-111.html" target="_blank">MEP-111</a> of MyHDL project.</p> <p>When the project finishes, MyHDL should have a complete implementation of <code>fixbv</code> and its compiler backend with complete documentation, include tutorials and reference.</p>