From: Hyung-Kyu Choi Date: Thu, 22 Mar 2018 01:09:49 +0000 (+0900) Subject: Apply review feedback X-Git-Tag: 0.1~634 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=eca3535fec23841cecd7246ba6cf16e2bb5b7015;p=platform%2Fcore%2Fml%2Fnnfw.git Apply review feedback - Apply review feedback on README.md Signed-off-by: Hyung-Kyu Choi --- diff --git a/src/runtime/ref/README.md b/src/runtime/ref/README.md index bd51cbf..27b9bba 100644 --- a/src/runtime/ref/README.md +++ b/src/runtime/ref/README.md @@ -4,19 +4,19 @@ This directory will host a reference implementation of NN runtime. ## What is a reference NN runtime ? -A reference NN runtime is a the first PoC (Proof of concept) implementation of NN runtime for quick development without concrete design. +A reference NN runtime is the first PoC (Proof of Concept) implementation of NN runtime for quick development without concrete design. -At the time of decision for this reference NN runtime, we don't have much time to bring up NN runtime. Precisely, by the first milestone, it would be great to have a naive but working SW stack. This is a our main goal of this reference NN runtime. +At the time of decision for this reference NN runtime, we don't have much time to bring up NN runtime. Precisely, by the first milestone, it would be great to have a naive but working SW stack. This is our main goal of this reference NN runtime. -There will be various approaches to implement NN runtime and this reference NN runtime is a designed from three possible approaches. +There will be various approaches to implement NN runtime and this reference NN runtime is designed from three possible approaches. - (Plan A) Implement by importing Android NN components as needed - (Plan B) Import and migrate Android NN to our environment and objectives, (i.e. porting and refactoring Android NN) - (Plan C) Implement from scratch (with knowledge from Android NN after analysis) -Considering given restrictions, Plan C might be not feasible for us right now, because it requires correct and time consuming analysis. Drop Plan C. And Plan B might not be easy to be worked by several developers in parallel. +Considering given restrictions, Plan C might not be feasible for us right now, because it requires correct and time consuming analysis. Drop Plan C. And Plan B might not be easy to be worked by several developers in parallel. Therefore, we decide to take below two approaches in parallel. - (1) start to implement NN runtime with Plan A by developers in parallel - - (2) make use of knowledge and result from Plan C. Of course, it would be great if we can successfully port Android NN in time. (Plan C). Then we can make use of Android NN itself for our purpose for later milestones. + - (2) make use of knowledge and result from Plan B. Of course, it would be great if we can successfully port Android NN in time, i.e. Plan B. Then we can make use of Android NN itself for our purpose for later milestones. Therefore we decide to implement a reference NN runtime with Plan A for quick development without concrete design. We will follow below philosophies to achieve a main goal. @@ -32,4 +32,4 @@ We will follow below philosophies until we have a working stack of NN runtime. - Introduce a new file if we have to introduce and define our own type, variable, function, namespace and etc. of C++ source code. - Don't share existing file of `experiments/android_nn` for our own implementation. -Simply keep as much as possible of `experiments/android_nn` when importing and introduce new files for our own implementation. +Simply keep as much as possible the code of `experiments/android_nn` when importing and introduce new files for our own implementation.