...
Complete the following edits to the MATLAB files of the module:
Add the line "isinterpreted M.isInterpreted = 1;" to the <modulename>_module.m file (found in the “matlab” folder of your custom module) anywhere after the “M = awe_module(…” assignment in the “matlab/” directory of your custom module.
Add spaces around equals signs for assignment functions (see lines 34-37 in Figure 1)
...
Separate out functions contained in the
...
<modulename>_module.m file to individual .m files.
...
NOTE: Confirm there is a corresponding .m file for any function being defined, otherwise comment out the definition. For example, this module was failing because there was no corresponding “chorus_process.m” file. Commenting out line 35 fixed the issue.
...
Move any module function up to the same folder as the <modulename>_module.m
Run “make_<modulename>_pack(1)” to create the updated .c and .h files.
NOTE: Setting “isInterpreted=1” in your module.m file will prevent breakpoints in your module’s MATLAB code from working properly. If you need to use breakpoints in your module’s MATLAB code, set “isInterpreted=0” to allow debugging and then change that value back to 1 before your final build of the module.
...