/dports/finance/R-cran-plm/plm/man/ |
H A D | has.intercept.Rd | 3 \name{has.intercept} 4 \alias{has.intercept} 5 \alias{has.intercept.default} 6 \alias{has.intercept.formula} 7 \alias{has.intercept.Formula} 8 \alias{has.intercept.panelmodel} 9 \alias{has.intercept.plm} 13 has.intercept(object, ...) 15 \method{has.intercept}{default}(object, ...) 17 \method{has.intercept}{formula}(object, ...) [all …]
|
H A D | cipstest.Rd | 21 \item{type}{one of \code{"trend"} (default), \code{"drift"}, \code{"none"},} 23 \item{model}{one of \code{"cmg"} (default), \code{"mg"}, \code{"dmg"},} 26 truncated version of the test (default: \code{FALSE}),} 41 has a unit root) is a so-called second-generation panel unit root test: it 42 is in fact robust against cross-sectional dependence, provided that the default 49 \item \code{"none"}: no intercept, no trend (Case I in \insertCite{pes07}{plm}), 50 \item \code{"drift"}: with intercept, no trend (Case II), 51 \item \code{"trend"} (default): with intercept, with trend (Case III).
|
/dports/math/R-cran-Formula/Formula/ |
H A D | NAMESPACE | 8 ## "has.intercept" 23 S3method("as.Formula", "default") 27 ## ## methods to has.intercept() 28 ## S3method("has.intercept", "default") 29 ## S3method("has.intercept", "formula") 30 ## S3method("has.intercept", "Formula")
|
/dports/finance/R-cran-plm/plm/ |
H A D | NAMESPACE | 7 S3method(Between,default) 13 S3method(Sum,default) 16 S3method(Within,default) 25 S3method(between,default) 47 S3method(has.intercept,Formula) 48 S3method(has.intercept,default) 49 S3method(has.intercept,formula) 50 S3method(has.intercept,panelmodel) 51 S3method(has.intercept,plm) 98 S3method(pdim,default) [all …]
|
/dports/math/R-cran-recipes/recipes/man/ |
H A D | step_intercept.Rd | 2 % Please edit documentation in R/intercept.R 5 \title{Add intercept (or constant) column} 12 name = "intercept", 15 id = rand_id("intercept") 26 they be assigned? By default, the new columns created by this step from 34 \item{value}{A numeric constant to fill the intercept column. Defaults to 1.} 51 will add an intercept or constant term in the first column of a data 52 matrix. \code{step_intercept} has defaults to \emph{predictor} role so 53 that it is by default called in the bake step. Be careful to avoid
|
/dports/www/firefox-esr/firefox-91.8.0/netwerk/protocol/http/ |
H A D | PClassifierDummyChannel.ipdl | 13 // This protocol provides a mechanism for the "child intercept" mode of 18 // In child intercept mode, the decision to intercept a channel is made in the 24 // should not intercept the channel. However, the decision for tracking 26 // dummy channel is a hack to allow the intercept decision process to ask the 28 // to the parent has overhead, the dummy channel is only created 1) if the 32 // This hack can be removed once Bug 1231208's new "parent intercept" mechanism 33 // fully lands, the pref is enabled by default it stays enabled for long enough
|
/dports/www/firefox/firefox-99.0/netwerk/protocol/http/ |
H A D | PClassifierDummyChannel.ipdl | 13 // This protocol provides a mechanism for the "child intercept" mode of 18 // In child intercept mode, the decision to intercept a channel is made in the 24 // should not intercept the channel. However, the decision for tracking 26 // dummy channel is a hack to allow the intercept decision process to ask the 28 // to the parent has overhead, the dummy channel is only created 1) if the 32 // This hack can be removed once Bug 1231208's new "parent intercept" mechanism 33 // fully lands, the pref is enabled by default it stays enabled for long enough
|
/dports/mail/thunderbird/thunderbird-91.8.0/netwerk/protocol/http/ |
H A D | PClassifierDummyChannel.ipdl | 13 // This protocol provides a mechanism for the "child intercept" mode of 18 // In child intercept mode, the decision to intercept a channel is made in the 24 // should not intercept the channel. However, the decision for tracking 26 // dummy channel is a hack to allow the intercept decision process to ask the 28 // to the parent has overhead, the dummy channel is only created 1) if the 32 // This hack can be removed once Bug 1231208's new "parent intercept" mechanism 33 // fully lands, the pref is enabled by default it stays enabled for long enough
|
/dports/lang/spidermonkey78/firefox-78.9.0/netwerk/protocol/http/ |
H A D | PClassifierDummyChannel.ipdl | 13 // This protocol provides a mechanism for the "child intercept" mode of 18 // In child intercept mode, the decision to intercept a channel is made in the 24 // should not intercept the channel. However, the decision for tracking 26 // dummy channel is a hack to allow the intercept decision process to ask the 28 // to the parent has overhead, the dummy channel is only created 1) if the 32 // This hack can be removed once Bug 1231208's new "parent intercept" mechanism 33 // fully lands, the pref is enabled by default it stays enabled for long enough
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/tinygo/tinygo-0.14.1/llvm-project/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/wasi-libcxx/llvm-project-13.0.1.src/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm12/llvm-project-12.0.1.src/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm11/llvm-11.0.1.src/tools/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm90/llvm-9.0.1.src/tools/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm10/llvm-10.0.1.src/tools/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/lang/rust/rustc-1.58.1-src/src/llvm-project/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/lang/clang-mesa/clang-13.0.1.src/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm13/llvm-project-13.0.1.src/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm80/llvm-8.0.1.src/tools/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|
/dports/devel/llvm70/llvm-7.0.1.src/tools/clang/tools/scan-build-py/ |
H A D | README.md | 6 the clang static analyzer. Includes intercept-build tool, which logs 15 - It has been tested on FreeBSD, GNU/Linux and OS X. 34 $ intercept-build <your build command> 47 To run the CTU analysis, a compilation database file has to be created: 49 $ intercept-build <your build command> 77 $ intercept-build <your build command> && analyze-build 80 tool has three distinct model to run the analyzer: 84 This is the default behaviour, can be enforced with `--override-compiler` 89 Use `--intercept-first` flag to get this model. 99 you need to pass the compiler wrappers manually. eg.: `intercept-build [all …]
|