Skip to content

  • 体验新版
    • 正在加载...
  • 登录
  • PaddlePaddle
  • Paddle
  • Issue
  • #3076

P
Paddle
  • 项目概览

PaddlePaddle / Paddle
大约 2 年 前同步成功

通知 2325
Star 20933
Fork 5424
  • 代码
    • 文件
    • 提交
    • 分支
    • Tags
    • 贡献者
    • 分支图
    • Diff
  • Issue 1423
    • 列表
    • 看板
    • 标记
    • 里程碑
  • 合并请求 543
  • Wiki 0
    • Wiki
  • 分析
    • 仓库
    • DevOps
  • 项目成员
  • Pages
P
Paddle
  • 项目概览
    • 项目概览
    • 详情
    • 发布
  • 仓库
    • 仓库
    • 文件
    • 提交
    • 分支
    • 标签
    • 贡献者
    • 分支图
    • 比较
  • Issue 1,423
    • Issue 1,423
    • 列表
    • 看板
    • 标记
    • 里程碑
  • 合并请求 543
    • 合并请求 543
  • Pages
  • 分析
    • 分析
    • 仓库分析
    • DevOps
  • Wiki 0
    • Wiki
  • 成员
    • 成员
  • 收起侧边栏
  • 动态
  • 分支图
  • 创建新Issue
  • 提交
  • Issue看板
已关闭
开放中
Opened 7月 26, 2017 by saxon_zh@saxon_zhGuest

Summary of debugging WarpCTCLayer

Created by: pkuyym

I often encounter inf cost when training mandanrin data using deep speech2 (GPU version). It seems that WarpCTCLayer may have potential numerical problems. So, @qingqing01 and I have been tried to figure out what leads to inf. Considering that inf doesn't appear regularly, we save the two inputs of WarpCTCLayer using printValueString firstly, then parse and load the saved context in debugging phase. However, loading the exception context only increases probability of inf which means that regular reproduction is not assured.

For inf, we find two suspicious snippets

seq2batchPadding

Please go to seq2batchPadding to see details. We detect -inf in batchValue_ just before calling hl_warpctc_compute_loss, since that seq2batchPadding is the only function in which batchValue is modified except resizeOrCreate. So we consider seq2batchPadding as a suspicious reason.

status: Fixed by #3105

compute_probs_kernel

We also dig into wrap ctc kernal and find that compute_probs_kernel will appear 0 after exponent operation. Location of exponent operation snnipet is at ctc_helper::exponential, this leads to 0 contained in probs_. Unfortunately, probs_ will be passed into compute_alpha_kernel and illegal operation log(0) is detected at line167 and line191 in compute_alpha_kernel. We also consider this as a suspicious reason.

status: Fixed by #5

Besides, we also encounter a validataion error, details are listed below:

F0726 17:18:41.516580 15765 hl_warpctc_wrap.cc:131] Check failed: CTC_STATUS_SUCCESS == dynload::compute_ctc_loss(batchInput, batchGrad, cpuLabels, cpuLabelLengths, cpuInputLeng ths, numClasses, numSequences, cpuCosts, workspace, *options) (0 vs. 3) warp-ctc [version 2] Error: execution failed-

This fatal exception is throwed by here. The reason hasn't been figured out.

指派人
分配到
无
里程碑
无
分配里程碑
工时统计
无
截止日期
无
标识: paddlepaddle/Paddle#3076
渝ICP备2023009037号

京公网安备11010502055752号

网络110报警服务 Powered by GitLab CE v13.7
开源知识
Git 入门 Pro Git 电子书 在线学 Git
Markdown 基础入门 IT 技术知识开源图谱
帮助
使用手册 反馈建议 博客
《GitCode 隐私声明》 《GitCode 服务条款》 关于GitCode
Powered by GitLab CE v13.7