 So, you already know about virtual labs, right, in repeat the already explained what are virtual labs. So, virtual labs are remote triggered projects, so we all do experiments, we do labs, we do practicals, we record data, we plot data, so these entire setup can be moved to a virtual place, a different place, server, ok, so that it can be centralized and many people can access it. So, this project named as creating generalized web based solution for remote triggered virtual labs. So, this does not exist now, so we have to repair such project. So, we have virtual labs, but it is not a web based one, it is a desktop one, so I will explain to that. So, let me show you straight away a simple block diagram, so at the left hand side we have SBHS, so SBHS is one of the virtual lab experiment, experiment kit, ok. So, SBHS stands for single board heater system, so this is at the server's end, so this is the central location, this is not available to all students at their home, at their lab, this is some, assume for now, this is available only in IIT, exclusively in IIT, the student in West Bengal want to do experiments using SBHS, so the present setup, this is the present setup what it does, so this is a client computer, this is student who is sitting in West Bengal, this is his computer, this is a server which is located in our IIT lab and that server adjacent to the servers, we have all these SBHS blocks connected. So, SBHS blocks look like one of these, so approximately of this size and it has this power supply, heater system and etcetera, this hardware anyway we will come to know. So, at the client side for now, user has to have a Linux machine, a python based client, a web browser and Sylab installed, so these are mandatory requirement, I think it also works on Windows, but I am not very sure, we have seen mostly on Linux side, so these many requirements are actually too much asked for a student to have, so nowadays students may not have a regular desktop, they will be moving around with their cell phones, they may not have access to a regular console where they can log in and do all such kind of experiments, they would have, they would easily go to the lab and do such experiments by themselves, so the whole idea is to move this entire setup, means on the client hand setup to web based, so completely independent of desktop applications, you can see as of now it requires Sylab to be installed on client machine, Python to be installed on client machine, so these dependences you want to remove, okay let me give you a small brief idea of how it works now, so student login to the server, it is a web interface, they go to www.blabs.itv.ac.in, they log in, they have a username password, they create a login, they book a slot, so the number of experiments, number of such boards, SBHS boards are limited, it is not that all the students can be provided each board at a time, so you have to book a slot in advance, so once you book a slot you get a time slot, one hour time slot, say 2 to 3 pm, you log in, you stay alive of course, you stay alive with your computer during that time slot and you enter the values, so how do you enter the values, now from the web interface, that's our final target, that's our final goal, it should be entirely from web interface, from now at present you have to fire another application, a Python based client, it's a small GUI window where you have to again log in and input the values, okay that's not end of it, you have to again run an application Sylab, okay, so this invoking the Sylab you have to run some scripts, then you can enter the values of, so for single board heater system you have to enter the value of fan and maybe heater and you have to say pass to server, so this Sylab interface will communicate to the server, this server at IIT, that will read the data present in the SBHS which is assigned to you and then it will change the value of speed, speed of fan and speed of heater etc, in return it will return you the temperature, the temperature you will receive in Sylab again, that will do the plotting at the client end, so for all of this you need a working system with Sylab and everything running, you need constant internet also, of course you need internet in other solution, so let me get back to this, so what exactly we want in this setup, as you can read we want the access to be completely moved to the web browser, no need of any Python client, no need of any Sylab on the client machine, configure input and outputs depending on the experiment, so the present configuration are done through the Sylab interface which we want again to be moved on, browser, read and write files and of course this is related to second point, see and download data and plots, see live feed of the setup hardware via webcam, so the webcam is still available but it is not integrated in the web page, you have to integrate it in the web page, store algorithms on the server as you have the login, so whatever code you have written there should be an option to nicely organize them and save it on the web page, website and of course you can choose from the existing database, so for admin for people like us or you in your college, so for the admin interface we need following changes, so the present setup it is actually not very easy to replicate in some other college because we have lot of scripts, lot of database changes, lot of integration need to be done before to move to other college, so we need a single click setup for all of these tools, configure inputs and outputs depending on the hardware, so these listings are actually for the admin interface, the admin interface looks like this, so this is an admin interface where we have list of boards on the left hand side, the status of the board whether it is offline or online, so red is offline, green is online, so webcam and some other temperature profile, so this interface need to be modified, this is for admin not for student, I think that is all for this project, of course you need to run and deploy the server easily and admin should easily be able to debug the code, everything should be under version control, the code should be easily manageable. I hope you got a clear idea of what is a virtual apps and what is HBHS and how we are accessing it, just remember this block diagram, so let me show you this block diagram so that question occur to you, these are the technologies we are looking for, so the server, the present server is already written in Django, so you need to add on this present server and we prefer Django that means Python because it is already written, it is easy for you to add code on that, bash is a Linux command line tool, you may or may not know bash already, that is fine, you can skip bash for now, HTML, CSS, MySQL and Apache are required, Apache is also not very mandatory for now because Apache server setup, etc., we can help you with that, MySQL database queries and all are must because you will be dealing them in and out, HTML I guess it is need not to explain, so bash and Apache you may say it is not mandatory, so this is the second project, so the first project was moving the client side entirely to browser right, clear, the first project moving the client side of the SBHS of the virtual labs to browser removing Psylab and Python dependencies from the client side and improving the admin interface of the server, first project, this is second project, the second project is improving the already available implementation, so we already have SBHS running, as everybody told we have already course running with students, they login and they create some experiments, so we need to modify those courses, those interfaces, this is the same architecture, same example, so what we are looking for in this, so the present architecture, present setup cannot detect failures, so suppose we have 38 SBHS, so at some time at the night, suppose one of the SBHS goes down and there is an experiment setup scheduled tomorrow morning 8am, so it does not automatically detect that and does not inform to the admin, so such things you have to take care, you have to add such modules, such APIs to the already existing Django code, providing periodic health statistics same as first and the third one is enabling client to conditionally choose an SBHS, suppose during an experiment one of the SBHS failed and at present a client has to contact admin and tell that see my SBHS has failed, please assign me a new SBHS, new virtual setup, this should be automated, so student if a machine fails should automatically be switched to a working machine, so again there are some to-do list for the admin interface, so admin should be able to do web-based changes, so if everything is moved to web, so the web interface requires the following changes, he should see all the SBHS setup and he should see, he could means he can analyze the statistics, the health of all SBHS unit over the past month, past year, so he can have the complete tabular data or a statistical data which shows SBHS 38 has been faulty for 3 days in the last month, so you can actually he could actually be able to diagnose how the trend is going on, how many SBHS are failing, which experiment is causing the problem, which experiment is good, all the statistics need to be generated and presented nicely on the admin interface, this one is the last, so packaging as I told in the previous experiment also, we need a single one-click installation, at present the installation is complex, so that your job would be to make the setup files integrated into one single Python script, so that one can do just pip install SBHS and it's done, live web cam feed checking client in activity during web cam feed, these can be discussed later, so last one is important, this is the last slide I guess, so adding quiz and auto evaluation, so this SBHS is integrated with the course, unless there is a course why do you run SBHS, because it's an experiment, it's an extension to the regular experiments, so we need to have a pre and post test quizzes right inside the SBHS web interface, virtual lab web interface, where after performing the lab experiments student should able to take a test, should able to have questions and answer, all the answers could be, questions could be randomized and there should be evaluation and reporting also for admin, so in short we want to take away the lab session entirely the web, so you understood the difference between the previous project and this project, the previous one was to remove Sylab and Python dependencies from the client side, so that a client side should be just a simple web browser, you can take out your cell phone, connect to this some URL and perform your experiments from anywhere, the second project is actually the existing project, existing project and adding improvements to existing project, so the admin doesn't have many features, so you have to add many features, listed features to the admin console, the last one which I showed there should be a question and answer adding quiz to the existing implementation, so that students after finishing the lab could able to do a pre and post test, is this clear, so all of this process slides which have seen this eight nine projects, they all based on open source tools, Linux tools, you may or may not be aware of all this Linux tools right, it's okay, it's completely okay, in terms like you from past many years they have come here and use such tools and they have learned them very fast, maybe one or two days, so tomorrow you have some orientation courses right, so I'm very sure you will be able to take all of these topics, maybe within two or three days, it's very easy, it's all you know but in a different operating system, many of the things can be done in windows also, but we encourage you to use Linux so that it is good for you also, if you go to some other places, maybe some startups or other companies, mostly they prefer Linux for such open source technologies, so for any queries regarding the presentations, the projects which we have displayed today, you can simply email at info at foci.info, so this email will reach to all the mentors who have presented today and your questions, queries will be answered, thank you.