Skip to content
项目
群组
代码片段
帮助
当前项目
正在载入...
登录 / 注册
切换导航面板
P
pytensor
项目
项目
详情
活动
周期分析
仓库
仓库
文件
提交
分支
标签
贡献者
图表
比较
统计图
议题
0
议题
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
CI / CD
CI / CD
流水线
作业
日程
统计图
Wiki
Wiki
代码片段
代码片段
成员
成员
折叠边栏
关闭边栏
活动
图像
聊天
创建新问题
作业
提交
问题看板
Open sidebar
testgroup
pytensor
Commits
c55bf98d
提交
c55bf98d
authored
3月 25, 2009
作者:
James Bergstra
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
had another crack at the find_bad_optimizations algorithm in DebugMode
上级
0bb038d7
显示空白字符变更
内嵌
并排
正在显示
1 个修改的文件
包含
50 行增加
和
4 行删除
+50
-4
debugmode.py
theano/compile/debugmode.py
+50
-4
没有找到文件。
theano/compile/debugmode.py
浏览文件 @
c55bf98d
...
@@ -285,9 +285,11 @@ def _lessbroken_deepcopy(a):
...
@@ -285,9 +285,11 @@ def _lessbroken_deepcopy(a):
return
rval
return
rval
def
_find_bad_optimizations0
(
order
,
reasons
,
r_vals
):
def
_find_bad_optimizations0
(
order
,
reasons
,
r_vals
):
"""Use a simple algorithm to find broken optimizations. This algorithm is simple to
"""Use a simple algorithm to find broken optimizations.
understand, but sometimes when there's a problem it identifies the wrong optimization as
the culprit.
This algorithm is simple to understand, but sometimes when there's a problem it identifies
the wrong optimization as the culprit. The problem stems from the fact that results are
not evaluated in chronological order (looking at when they were introduced to the graph).
"""
"""
# iterate over variables looking for values that don't match the values of the
# iterate over variables looking for values that don't match the values of the
# variables they replaced. This is the sign of a broken optimization.
# variables they replaced. This is the sign of a broken optimization.
...
@@ -357,8 +359,52 @@ def _find_bad_optimizations1(order, reasons, r_vals):
...
@@ -357,8 +359,52 @@ def _find_bad_optimizations1(order, reasons, r_vals):
print
first_broken_set
print
first_broken_set
raise
Exception
(
'broken'
)
raise
Exception
(
'broken'
)
def
_find_bad_optimizations2
(
order
,
reasons
,
r_vals
):
"""Use a simple algorithm to find broken optimizations.
This algorithm is simple to understand, but sometimes when there's a problem it identifies
the wrong optimization as the culprit. The problem stems from the fact that results are
not evaluated in chronological order (looking at when they were introduced to the graph).
"""
checked_variables
=
set
()
def
check_variable_norec
(
new_r
):
"""Verify that `r` has the same value as the results it replaces """
for
reason
,
r
,
old_graph_str
,
new_graph_str
in
reasons
[
new_r
]:
new_r_val
=
r_vals
[
new_r
]
r_val
=
r_vals
[
r
]
if
(
r
.
type
!=
new_r
.
type
)
or
(
not
r
.
type
.
values_eq_approx
(
r_val
,
new_r_val
)):
raise
BadOptimization
(
old_r
=
r
,
new_r
=
new_r
,
old_r_val
=
r_val
,
new_r_val
=
new_r_val
,
reason
=
reason
,
old_graph
=
old_graph_str
,
new_graph
=
new_graph_str
)
def
check_variable
(
r
):
if
r
in
checked_variables
:
return
# (recursively) first check all the variables that could make r look bad:
for
var_that_could_make_r_look_bad
in
\
[
old_r
for
(
reason
,
old_r
,
olds
,
news
)
in
reasons
[
r
]]
\
+
([]
if
(
None
is
r
.
owner
)
else
r
.
owner
.
inputs
):
check_variable
(
var_that_could_make_r_look_bad
)
check_variable_norec
(
r
)
checked_variables
.
add
(
r
)
# iterate over variables looking for values that don't match the values of the
# variables they replaced. This is the sign of a broken optimization.
for
i
,
node
in
enumerate
(
order
):
for
new_r
in
node
.
outputs
:
check_variable
(
new_r
)
_find_bad_optimizations
=
_find_bad_optimizations2
class
_EnvEvent
(
object
):
class
_EnvEvent
(
object
):
"""A record of an event in the life of an Env.
"""A record of an event in the life of an Env.
...
@@ -737,7 +783,7 @@ class _Linker(gof.link.LocalLinker):
...
@@ -737,7 +783,7 @@ class _Linker(gof.link.LocalLinker):
except
:
except
:
raise_with_op
(
node
)
raise_with_op
(
node
)
_find_bad_optimizations
0
(
order
,
env
.
equivalence_tracker
.
reasons
,
r_vals
)
_find_bad_optimizations
(
order
,
env
.
equivalence_tracker
.
reasons
,
r_vals
)
#####
#####
# Postcondition: the input and output variables are in the storage map, nothing more
# Postcondition: the input and output variables are in the storage map, nothing more
...
...
编写
预览
Markdown
格式
0%
重试
或
添加新文件
添加附件
取消
您添加了
0
人
到此讨论。请谨慎行事。
请先完成此评论的编辑!
取消
请
注册
或者
登录
后发表评论