Skip to main content

Virtual Labs launched

[21 March 2015] Update: The original URLs for the Software Engineering and Advanced Network Technologies Virtual Labs are temporarily not working. You can access these labs here:
vlssit.iitkgp.ernet.in/isad/isad/
and 
vlssit.iitkgp.ernet.in/ant/ant/

The Virtual Labs project has been formally launched today.

This is a day perhaps many of us have been waiting for long. The Virtual Labs is an ambitious project undertaken by Ministry of Human Resource Development (MHRD) as part of the National Mission on Education through Information and Communication Technology (NMEICT) program. This project, I believe, has the potential to bring considerable improvement in science and engineering education in India. The world has changed, and learning (or teaching) is no more confined to the traditional books. Rapid progress in technologies and increasing accessibility to Internet gives ample scope to gain clear understanding of the subject matter. However, something still lacked there. Contents available online tend to provide theoretical knowledge. In many cases one doesn't get a hands-on exposure to related things and techniques.

Virtual Labs attempts to provide a online laboratory to overcome this lacking.



I've been involved with the development of two virtual labs (Software Engineering Virtual Lab and Advanced Network Technologies Virtual Lab) for more than a year. I've joined this project in 2010 after the pilot phase was over. I remember the initial days when we were struggling with the idea of a virtual experiment:
  • What could be called as an experiment in Software Engineering?
  • How could one possibly work online on a problem on say, class diagram?
  • Even if he is able to do so, how does the user get to know whether he is correct?
And there were many such questions. Not to forget, different technical issues that came along the course. For instance, I had a hard time in finding a software that could automatically generate UML diagram from user input. PlantUML finally saved me.

Apart from Software Engineering Virtual Lab, I've also been a part of the Advanced Network Technologies Virtual Lab. This lab, too, has been quite challenging. Nevertheless, together with other team members, all such challenges have been met till date.

That am a developer of these labs, of course, makes me proud. This is the largest project that I've undertaken till now. Work on these labs have given me exposure to the recent trends in web technologies. This is my first real-life work with Python and Django. And I feel I'm growing a taste in UI design as well. But what is more important: this project gave me a scope to contribute something towards my country and society. Being a "software guy", this is possibly the best way I could do so :)

Work on these two labs would be over in the coming few weeks. Kudos to the qualified team (Tuhin Chakraborty, Sujata Pal, Bibhudendu Pati, Arijit Roy, Tanay Chaki) who have contributed largely to these projects. Hope Virtual Labs would benefit the future scientists and engineers of our country!








Comments

Popular posts from this blog

Text Highlighting in Latex

While preparing a manuscript with Latex, it is often useful to highlight the changes made in the current revision with a different color. This can be achieved using the \ textcolor command provided by Latex. For example, \textcolor {red}{Hello World} would display the string "Hello World" in red color. However, the final/published copy of the manuscript does not contain any highlighted text. Therefore, if a large volume of changes were made, it becomes tiresome at the end to find and remove all the individual portions of highlighted text. This can be circumvented by defining a utility command to switch highlighting on and off as desired. In the following, we define a new Latex command, highlighttext , for this purpose. The command takes only a single argument—the text to be highlighted.     \usepackage {color}    % For highlighting changes in this version with red color   \newcommand { \highlighttext }[1] { \textcolor {red}{#1}}   % Remove...

Cohere Aya Dataset: Exploring the Split-by-language Collection

A snapshot of the Aya collection (Bengali) . Image taken from HuggingFace. In February 2024, Cohere launched Aya , a multilingual Large Language Model (LLM). Alongside, a set of datasets used to train Aya has also been released. For example, the aya_dataset consists around 205K examples annotated by humans. On the other hand, the recently released aya_collection_language_split is a gigantic dataset with more than 500 million data points spread across more than 100 languages. As the name suggests, this dataset is split by language. For example, all data points in Bengali, irrespective of the underlying task, can be found in a single split. Apart from the original human-annotated examples from the aya_dataset, aya_collection_language_split also contains a lot of translated and templated data. The dataset is released using an Apache-2.0 license, allowing academic and commercial use. The Bengali Language Split Each language split in the Aya collection has three splits. The Bengali split,...

Specifying Source and Destination of Messages

One of the frequently asked questions in the community is how to specify which particular nodes would act as source(s) and destination(s) of the messages created in the ONE simulator. The simulator, in fact, provides a pair of settings (shown below in bold face) aimed for this particular purpose. Let us consider that there are $n + 1$ nodes in an OMN.  Further, let the nodes with addresses from $x$ to $y$, both inclusive, would create messages. The nodes in the range $w$ to $z$, both inclusive, would be the destinations of those messages, where $0 \le x \le y \le n$, and $0 \le w \le z \le n$. Then, the corresponding simulation scenario can be configured as follows. ## Message creation parameters # How many event generators Events.nrof = 1 # Class of the first event generator Events1.class = MessageEventGenerator # (Following settings are specific for the MessageEventGenerator class) # Creation interval in seconds (one new message every 25 to 35 seconds) Events1.interval ...