Command window output of still running task

Hello,

does anyone whether there is a way to get the command window output of a task while it is still running?

If not, is there another built-in way of monitoring running tasks (besides the state?)?

Thanks,

Pieter

Answer 1

[Walter Roberson]

Start the session from another process, using OS-level pipe() to communicate with it. Unfortunately MATLAB does not flush its buffer at any particular time.

If you need graphics, you might have to read the output using screen capture techniques.

There is no mechanism within MATLAB to do what you would like (unfortunately.)

[Pieter van den Berg]

That is unfortunate... thanks for the info.

[Mustafa]

I just posted a question and i thought this is somewhat relevant to my question. I will appreciate any help

"Is it possible to check the whole history of a program which has let say i=20000 iteration. I have tried to debug the code but everything works fine till i=200 but i can't go till 20000.

The thing is when the program finishes, i can only see last couple of hundred iterations.

Is there anyway,i can check the whole program iteration(other than debugging)"

Cheers.

Answer 2

[Thomas Ibbotson]

Hi Pieter,

Starting in R2012b it is now possible to get the diary output of a task while it is still running. See http://www.mathworks.com/help/distcomp/release-notes.html.

Cheers, Tom

[Xinyi Shen]

nobody explains how to use it. Therefore, there's still no way of doing so.

[Thomas Ibbotson]

Here are some examples of how you might do this:

If you are using a batch job to run your task, then you can use the diary() function passing in the job while it is still running e.g.

job = batch('myScript');
diary(job)

If you are using jobs and tasks, you must set the CaptureDiary flag on the task to true, and then query the Diary property of the task e.g.

myCluster = parcluster;
job = createJob(myCluster);
task = createTask(job, @myFunction, 0, {}, 'CaptureDiary', true);
submit(job);
task.Diary

Answer 3

[Pieter van den Berg]

A hack that worked very well for me is to overload the built-in disp function with something that writes the output of the built-in disp to a logfile.