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.
Cyfra is a GPU runtime and a DSL that makes Scala a viable choice for GPU programming. Currently, the Scala ecosystem does not have an easy-to-use library for doing general computations on the GPU. Cyfra aims to fill this gap. Goal of the project is to implement support for GPU computations on data streams, with focus on usability, and integration with the popular fs2 (Functional Streams for Scala) library, which is used widely in the Scala ecosystem. Cyfra should enable developers that do not have background in GPU programming to write a simple data processing pipeline in Cyfra that performs compute on GPU and efficiently manages memory. The pipeline should be interoperable with fs2. Integrating Cyfra's pipeline with fs2 will also make it compatible with major Scala open source libraries, opening them up to execution on the GPU.
This project aims to expand the texor package by incorporating features to convert Sweave (.Rnw) files into R Markdown effectively, while preserving the integrity of executable code segments. This project holds the potential to greatly assist numerous R packages that currently utilize Sweave-based vignettes by facilitating their migration to R Markdown. A particular target of this project will be packages that have used the Journal of Statistical Software template to create package vignettes - there are over 200 such examples on CRAN. These articles are expected to be similar to R Journal articles in the sense of making heavy use of LaTeX markup for mathematics, algorithms, tables, etc, that would benefit from the functionality of texor. Therefore, outputs from this project could prove valuable to journals or authors that wish to produce HTML versions of articles created with Sweave.
Moving towards enforcing stricter types for the django backend endpoints by using @typed_endpoint decorator instead of the current @has_request_variables. Transitioning to pydantic's data validation provides much more flexibility with the availability of base models as well as different validators. Defining more coherent data classes and base models for complex parameters like 'narrow' will help improve the overall usage experience of these parameters in the entire codebase. Proposed Solution I would start by prioritizing the data driven endpoints, especially those involving authentication and user profile creation and updation as these endpoints deal with a lot of sensitive data and will benefit the most from data validation. My next focus would be the message endpoints because these endpoints deal with large amounts of traffic and need to have robust types in order to avoid any issues with sending/updating messages, their flags and reactions, etc. Switching the streams and dms over to @typed_endpoint will help better manage the streams and make them ready to easily implement the changes proposed in migrating Zulip’s direct message recipient data structures along with any other future plans for these sections. While migrating these endpoints, I will simultaneously add more robust test cases to test all the different data validators.
The problem we are trying to solve is, developers struggle to analyze massive CI test logs, especially for rare intermittent failures. This project tackles this by building a Haskell web tool. In phase 1, it leverages an existing service (spuriobot) to collect test log data and stores it in a full text search database. In Phase 2 we have three options to do, but we’ll try to work on all three. So Phase 2, focuses on improvements based in the web UI on user feedback. This UI will allow searching by keywords or test names, with clear results including timestamps and failure messages. Also, it will automatically insert logs from github workflows action. Last part includes spurious failure analysis, which utilizes the tool to analyze test log data in GHC to identify patterns and root causes of intermittent test failures (or characterizing spurious failures).
Direct interoperability between molecular dynamics software is critical for enabling collaboration, data transfer and easy use by scientists. OpenBabel is a popular toolbox for chemical molecular modelling as it enables searching, conversions, analysis and data storage. The ability to interconvert chemical file formats with OpenBabel, in particular, opens up the ability to utilise and work with other packages, as OpenBabel enables input and writing of over 100 chemical data file formats. Therefore, expanding to OpenBabel will hugely increase the ability of MDAnalysis to handle a variety of data formats and encourage greater adoption of MDAnalysis as an “all-in-one” package for molecular dynamics analysis. The converters already established in the MDAnalysis package for OpenMM, ParmED and RDKit either read coordinate files into their respective objects before using them to create a MDAnalysis Universe or convert Universes in the reverse direction. I plan to take a similar approach to these existing converters. I will utilise OpenBabel Python bindings to make my task of introducing interoperability much easier, since Python code in the MDAnalysis package can easily access OpenBabel attributes (as long as the user has installed OpenBabel in an appropriate directory). I will start with conversion of MDAnalysis AtomGroup objects to OpenBabel OBMol objects, then work on conversion in the reverse direction. This means access to alternative formats and file type export options will be prioritised. Then, I will create a second converter file to convert OpenBabel OBMols to MDAnalysis Topologies, or adds them to a pre-existing Topology.
Not only can clustering in itself be a useful task to solve, features learnt from deep clustering algorithms can also be used in downstream tasks such as sleep stage classification. Using an open dataset such as the Temple University Hospital EEG corpus, I plan to develop a method for Deep Clustering of EEG data based on autoencoders. Having previously worked with this dataset, I am familiar with it's processing and using the processed data for Transformer pretraining. In addition to this, I am also familiar with general signal processing as I am an Electrical Engineering Masters student. At the end of the program I would hope to have developed an opensource method which can be published and which can be finetuned for other downstream tasks.
I propose to enhance the AsyncAPI Preview and Spectral VS Code extension by adding an autofix feature for common Spectral linting errors. This project aims to improve developer efficiency by automating error corrections within AsyncAPI documents. Using VS Code’s APIs, the feature will identify errors, consult a detailed ruleset for applicable fixes, and apply these corrections directly in the editor. Key Deliverables: **Implementation of the Autofix Feature** Automatically corrects predefined linting errors detected by Spectral **Development of a Comprehensive Ruleset** Outlines eligible errors for autofix with specific fix logic. **User Experience Enhancements** Ensures modifications are precise, affecting only relevant lines to prevent structural errors. **Unit Testing for Each Fix Function** Ensures the reliability and accuracy of autofixes through comprehensive unit tests, covering all scenarios to catch potential issues early.
The CARE project aims to enhance healthcare management by digitizing patient records, streamlining workflows, and enabling TeleICU services.My proposal aims to improve the efficiency and streamline the PDF report generation process within the CARE system. The current browser-based rendering approach can be resource-intensive. I plan to implement Typst to generate PDF reports. This solution promises to reduce resource overhead and potentially improve performance. My project will involve evaluating Typst's capabilities, adjusting templates, benchmarking resource usage, and gathering user feedback to ensure a smooth transition. My goal is to enhance the report generation workflow, ultimately benefiting the CARE system.
The goal of this project is to develop a debugging page called "xr-internals" to help developers debug and optimize AR/VR web applications. The page will provide relevant information and data to help identify performance issues and other problems with the application, while augment existing performance metrics to be effectively surfaced within the same page. Also improve the WebXR experience in Chromium by addressing critical issues reported in the bug tracker and implementing missing features.
A small benchmark suite already exists for CVXPY. The suite measures both the time to compile a problem into the solver standard form, and the time spent in the solver. Benchmarks are needed so that we can better understand how long it takes CVXPY to compile an issue. The benchmark suite needs to be extended substantially, with a wider range of problems. It should be simple to see how performance changes as a result of a PR or commit, as well as to follow those changes over time.
The killer whale, also known as orca, is the largest dolphin species. Commercial hunting and culling for fisheries protection are threatening its existence. They are also captured for commercial displays in aquariums. Food contamination, chemical contaminants in water, and naval traffic disturbance all pose serious threats to their habitat. A group of orcas known as the Southern Residents is threatened in the United States, with only 71 remaining species in 1974 and 75 by 2020 . By listening for orcas and learning about marine bioacoustics, the Orcasound intends to study and save Southern Resident orcas in the Pacific Northwest . The proposed project uses machine learning and time-series approaches to improve real-time underwater sound interpretation
The Shmdata library provides a layer to share streams of framed data between processes via shared memory. It supports any kind of data stream: it has been used with multichannel audio, video frames, 3D models, OSC messages, and various others types of data. Shmdata is server-less, but requires applications to link data streams using socket path (e.g. "/tmp/my-shmdata-stream"). Shmdata is very fast and allows processes to access data streams without the need for extra copies. However, permissions are not supported, and any stream shared on the system with Shmdata is accessible system-wide. The project will enable the possibility for a Shmdata user to configure streams permission using shared memory right setting at the API level. When sharing data between processes via shared memory, not all components of the data need to be visible to everyone. Different groups might need to access different data, furthermore, some data might only be needed to be visible to the owner of the files. In such cases, the permissions that would have to be implemented are combinations of 'read', 'write' and 'execute' permissions that would be given to the owner, group or common user(i.e. everyone else). Permissions would be 'none', 'execute only', 'write only', 'write and execute', 'read only', 'read and execute', 'read and write', 'read, write and execute' with corresponding values of 0-7 respectively. DELIVERABLES * Providing an option for users to restrict or openly share data streams via these file/ directory access modes: read, write and execute/traverse. * Changing data access permissions. * Documentation for the improvements made. * Incorporation of ACL to assist with Unix file permissions. (optional/if time allows).
<p>Asterix currently requires a static range hint in the query when performing interval joins. The range hint supplies split points for input data, then data is partitioned and sent to separate nodes based on those split points. A static query hint is nice because it gives the user more control over the split points and data partitioning, but it would be nice to have the option to run a query without having to process the data and its split points in advance. Within the last year, code was added to Asterix that implemented a spatial join with a dynamic range hint. This code can pick split points (or tiles) before the join. For my project, I am going to take that code, learn how it works, and then refactor and write code to make it work with interval data and interval joins.</p>
<p>This project revolves around designing a reusable framework for mocking the driver side of a VirtQueue operation. It would allow rust-vmm crates and other projects to use it and would provide a cleaner alternative to mocking code already found in vm-virtio.</p> <p>The framework would at first provide users with more granular control over mocking what the driver will place in the queue and will later support mocking more advanced features such as notification suppression, indirect descriptors and other device specific features.</p>
<p>AsyncAPI aims to set an industry standard for messaging APIs by providing a set of tools and features to improve the current state of Event-Driven Architecture in the world of APIs so that it can be referred to as a single source of truth.</p> <p>This project idea aims to develop a library that focuses on finding and analyzing the relationships between AsyncAPI Documents to get information about Applications described by those files. It would be extendable in a way such that one can provide an additional plugin to the library to obtain output formats other than the default one.</p>
<p>This project is based on the idea <a href="https://github.com/elm-tooling/gsoc-projects#improve-pure-elm-markdown-parser" target="_blank">Improve pure Elm markdown parser</a>. As the idea described, some specs of the pure Elm markdown parser <a href="https://github.com/dillonkearns/elm-markdown" target="_blank">dillonkearns/elm-markdown</a> are not yet implemented. So, the goal is to complete the current implementation of <a href="https://github.github.com/gfm/" target="_blank">Github-flavored markdown style</a>, get the automated spec tests passing, and clarify places where it needs to diverge from the spec because of its specific handling of HTML for extensibility.</p>
<p>4D STEM data in datasets can be stored with different shapes as different representations may be possible depending on the application. For example, data is sometimes stored with a 3D shape as some software for crystallography expects data stored in 3D and currently, LiberTEM’s GUI is limited to 4D datasets. Some datasets with synchronisation/acquisition problems also require specifying the offset. The proposed project aims to enhance LiberTEM’s data pipeline by supporting reshaping of datasets in the GUI which would provide its users with more flexibility to load and perform analyses of multidimensional data.</p>
<p>My proposal consist on rewriting the 1DRadialmodel function to work under the Factory method design pattern. This method decouples classes from constructors, which would give a wider range of option to what the Class can do or be and delegating to Subclasses, instead of defining new Class for every difference the created products might present.</p>
<p>The following modules are to be integrated with caMicroscope:</p> <ul> <li>Creating a workflow to allow model developers to allow their model to be run on a selected image or region of interest by the client, to identify cellular features or cancer.</li> <li>Add the latest deep learning models researched in the area of digital pathology to caMicroscope to help the pathologists.</li> <li>Improve the segmentation app.</li> <li>A tutorial to enable users to make models compatible with caMicroscope.</li> </ul> <p>The motto of this project is to make the recent research in deep learning more accessible</p>
<p>In this project, I propose to add Recurrent Neural Networks to ChainerX. RNNs are a very integral part of deep learning research. ChainerX is faster as compared to other frameworks (eg: Chainer, PyTorch) since its core code is completely implemented in C++. It currently lacks implementations of RNNs. In this project, I will provide C++ implementations of RNN models (LSTM, GRU). This will bring the fast speed of ChainerX to RNN models. I aim to replicate all RNN-related chainer ops in ChainerX. I will also provide sufficient code examples on how to use the RNN models of ChainerX.</p>
<p>The sample platform has been a good way to test regression tests. The main aim of the project is to make sample platform fully finalized (at least with the current list of ideas), and be as stable as possible. It will include adding some new features and fixes which will increase the stability of the platform.</p>
<p>Currently, there are many features of the android viewer are either not implemented or not working properly. For instance theres no option for neither priting the documents nor exporting to pdf. Also tile rendering is working extremely slow and sometimes it causes a crash especially on Calc documents. I have some ideas to this rendering problem such as using cache because i noticed the android viewer renders the same tiles over and over again even tho they are not changed while the zoom is the same. Maybe we dont need to use cache to fix this maybe some other mechanism can be implemented to prevent this from happening which is why I need a mentor :). There are a lot of work to do not just these two of them of course. I hope you guys accept my proposal so that we can start working on it.</p>
<p>Until recently, biodiversity data was scattered in different formats in natural history collections, survey reports, and in literature. In the last fifteen years, lot of efforts are being made to establish standards in the biodiversity database structure and to centralize the data for better accessibility. But the data gathered by such entities does not enforce strong data quality standards. These sources often tend to be prone to many flaws. Thus the data retrieved from centralized sources needs to go through a well formed quality-control process to be used in researches.</p> <p>Bdclean was created for that same purpose. So far we have been able to create numerous quality checks, work-flows, analyses and visualization functionalities in the taxonomical, spatial and temporal aspects. But all these remain as standalone components without much synchronization or connectivity. We propose to refine the overall data cleaning pipeline of bdclean and bring synergy to all the developed components as well as develop new important functionalities. At the end of this project, users will be able go through the quality control process in a very structured, intuitive and effective way.</p>