Apparently focus was in the editor and some of your keystrokes CTRL^C got interpreted to paste and some extra end statements were inserted at the end of the main function around line 520ff.
There also was a missing closing bracket and parenthesis on the extremely long ylim() line 342...I wrapped that line and reformatted indenting to be more consistent and closed up quite a lot of white space.
I'd strongly recommend refactoring the function to not have 500+ line function...
BTW, the problem was given in the main error message in the editor as unbalanced END statements.
Both missing or extra END and closing brackets/parentheses confuse the input parser greatly and can interact--particularly the [ ... missing the closing ] tries to just keep on agglomerating stuff...
ADDENDUM
BTW, I converted one nested if...elseif...end construct on the case_acc variable to a SWITCH block while was checking for where the broken END construct could be...much cleaner. But, while doing that I noticed
case 2
if trig>1.2 || err==1
i=i-1;
Content=Content_save;
delta=delta/1.5;
t=time(i-1)+delta;
elseif err==1
precip_dist=precip_dist2;
grains=grains_new;
end
in which the elseif block will never get triggered because the if clause is written as or and so if err==1 it's the clause that will be executed irrespective of the value of trig
Dunno if that's of any concern or not, but probably not what was intended, exactly.
