Difference: CLUMEQ (1 vs. 2)

Stupid Cluster Tricks

10) To solve the point above for matlab licenses, one may include the following line of execution into your matlab code:

	 % halt execution for a minute if we can't get the image toolbox
	 while (~license('checkout','image_toolbox'))
		  pause(60); 
	 end;

deadlocks

license()

11) To solve the above 2 problems, one can take the ultimate step and compile the M-file into a system executable. This is done via matlab's compiler. However, one must be aware of the licensing limitations associated with a stand-alone system executable from the matlab compiler. Of course, if one uses a call in the "Can not be compiled" column, then one must revert back to the solution above. Gee, this is getting complicated.

12) The ultimate matlab licensing solution would involved a system executable which attempts to launch a matlab engine. Whilst monitoring the standard error output stream (ie: stderr), if it detects an error "-4" (the error number associated with insufficient matlab licenses), then it can relaunch the matlab engine until it doesn't fail. The problem with this solution is that it is racing against all the other processes in a polling manner-- quite inelegant. So really this isn't the ultimate solution.

McGill

http://www.clumeq.mcgill.ca/

Here are some things found out about CLUMEQ that might help someone who is new to CLUMEQ (after reading the CLUMEQ FAQ).

0) Forget about CLUMEQ. WESTGRID's http://www.westgrid.ca/support/Facilities#head-7d986acf67ff63ef2a2e9d0553cd80bba84c2aa3|glacier (http://www.westgrid.ca) is much bigger and better in almost every single way. See the WESTGRID wiki.

Note: 2006-05-05 CLUMEQ is about to get a $30,000,000 upgrade. It might be worth compairing the two systems in 2007.\ 1) Opening an account is more of a formality than anything. Everyone gets accepted.

2) Matlab is available but only in single processor format.

3) I have made a Matlab script that will take an M-file (whose primary function is to run many identical test cases with different parameters after some setup code at the top of the M-file) and create a queue to submit to the CLUMEQ queue. See a graphics explanation here. See the code here clumeq.m.

Note: Albert has made a better launcher file, and it can be found in the WESTGRID wiki. However, it seems to fail to input jobs into the proper queues of (single/multi/big/clumeq). It doesn't affect the processes.

4) Only 16 single processor processes will be executed at any one time. 12 of which may be yours.

5) The admin, Patrice, if a very useful and responsive. When troubles arise, do email him.

6) CLUMEQ is woefully under used. So there's alot of time available to each active user. This applies more or less for the general usage of single processors.

7) CLUMEQ makes 2 files, stdout and errout, after running your job queue file (ie: PBS file). However, the error file sometimes cuts off if Matlab is writing to that error file (unknown why). This makes debugging Matlab sometimes difficult. Beware....

8) I have made a matlab script that will kill all the user queues. Check it out here qdelall.m. One uses it like this under matlab: qdelall('your_user_name');

Note: Please feel free to edit this page. If something isn't clear, then feel free to email Albert Law.