Explore Projects

<p>This Graphical User Interface is responsible for the Robot's controlling and monitoring. This uses CORTEX architecture which is a cognitive robotics architecture and communicate through a graph structure called Deep State Representation (DSR).</p>

<p>The project is about implementing a Qt5 and ROS support in RoboComp’s DSL</p>

<p>Robocomp current tutorials are simple and cover just the basics. Improved tutorials and use cases need to be created for Robocomp to be a framework friendly for beginners as well as more advanced users.</p> <p>Working on creating examples of how Robocomp can be implemented, and why it should be used, would make it more accessible to the general public. As will improving the "How to Contribute Page", and making pull requests templates would make it easier to collaborate for more advance developers.</p> <p>Getting Robocomp available in other operating systems it's necessary to making it more well-known, in other Linux distros as well as Windows. This can be done with virtual machines images or making tutorials to download it with their respective dependencies on each OS.</p> <p>In summary, Robocomp would be benefited from offering a better user experience and a more seamlessly transition for collaborators to work on it.</p>

I am proposing the use of Convex Inner Approximations to plan the trajectories. The Convex Inner Approximation method finds kinodynamically feasible trajectories that guarantees collision avoidance. It also finds the trajectories in fewer iterations and as a result is much faster than traditional obstacle avoidance constraints.

<p>Building an interactive robotic simulator in order to simulate the complex real world. As real worlds are dynamic in nature we need a simulator where these type of environment can be provided to the robot.</p>

<p>The purpose of this project is to make the Help Screen more manageable for the Volunteers which will require less time to keep the documentation up to date work in Joomla!. For the Volunteers, the current Help System is becoming Unmanageable as they have to update the Help Screen for each Joomla Page and for every New version. Keeping them up to date (content as well as numerous screenshots of the backend) is important for our users but it has become an impossible goal, even more, because they also need to be localized.</p>

<p>Automated Planning involves taking actions to reach the goal. The problem is that most of the practical situations have lots of actions involved, and given a situation, some of these actions might be unnecessary for computing the plan. Therefore planning agents take a lot of time for computing plans because they might be considering redundant actions while planning.</p> <p>The first part of this project is to use Machine Learning algorithms to learn which actions can be useful for computing the plan. Therefore the idea is to train our learning algorithms on many such instances, and given a planning problem, output a probability distribution over all the actions (which indicates the relevance of each action).</p> <p>We'll be applying following learning algorithms for getting the probability distribution over actions:</p> <ol> <li>Bayes Classifier</li> <li>Artificial Neural Networks</li> </ol> <p>The second part of the project is to improve AGGLEditor. For this part, we’ll resolve bugs that are present in the current version of the editor. Documentation and tutorials for AGGLEditor will also be added.</p>

<p>The existing RCIS simulator is not very efficient when our robot get more complex so we need more advanced functions in RCIS. This project is to improve the current RCIS with new functions dealing with contact physics. Currently RCIS has only collision detection feature. We have to add more functionalities like what happen after collision with the help of collision angle, gravity and contact physics.</p>

<p>C++ as a programming language comes in handy in case of performance oriented applications for example: a simulator. But when it comes to rapidly prototyping of applications and ease of use of APIs, it lags behind other languages like python which is one of the most widely used languages just because of this reason and also due to the plethora of libraries that it provides. So, binding the C++ APIs and exposing them to the python interface can be helpful in extending the use of innermodel lib to beginner developers with minimal knowledge of programming. By exposing C++ APIs to python we are achieving two things at the same time: getting the performance from C++ and ease of use through python, which can also increase contributions from the dev community and later help in the development of innermodel lib or robocomp in general.</p>

<p>This project involved improving the mobile app. Primarily, the work was on developing high-priority features for the app. Apart from this, the project also focused on fixing bugs, migrating to new APIs, and improving unit test coverage and documentation, while at the same time ensuring compatibility with older versions of the Zulip server. The overall aim was to provide an experience similar to the web app, both in terms of features and stability.</p> <p>Areas I worked on included:</p> <ul> <li>Adding support for rendering new markdown elements.</li> <li>Developing the 'share from other apps feature' - this also involved working on Kotlin to develop Android-native features and interacting with the React Native bridge.</li> <li>Improving the architecture of some regions of the app, such as the edit message state.</li> <li>Fixing several high-priority bugs and making UI improvements.</li> </ul>

<p>A major component of the Fedora Server is the Cockpit Project, a web-based management console for servers. Systemd provides timer support for system services. I would like to implement a module in Cockpit that manages scheduled tasks using systemd timers. This project is also mentioned in the TODO-list of the Cockpit feature roadmap page.</p>

