WnCC - Seasons of Code
Seasons of Code is a programme launched by WnCC along the lines of the Google Summer of Code. It provides one with an opprtunity to learn and participate in a variety of interesting projects under the mentorship of the very best in our institute.
List of Projects
- Scilab-Julia Interface
- Scilab Video Player
- Scilab server
- Xcos on Web
- Remote Triggered Virtual Lab
- FOSSEE Toolbox Project
- Front end development for FOSSEE websites
- Common Drupal based theme for FOSSEE Websites
- Develop GUI for OpenModelica using Python
- SBHS Virtual lab server and website
- Image Processing for Healthcare Research
- To Create Dynamic Syllabus Matrix for Virtual Labs Community portal
- Mapping Analytics from Virtual lab to edX
- Continuous integration for Virtual Labs
- Establishing P2P communication on edX mobile client
- Revive pythonFlu package for OpenFOAM
- Website development for Spoken Tutorial project
- Smart Mouse
- IIT-B App
- Tum Tum Tracker
- Learn To Flap
- Panorama in Cam-Scanner
- LendIt- A sharing platform
- Interactive textbook for Probability & Statistics
- Game-playing AI agents
- Competitive Programming
- Functional Programming
- Poisson Solver with Image Editing
- Blind Source Separation
A Virtual Laboratory is an online facility aimed at providing a laboratory experience to students. Unlike Simulation Virtual Labs, Remote Triggered Virtual Labs (RT labs for short) is that category of Virtual Labs which enables the student to access a real experimental setup, remotely. One such facility is available for a laboratory setup known as “Single Board Heater System”, SBHS for short.
The SBHS RT lab can be accessed here. To understand what is SBHS, see the spoken tutorial available here. If you want to quickly learn how to access SBHS RT labs click here. A good documentation on this is available here under the “Documentation” section. The document contains a dedicated chapter which attempts to explain the Client-Server architecture.
Shortcomings in the current solution:
- The solution is very specific to SBHS experimental setup. The architecture cannot work without re-writing a few modules if there is even a slight change in the hardware.
- There are some known software bugs which make a few SBHS unusable. These bugs are random and are currently unsolved. It has very less admin specific features.
- You are expected to come up with a more generic solution for RT labs in general. The solution should be robust, low on maintenance, automated and easily adaptable for a new hardware experimental setup, with minimum changes in the code. You may think of a central interface to customise the web solution as per the new hardware. For example, a number of inputs-outputs, protocol etc.
- The solution should have all the features of the existing SBHS RT lab solution. You can propose better alternatives, though.
- The solution has to be well documented with a regular version controlling/ backup setup.
- The admin should have easy interfaces to do health checkup of the hardware(s), bypassing all the user rules and also should be able to download users experimental data files based on the slot date-time value. Basically, the admin should have an easy control over the server without being a domain expert.