Add left biphone recipe for swbd #774

naxingyu · 2016-05-11T08:54:10Z

This is a WIP PR to track the progress in left biphone chain modeling, as requested by #766 . The results will be updated in the script instead of RESULT because it is WIP.

vijayaditya · 2016-05-13T02:20:38Z

egs/swbd/s5c/local/chain/run_tdnn_7d.sh

+train_stage=-10
+get_egs_stage=-10
+speed_perturb=true
+dir=exp/chain/tdnn_7b  # Note: _sp will get added to this if $speed_perturb == true.


tdnn_7b --> tdnn_7d

vijayaditya · 2016-05-13T02:24:44Z

I will merge once the conflicts have been resolved.

naxingyu · 2016-05-13T02:30:01Z

Thanks Vij. There should be no conflict. Maybe it is the WIP tag that
disable the merging.
The '.nodelete' line of script came from run_tdnn_7b.sh. I'll deleted
it, but I think there should be a cleanup in the swbd chain recipe dir,
since it is quite noisy AS IS.

在 2016/5/13 10:24, Vijayaditya Peddinti 写道:

I will merge once the conflicts have been resolved.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#774 (comment)

naxingyu · 2016-05-13T03:00:22Z

Updated and WIP removed. Ready to merge.

在 2016/5/13 10:24, Vijayaditya Peddinti 写道:

I will merge once the conflicts have been resolved.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#774 (comment)

vijayaditya · 2016-05-16T02:02:17Z

Sorry @naxingyu I failed to merge this last time you cleared the conflicts. Could you do a rebase your branch as it is currently out-of-date ? I will merge immediately now.

naxingyu · 2016-05-16T02:13:17Z

I could, but it's strange that I don't see a conflict message on
Github... The files I committed are not conflicting with any other PR.

在 2016/5/16 10:02, Vijayaditya Peddinti 写道:

Sorry @naxingyu https://github.com/naxingyu I failed to merge this
last time you cleared the conflicts. Could you do a rebase your branch
as it is currently out-of-date ? I will merge immediately now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

vijayaditya · 2016-05-16T02:18:27Z

There are no conflicts, github is just saying that your branch is stale
compared to the master. A rebase would solve this issue.

--Vijay

On Mon, May 16, 2016 at 7:43 AM, Xingyu Na notifications@github.com wrote:

I could, but it's strange that I don't see a conflict message on
Github... The files I committed are not conflicting with any other PR.

在 2016/5/16 10:02, Vijayaditya Peddinti 写道:

Sorry @naxingyu https://github.com/naxingyu I failed to merge this
last time you cleared the conflicts. Could you do a rebase your branch
as it is currently out-of-date ? I will merge immediately now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#774 (comment)

naxingyu · 2016-05-16T02:19:58Z

I see. Is it ok now?

Xingyu

在 2016/5/16 10:18, Vijayaditya Peddinti 写道:

There are no conflicts, github is just saying that your branch is stale
compared to the master. A rebase would solve this issue.

--Vijay

On Mon, May 16, 2016 at 7:43 AM, Xingyu Na notifications@github.com
wrote:

I could, but it's strange that I don't see a conflict message on
Github... The files I committed are not conflicting with any other PR.

在 2016/5/16 10:02, Vijayaditya Peddinti 写道:

Sorry @naxingyu https://github.com/naxingyu I failed to merge this
last time you cleared the conflicts. Could you do a rebase your branch
as it is currently out-of-date ? I will merge immediately now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

danpovey · 2016-05-16T02:19:59Z

I think it's OK. It's because yenda made that github configuration
change. As long as it's only changes in scripts, it's always safe to merge
such things.

On Sun, May 15, 2016 at 10:18 PM, Vijayaditya Peddinti <
notifications@github.com> wrote:

There are no conflicts, github is just saying that your branch is stale
compared to the master. A rebase would solve this issue.

--Vijay

On Mon, May 16, 2016 at 7:43 AM, Xingyu Na notifications@github.com
wrote:

I could, but it's strange that I don't see a conflict message on
Github... The files I committed are not conflicting with any other PR.

在 2016/5/16 10:02, Vijayaditya Peddinti 写道:

