From: supriya on
I am unable to find out the flaw in my code (Ref.End point detection algo flowchart., pg-7,Rabiner &amp_ Sambur-Algo for endpoint detection of isolated utterances.pdf-Available at http://users.ecel.ufl.edu/~dulberg/endpointdetection.pdf).

I am a new user..please help?
code:-
while (E(m)<E_tl)
m=m-1;
if(E(m)<E_tl)
continue;
end

i=m;
if(E(i)<E_tl)
m=i-1;
continue;
end
while(E(i)<E_th)
i=i-1;
if(E(i)<E_tl)
break;
else
continue;
end
end
if(E(i)<E_tl)
m=i-1;
continue;
end
N2=i;
if(i==m)
N2=N2+1;
end
end

--------
Thanks.
From: us on
"supriya " <skirtiman(a)gmail.com> wrote in message <hvd3bd$49k$1(a)fred.mathworks.com>...
> I am unable to find out the flaw in my code (Ref.End point detection algo flowchart., pg-7,Rabiner &_ Sambur-Algo for endpoint detection of isolated utterances.pdf-Available at http://users.ecel.ufl.edu/~dulberg/endpointdetection.pdf).
>
> I am a new user..please help?
> code:-
> while (E(m)<E_tl)
> m=m-1;
> if(E(m)<E_tl)
> continue;
> end
>
> i=m;
> if(E(i)<E_tl)
> m=i-1;
> continue;
> end
> while(E(i)<E_th)
> i=i-1;
> if(E(i)<E_tl)
> break;
> else
> continue;
> end
> end
> if(E(i)<E_tl)
> m=i-1;
> continue;
> end
> N2=i;
> if(i==m)
> N2=N2+1;
> end
> end
>
> --------
> Thanks.

and ...the flaw... IS(?)...

us
From: Steven Lord on

"supriya " <skirtiman(a)gmail.com> wrote in message
news:hvd3bd$49k$1(a)fred.mathworks.com...
>I am unable to find out the flaw in my code (Ref.End point detection algo
>flowchart., pg-7,Rabiner &amp_ Sambur-Algo for endpoint detection of
>isolated utterances.pdf-Available at
>http://users.ecel.ufl.edu/~dulberg/endpointdetection.pdf).
>
> I am a new user..please help?

Your code appears to be syntactically correct, so it sounds like you've got
some testing ahead of you. Working from the flowchart in that paper, create
SMALL signals that cover each of the paths through that flowchart and run
them BY HAND through the procedure in the flowchart, recording the results
at each step. [This is going to be the first hard part of your task.] Then
set a breakpoint on the first line of your code and run your code on each of
the signals you generated. Watch the contents of the variables (either
using the Workspace Browser or by simply typing their names in the Command
Window) and look for the first time your results differ from the results you
generated by hand. Now that you have a test case that demonstrates the
incorrect behavior you can determine WHY the results differ and how to make
them the same. [This is the second hard part.]

For more information on debugging functions in MATLAB, read this section of
the documentation:

http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_env/f2-4931.html

--
Steve Lord
slord(a)mathworks.com
comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ
To contact Technical Support use the Contact Us link on
http://www.mathworks.com


From: supriya on
"Steven Lord" <slord(a)mathworks.com> wrote in message <hvd7da$m1n$1(a)fred.mathworks.com>...
>
> "supriya " <skirtiman(a)gmail.com> wrote in message
> news:hvd3bd$49k$1(a)fred.mathworks.com...
> >I am unable to find out the flaw in my code (Ref.End point detection algo
> >flowchart., pg-7,Rabiner &amp_ Sambur-Algo for endpoint detection of
> >isolated utterances.pdf-Available at
> >http://users.ecel.ufl.edu/~dulberg/endpointdetection.pdf).
> >
> > I am a new user..please help?
>
> Your code appears to be syntactically correct, so it sounds like you've got
> some testing ahead of you. Working from the flowchart in that paper, create
> SMALL signals that cover each of the paths through that flowchart and run
> them BY HAND through the procedure in the flowchart, recording the results
> at each step. [This is going to be the first hard part of your task.] Then
> set a breakpoint on the first line of your code and run your code on each of
> the signals you generated. Watch the contents of the variables (either
> using the Workspace Browser or by simply typing their names in the Command
> Window) and look for the first time your results differ from the results you
> generated by hand. Now that you have a test case that demonstrates the
> incorrect behavior you can determine WHY the results differ and how to make
> them the same. [This is the second hard part.]
>
> For more information on debugging functions in MATLAB, read this section of
> the documentation:
>
> http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_env/f2-4931.html
>
> --
> Steve Lord
> slord(a)mathworks.com
> comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ
> To contact Technical Support use the Contact Us link on
> http://www.mathworks.com
>
Actually I tried debugging step by step. There is an alltogether
similar loop for beginning point detection except that '+' occurs
instead of minus in its code(ex. m=i+1) The problem comes when I
enter this part after completing the end point search-
my cursor gets lost and the breakpoint also vanishes. And the required
variables do not show up in workspace.:(

---
Regards,
Supriya