HTCondor Cluster--Saving the Output From the M File

4 views (last 30 days)
Hello,
I am currently attempting to set up a small HTCondor pool consisting of 5 mac computers with a total of 28 cores. Every node in the pool currently has the most recent version of Matlab installed.
Just to get a handle on the process, I am currently attempting to run an HTCondor job on my local processors. I can successfully submit, run, and complete an HTCondor job using the below submit file:
executable = /Applications/MATLAB_R2013a.app/bin/matlab
arguments = -nodisplay -nojvm condortest.m
Universe = vanilla
transfer_input_files= condortest.m
output = matlab.m
error = condorerror.m
queue
With a simple m file (saved as condortest.m) that looks like:
clc
clear all
b=0;
for a=1:100
b(a)=a
filename=strcat('input',int2str(a));
save(filename,'b');
end
HTCondor indicates that the job has finished running through use of condor_history, but the saved files are no where to be found. Furthermore, the output file is simply the login workspace file.
I'm unsure of where in the process I am going wrong in order to successfully run and complete these simple test matlab files.
Thanks for any help.
  1 Comment
Cory Adams
Cory Adams on 12 Apr 2016
Edited: Cory Adams on 12 Apr 2016
Have you looked in your error outputs? You may not be transferring your files back to your computer properly. Try compiling your matlab code. A sample submit: universe = vanilla notify_user = email@email.com notification = complete executable = run_Batch.sh request_memory = 2048 request_disk = 2GB error = error.log output = output.log log = condor.log transfer_input_files = /usr/apps1/matlab-2015a/linux_x86-64/mcr/v85,./ arguments = "v85" queue
A workaround: If you have variables you want to save you can choose to not suppress them from being outputted (aka don't use ; at the end). This will be annoying when running a display and the MATLAB gui but if you have a version of your code that you only run on HTCondor then your output.log file will show these variables. Then you could use grep varname or something to grab these and save them to another file.

Sign in to comment.

Answers (0)

Categories

Find more on Search Path in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!