Scilab Enterprises

Mentors: Student: sampig

<p>Xcos is a great tool for modeling and simulation. However, as the number of the blocks increases, an Xcos schema can become quickly messy. This idea of is to provide options to automatically update the layout of an Xcos schema including its links and blocks, so that the diagrams could be kept well-presented. Based on the optimal route for a link, I will try to improve the positions of blocks and implement the preview functionality.</p>

Mentors: Student: Rishubh Jain

<p>Scilab being a software used worldwide, needs to focus on how its users (potential developers) interact with Scilab and how comfortable they are with using the features provided by Scilab. Scilab already incorporates the facility to make figures such as tables labels etc and allows insertion and manipulation of data. Unfortunately even though the facility is provided the features have been found buggy and not well documented making its usage very limited and which incapacitates the current users and fails to attract new users .There are some most wanted features like spreadsheets, progress bar etc which are not present and are highly wished for by the users of Scilab,and others.</p> <p>My aim is to improve/upgrade the already existing facility to such a level that the users become very comfortable using it and to further introduce much needed user interface elements in Scilab User Interface Control to make it most favoured software. My work starts with modifying and documenting Uitables and Uitrees and extends upto incorporating ProgressBar. These development would solve major issues with GUI,would attract more users to Scilab and would help in retaining already existing users</p>

Mentors: Student: leonardojc

<p>Jupyter project provides a way to perform scientific/mathematical computations with several different programming languages using the same user interface. It achieves that by distributing the processing between a front-end (Jupyter clients, like the web based Jupyter Notebook) and a back-end (Jupyter kernels, written in Python, R, Java, etc.), that communicate among themselves with standardized format messages, transmitted through ZeroMQ connection.</p> <p>Besides the ability to switch across different kernels from the same common interface, another advantage of this approach is the possibility to run the two software components on different machines, e.g., offloading the heavier backend processing to a remote server while sending commands and visualizing data from a mobile device running the frontend.</p> <p>For Scilab, there is currently a kernel that uses a compatibility layer with file access data exchange and numpy calls to communicate with clients through the Python reference implementation.</p> <p>This Google Summer of Code proposal aims to adapt or rewrite the current suboptimal solution, to make it a truly native kernel, linking ZeroMQ messages directly to Scilab API.</p>

Mentors: Student: Dhruv Khattar

<p>The main objective of this project is to reduce the memory errors faced by the Scilab code-base and ensure memory safety.</p>

Mentors: Student: Caio Souza

<p>This project aims to polish the current graphics features of Scilab such as zooming, datatips and interactive curve edition through plotting. Usually the Scilab is widely used by students and engineers as a completely free and open source numerical software solution for fast prototyping and data visualization. In this context the user experience is dictated by how well one can view and easily interact with its data. This makes the plotting capabilities and interactions, besides performance, a key factor of the perceived easiness and software quality.</p>