Menu
▾
▴
kaldi-developers — Kaldi Developers
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(1) |
Feb
(8) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(13) |
Jul
(7) |
Aug
(11) |
Sep
(6) |
Oct
(14) |
Nov
(16) |
Dec
(1) |
| 2013 |
Jan
(3) |
Feb
(8) |
Mar
(17) |
Apr
(21) |
May
(27) |
Jun
(11) |
Jul
(11) |
Aug
(21) |
Sep
(39) |
Oct
(17) |
Nov
(39) |
Dec
(28) |
| 2014 |
Jan
(36) |
Feb
(30) |
Mar
(35) |
Apr
(17) |
May
(22) |
Jun
(28) |
Jul
(23) |
Aug
(41) |
Sep
(17) |
Oct
(10) |
Nov
(22) |
Dec
(56) |
| 2015 |
Jan
(30) |
Feb
(32) |
Mar
(37) |
Apr
(28) |
May
(79) |
Jun
(18) |
Jul
(35) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: azin f. <fan...@gm...> - 2015-09-05 09:22:16
|
Hello Thank you to help me and I apologize to you because my English is not so good. Another error in the Kaldi is created in the image below Please help me. |
|
From: Jan T. <jt...@gm...> - 2015-07-31 12:59:31
|
Hi, I'm not gonna answer your question here -- the sourceforge lists are closed and not active anymore. Visit http://kaldi-asr.org/forums.html for additional info. Yenda On Fri, Jul 31, 2015 at 4:58 AM, Naresh kumar <ell...@gm...> wrote: > Dear all, > I am trying to install latest ATLAS package (3.10.0) in cygwin 32-bit > system. > I found following errors when I run install_atlas.sh > My gcc version is 4.9.3 > > Vector ISA Extension configured as SSE3 (6,448) > ERROR: enum fam=3, chip=2, mach=0 > make[3]: *[atlas_run] Error 44* > * make[2]: *[IRunArchInfo_x86] Error 2 > > Architecture configured as UNKNOWNx86 (35) > ERROR: enum fam=3, chip=2, mach=0 > make[3]: *[atlas_run] Error 44* > * make[2]: *[IRunArchInfo_x86] Error 2 > > Clock rate configured as 3092Mhz > ERROR: enum fam=3, chip=2, mach=0 > make[3]: *[atlas_run] Error 44* > * make[2]: *[IRunArchInfo_x86] Error 2 > > Maximum number of threads configured as 8 > Parallel make command configured as '$(MAKE)' > ERROR: enum fam=3, chip=2, mach=0 > make[3]: *[atlas_run] Error 44* > * make[2]: *[IRunArchInfo_x86] Error 2 > * Cannot detect CPU throttling.* > > gcc > -I/cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/..//CONFIG/include > -g -w -o xisgcc > /cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/..//CONFIG/src/IsGcc.c > atlconf_misc.o > gcc > -I/cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/..//CONFIG/include > -g -w -c > /cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/..//CONFIG/src/probe_comp.c > gcc > -I/cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/..//CONFIG/include > -g -w -o xprobe_comp probe_comp.o atlconf_misc.o > rm -f config1.out > make atlas_run > atldir=/cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build > exe=xprobe_comp redir=config1.out \ args="-v 0 -o atlconf.txt -O 8 -A 35 > -Si nof77 0 -V 448 -b 32 -d b > /cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build" > make[1]: Entering directory > '/home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build' > cd > /cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build ; > ./xprobe_comp -v 0 -o atlconf.txt -O 8 -A 35 -Si nof77 0 -V 448 -b 32 -d b > /cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build > > config1.out > sh: -c: line 0: syntax error near unexpected token (' sh: -c: line 0:find > /usr/local/bin /usr/bin /cygdrive/c/ProgramData/Oracle/Java/javapath > /cygdrive/c/Program\ Files/SlickEditV18.0.1\ x64/win /cygdrive/c/Program\ > Files/Common\ Files/Microsoft\ Shared/Windows\ Live /cygdrive/c/Program\ > Files\ (x86)/Common\ Files/Microsoft\ Shared/Windows\ Live > /cygdrive/c/Program\ Files\ (x86)/Intel/iCLS\ Client /cygdrive/c/Program\ > Files/Intel/iCLS\ Client /cygdrive/c/Windows/system32 /cygdrive/c/Windows > /cygdrive/c/Windows/System32/Wbem > /cygdrive/c/Windows/System32/WindowsPowerShell/v1.0 /cygdrive/c/Program\ > Files/Intel/WiFi/bin /cygdrive/c/Program\ Files/Common\ > Files/Intel/WirelessCommon /cygdrive/c/Program\ Files\ (x86)/Windows\ > Live/Shared /cygdrive/c/Program\ Files\ (x86)/Microsoft\ SQL\ > Server/100/Tools/Binn /cygdrive/c/Program\ Files/Microsoft\ SQL\ > Server/100/Tools/Binn /cygdrive/c/Program\ Files/Microsoft\ SQL\ > Server/100/DTS/Binn /cygdrive/c/Program\ Files/Perforce > /cygdrive/c/Program\ Files\ (x86)/Interactive\ Intelligence/ININ\ Trace\ > Initialization /cygdrive/c/Program\ Files/Intel/Intel(R)\ Management\ > Engine\ Components/DAL /cygdrive/c/Program\ Files\ (x86)/Intel/Intel(R)\ > Management\ Engine\ Components/DAL /cygdrive/c/Program\ > Files/Intel/Intel(R)\ Management\ Engine\ Components/IPT > /cygdrive/c/Program\ Files\ (x86)/Intel/Intel(R)\ Management\ Engine\ > Components/IPT /cygdrive/c/xampp/php > /cygdrive/c/ProgramData/ComposerSetup/bin > /cygdrive/c/builds/tools_main_systest > /cygdrive/c/builds/tools_main_systest/ruby/bin > /cygdrive/d/builds/tools_main_systest > /cygdrive/d/builds/tools_main_systest/ruby/bin /usr/lib/lapack -maxdepth 1 > -name '*gcc*' -exec ./xisgcc '{}' \; > /tmp/t6dc.0 2>&1' > /tmp/cczwkvVD.s: Assembler messages: > /tmp/cczwkvVD.s:11: Error: bad register name %rsp' /tmp/cczwkvVD.s:12: > Warning: .seh_stackalloc ignored for this target /tmp/cczwkvVD.s:15: Error: > bad register name%rip)' > /tmp/cczwkvVD.s:18: Error: bad register name %rsp' /tmp/cczwkvVD.s:20: > Warning: zero assumed for missing expression /tmp/cczwkvVD.s:20: Warning: > zero assumed for missing expression make[2]: *** [IRunCComp] Error 1 > /tmp/ccXjwsY6.s: Assembler messages: /tmp/ccXjwsY6.s:11: Error: bad > register name%rsp' > /tmp/ccXjwsY6.s:12: Warning: .seh_stackalloc ignored for this target > /tmp/ccXjwsY6.s:15: Error: bad register name %rip)' /tmp/ccXjwsY6.s:18: > Error: bad register name%rsp' > /tmp/ccXjwsY6.s:20: Warning: zero assumed for missing expression > /tmp/ccXjwsY6.s:20: Warning: zero assumed for missing expression > make[2]: *** [IRunCComp] Error 1 > /tmp/cchHKpJ0.s: Assembler messages: > /tmp/cchHKpJ0.s:11: Error: bad register name %rsp' /tmp/cchHKpJ0.s:12: > Warning: .seh_stackalloc ignored for this target /tmp/cchHKpJ0.s:15: Error: > bad register name%rip)' > /tmp/cchHKpJ0.s:18: Error: bad register name `%rsp' > /tmp/cchHKpJ0.s:20: Warning: zero assumed for missing expression > /tmp/cchHKpJ0.s:20: Warning: zero assumed for missing expression > > make[2]: *[IRunCComp] Error 1* > > * /tmp/ccXjwsY6.s: Assembler messages: /tmp/ccXjwsY6.s:11: Error: bad > register name **%rsp' /tmp/ccXjwsY6.s:12: Warning: .seh_stackalloc > ignored for this target /tmp/ccXjwsY6.s:15: Error: bad register name* > *%rip)'* > * /tmp/ccXjwsY6.s:18: Error: bad register name **%rsp' > /tmp/ccXjwsY6.s:20: Warning: zero assumed for missing expression > /tmp/ccXjwsY6.s:20: Warning: zero assumed for missing expression make[2]: > *** [IRunCComp] Error 1 /tmp/cchHKpJ0.s: Assembler messages: > /tmp/cchHKpJ0.s:11: Error: bad register name**%rsp'* > > * /tmp/cchHKpJ0.s:12: Warning: .seh_stackalloc ignored for this target > /tmp/cchHKpJ0.s:15: Error: bad register name **%rip)' /tmp/cchHKpJ0.s:18: > Error: bad register name**%rsp'* > > > * /tmp/cchHKpJ0.s:20: Warning: zero assumed for missing expression > /tmp/cchHKpJ0.s:20: Warning: zero assumed for missing expression make[2]: *[IRunCComp] > Error 1 > /tmp/ccFNx4Va.s: Assembler messages: > /tmp/ccFNx4Va.s:11: Error: bad register name %rsp' /tmp/ccFNx4Va.s:12: > Warning: .seh_stackalloc ignored for this target /tmp/ccFNx4Va.s:15: Error: > bad register name%rip)' > /tmp/ccFNx4Va.s:18: Error: bad register name `%rsp' > /tmp/ccFNx4Va.s:20: Warning: zero assumed for missing expression > /tmp/ccFNx4Va.s:20: Warning: zero assumed for missing expression > make[2]: *[IRunCComp] Error 1* > * make[3]: *[atlas_run] Error 127 > make[2]: *[IRunCComp] Error 2* > * make[3]: *[atlas_run] Error 127 > make[2]: *[IRunCComp] Error 2* > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > * > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingw32.a when searching for > -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingw32.a when searching for > -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingw32.a when searching for > -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc.a when > searching for -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc.a when > searching for -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc.a when > searching for -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc_eh.a > when searching for -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc_eh.a > when searching for -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc_eh.a > when searching for -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmoldname.a when searching for > -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmoldname.a when searching for > -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmoldname.a when searching for > -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingwex.a when searching for > -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingwex.a when searching for > -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingwex.a when searching for > -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmsvcrt.a when searching for > -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmsvcrt.a when searching for > -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmsvcrt.a when searching for > -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libadvapi32.a when searching for > -ladvapi32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libadvapi32.a when searching for > -ladvapi32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libadvapi32.a when searching for > -ladvapi32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -ladvapi32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libshell32.a when searching for > -lshell32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libshell32.a when searching for > -lshell32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libshell32.a when searching for > -lshell32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lshell32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libuser32.a when searching for > -luser32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libuser32.a when searching for > -luser32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libuser32.a when searching for > -luser32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -luser32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libkernel32.a when searching for > -lkernel32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libkernel32.a when searching for > -lkernel32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libkernel32.a when searching for > -lkernel32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lkernel32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingw32.a when searching for > -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingw32.a when searching for > -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingw32.a when searching for > -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmingw32 > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc.a when > searching for -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc.a when > searching for -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc.a when > searching for -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lgcc > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc_eh.a > when searching for -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc_eh.a > when searching for -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/libgcc_eh.a > when searching for -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lgcc_eh > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmoldname.a when searching for > -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmoldname.a when searching for > -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmoldname.a when searching for > -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmoldname > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingwex.a when searching for > -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingwex.a when searching for > -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmingwex.a when searching for > -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmingwex > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmsvcrt.a when searching for > -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmsvcrt.a when searching for > -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > skipping incompatible > /usr/x86_64-w64-mingw32/sys-root/mingw/lib/libmsvcrt.a when searching for > -lmsvcrt > /usr/lib/gcc/x86_64-w64-mingw32/4.9.2/../../../../x86_64-w64-mingw32/bin/ld: > cannot find -lmsvcrt collect2: error: ld returned 1 exit status make[2]: *[IRunCComp] > Error 1 > /bin/sh: cl: command not found > make[2]: *[/cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/ATLwin_cl.exe] > Error 127* > > > > * Unable to to build ATLwin_cl, quitting cmnd='make > /cygdrive/c/cygwin//home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build/ATLwin_cl.exe' > Makefile:106: recipe for target 'atlas_run' failed make[1]: *[atlas_run] > Error 255 > make[1]: Leaving directory > '/home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build' > Makefile:117: recipe for target 'IRun_comp' failed > make: *[IRun_comp] Error 2* > > > > > > > > > > > > > > > > > > > > > > > > > > > > * ERROR 512 IN SYSCMND: 'make IRun_comp args="-v 0 -o atlconf.txt -O 8 -A > 35 -Si nof77 0 -V 448 -b 32"' mkdir src bin tune interfaces cd src ; mkdir > testing auxil blas lapack pthreads threads cd src/blas ; \ mkdir > f77reference reference gemv ger gemm kbmm \ level1 level2 level3 pklevel3 > cd src/blas/reference ; mkdir level1 level2 level3 cd src/blas/level2 ; > mkdir kernel cd src/blas/pklevel3 ; mkdir gpmm sprk cd src/blas/level3 ; > mkdir rblas kernel cd src/pthreads ; mkdir blas misc cd src/pthreads/blas ; > mkdir level1 level2 level3 cd src/threads ; mkdir blas lapack cd > src/threads/blas ; mkdir level3 level2 cd tune ; mkdir blas sysinfo lapack > threads cd tune/blas ; mkdir gemm gemv ger level1 level3 cd interfaces ; > mkdir blas lapack cd interfaces/lapack ; mkdir C F77 cd interfaces/lapack/C > ; mkdir src testing cd interfaces/lapack/F77 ; mkdir src testing cd > interfaces/blas ; mkdir C F77 cd interfaces/blas/C ; mkdir src testing cd > interfaces/blas/F77 ; mkdir src testing cd interfaces/lapack ; mkdir C2F cd > interfaces/lapack/C2F ; mkdir src mkdir ARCHS make -f Make.top startup > make[1]: Entering directory > '/home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build' Make.top:1: > Make.inc: No such file or directory make[1]: *No rule to make target > 'Make.inc'. Stop. > make[1]: Leaving directory > '/home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build' > Makefile:493: recipe for target 'startup' failed > make: *[startup] Error 2* > > > > > > > > > > > * mv: cannot stat ‘lib/Makefile’: No such file or directory ../configure: > line 450: lib/Makefile: No such file or directory ../configure: line 451: > lib/Makefile: No such file or directory ../configure: line 452: > lib/Makefile: No such file or directory ../configure: line 453: > lib/Makefile: No such file or directory ../configure: line 509: > lib/Makefile: No such file or directory DONE configure make -f Make.top > build make[1]: Entering directory > '/home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build' Make.top:1: > Make.inc: No such file or directory make[1]: *No rule to make target > 'Make.inc'. Stop. > make[1]: Leaving directory > '/home/Naresh.Kumar/work/kaldi-trunk/tools/ATLAS/build' > Makefile:488: recipe for target 'build' failed > make: *** [build] Error 2 > > Please let me know how to solve this problem > > > -- > > > Regards > Naresh Kumar > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Kaldi-users mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-users > > |
|
From: Vijayaditya P. <p.v...@gm...> - 2015-07-24 05:52:31
|
The kaldi project has moved to Github. Please use https://github.com/kaldi-asr/kaldi .The documentation is available @ http://kaldi-asr.org/doc/ Vijay On Thu, Jul 23, 2015 at 10:46 PM, Niranjan Viladkar <nvi...@gm...> wrote: > Hello, > > I am getting a 404 error on any address of the form " > http://kaldi.sourceforge.net/*" > Error is as follows : > > An error has been encountered in accessing this page. > > 1. *Server:* kaldi.sourceforge.net > 2. *URL path:* /about.html > 3. *Error notes:* NONE > 4. *Error type:* 404 > 5. *Request method:* GET > 6. *Request query string:* NONE > 7. *Time:* 2015-07-24 05:43:32 UTC (1437716612) > > *Reporting this problem:* The problem you have encountered is with a > project web site hosted by SourceForge.net. This issue should be reported > to the SourceForge.net-hosted project (not to SourceForge.net). > > *If this is a severe or recurring/persistent problem,* please do one of > the following, and provide the error text (numbered 1 through 7, above): > > 1. Contact the project via their designated support resources > <http://sourceforge.net/support/prweb-lookup.php?host=kaldi.sourceforge.net&support=1>. > > 2. Contact the project administrators of this project via email (see > the upper right-hand corner of the Project Summary page > <http://sourceforge.net/support/prweb-lookup.php?host=kaldi.sourceforge.net> > for their usernames) at *user-name*@users.sourceforge.net > > If you are a maintainer of this web content, please refer to the Site > Documentation regarding web services > <https://sourceforge.net/p/forge/documentation/Project%20Web%20Services/> > for further assistance. > > NOTE: As of 2008-10-23 directory index display has been disabled by > default. This option may be re-enabled by the project by placing a file > with the name ".htaccess" with this line: > > Options +Indexes > > Thanks, > Niranjan. > > -- > Effort is important, but knowing where to make an effort in your life > makes all the difference. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > |
|
From: Daniel P. <dp...@gm...> - 2015-07-24 05:52:28
|
Sourceforge has been down for 2 weeks. kaldi has moved on to github and kaldi-asr.org, where you can find info about th new lists. Dan On Thu, Jul 23, 2015 at 10:46 PM, Niranjan Viladkar <nvi...@gm...> wrote: > Hello, > > I am getting a 404 error on any address of the form " > http://kaldi.sourceforge.net/*" > Error is as follows : > > An error has been encountered in accessing this page. > > 1. *Server:* kaldi.sourceforge.net > 2. *URL path:* /about.html > 3. *Error notes:* NONE > 4. *Error type:* 404 > 5. *Request method:* GET > 6. *Request query string:* NONE > 7. *Time:* 2015-07-24 05:43:32 UTC (1437716612) > > *Reporting this problem:* The problem you have encountered is with a > project web site hosted by SourceForge.net. This issue should be reported > to the SourceForge.net-hosted project (not to SourceForge.net). > > *If this is a severe or recurring/persistent problem,* please do one of > the following, and provide the error text (numbered 1 through 7, above): > > 1. Contact the project via their designated support resources > <http://sourceforge.net/support/prweb-lookup.php?host=kaldi.sourceforge.net&support=1>. > > 2. Contact the project administrators of this project via email (see > the upper right-hand corner of the Project Summary page > <http://sourceforge.net/support/prweb-lookup.php?host=kaldi.sourceforge.net> > for their usernames) at *user-name*@users.sourceforge.net > > If you are a maintainer of this web content, please refer to the Site > Documentation regarding web services > <https://sourceforge.net/p/forge/documentation/Project%20Web%20Services/> > for further assistance. > > NOTE: As of 2008-10-23 directory index display has been disabled by > default. This option may be re-enabled by the project by placing a file > with the name ".htaccess" with this line: > > Options +Indexes > > Thanks, > Niranjan. > > -- > Effort is important, but knowing where to make an effort in your life > makes all the difference. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > |
|
From: Niranjan V. <nvi...@gm...> - 2015-07-24 05:46:53
|
Hello, I am getting a 404 error on any address of the form " http://kaldi.sourceforge.net/*" Error is as follows : An error has been encountered in accessing this page. 1. *Server:* kaldi.sourceforge.net 2. *URL path:* /about.html 3. *Error notes:* NONE 4. *Error type:* 404 5. *Request method:* GET 6. *Request query string:* NONE 7. *Time:* 2015-07-24 05:43:32 UTC (1437716612) *Reporting this problem:* The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net). *If this is a severe or recurring/persistent problem,* please do one of the following, and provide the error text (numbered 1 through 7, above): 1. Contact the project via their designated support resources <http://sourceforge.net/support/prweb-lookup.php?host=kaldi.sourceforge.net&support=1>. 2. Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page <http://sourceforge.net/support/prweb-lookup.php?host=kaldi.sourceforge.net> for their usernames) at *user-name*@users.sourceforge.net If you are a maintainer of this web content, please refer to the Site Documentation regarding web services <https://sourceforge.net/p/forge/documentation/Project%20Web%20Services/> for further assistance. NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name ".htaccess" with this line: Options +Indexes Thanks, Niranjan. -- Effort is important, but knowing where to make an effort in your life makes all the difference. |
|
From: Alexander S. <aso...@gm...> - 2015-07-24 05:15:11
|
How's about `git pull --rebase`? Will be able to keep the history linear as before. On Fri, Jul 24, 2015 at 3:42 AM, Kirill Katsnelson < kir...@sm...> wrote: > Dan, I am suspecting a bit of misunderstanding here. I am not sure I am > reading your intention here: > > $ git diff master remotes/upstream/master > > This compares the tip of your master branch with the tip of the remote > branch. Generally, this comparison does not make much sense. You'll see > your additions as '-', and master additions as a '+'. Then, you are not > probably doing work on master anyway. > > Let's begin from the beginning. When you go 'git clone', you do not "check > out;" rather you create *another repository* with its own set of branches. > Git is distributed, and there is not a server-sandbox relationship; rather, > the two are just two repos (with a lot of common history, of course), but > none of these is "more important." > > *Important note 1*: Many people ask how do they keep their GitHub clone's > master branch in synch with the "golden" master branch. The answer is: > please do not. There is no point in spending your time on keeping two > identical branches in sync! > > *Important note 2*: You do not need to involve your personal fork in > development at all until you are ready to send a PR. > > So how you do the work, generally? > > You already have a repo with 2 remotes. This is what you need. > > origin = gi...@gi...:/danpovey/kaldi.git > upstream = gi...@gi...:/kaldi-asr/kaldi.git > > Next, you want to design a feature. Just branch off the upstream/master, > because this is where the most up-to-date code is: > > $ git fetch upstream > $ git co upstream/master -b my-feature > > The 'git fetch' will fetch all commits that are not yet there in your > local repo. The ref 'upstream/master' will point to the tip of the master > branch. > > Work on your branch. Do commits on it once in a while. Maybe you even > fetch the upstream again, so that upstream/master and my-feature diverge. > This is ok. > > Now, we are back at diffing. The question "what is the difference between > contents at points in history A and B" is not the best one, because the > point B is often not well known. Subversion thinking goes like this: first > you rebase your changes in sandbox on the trunk, then you do 'svn diff' > which shows your changes only. If you are nimble enough, this is what you > commit, if not, do the update again. In Git, the question is stated > differently: "If I merge all changes from the branch F into branch M, what > is the summary patch that I'll apply to M?" The answer is not identical, of > course, assuming M has likely changed. But it is the most informative > really. > > The way to see that diff is > > $ git diff upstream/master...my-feature > > (or simply "git diff upstream/master..." assuming you are on the > my-feature branch) > > NB: This does not take the *current* state of upstream/master into > account. The golden/master is only used to find the closest common history > point, and the summary diff is given as the sum of commits from that point > on your branch. > > For example, try > > $ git diff upstream/master...upstream/nnet3 > > This is the summary patch that "would be applied" (quotes because it does > not work that way, this is only a way to think about it) to upstream/master > if you merge upstream/nnet3 into it. > > But if you do (your initial idea) > > $ git diff upstream/master upstream/nnet3 > $ git diff upstream/nnet3 upstream/master > > you'll see a *symmetrical* difference: the two diffs will just change > signs. They are generally meaningless. > > Notice something cool? You do not use the master branch in your own repo! > No point, really. > > Now, suppose you want to merge your work with a PR. This is how I do it: > > $ git fetch upstream > $ git upstream/master -b testmerge --no-track > $ git merge my-feature > > (--no-track is optional, as you'll kill the branch soon, but helps keep > your config data tidy). > > At this point, you can run tests to make sure everything is ok. You can > then push your feature branch to create a PR. > > $ git checkout my-feature > $ git push origin HEAD > > This will create the branch in your own GitHub's repo, and you'll send the > PR as the difference between kaldi-asr/kaldi:master and > danpovey/kaldi:my-feature > > And I'll write a short doc on that tonight. I feel how painful the > transition is. I'll put a draft on GitHub, and with somebodys help > doxygenate it later. > > -kkm > > > > -----Original Message----- > > From: Daniel Povey [mailto:dp...@gm...] > > Sent: 2015-07-23 1636 > > To: Jan Trmal > > Cc: kal...@li... > > Subject: Re: [Kaldi-developers] Git upstream > > > > (keeping this discussion on kaldi-developers as I'm sure not everyone > > is a git expert and some might benefit), After doing that, how do I > > compare my current branch from the upstream to see how it differs? > > I tried doing things like > > git diff master remotes/upstream/master > > > > git checkout master; git diff upstream/master and even trying to > > create a branch reflecting upstream, by things like > > > > git branch remotes/upstream/master upstream-master > > > > but none of this worked. I guess there's something I'm missing. > > The state of my setup is as given below. > > Dan > > > > > > > > > > mac:kaldi-git: git branch -a > > * master > > remotes/origin/HEAD -> origin/master > > remotes/origin/master > > mac:kaldi-git: git remote -vv > > origin gi...@gi...:/danpovey/kaldi.git (fetch) origin > > gi...@gi...:/danpovey/kaldi.git (push) > > upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) > > upstream NOT-ALLOWED (push) > > mac:kaldi-git: > > > > > > On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: > > > > > > There is github doc that does the same (using fetch and merge) > > https://help.github.com/articles/syncing-a-fork/ > > y. > > > > > > On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> > > wrote: > > > > > > I usually do > > git checkout master # just to be sure I'm on master > > git pull upstream master # that will do fetch & merge > > > > # you can do also git pull --all which should give you also > > all branches, but that I dont use. > > > > y. > > > > On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey > > <dp...@gm...> wrote: > > > > > > I'm sure someone on this list will be able to > answer > > this easily, > > Suppose I have my own clone of > > kaldi-asr/kaldi.git at Sourceforge, as danielpovey/kaldi.git, and have > > checked it out using > > git clone > > gi...@gi...:/danielpovey/kaldi.git > > Suppose I then set the official kaldi-asr as the > > upstream, by doing > > git remote add upstream > > gi...@gi...:/kaldi-asr/kaldi.git > > > > so that > > git remote -vv > > shows me > > git remote -vv > > origin gi...@gi...:/danpovey/kaldi.git > > (fetch) > > origin gi...@gi...:/danpovey/kaldi.git > > (push) > > upstream > > gi...@gi...:/kaldi-asr/kaldi.git (fetch) > > upstream > > gi...@gi...:/kaldi-asr/kaldi.git (push) > > > > Then how do I merge changes from the upstream? > > > > We should have instructions on this somewhere. > > Dan > > > > > > > > > > ----------------------------------------------------------------------- > > - > > ------ > > > > _______________________________________________ > > Kaldi-developers mailing list > > Kal...@li... > > > > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > > > > > > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > -- Sincerely, Alexander |
|
From: Kirill K. <kir...@sm...> - 2015-07-24 02:43:04
|
Dan, I am suspecting a bit of misunderstanding here. I am not sure I am reading your intention here: $ git diff master remotes/upstream/master This compares the tip of your master branch with the tip of the remote branch. Generally, this comparison does not make much sense. You'll see your additions as '-', and master additions as a '+'. Then, you are not probably doing work on master anyway. Let's begin from the beginning. When you go 'git clone', you do not "check out;" rather you create *another repository* with its own set of branches. Git is distributed, and there is not a server-sandbox relationship; rather, the two are just two repos (with a lot of common history, of course), but none of these is "more important." *Important note 1*: Many people ask how do they keep their GitHub clone's master branch in synch with the "golden" master branch. The answer is: please do not. There is no point in spending your time on keeping two identical branches in sync! *Important note 2*: You do not need to involve your personal fork in development at all until you are ready to send a PR. So how you do the work, generally? You already have a repo with 2 remotes. This is what you need. origin = gi...@gi...:/danpovey/kaldi.git upstream = gi...@gi...:/kaldi-asr/kaldi.git Next, you want to design a feature. Just branch off the upstream/master, because this is where the most up-to-date code is: $ git fetch upstream $ git co upstream/master -b my-feature The 'git fetch' will fetch all commits that are not yet there in your local repo. The ref 'upstream/master' will point to the tip of the master branch. Work on your branch. Do commits on it once in a while. Maybe you even fetch the upstream again, so that upstream/master and my-feature diverge. This is ok. Now, we are back at diffing. The question "what is the difference between contents at points in history A and B" is not the best one, because the point B is often not well known. Subversion thinking goes like this: first you rebase your changes in sandbox on the trunk, then you do 'svn diff' which shows your changes only. If you are nimble enough, this is what you commit, if not, do the update again. In Git, the question is stated differently: "If I merge all changes from the branch F into branch M, what is the summary patch that I'll apply to M?" The answer is not identical, of course, assuming M has likely changed. But it is the most informative really. The way to see that diff is $ git diff upstream/master...my-feature (or simply "git diff upstream/master..." assuming you are on the my-feature branch) NB: This does not take the *current* state of upstream/master into account. The golden/master is only used to find the closest common history point, and the summary diff is given as the sum of commits from that point on your branch. For example, try $ git diff upstream/master...upstream/nnet3 This is the summary patch that "would be applied" (quotes because it does not work that way, this is only a way to think about it) to upstream/master if you merge upstream/nnet3 into it. But if you do (your initial idea) $ git diff upstream/master upstream/nnet3 $ git diff upstream/nnet3 upstream/master you'll see a *symmetrical* difference: the two diffs will just change signs. They are generally meaningless. Notice something cool? You do not use the master branch in your own repo! No point, really. Now, suppose you want to merge your work with a PR. This is how I do it: $ git fetch upstream $ git upstream/master -b testmerge --no-track $ git merge my-feature (--no-track is optional, as you'll kill the branch soon, but helps keep your config data tidy). At this point, you can run tests to make sure everything is ok. You can then push your feature branch to create a PR. $ git checkout my-feature $ git push origin HEAD This will create the branch in your own GitHub's repo, and you'll send the PR as the difference between kaldi-asr/kaldi:master and danpovey/kaldi:my-feature And I'll write a short doc on that tonight. I feel how painful the transition is. I'll put a draft on GitHub, and with somebodys help doxygenate it later. -kkm > -----Original Message----- > From: Daniel Povey [mailto:dp...@gm...] > Sent: 2015-07-23 1636 > To: Jan Trmal > Cc: kal...@li... > Subject: Re: [Kaldi-developers] Git upstream > > (keeping this discussion on kaldi-developers as I'm sure not everyone > is a git expert and some might benefit), After doing that, how do I > compare my current branch from the upstream to see how it differs? > I tried doing things like > git diff master remotes/upstream/master > > git checkout master; git diff upstream/master and even trying to > create a branch reflecting upstream, by things like > > git branch remotes/upstream/master upstream-master > > but none of this worked. I guess there's something I'm missing. > The state of my setup is as given below. > Dan > > > > > mac:kaldi-git: git branch -a > * master > remotes/origin/HEAD -> origin/master > remotes/origin/master > mac:kaldi-git: git remote -vv > origin gi...@gi...:/danpovey/kaldi.git (fetch) origin > gi...@gi...:/danpovey/kaldi.git (push) > upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) > upstream NOT-ALLOWED (push) > mac:kaldi-git: > > > On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: > > > There is github doc that does the same (using fetch and merge) > https://help.github.com/articles/syncing-a-fork/ > y. > > > On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> > wrote: > > > I usually do > git checkout master # just to be sure I'm on master > git pull upstream master # that will do fetch & merge > > # you can do also git pull --all which should give you also > all branches, but that I dont use. > > y. > > On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey > <dp...@gm...> wrote: > > > I'm sure someone on this list will be able to answer > this easily, > Suppose I have my own clone of > kaldi-asr/kaldi.git at Sourceforge, as danielpovey/kaldi.git, and have > checked it out using > git clone > gi...@gi...:/danielpovey/kaldi.git > Suppose I then set the official kaldi-asr as the > upstream, by doing > git remote add upstream > gi...@gi...:/kaldi-asr/kaldi.git > > so that > git remote -vv > shows me > git remote -vv > origin gi...@gi...:/danpovey/kaldi.git > (fetch) > origin gi...@gi...:/danpovey/kaldi.git > (push) > upstream > gi...@gi...:/kaldi-asr/kaldi.git (fetch) > upstream > gi...@gi...:/kaldi-asr/kaldi.git (push) > > Then how do I merge changes from the upstream? > > We should have instructions on this somewhere. > Dan > > > > > ----------------------------------------------------------------------- > - > ------ > > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > > > > |
|
From: Vijayaditya P. <p.v...@gm...> - 2015-07-23 23:50:55
|
Also you need not merge with local every time you want to compare. You can just do git fetch git diff master upstream/master On Thu, Jul 23, 2015 at 4:42 PM, Vijayaditya Peddinti < p.v...@gm...> wrote: > You can do > > git diff master upstream/master > > Vijay > > > On Thu, Jul 23, 2015 at 4:35 PM, Daniel Povey <dp...@gm...> wrote: > >> (keeping this discussion on kaldi-developers as I'm sure not everyone is >> a git expert and some might benefit), >> After doing that, how do I compare my current branch from the upstream to >> see how it differs? >> I tried doing things like >> git diff master remotes/upstream/master >> git checkout master; git diff upstream/master >> and even trying to create a branch reflecting upstream, by things like >> git branch remotes/upstream/master upstream-master >> >> but none of this worked. I guess there's something I'm missing. >> The state of my setup is as given below. >> Dan >> >> >> >> >> mac:kaldi-git: git branch -a >> * master >> remotes/origin/HEAD -> origin/master >> remotes/origin/master >> mac:kaldi-git: git remote -vv >> origin gi...@gi...:/danpovey/kaldi.git (fetch) >> origin gi...@gi...:/danpovey/kaldi.git (push) >> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >> upstream NOT-ALLOWED (push) >> mac:kaldi-git: >> >> >> On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: >> >>> There is github doc that does the same (using fetch and merge) >>> https://help.github.com/articles/syncing-a-fork/ >>> y. >>> >>> >>> On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> wrote: >>> >>>> I usually do >>>> git checkout master # just to be sure I'm on master >>>> git pull upstream master # that will do fetch & merge >>>> >>>> # you can do also git pull --all which should give you also all >>>> branches, but that I dont use. >>>> >>>> y. >>>> >>>> On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> wrote: >>>> >>>>> I'm sure someone on this list will be able to answer this easily, >>>>> Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as >>>>> danielpovey/kaldi.git, and have checked it out using >>>>> git clone gi...@gi...:/danielpovey/kaldi.git >>>>> Suppose I then set the official kaldi-asr as the upstream, by doing >>>>> git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git >>>>> so that >>>>> git remote -vv >>>>> shows me >>>>> git remote -vv >>>>> origin gi...@gi...:/danpovey/kaldi.git (fetch) >>>>> origin gi...@gi...:/danpovey/kaldi.git (push) >>>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >>>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (push) >>>>> >>>>> Then how do I merge changes from the upstream? >>>>> We should have instructions on this somewhere. >>>>> Dan >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> Kaldi-developers mailing list >>>>> Kal...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >>>>> >>>>> >>>> >>> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Kaldi-developers mailing list >> Kal...@li... >> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >> >> > |
|
From: Jan T. <jt...@gm...> - 2015-07-23 23:47:04
|
I don;t want to start a flame, but I find the git fairly inconsistent in the way how the individual commands expect parameters. Still learning y. On Thu, Jul 23, 2015 at 7:43 PM, Vijayaditya Peddinti < p.v...@gm...> wrote: > Also you need not merge with local every time you want to compare. > You can just do > > git fetch > git diff master upstream/master > > > > On Thu, Jul 23, 2015 at 4:42 PM, Vijayaditya Peddinti < > p.v...@gm...> wrote: > >> You can do >> >> git diff master upstream/master >> >> Vijay >> >> >> On Thu, Jul 23, 2015 at 4:35 PM, Daniel Povey <dp...@gm...> wrote: >> >>> (keeping this discussion on kaldi-developers as I'm sure not everyone is >>> a git expert and some might benefit), >>> After doing that, how do I compare my current branch from the upstream >>> to see how it differs? >>> I tried doing things like >>> git diff master remotes/upstream/master >>> git checkout master; git diff upstream/master >>> and even trying to create a branch reflecting upstream, by things like >>> git branch remotes/upstream/master upstream-master >>> >>> but none of this worked. I guess there's something I'm missing. >>> The state of my setup is as given below. >>> Dan >>> >>> >>> >>> >>> mac:kaldi-git: git branch -a >>> * master >>> remotes/origin/HEAD -> origin/master >>> remotes/origin/master >>> mac:kaldi-git: git remote -vv >>> origin gi...@gi...:/danpovey/kaldi.git (fetch) >>> origin gi...@gi...:/danpovey/kaldi.git (push) >>> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >>> upstream NOT-ALLOWED (push) >>> mac:kaldi-git: >>> >>> >>> On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: >>> >>>> There is github doc that does the same (using fetch and merge) >>>> https://help.github.com/articles/syncing-a-fork/ >>>> y. >>>> >>>> >>>> On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> wrote: >>>> >>>>> I usually do >>>>> git checkout master # just to be sure I'm on master >>>>> git pull upstream master # that will do fetch & merge >>>>> >>>>> # you can do also git pull --all which should give you also all >>>>> branches, but that I dont use. >>>>> >>>>> y. >>>>> >>>>> On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> >>>>> wrote: >>>>> >>>>>> I'm sure someone on this list will be able to answer this easily, >>>>>> Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as >>>>>> danielpovey/kaldi.git, and have checked it out using >>>>>> git clone gi...@gi...:/danielpovey/kaldi.git >>>>>> Suppose I then set the official kaldi-asr as the upstream, by doing >>>>>> git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git >>>>>> so that >>>>>> git remote -vv >>>>>> shows me >>>>>> git remote -vv >>>>>> origin gi...@gi...:/danpovey/kaldi.git (fetch) >>>>>> origin gi...@gi...:/danpovey/kaldi.git (push) >>>>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >>>>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (push) >>>>>> >>>>>> Then how do I merge changes from the upstream? >>>>>> We should have instructions on this somewhere. >>>>>> Dan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> Kaldi-developers mailing list >>>>>> Kal...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >>>>>> >>>>>> >>>>> >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Kaldi-developers mailing list >>> Kal...@li... >>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >>> >>> >> > |
|
From: Jan T. <jt...@gm...> - 2015-07-23 23:43:31
|
Hmm, I think that if you do "pull", the changes will get automatically merged. Unless you did it, you can do git fetch upstream git diff master upstream/master if you did "git pull", the the chances are the changes were merged automatically and you should use this git diff HEAD^ HEAD #compare current version with previous But I'm not 100 % sure in this... there might be some gotchas.. y. On Thu, Jul 23, 2015 at 7:35 PM, Daniel Povey <dp...@gm...> wrote: > (keeping this discussion on kaldi-developers as I'm sure not everyone is a > git expert and some might benefit), > After doing that, how do I compare my current branch from the upstream to > see how it differs? > I tried doing things like > git diff master remotes/upstream/master > git checkout master; git diff upstream/master > and even trying to create a branch reflecting upstream, by things like > git branch remotes/upstream/master upstream-master > > but none of this worked. I guess there's something I'm missing. > The state of my setup is as given below. > Dan > > > > > mac:kaldi-git: git branch -a > * master > remotes/origin/HEAD -> origin/master > remotes/origin/master > mac:kaldi-git: git remote -vv > origin gi...@gi...:/danpovey/kaldi.git (fetch) > origin gi...@gi...:/danpovey/kaldi.git (push) > upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) > upstream NOT-ALLOWED (push) > mac:kaldi-git: > > > On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: > >> There is github doc that does the same (using fetch and merge) >> https://help.github.com/articles/syncing-a-fork/ >> y. >> >> >> On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> wrote: >> >>> I usually do >>> git checkout master # just to be sure I'm on master >>> git pull upstream master # that will do fetch & merge >>> >>> # you can do also git pull --all which should give you also all >>> branches, but that I dont use. >>> >>> y. >>> >>> On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> wrote: >>> >>>> I'm sure someone on this list will be able to answer this easily, >>>> Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as >>>> danielpovey/kaldi.git, and have checked it out using >>>> git clone gi...@gi...:/danielpovey/kaldi.git >>>> Suppose I then set the official kaldi-asr as the upstream, by doing >>>> git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git >>>> so that >>>> git remote -vv >>>> shows me >>>> git remote -vv >>>> origin gi...@gi...:/danpovey/kaldi.git (fetch) >>>> origin gi...@gi...:/danpovey/kaldi.git (push) >>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (push) >>>> >>>> Then how do I merge changes from the upstream? >>>> We should have instructions on this somewhere. >>>> Dan >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Kaldi-developers mailing list >>>> Kal...@li... >>>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >>>> >>>> >>> >> > |
|
From: Vijayaditya P. <p.v...@gm...> - 2015-07-23 23:43:18
|
You can do git diff master upstream/master Vijay On Thu, Jul 23, 2015 at 4:35 PM, Daniel Povey <dp...@gm...> wrote: > (keeping this discussion on kaldi-developers as I'm sure not everyone is a > git expert and some might benefit), > After doing that, how do I compare my current branch from the upstream to > see how it differs? > I tried doing things like > git diff master remotes/upstream/master > git checkout master; git diff upstream/master > and even trying to create a branch reflecting upstream, by things like > git branch remotes/upstream/master upstream-master > > but none of this worked. I guess there's something I'm missing. > The state of my setup is as given below. > Dan > > > > > mac:kaldi-git: git branch -a > * master > remotes/origin/HEAD -> origin/master > remotes/origin/master > mac:kaldi-git: git remote -vv > origin gi...@gi...:/danpovey/kaldi.git (fetch) > origin gi...@gi...:/danpovey/kaldi.git (push) > upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) > upstream NOT-ALLOWED (push) > mac:kaldi-git: > > > On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: > >> There is github doc that does the same (using fetch and merge) >> https://help.github.com/articles/syncing-a-fork/ >> y. >> >> >> On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> wrote: >> >>> I usually do >>> git checkout master # just to be sure I'm on master >>> git pull upstream master # that will do fetch & merge >>> >>> # you can do also git pull --all which should give you also all >>> branches, but that I dont use. >>> >>> y. >>> >>> On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> wrote: >>> >>>> I'm sure someone on this list will be able to answer this easily, >>>> Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as >>>> danielpovey/kaldi.git, and have checked it out using >>>> git clone gi...@gi...:/danielpovey/kaldi.git >>>> Suppose I then set the official kaldi-asr as the upstream, by doing >>>> git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git >>>> so that >>>> git remote -vv >>>> shows me >>>> git remote -vv >>>> origin gi...@gi...:/danpovey/kaldi.git (fetch) >>>> origin gi...@gi...:/danpovey/kaldi.git (push) >>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >>>> upstream gi...@gi...:/kaldi-asr/kaldi.git (push) >>>> >>>> Then how do I merge changes from the upstream? >>>> We should have instructions on this somewhere. >>>> Dan >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Kaldi-developers mailing list >>>> Kal...@li... >>>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >>>> >>>> >>> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > |
|
From: Daniel P. <dp...@gm...> - 2015-07-23 23:36:01
|
(keeping this discussion on kaldi-developers as I'm sure not everyone is a git expert and some might benefit), After doing that, how do I compare my current branch from the upstream to see how it differs? I tried doing things like git diff master remotes/upstream/master git checkout master; git diff upstream/master and even trying to create a branch reflecting upstream, by things like git branch remotes/upstream/master upstream-master but none of this worked. I guess there's something I'm missing. The state of my setup is as given below. Dan mac:kaldi-git: git branch -a * master remotes/origin/HEAD -> origin/master remotes/origin/master mac:kaldi-git: git remote -vv origin gi...@gi...:/danpovey/kaldi.git (fetch) origin gi...@gi...:/danpovey/kaldi.git (push) upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) upstream NOT-ALLOWED (push) mac:kaldi-git: On Thu, Jul 23, 2015 at 4:27 PM, Jan Trmal <jt...@gm...> wrote: > There is github doc that does the same (using fetch and merge) > https://help.github.com/articles/syncing-a-fork/ > y. > > > On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> wrote: > >> I usually do >> git checkout master # just to be sure I'm on master >> git pull upstream master # that will do fetch & merge >> >> # you can do also git pull --all which should give you also all branches, >> but that I dont use. >> >> y. >> >> On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> wrote: >> >>> I'm sure someone on this list will be able to answer this easily, >>> Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as >>> danielpovey/kaldi.git, and have checked it out using >>> git clone gi...@gi...:/danielpovey/kaldi.git >>> Suppose I then set the official kaldi-asr as the upstream, by doing >>> git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git >>> so that >>> git remote -vv >>> shows me >>> git remote -vv >>> origin gi...@gi...:/danpovey/kaldi.git (fetch) >>> origin gi...@gi...:/danpovey/kaldi.git (push) >>> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >>> upstream gi...@gi...:/kaldi-asr/kaldi.git (push) >>> >>> Then how do I merge changes from the upstream? >>> We should have instructions on this somewhere. >>> Dan >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Kaldi-developers mailing list >>> Kal...@li... >>> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >>> >>> >> > |
|
From: Jan T. <jt...@gm...> - 2015-07-23 23:27:37
|
There is github doc that does the same (using fetch and merge) https://help.github.com/articles/syncing-a-fork/ y. On Thu, Jul 23, 2015 at 7:24 PM, Jan Trmal <jt...@gm...> wrote: > I usually do > git checkout master # just to be sure I'm on master > git pull upstream master # that will do fetch & merge > > # you can do also git pull --all which should give you also all branches, > but that I dont use. > > y. > > On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> wrote: > >> I'm sure someone on this list will be able to answer this easily, >> Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as >> danielpovey/kaldi.git, and have checked it out using >> git clone gi...@gi...:/danielpovey/kaldi.git >> Suppose I then set the official kaldi-asr as the upstream, by doing >> git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git >> so that >> git remote -vv >> shows me >> git remote -vv >> origin gi...@gi...:/danpovey/kaldi.git (fetch) >> origin gi...@gi...:/danpovey/kaldi.git (push) >> upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) >> upstream gi...@gi...:/kaldi-asr/kaldi.git (push) >> >> Then how do I merge changes from the upstream? >> We should have instructions on this somewhere. >> Dan >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Kaldi-developers mailing list >> Kal...@li... >> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >> >> > |
|
From: Jan T. <jt...@gm...> - 2015-07-23 23:24:32
|
I usually do git checkout master # just to be sure I'm on master git pull upstream master # that will do fetch & merge # you can do also git pull --all which should give you also all branches, but that I dont use. y. On Thu, Jul 23, 2015 at 7:13 PM, Daniel Povey <dp...@gm...> wrote: > I'm sure someone on this list will be able to answer this easily, > Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as > danielpovey/kaldi.git, and have checked it out using > git clone gi...@gi...:/danielpovey/kaldi.git > Suppose I then set the official kaldi-asr as the upstream, by doing > git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git > so that > git remote -vv > shows me > git remote -vv > origin gi...@gi...:/danpovey/kaldi.git (fetch) > origin gi...@gi...:/danpovey/kaldi.git (push) > upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) > upstream gi...@gi...:/kaldi-asr/kaldi.git (push) > > Then how do I merge changes from the upstream? > We should have instructions on this somewhere. > Dan > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > |
|
From: Ondrej P. <ond...@gm...> - 2015-07-23 23:22:59
|
git checkout master # to be sure you are on the local master branch git pull upstream master # git fetch and git merge upstream/master in one command On Fri, Jul 24, 2015 at 12:13 AM, Daniel Povey <dp...@gm...> wrote: > I'm sure someone on this list will be able to answer this easily, > Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as > danielpovey/kaldi.git, and have checked it out using > git clone gi...@gi...:/danielpovey/kaldi.git > Suppose I then set the official kaldi-asr as the upstream, by doing > git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git > so that > git remote -vv > shows me > git remote -vv > origin gi...@gi...:/danpovey/kaldi.git (fetch) > origin gi...@gi...:/danpovey/kaldi.git (push) > upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) > upstream gi...@gi...:/kaldi-asr/kaldi.git (push) > > Then how do I merge changes from the upstream? > We should have instructions on this somewhere. > Dan > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > -- Ondřej Plátek, +420 737 758 650, skype:ondrejplatek, ond...@gm... |
|
From: Daniel P. <dp...@gm...> - 2015-07-23 23:13:53
|
I'm sure someone on this list will be able to answer this easily, Suppose I have my own clone of kaldi-asr/kaldi.git at Sourceforge, as danielpovey/kaldi.git, and have checked it out using git clone gi...@gi...:/danielpovey/kaldi.git Suppose I then set the official kaldi-asr as the upstream, by doing git remote add upstream gi...@gi...:/kaldi-asr/kaldi.git so that git remote -vv shows me git remote -vv origin gi...@gi...:/danpovey/kaldi.git (fetch) origin gi...@gi...:/danpovey/kaldi.git (push) upstream gi...@gi...:/kaldi-asr/kaldi.git (fetch) upstream gi...@gi...:/kaldi-asr/kaldi.git (push) Then how do I merge changes from the upstream? We should have instructions on this somewhere. Dan |
|
From: Jan T. <jt...@gm...> - 2015-07-23 01:42:24
|
If the web interface does not work (for whatever reason), you can also subscribe using an e-mail. Just send an empty e-mail to the following addresses kal...@go... kal...@go... and you should receive a welcome e-mail shortly afterwards. NB: I tried signing up using several e-mails and not all were willing to accept the aforementioned addresses as valid. Gmail should be ok. In case of problems, feel free to e-mail me directly (jt...@gm...) and I will subscribe you manually. y. On Wed, Jul 22, 2015 at 12:04 PM, Jan Trmal <jt...@gm...> wrote: > All, > we are phasing out using the sf.net mailing lists and moving to > googlegroups.com. > You are welcome to join us. > Further info here: http://kaldi-asr.org/forums.html > > yenda > |
|
From: Jan T. <jt...@gm...> - 2015-07-22 16:04:25
|
All, we are phasing out using the sf.net mailing lists and moving to googlegroups.com. You are welcome to join us. Further info here: http://kaldi-asr.org/forums.html yenda |
|
From: Cemil D. <cem...@gm...> - 2015-07-15 20:17:09
|
Yes, I am using CUDA. I am using nvidia-smi and GPU utilizaiton is seen. Although, TITAN X has 12 GB memory, only 300 MB of it is used by nnet trainer process. On Wed, Jul 15, 2015 at 7:04 PM, Jan Trmal <jt...@gm...> wrote: > Are you sure you are using CUDA? You have to enable the support > manually when running the kaldi configure script. As you have gaming cards, > nvidia-smi won't probably display GPU utilization. You can have a look at > the temperature of the cards to verify the GPUs are used. > Expect ~ 4 times longer time for the ensemble training than for the > "normal" training. > y. > > On Wed, Jul 15, 2015 at 5:10 AM, Cemil Demir <cem...@gm...> > wrote: > >> Hi, >> >> I have a workstation which have 4 NVIDIA TITAN X GPU card. >> >> I want to train a DNN model using egs/babel/s5c recipe. I am using >> "run-2a-nnet-ensemble-gpu.sh" script. >> >> When I use "run-2a-nnet-gpu.sh" script, the accuracy is below as compared >> to sgmm-mmi case. Therefore I >> >> Total amount of training data is 13 hours. >> want to use "ensemble" version. >> >> Training takes about 35 hours. I think, it is too slow. >> >> Could give me any suggestion to speed up training? >> >> İt is a little bit urgent for me. >> >> Thank you. >> >> -- >> Cemil Demir >> >> cem...@gm... >> >> >> ------------------------------------------------------------------------------ >> Don't Limit Your Business. Reach for the Cloud. >> GigeNET's Cloud Solutions provide you with the tools and support that >> you need to offload your IT needs and focus on growing your business. >> Configured For All Businesses. Start Your Cloud Today. >> https://www.gigenetcloud.com/ >> _______________________________________________ >> Kaldi-developers mailing list >> Kal...@li... >> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >> >> > -- Cemil Demir cem...@gm... |
|
From: Daniel P. <dp...@gm...> - 2015-07-15 17:47:19
|
Also, make sure the different jobs are using different GPUs. Setting to exclusive mode (nvidia-smi -c 1) will help. Dan On Wed, Jul 15, 2015 at 9:04 AM, Jan Trmal <jt...@gm...> wrote: > Are you sure you are using CUDA? You have to enable the support manually > when running the kaldi configure script. As you have gaming cards, > nvidia-smi won't probably display GPU utilization. You can have a look at > the temperature of the cards to verify the GPUs are used. > Expect ~ 4 times longer time for the ensemble training than for the "normal" > training. > y. > > On Wed, Jul 15, 2015 at 5:10 AM, Cemil Demir <cem...@gm...> wrote: >> >> Hi, >> >> I have a workstation which have 4 NVIDIA TITAN X GPU card. >> >> I want to train a DNN model using egs/babel/s5c recipe. I am using >> "run-2a-nnet-ensemble-gpu.sh" script. >> >> When I use "run-2a-nnet-gpu.sh" script, the accuracy is below as compared >> to sgmm-mmi case. Therefore I >> >> Total amount of training data is 13 hours. >> want to use "ensemble" version. >> >> Training takes about 35 hours. I think, it is too slow. >> >> Could give me any suggestion to speed up training? >> >> İt is a little bit urgent for me. >> >> Thank you. >> >> -- >> Cemil Demir >> >> cem...@gm... >> >> >> ------------------------------------------------------------------------------ >> Don't Limit Your Business. Reach for the Cloud. >> GigeNET's Cloud Solutions provide you with the tools and support that >> you need to offload your IT needs and focus on growing your business. >> Configured For All Businesses. Start Your Cloud Today. >> https://www.gigenetcloud.com/ >> _______________________________________________ >> Kaldi-developers mailing list >> Kal...@li... >> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >> > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > |
|
From: Jan T. <jt...@gm...> - 2015-07-15 16:04:07
|
Are you sure you are using CUDA? You have to enable the support manually when running the kaldi configure script. As you have gaming cards, nvidia-smi won't probably display GPU utilization. You can have a look at the temperature of the cards to verify the GPUs are used. Expect ~ 4 times longer time for the ensemble training than for the "normal" training. y. On Wed, Jul 15, 2015 at 5:10 AM, Cemil Demir <cem...@gm...> wrote: > Hi, > > I have a workstation which have 4 NVIDIA TITAN X GPU card. > > I want to train a DNN model using egs/babel/s5c recipe. I am using > "run-2a-nnet-ensemble-gpu.sh" script. > > When I use "run-2a-nnet-gpu.sh" script, the accuracy is below as compared > to sgmm-mmi case. Therefore I > > Total amount of training data is 13 hours. > want to use "ensemble" version. > > Training takes about 35 hours. I think, it is too slow. > > Could give me any suggestion to speed up training? > > İt is a little bit urgent for me. > > Thank you. > > -- > Cemil Demir > > cem...@gm... > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > Kaldi-developers mailing list > Kal...@li... > https://lists.sourceforge.net/lists/listinfo/kaldi-developers > > |
|
From: Cemil D. <cem...@gm...> - 2015-07-15 09:10:49
|
Hi, I have a workstation which have 4 NVIDIA TITAN X GPU card. I want to train a DNN model using egs/babel/s5c recipe. I am using "run-2a-nnet-ensemble-gpu.sh" script. When I use "run-2a-nnet-gpu.sh" script, the accuracy is below as compared to sgmm-mmi case. Therefore I Total amount of training data is 13 hours. want to use "ensemble" version. Training takes about 35 hours. I think, it is too slow. Could give me any suggestion to speed up training? İt is a little bit urgent for me. Thank you. -- Cemil Demir cem...@gm... |
|
From: Jan T. <jt...@gm...> - 2015-07-13 17:22:39
|
And what does it do? Asking this way you won't get anywhere.
y.
On Mon, Jul 13, 2015 at 10:59 AM, azin fantastice <fan...@gm...>
wrote:
> Hello
> I have a problem with Installation for
> C:/cygwin/home/Administrator/kaldi-trunk/tools/INSTALL ;Please help me.
> I run the program to step 2 and problem is in running ''for'' loop.
>
>
> for dir in openfst-1.3.2/{src/,}include/fst; do
> ( [ -d $dir ] && cd $dir && patch -p0 -N <../../../../openfst.patch )
> done
>
>
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Kaldi-developers mailing list
> Kal...@li...
> https://lists.sourceforge.net/lists/listinfo/kaldi-developers
>
>
|
|
From: Daniel P. <dp...@gm...> - 2015-07-13 17:20:56
|
Please don't say you have a problem without showing the error message.
It worries me a little that you are showing the DOS-style paths-
perhaps you don't realize that you need to run all this from the
Cywgin shell? Best to use UNIX-style paths.
You may need to do a tutorial on UNIX shell before attempting to use Kaldi.
Dan
On Mon, Jul 13, 2015 at 7:59 AM, azin fantastice
<fan...@gm...> wrote:
> Hello
> I have a problem with Installation for
> C:/cygwin/home/Administrator/kaldi-trunk/tools/INSTALL ;Please help me.
> I run the program to step 2 and problem is in running ''for'' loop.
>
>
> for dir in openfst-1.3.2/{src/,}include/fst; do
> ( [ -d $dir ] && cd $dir && patch -p0 -N <../../../../openfst.patch )
> done
>
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Kaldi-developers mailing list
> Kal...@li...
> https://lists.sourceforge.net/lists/listinfo/kaldi-developers
>
|
|
From: azin f. <fan...@gm...> - 2015-07-13 14:59:29
|
Hello
I have a problem with Installation for
C:/cygwin/home/Administrator/kaldi-trunk/tools/INSTALL ;Please help me.
I run the program to step 2 and problem is in running ''for'' loop.
for dir in openfst-1.3.2/{src/,}include/fst; do
( [ -d $dir ] && cd $dir && patch -p0 -N <../../../../openfst.patch )
done
|
23 messages has been excluded from this view by a project administrator.