How do I put in a specific mechanism to ensure that the execution due to the publish() run does not trigger another call to publish()

To save time not running through our entire program (3D imaging device that quantifies and monitors diabetic ulcers), I've made a separate .m file called clinical report wherein the outputs of some image analysis exist and I'm looking to run THIS smaller file and have the report published. I'm receiving a recursive run, however, because of this "nested"ness, it seems.

options_pdf_nocode.format = 'pdf';
options_pdf_nocode.showCode = false;
publish('clinicalreport.m',options_pdf_nocode);

Will the idea of first copying the file, ie.

copyfile(fullfile(matlabroot,'help','techdoc',...
'matlab_env','examples','fourier_demo2.m'),'.','f')

do the trick? I don't know how to make use of this last line of code.

Answer 1

[Walter Roberson]

Use a different file

   function publishclinicalreport
     options_pdf_nocode.format = 'pdf';
     options_pdf_nocode.showCode = false;
     publish('clinicalreport.m',options_pdf_nocode);
   end

and run that instead of running clinicalreport and expecting it to publish itself.

[Golnar]

It worked, Walter! It worked!