How to Get Started with an iLabs Batch Mode Experiment
Deploy a local Service Broker
- Go to the website http://icampus.mit.edu.ezproxy.canberra.edu.au/ilabs.
- On the left hand side of the page, find iLabs Architecture and follow the link.
- On the left hand side of the page, find Downloads and follow the link.
- On the Downloads page, select the tab 'Documentation'. Then select the item iLabs Service Broker Installation Instructions (Release 6.1) - 04-11-2006. Open this file and read the instructions provided.
- Still on the Downloads page, click on the tab 'Software'. Then select the item iLabs Release 6.1 Deployment Kit - 04-11-2006.
- Using the computer you have set aside to be your trial Service Broker, start the installation of the software.
Liaise with MIT iLab team.
At this stage, you have an operational service broker. Now, contact Dr Phil Long at pdl@mit.edu the Learning Outreach Dir. of the MIT iLab team. After you have discussed your plans with the MIT iLab team, you may be able to connect with a designated experiment at MIT (or somewhere else in the world) in order to test out your new service broker against a working experiment. You will need to add your local users, maybe link into your local authorization system so users have a single login to the new resource. All this can be discussed with the MIT iLab team while you progress the installation.
You should now considering ,the particular experiment(s) you are going to place within the iLab environment. A couple of pointers might help here:
- The experimental hardware should a digital control interface, i.e., be controlled from a local computer.
- Ideally the experiment hardware/software should have an existing API. MATLAB provides a nice interface to the control type experiments, so give that a thought. LabView is of more use in interactive mode experiments, so you may want to develop this type of experiment until after you have mastered a batch mode experiment.
- Think about the experiment you will be running on the hardware. In the first instance, keep it very simple. This means that the user interface you write will also be simple, and might actually work with minimum effort.
- The experiment should be able to run to completion without the intervention of the user (i.e., be a batch mode experiment as opposed to an interactive experiment in which the user can modify settings while the experiment is in operation).
- Discuss your plans with the MIT iLab team to check that you are not becoming overambitious - we all want to see your first experiment up and running as soon as possible. If you pick a difficult experiment it may take quite some time to get it running, squandering the initial enthusiassm before iLabs is given a chance to succeed.
Consideration of these properties will speed the implementation under iLabs. This also allows you to get on with the development of the experiment while gaining experience with iLabs software.
Deploy the Sample Lab Server
- Return to the Downloads menu and the Software tab. Select the item iLabs Time of Day Sample Lab Server Installation Instructions (Release 6.1) - 06-22-2006. Open this and read the instructions provided.
- Still on the Downloads page, click on the tab 'Software'. Then select the item iLabs Time of Day Sample Lab Server SDK (Release 6.1) - 06-20-2006
- Install and run the Time of Day Server.
Refine Your Proposed Experiment
- Finalize the proposal of the experiment you wish to develop. Start looking at the Time of Day code to see how you could modify this to run your new experiment.
- Forward your experiment proposal to MIT to iLabs_support@mit.edu At this time, arrange an email and/or videoIP conference with MIT. You will be linked with a number of people who will be able to advise you on the feasibility of success of the experiment you propose to implement within iLabs.
Share Your Experience and Knowledge
- Once you have your experiment running, consider making it available to the global community.
- Tell all your friends and colleagues about iLabs, and help them now to get an online experiment running under iLabs.