vec] ▪ h/c: [num_layer, b, h] ▪ out: [seq, b, h] nn.LSTM nn.LSTMCell ▪ __init__ LSTMCell.forward() ▪ ht, ct = lstmcell(xt, [ht_1, ct_1]) ▪ xt: [b, vec] ▪ ht/ct: [b, h] Single layer Two Layers 下一课时

RNN Layer使用 主讲人：龙良曲 Folded model feature ??@??ℎ + ℎ?@?ℎℎ [0,0,0 … ] x: ??? ???, ????ℎ, ??????? ??? ????ℎ, ??????? ??? @[ℎ????? ???, ??????? ???]?+ ????ℎ, ℎ????? ??? @ ℎ????? ???, ℎ????? ??? ? layers, b, h dim] ▪ out: [seq len, b, h dim] Single layer RNN feature ??@??ℎ 1 + ℎ? 1@?ℎℎ 1 [0,0,0 … ] ℎ? 1@??ℎ 2 + ℎ? 2@?ℎℎ 2 [0,0,0 … ] 2 layer RNN [T, b, h_dim], [layers, b, h_dim] nn.RNNCell

API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 36 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 29. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 36 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 29. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 34 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 27. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 34 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 27. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 34 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 27. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 36 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 29. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 36 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 29. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation

API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3.2 Common Python bindings layer . . . . . . . . . . . . . . . . . . . . . . 39 2.3.3 C++ COM API . . . . . . . . . . . . . . . . process of being added to VirtualBox. What is primarily of interest for purposes of the SDK is the API layer block that sits on top of all the previously mentioned blocks. This API, which we call the “Main API” page 31. b) Alternatively, you can use the web service directly, without the object-oriented client layer. We shall refer to this as the “raw web service”. You will then have neither native object orientation