<ul> <li>Fix quality-of-life issues in the frontend</li> <li>Migrate the frontend to TypeScript</li> <li>Start the process of rebuilding the Zulip web UI in React</li> </ul>

Zulip Terminal (zulip-term) is a TUI based Zulip’s client, powered by Python module urwid. As mentioned in the proposal, I will be doing the following: handle updates of user data, migration to server version 2.1 and improve the search feature

This project aims to implement high-priority features in the 'Zulip server and web application' project, focused around topics and notifications (messages) areas. The issues I specifically aim to solve this summer are: ➔ Implement 'Follow a Topic' feature ➔ Develop @topic mention feature

<p>For Zulip Desktop:</p> <ul> <li>Quicker Response to Customer Issues</li> <li>Multi-Server Login</li> <li>Centralized Preference Panel</li> <li>Adjustments on Different OS Versions</li> <li>Testing</li> </ul>

<p>The current react native project runs great for iOS but a little buggy for Android. I intend to make it more robust, easy to use by implementing a plethora of new features like a new compose message layout/action system, push notifications, drafts screen, settings screen etc. while fixing most of the bugs to make the project near perfect before my program ends.</p>

This project will include implementing cluster of new features, fixing existing performance or functional bugs and adding new testing infrastructure that will progress the Zulip Flutter app towards Launch, which is currently in Beta. Some of the features that I look forward to implement are video previews, Android inbox-style & conversation notifications, ASWebAuthenticationSession on iOS for webauth, Table message content, handling more server events.

This project proposal aims towards implementing a cluster of diverse high priority features in the 'Zulip server and web application' project. The issues I specifically aim to solve this summer are: ➔ Providing a way to temporarily suppress notifications for all streams. ➔ Timed Mutes ➔ Managing resolve topics independently ➔ Cluster of features around message flagging and reporting of users ➔ Provide a way to convert direct message threads to topics

<p>With its innovative threading model and robust web app, Zulip has received a lot of praise from remote teams that use it. While the desktop app is certainly complete in terms of features, it needs some polish and certain standout features to make it an obvious choice for a Zulip user to install. In this proposal, I suggest the implementation of multiple features like enterprise deployment, an updated server validation logic, migration to another database, and a resource manager to improve the overall performance and stability of the app.</p>

This project aims to implement high-priority features in the Zulip server and web application, focusing on message editing and settings. In message editing, the project aims to add support for moving messages by recency, improve permission checks by hiding specific message move options when not allowed, refine how message move history is displayed, and enable deleting items from a message’s edit history. In settings, the project aims to introduce group-based, per-channel permissions for those who can create and edit topics to give organizations better control over channel permissions.

<p>This project aims at making Zulip better by working on features which users in large, high-traffic organizations will find valuable. This mainly involves fixing bugs and implementing and/or completing new features in <a href="https://github.com/zulip/zulip" target="_blank">zulip server project</a> in the <a href="https://github.com/zulip/zulip/issues?q=is%3Aissue+is%3Aopen+label%3A%22area%3A+notifications+%28messages%29%22" target="_blank">notifications</a> and <a href="https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22area%3A+stream+settings%22" target="_blank">stream-settings</a> area.</p>

Zulip's REST API documentation framework is well-built but incomplete, approximately 28 actionable endpoints remain undocumented, and the OpenAPI spec has accumulated structural debt through years of organic growth. This project has two phases. Phase 1 achieves complete endpoint coverage by documenting all remaining high and moderate priority endpoints following the full pipeline: OpenAPI schema, Python and cURL examples, sidebar registration, and changelog entries. Phase 2 refactors the spec's structure, promoting inline parameters to shared components, rationalising the Can*Group schema family, and cleaning up repeated inline response blocks. Deliverables: (1) Zero undocumented actionable endpoints in pending_endpoints. (2) A cleaner, more consistent OpenAPI spec with reduced duplication across parameters, schemas, and response blocks.

<p>Public access to communications is an important aspect to some communities. These communities may or may not be open source communities but still might desire that people on web should be able to access their communications without the need getting an account. With this project we want Zulip to become capable of serving chats that happened in public streams to anyone on the web. Essentially one will be able to read the chats of a web public stream. Members of such a stream will consent to terms of publishing their conversations online. Also this project will help search engines index public chats that happened on a Zulip server accessible to anyone on the web. This will greatly enhance the support available for debugging issues with Zulip installations since we can expect solutions provided on Zulip developers chat to pop up in search results of a search engine query.</p>