| /external/webkit/Source/WebCore/fileapi/ |
| FileReader.cpp | 128 if (m_state != None && m_state != Starting)
136 m_state = Starting;
234 case Starting:
|
| FileReader.h | 109 Starting,
|
| /external/webkit/Source/WebCore/bridge/ |
| testM.js | 1 myInterface.logMessage ("Starting test");
|
| /system/core/rootdir/etc/ |
| init.testmenu | 234 echo Starting android runtime
241 echo Starting android runtime
|
| /external/v8/tools/ |
| profile.js | 99 * @param {number} startAddr Starting address.
115 * @param {number} startAddr Starting address.
132 * @param {number} start Starting address.
148 * @param {number} start Starting address.
197 * @param {number} start Starting address.
233 * addresses starting with the program counter value.
330 * Calculates a flat profile of callees starting from a node with
333 * @param {string} opt_label Starting node label.
|
| test.py | 82 self.Starting()
153 def Starting(self):
187 print 'Starting %s...' % case.GetLabel()
233 def Starting(self):
[all...] |
| /external/ceres-solver/docs/ |
| curvefitting.tex | 77 Starting from parameter values $m = 0, c=0$ with an initial objective function value of $121.173$ Ceres finds a solution $m= 0.291861, c = 0.131439$ with an objective function value of $1.05675$. These values are a a bit different than the parameters of the original model $m=0.3, c= 0.1$, but this is expected. When reconstructing a curve from noisy data, we expect to see such deviations. Indeed, if you were to evaluate the objective function for $m=0.3, c=0.1$, the fit is worse with an objective function value of 1.082425. Figure~\ref{fig:exponential} illustrates the fit.
|
| helloworld.tex | 71 Starting from a $x=5$, the solver in two iterations goes to 10~\footnote{Actually the solver ran for three iterations, and it was by looking at the value returned by the linear solver in the third iteration, it observed that the update to the parameter block was too small and declared convergence. Ceres only prints out the display at the end of an iteration, and terminates as soon as it detects convergence, which is why you only see two iterations here and not three.}. The careful reader will note that this is a linear problem and one linear solve should be enough to get the optimal value. The default configuration of the solver is aimed at non-linear problems, and for reasons of simplicity we did not change it in this example. It is indeed possible to obtain the solution to this problem using Ceres in one iteration. Also note that the solver did get very close to the optimal function value of 0 in the very first iteration. We will discuss these issues in greater detail when we talk about convergence and parameter settings for Ceres.
|
| /external/webkit/LayoutTests/dom/html/level1/core/ |
| hc_textsplittextfour.js | 86 (Starting count at 0)
|
| hc_textsplittextthree.js | 88 (Starting count at 0)
|
| /external/webkit/LayoutTests/dom/xhtml/level1/core/ |
| hc_textsplittextfour.js | 86 (Starting count at 0)
|
| hc_textsplittextthree.js | 88 (Starting count at 0)
|
| /external/bison/examples/calc++/ |
| calc++-parser.cc | 367 YYCDEBUG << "Starting parse" << std::endl;
946 First, the terminals, then, starting at \a yyntokens_, nonterminals. */
[all...] |
| /external/bison/data/ |
| lalr1.cc | 543 YYCDEBUG << "Starting parse" << std::endl;
1054 First, the terminals, then, starting at \a yyntokens_, nonterminals. */
[all...] |
| lalr1.java | 456 yycdebug ("Starting parse\n");
851 First, the terminals, then, starting at \a yyntokens_, nonterminals. */
|
| glr.c | 365 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
790 /** Fill in YYVSP[YYLOW1 .. YYLOW0-1] from the chain of states starting
[all...] |
| yacc.c | 653 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
[all...] |
| /external/elfutils/src/ |
| ldscript.c | 585 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
[all...] |
| /external/libpcap/ |
| grammar.c | 779 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
[all...] |
| /external/webkit/Source/ThirdParty/ANGLE/src/compiler/ |
| glslang_tab.cpp | 757 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
[all...] |
| /frameworks/base/docs/html/training/ |
| training_toc.cs | 33 <li><a href="<?cs var:toroot ?>training/basics/firstapp/starting-activity.html">
34 Starting Another Activity
49 <li><a href="<?cs var:toroot ?>training/basics/activity-lifecycle/starting.html">
50 Starting an Activity
707 Preserving Navigation when Starting an Activity
[all...] |
| /external/bison/doc/ |
| refcard.tex | 308 \section{Starting Bison}
|
| /external/elfutils/libcpu/ |
| i386_parse.c | 664 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
[all...] |
| /ndk/sources/host-tools/make-3.81/ |
| job.c | [all...] |
