Explore chapters and articles related to this topic
RLaaS-Frame
Published in J. P. Mohsen, Mohamed Y. Ismail, Hamid R. Parsaei, Waldemar Karwowski, Global Advances in Engineering Education, 2019
Xuemin Chen, Qianlong Lan, Ning Wang, Gangbing Song, Hamid R. Parsaei
To integrate the Wiki-based remote laboratory platform and mobile-optimized remote laboratory application architecture into the RLaaS-Frame, the Docker is adopted to provide a running environment for these frameworks. As shown in Figure 7.8, all of modules in the RLaaS-Frame, which include real-time data transmission module, real-time video transmission module, security module, MediaWiki engine, Ionic framework and all of the supporting components for the RLaaS-Frame which include Apache, Node.js, MySQL, PHP, RESTful Services, AngularJS are installed into the Docker image. The Docker container is created from Docker image, and it supports rapid deployment. Docker container is supported by Docker Engine, and it needs to be installed and configured in Linux OS. In the server side, Docker 0.9 is executed in the server OS, CentOS. To successfully execute Docker 0.9, the execution environment must be built up and configured. Some important build-in execution drivers, such as libcontainer, Libvirt, LXC, Systemd-nspawn, must be installed. Figure 7.9 shows the Docker Engine’s execution environment. As the Docker can image the full-fledged RLaaS-Frame based server, it greatly reduces the burden of building, deploying and maintaining the entire remote laboratory systems, and only need to update the application layer based on users’ various requirements.
Wiki-Based Remote Laboratory Platform for Engineering Education
Published in Ning Wang, Qianlong Lan, Xuemin Chen, Gangbing Song, Hamid Parsaei, Development of a Remote Laboratory for Engineering Education, 2020
Ning Wang, Qianlong Lan, Xuemin Chen, Gangbing Song, Hamid Parsaei
Execution: On the process of execution, Wiki markup typically contains a code that defines and implements custom XML tags, parser functions, and variables. The system will seamlessly integrate MediaWiki with its backing database. It also needs to check contents (such as remote experiments and learning materials) for integrity features and add functions for contents management. The scheduler and confliction management module is also executed to manage the remote experiments at this stage. With MediaWiki users’ permission system, the security system for the remote experiment will be greatly improved.
Web 2 to Enterprise 2
Published in Jessica Keyes, Enterprise 2.0, 2016
Intellipedia includes information on the regions, people, and issues of interest to the communities using its host networks. Intellipedia uses MediaWiki, the same software used by the Wikipedia free-content encyclopedia project. Officials say that the project will change the culture of the U.S. intelligence community, widely blamed for failing to “connect the dots” before the September 11 attacks.
Embedding building performance evaluation in UK architectural practice and beyond
Published in Building Research & Information, 2019
One example of this type of activity enabled a full-time graduate associate engineer, with back up from two senior architecture academics (one being the author), to act as a BPE ‘broker’ when this team undertook a two-year Innovate UK Knowledge Transfer Partnership BPE project in collaboration with Architype Architects, a leading sustainable design practice in the UK, from 2010 to 2011 (Pasquale, Hancock, & Stevenson, 2011). The ‘brokering’ worked here because the graduate associate was able to work with the most senior figure in the practice, the managing director, who provided the necessary leadership as the overall BPE practice ‘champion’, as well as with key individual ‘champions’ in different areas of the practice. This project resulted in 10 iterative BPE studies of schools and other buildings that the practice had designed and delivered with contractors and, more importantly, in vital co-learning between the senior academics, the graduate associate and the key practice ‘champions’. Over time, the graduate associate was able to build up significant credibility and trust as a BPE ‘broker’ for the practice, challenging them not only to improve their performance but also to question the tacit design assumptions and work procedures within their two offices, in order to improve the performance of their buildings. This resulted in the practice developing new ways of thinking about its design work. Together with the graduate associate and others, the practice developed new learning tools and processes for deeply embedding BPE in every aspect of its approach to producing architecture. This included an internal knowledge-sharing website using an open-source MediaWiki framework with multiple plug-ins, as well as internal continuing professional development presentations.