Skip to content
项目
群组
代码片段
帮助
当前项目
正在载入...
登录 / 注册
切换导航面板
P
pytensor
项目
项目
详情
活动
周期分析
仓库
仓库
文件
提交
分支
标签
贡献者
图表
比较
统计图
议题
0
议题
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
CI / CD
CI / CD
流水线
作业
日程
统计图
Wiki
Wiki
代码片段
代码片段
成员
成员
折叠边栏
关闭边栏
活动
图像
聊天
创建新问题
作业
提交
问题看板
Open sidebar
testgroup
pytensor
Commits
69a9a498
提交
69a9a498
authored
8月 21, 2014
作者:
Frederic Bastien
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Some update to pres.
上级
f914a40c
隐藏空白字符变更
内嵌
并排
正在显示
1 个修改的文件
包含
58 行增加
和
7 行删除
+58
-7
presentation.tex
doc/omlw2014/presentation.tex
+58
-7
没有找到文件。
doc/omlw2014/presentation.tex
浏览文件 @
69a9a498
...
...
@@ -129,21 +129,19 @@ Montréal, Canada \newline
\begin{itemize}
\item
Syntax as close to NumPy as possible
\item
Compiles most common expressions to C for CPU and GPU
\item
Limited expressivity means
lots of opportunities for expression-level
optimizations
\item
Limited expressivity means
more opportunities
optimizations
\begin{itemize}
\item
No subroutines -> global optimization
\item
Strongly typed -> compiles to machine instructions
\item
Array oriented -> easy parallelism
\item
Support for looping and branching in expressions
\end{itemize}
\item
Expression substitution optimizations automatically draw
on many back-end
technologies for best performance.
\item
Automatic speed and stability optimizations
\item
Can reuse other
technologies for best performance.
\begin{itemize}
\item
BLAS, SciPy, Cython, CUDA
\item
Slower fallbacks always available
\item
BLAS, SciPy, Cython, Numba, PyCUDA, CUDA
\end{itemize}
\item
Automatic differentiation and R op
\item
Sparse matrices
\end{itemize}
\end{frame}
...
...
@@ -166,11 +164,32 @@ Montréal, Canada \newline
\item
Experiments can be specified through a YAML config file, or by a Python script
\item
Scripts for visualizing weights, plot monitored values
\end{itemize}
\end{frame}
\begin{frame}
{
Goal of the stack
}
You can't have your cake and eat it too.
\newline
We want our cake and eat it too.???
\newline
Target the holy grail:
\begin{bf}
fast to develop
\end{bf}
and
\begin{bf}
fast to run
\end{bf}
.
\end{frame}
\begin{frame}
{
libgpuarray
}
GOAL: A common GPU n dimensions array that can be reused by all projects. It support CUDA and OpenCL.
\newline
\newline
Motivation:
\begin{itemize}
\item
Currently there are at least 6 different gpu arrays in python
\begin{itemize}
\item
CudaNdarray(Theano), GPUArray(pycuda), CUDAMatrix(cudamat), GPUArray(pyopencl), Clyther, Copperhead, ...
\item
There are even more if we include other languages.
\end{itemize}
\item
They are incompatible
\begin{itemize}
\item
None have the same properties and interface.
\end{itemize}
\item
All of them are a subset of numpy.ndarray on the gpu!
\end{itemize}
\end{frame}
...
...
@@ -264,13 +283,45 @@ print f([0, 1, 2])
\end{frame}
\section
{
libgpuarray
}
\begin{frame}
{
libgpuarray details
}
\begin{frame}
{
libgpuarray: Design Goals
}
\begin{itemize}
\item
Have the base object in C to allow collaboration with more projects.
\begin{itemize}
\item
We want people from C, C++, ruby, R, ... all use the same base GPU ndarray.
\end{itemize}
\item
Be compatible with CUDA and OpenCL.
\item
Not too simple, (don’t support just matrix).
\item
But still easy to develop new code that support only a few memory layout.
\begin{itemize}
\item
This ease the development of new code.
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}
{
Project status?
}
\begin{itemize}
\item
Usable directly, but not all implementation available.
\item
Multiple GPU work.
\item
Is the next GPU array container for Theano and is working.
\begin{itemize}
\item
Not all Theano implementation available now.
\item
OpenCL miss more implementation.
\item
Multiple GPU on the way.
\end{itemize}
\item
Web site:
\url
{
http://deeplearning.net/software/libgpuarray/
}
\end{itemize}
\end{frame}
\section
{
sharing
}
\begin{frame}
{
How can we do it?
}
\only
<1>
{
License: Suggest BSD as it is used by many software in our field.
}
\only
<1>
{
Common license help share code.
}
\only
<1>
{
Don't forget to copy the copyright notice when you copy code.
}
\only
<2>
{
Common base object!
\begin{bf}
libgpuarray
\end{bf}
}
\only
<3>
{
Otherwise: put important implementation(e.g convolution) in separate file and use raw ptr/shape/strides as inputs? Doc that interface.
}
\only
<4>
{
acknowled reuse
\begin{bf}
in section on web site
\end{bf}
AND
\begin{bf}
in paper
\end{bf}
about the software we reuse! (and use too)
}
\end{frame}
\begin{frame}
{
OLD STUFF Why do we need this?
}
...
...
编写
预览
Markdown
格式
0%
重试
或
添加新文件
添加附件
取消
您添加了
0
人
到此讨论。请谨慎行事。
请先完成此评论的编辑!
取消
请
注册
或者
登录
后发表评论