Sorry @naxingyu https://github.com/naxingyu I failed to merge this
last time you cleared the conflicts. Could you do a rebase your branch
as it is currently out-of-date ? I will merge immediately now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#774 (comment)

vijayaditya · 2016-05-16T02:22:13Z

Yep. Thanks for making the change. I merged the PR.

On Mon, May 16, 2016 at 7:50 AM, Xingyu Na notifications@github.com wrote:

I see. Is it ok now?

Xingyu

在 2016/5/16 10:18, Vijayaditya Peddinti 写道:

There are no conflicts, github is just saying that your branch is stale
compared to the master. A rebase would solve this issue.

--Vijay

On Mon, May 16, 2016 at 7:43 AM, Xingyu Na notifications@github.com
wrote:

I could, but it's strange that I don't see a conflict message on
Github... The files I committed are not conflicting with any other PR.

在 2016/5/16 10:02, Vijayaditya Peddinti 写道:

Sorry @naxingyu https://github.com/naxingyu I failed to merge this
last time you cleared the conflicts. Could you do a rebase your
branch
as it is currently out-of-date ? I will merge immediately now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#774 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#774 (comment)

danpovey · 2016-08-05T00:04:19Z

@naxingyu , I notice in the RESULTS file in swbd/s5c there is a very out-of-date, suboptimal chain system listed there. Currently I think this 7d is the recommended system, but I don't have access to it because you ran it. Can you please remove the current chain+tdnn system in the RESULTS file and replace it with the corresponding results from this system?

naxingyu · 2016-08-05T05:44:12Z

OK

在 2016/8/5 8:04, Daniel Povey 写道:

@naxingyu https://github.com/naxingyu , I notice in the RESULTS file
in swbd/s5c there is a very out-of-date, suboptimal chain system
listed there. Currently I think this 7d is the recommended system, but
I don't have access to it because you ran it. Can you please remove
the current chain+tdnn system in the RESULTS file and replace it with
the corresponding results from this system?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#774 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKpxMqOebk489rF3BjQxQXOUnIScPA3ks5qcn4GgaJpZM4Ib3YV.

naxingyu force-pushed the chain-left-biphone branch 2 times, most recently from f967c2e to 27c8531 Compare May 11, 2016 09:49

vijayaditya mentioned this pull request May 13, 2016

Left-biphone recipe for Librispeech #776

Closed

vijayaditya reviewed May 13, 2016
View reviewed changes

add left biphone recipe for swbd

8293df6

naxingyu force-pushed the chain-left-biphone branch from 27c8531 to 8293df6 Compare May 13, 2016 02:58

naxingyu changed the title ~~WIP: add left biphone recipe for swbd~~ Add left biphone recipe for swbd May 13, 2016

Merge branch 'master' into chain-left-biphone

85bb082

vijayaditya merged commit 80d6d07 into kaldi-asr:master May 16, 2016

naxingyu deleted the chain-left-biphone branch May 16, 2016 02:27

naxingyu mentioned this pull request Aug 5, 2016

update swbd chain result #949

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add left biphone recipe for swbd #774

Add left biphone recipe for swbd #774

naxingyu commented May 11, 2016

vijayaditya May 13, 2016

vijayaditya commented May 13, 2016

naxingyu commented May 13, 2016

naxingyu commented May 13, 2016

vijayaditya commented May 16, 2016

naxingyu commented May 16, 2016

vijayaditya commented May 16, 2016

naxingyu commented May 16, 2016

danpovey commented May 16, 2016

vijayaditya commented May 16, 2016

danpovey commented Aug 5, 2016

naxingyu commented Aug 5, 2016

Add left biphone recipe for swbd #774

Add left biphone recipe for swbd #774

Conversation

naxingyu commented May 11, 2016

vijayaditya May 13, 2016

Choose a reason for hiding this comment

vijayaditya commented May 13, 2016

naxingyu commented May 13, 2016

naxingyu commented May 13, 2016

vijayaditya commented May 16, 2016

naxingyu commented May 16, 2016

vijayaditya commented May 16, 2016

naxingyu commented May 16, 2016

danpovey commented May 16, 2016

vijayaditya commented May 16, 2016

danpovey commented Aug 5, 2016

naxingyu commented Aug 5, 2016