 Good evening, my name is Prince. This is Rubal. This is Akash. We have worked on the SyLab website. So what the SyLab website does is, there are two main features. One is textbook companion and one is lab migration. Lab migration is, lab migration proposes to migrate labs of different colleges which use MATLAB and Simulink for their experiments to use FOSS software, mainly SyLab and XCOS. So what happens? The process is simple. The teachers propose their labs with the desired experiments and open-source contributors provide code for the labs. And another module is textbook companion. As you know, many technical textbooks have MATLAB solutions in them or give links in their websites or provide MATLAB solutions for the questions, for the examples there on their websites, on the accompanying websites of the textbook. But we propose to provide SyLab examples for, SyLab solutions for the textbook examples. So this website facilitates that. So we added features to the, the main problem was this website was earlier in Drupal 6. Okay. So and now it's, it uses Drupal 7x score. And when it was converted from Drupal 6 to 7, there's a lot of scaffolding done and this website was very unstable and the code was unformatted. So we had to deal with that and we did our edits on that. Okay. Now Akash will tell you about textbook companion. So these are three modules that we have mainly worked on. So we have updated textbook companion and lab migration and we have built user dashboard. So the, this user dashboard module aims to provide user and with the track the status of proposal more interactively for TBC and LLM project. This module can be used in many other foxy websites supporting Drupal 7. It helps the user to view the current proposals and it helps the admin to view the all the status of the, all the proposal that exists. So these are some screenshots. I will be explaining this in a demo. So about textbook companion. So textbook companion aims to port solved examples from standard textbooks using open source software such as Sylab. Sylab is a open source version of MATLAB and any ASC to non-ASC textbook can be used for this purpose. The objective of this Sylab textbook project is to create Sylab textbook companions to make it easy to users of such textbook to start using Sylab which is free to improve the documentation available for Sylab. Now I will show one video of how it works. So now user will log in. So user will log in and it will click on textbook companion and it will select the, it will select the book that he wants to convert in Sylab. So from here he will select the book and he will propose the book to the admin that is Sylab team. So he will fill up this form detailing the all the details of the book. So after filling the form, the form is submitted and the mail is gone to the admins suggesting that the user wants to propose a book to convert in into Sylab. The admin will get the mail regarding that. We have just submitted the proposal that user wants to convert this book, this particular book in the Sylab. So we have submitted a proposal for it. Right now the, just proposal. Now I am logging in as an admin. So now admin will, so this is the interface that we have made for the admin. So you can see the pending proposal, all proposal categorized and failed proposal. So the pending proposal right now, the Akash Padel that I have made right now has arrived. So the admin will check the all the details of the book and it will approve from this action. It is a proposed date of completion that he will be completing the book by that day. So after checking the all the details, he will approve the proposal and round. Proposal is from him. Proposal is from the user, the student. No sir. I will take this book by Mr. Chawli, Dr. Chawli. And I will convert it in this time. Yes, sir. So, so I think. Okay. So after approving user, user will start sending the course, course of the book. The solved examples that are in the book, it will be converted into Sylab. It will send to the site. So here we have made the dashboard that will show the status of current status of the user proposal, which is not implemented here till yet. And this, this will select. So user will select the code submission and start submitting the course. So now the code submission previously was not so dynamic. It was hard coding mostly. So we have tried to make it more dynamic. So here user will upload this Sylab files, the dependencies, etc. So here you can see the whatever that user has uploaded right now, it will display this edit and delete was not there previously. Sir, yes, there were, this thing is already going on, but there was not the edit and delete option. Yes, no, no, sir. Sir, actually what happens was, so if there was one error in the system that user biomistically submitted the wrong example is wrong, wrong chapter. So what happens was, he will call the Sylab team and then Sylab team will go into the database and they will delete it. There was not like, there was no, yes, any proposal there. So this thing, the main score submission was done by us. I know, yes, most of this was there, but we have to make small changes. Like we are given orders from the Sylab team that we need this interface, we need a text box, we need a data paper here and something like that. So we have to choose that we have to supply the interface as their requirements. We have no control like what to do. We have to supply according to their requirements. That's what we did. Sir, they just tell us and we have to... Sir, we had a task list. We got mailed a task list every day, like these are the tasks you have to do and we followed that. That's on our email. That's what we are presenting. Sir, we changed everything a little bit. Sir, these were the requirements, the interface. Sir, our main aim was to make more interactively the side. No, but that, no. You have told me already that your requirement was in a mail. Yeah. So we can show you the mail if you want, but... This is our requirement. So we are taking over the mail. Okay. Change the edit, delete from black to blue. Sir, all the interface we are showing you are updated interface. These were... I understand, but you are not telling me what you have done. Sir, these, this table like editing and deleting uploaded codes was not... No, but you first said it's the edit code, then you said we have done this. Yeah. So, sir, we are saying that you are telling that we, we did not change the whole interface. We edited specific features. Yeah. It was already... Yes, sir. Sir, the form that... Sir, the proposal submission form did not look like that before. Like, not look in the fields there, we have to add more tables in the database. Now, more data is being fetched from the user. And, sir, let me like, first... So, after completing all the, after submitting all the books, so, user, we click, I have submitted codes for all the examples and the interface will be... Okay, sir, this was a new feature. Earlier, the user acknowledgement was not there. So, what happened was, whenever the user submitted codes, after that, the code interface did not get logged something. So, the user delete, sometimes deleted the codes after they uploaded and, like, there are some blank files left. So, we remove that. Now, the code, the interface gets logged after the user uploads. Sir, this is not done by previous batch of interns. Yes. Okay, then have you gone to their presentation and have they said it can work? Sir, this is not done by previous batch of interns. Sir, this is not done by previous batch of interns. Then, I will say that the interns are submitting code which is useless. Sir, the... Sir, this was not done by interns. It is a live website maintained by web admins. So, we... SILAP team. The SILAP team, the faucet team. Why they are not... Why they are not... Because the web team, they have only... Sir, if you... The SILAP team is on a shortage of web developers. If you go to the SILAP website, there is an ad for hiring web developers. So, what was the site... Okay, I agree that we have done everything. So, after completing the book and after checking all the codes, the status of the book will change here by the admin which will be under you for checking. And after checking, it will be completed and it will displayed in the completed tab. And now you can see your dashboard that the proposal has been completed. This is of TBC. Now, Rupal, we explain the lab migration. This is what we have done. We have completed. So, this is the lab migration module. I worked on this. So, this is the common workflow. It's similar to the TBC module. And the areas and circles I worked on them. Upload code. Okay, so the earlier the code upload interface was such that for SILAP files, you know, they generate, they require sometimes, like signal processing files, they require audio files or something, or image processing files, they require images to work upon. So, earlier what happened was for every lab, you had to upload different dependencies. Like there's this image processing people will know, there's this lena.jpg file and it's used in most image processing experiments, like it's very basic. It had to be uploaded, for every lab, it had to be uploaded separately. But now, you can select from existing dependencies and just the database is updated, but the file remains same. So, that saves space. Then in the code approval by admin. So, this feature was added new. The admins earlier did not have a full view of all the codes and all the status of the codes. Now, they have the view, like they can see what the status of the code is and what the, they can assign new status to the code. Like they can approve or disapprove proposals, approve or disapprove solutions. Then there's this upload journal. This was requested, this feature was requested. The written lab journal in PDF format is uploaded. This was not earlier present. This was added. And these are the two new, you talked about money, sir. This is that part. So, send forms, send forms by post. After the lab is, the lab conversion over the user sends an undertaking saying that I, like he transfers his intellectual property to the SyLab team. He gives them the right to use their codes. That's some official documents. So, there's this bridge between the account section and the user, which enables them to check the status of these dispatch documents and send dispatch the checks accordingly. This is the interface that's we have uploaded. So, the accounting module is not yet completed. And another thing is we are automating the testing of SyLab codes. When the SyLab codes get uploaded right then and there, they're executed on the server and we are logging the output. If the output contains, like we are searching by a keyword error. If the output contains the word error, like the generic SyLab error, then the upload will be rejected at that moment. This will decrease the pressure on admins. We had to earlier review each and every code, but now they can just, the server will automatically do that. This has not been completely into it, but we have made significant progress. That's it. So, we had to maintain and upgrade that SyLab website. The website had all unformatted code and no documentation. Web development for SyLab. Optimization. Thank you.