| /dports/math/R-cran-lme4/lme4/tests/ |
| H A D | boundary.R | 16 control= lmerControl(optimizer="Nelder_Mead"))
18 control= lmerControl(optimizer="bobyqa", restart_edge=FALSE))
45 fm4c <- lmer(y ~ (1|Var2), ldata, control=lmerControl(optimizer="bobyqa",
63 fm5c <- lmer(y ~ (1|Var2), ldata, control=lmerControl(optimizer="bobyqa"),
72 fm5d <- update(fm5,control=lmerControl(optimizer="optimx",
75 fm5e <- update(fm5, control=lmerControl(optimizer="nloptwrap"))
80 pp <- profile(fm5c,which=1)
117 which(log(ss)<(-40)) ## 5, 7-13, 15, 21, ...
119 which(log(ss)>(-40) & log(ss) <(-20)) ## 16, 44, 80, 86, 116, ...
183 head(which(log(ss)<(-50))) ## 1-5, 7 ...
[all …]
|
| H A D | profile-tst.R | 13 … system.time( tpr.fm1 <- profile(fm1, optimizer="Nelder_Mead") ) ## 5 sec (2018); >= 50 warnings !?
41 invisible(lapply(wlist,function(w) xyplot(profile(fm01ML,which=w))))
56 control = lmerControl(optimizer = "bobyqa"))
57 (pfmoB <- profile(fmoB, which = "beta_", alphamax=.001))
62 control = lmerControl(optimizer = "nloptwrap",
99 pr4.3 <- profile(gm1,which=3)
108 pr5 <- profile(nm1,which=1,verbose=1,maxmult=1.2)
138 p0 <- profile(fm1, which="theta_")
142 prof01P <- profile(fm1, which="theta_", parallel="multicore", ncpus=2)
150 prof01P.snow <- profile(fm1, which="theta_", parallel="snow", ncpus=2)
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm10/llvm-10.0.1.src/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/graphics/llvm-mesa/llvm-13.0.1.src/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm11/llvm-11.0.1.src/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/lang/rust/rustc-1.58.1-src/src/llvm-project/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm90/llvm-9.0.1.src/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm70/llvm-7.0.1.src/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm13/llvm-project-13.0.1.src/llvm/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/devel/llvm80/llvm-8.0.1.src/docs/ |
| H A D | LinkTimeOptimization.rst | 11 LLVM features powerful intermodular optimizations which can be used at link
36 and clean interface. This example requires a system linker which supports LTO
101 < 0`` is always false, which means ``foo3()`` is never used. Hence, the
102 optimizer also removes ``foo3()``.
118 optimizer from removing ``foo3()``.
128 link time optimizer significantly, which is not necessary. This approach
130 platforms, which is not the main focus of the link time optimizer. Finally,
138 link objects which is more accurate than any information collected by other
182 optimizer and code generators using ``lto_codegen_compile()`` which returns a
217 a file which libLTO can process:
[all …]
|
| /dports/math/ensmallen/ensmallen-2.17.0/doc/ |
| H A D | callbacks.md | 2 optimization process, which can be used to implement and control behaviors such
61 // which will store the best objective and the corresponding model parameter
160 | `std::ostream` | **`output`** | Ostream which receives output from this object. | `stdout` |
193 | `std::ostream` | **`output`** | Ostream which receives output from this object. | `stdout` |
227 | `std::ostream` | **`output`** | Ostream which receives output from this object. | `stdout` |
361 | `OptimizerType` | **`optimizer`** | The optimizer used to update the function. |
375 | `OptimizerType` | **`optimizer`** | The optimizer used to update the function. |
389 | `OptimizerType` | **`optimizer`** | The optimizer used to update the function. |
404 | `OptimizerType` | **`optimizer`** | The optimizer used to update the function. |
607 // Set up the early stop at min loss class, which keeps track of the minimum
[all …]
|
| /dports/misc/py-mxnet/incubator-mxnet-1.9.0/tests/nightly/ |
| H A D | test_image_classification.sh | 21 if [ -f $(which nvidia-smi) ]; then
47 for optimizer in ${optimizers}; do
48 echo "OPTIMIZER: $optimizer"
49 if [ "$optimizer" == "adam" ]; then
56 --network lenet --optimizer $optimizer --gpus $gpus \
|
| /dports/misc/mxnet/incubator-mxnet-1.9.0/tests/nightly/ |
| H A D | test_image_classification.sh | 21 if [ -f $(which nvidia-smi) ]; then
47 for optimizer in ${optimizers}; do
48 echo "OPTIMIZER: $optimizer"
49 if [ "$optimizer" == "adam" ]; then
56 --network lenet --optimizer $optimizer --gpus $gpus \
|
| /dports/science/dakota/dakota-6.13.0-release-public.src-UI/docs/KeywordMetadata/ |
| H A D | method-ncsu_direct-solution_target | 2 Specifies a globally optimal value toward which the optimizer should track
4 The solution target specifies a goal toward which the optimizer should
|
| /dports/science/dakota/dakota-6.13.0-release-public.src-UI/packages/external/acro/packages/colin/ |
| H A D | README | 8 NLP0. This effectively ignores the other parameters, which is probably
13 When evaluating a real vectors, these vars are mapped into a MixedIntVars object, which has been pr…
31 test7 simple derived optimizer
32 test8 simple derived optimizer with a generic datatype
33 test9 simple optimizer testing command shell mode
44 DomainOptimizer Define an optimizer over that domain
69 employ syntactic distinctions within an optimizer? We need to know when an
70 optimizer must perform finite differencing for us, but this is no longer
98 Problem: How categorize methods like NPSOL, which can accept either
|
| /dports/science/py-kliff/kliff-0.3.0/docs/source/modules/ |
| H A D | calculators.rst | 13 minimized by the optimizer.
15 provide these parameters to the optimizer, which will be used as the initial values
16 by the optimizer to carry out the optimization.
18 parameters from the optimizer and update the model parameters with the new ones.
36 :ref:`doc.dataset`), for which the calculator is going to make predictions.
40 ``use_forces`` and ``use_stress`` to ``False``, which turns off the calculations for
|
| /dports/sysutils/vector/lucet-d4fc14a03bdb99ac83173d27fddf1aca48412a86/wasmtime/cranelift/ |
| H A D | rustc.md | 15 good low-level optimizations to produce code which has a chance of being
28 With all that said, there is a potential goal beyond that, which is to
33 - Take advantage of Rust language properties in the optimizer. With
36 limited. An optimizer that can represent the core aliasing
40 cases, like `Vec`, it may be possible to recover what the optimizer
48 superoptimizers miss. This has the potential to take a new optimizer
51 - Build an optimizer IR without the constraints of fast-debug-build
53 full-strength optimizer would either use an IR layer on top of it
56 IR. Either way, this overall architecture would keep the optimizer
57 out of the way of the non-optimizing build path, which keeps that
[all …]
|