Last updated on 2024-11-21 19:52:43 CET.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 1.1.2 | 2.32 | 20.80 | 23.12 | NOTE | |
r-devel-linux-x86_64-debian-gcc | 1.1.2 | 1.71 | 16.29 | 18.00 | NOTE | |
r-devel-linux-x86_64-fedora-clang | 1.1.2 | 40.07 | NOTE | |||
r-devel-linux-x86_64-fedora-gcc | 1.1.2 | 35.24 | NOTE | |||
r-devel-windows-x86_64 | 1.1.2 | 3.00 | 44.00 | 47.00 | NOTE | |
r-patched-linux-x86_64 | 1.1.2 | 3.59 | 19.94 | 23.53 | NOTE | |
r-release-linux-x86_64 | 1.1.2 | 2.27 | 20.18 | 22.45 | NOTE | |
r-release-macos-arm64 | 1.1.2 | 16.00 | NOTE | |||
r-release-macos-x86_64 | 1.1.2 | 21.00 | NOTE | |||
r-release-windows-x86_64 | 1.1.2 | 3.00 | 57.00 | 60.00 | NOTE | |
r-oldrel-macos-arm64 | 1.1.2 | 17.00 | OK | |||
r-oldrel-macos-x86_64 | 1.1.2 | 22.00 | OK | |||
r-oldrel-windows-x86_64 | 1.1.2 | 4.00 | 43.00 | 47.00 | OK |
Version: 1.1.2
Check: Rd files
Result: NOTE
checkRd: (-1) pampe.Rd:54: Lost braces; missing escapes or markup?
54 | The way they propose to estimate the outcome of the treated unit under no treatment, Y^0_{1t}, is to use the following modeling strategy: use R^2 (or likelihood values) in order to select the best OLS estimator for Y^0_{1t} using j out of the J units in the donor pool, denoted by M(j)* for j=1, ..., J; then choose M(m)* from M(1)*, ..., M(J)* in terms of a model selection criterion, like AICc, AIC or BIC. Note that the method calculates OLS models of up to J+1 parameters; so that if the length of the pre-treatment period t=1, 2, ..., T'-1 is not of a much higher order than that, the regressions M(J-1)*, M(J)* can not be calculated because there are not enough degrees of freedom.
| ^
checkRd: (-1) pampe.Rd:54: Lost braces; missing escapes or markup?
54 | The way they propose to estimate the outcome of the treated unit under no treatment, Y^0_{1t}, is to use the following modeling strategy: use R^2 (or likelihood values) in order to select the best OLS estimator for Y^0_{1t} using j out of the J units in the donor pool, denoted by M(j)* for j=1, ..., J; then choose M(m)* from M(1)*, ..., M(J)* in terms of a model selection criterion, like AICc, AIC or BIC. Note that the method calculates OLS models of up to J+1 parameters; so that if the length of the pre-treatment period t=1, 2, ..., T'-1 is not of a much higher order than that, the regressions M(J-1)*, M(J)* can not be calculated because there are not enough degrees of freedom.
| ^
checkRd: (-1) pampe.Rd:56: Lost braces; missing escapes or markup?
56 | To avoid this problem, the pampe package proposes the following slight modification to the previously outlined modeling strategy: use R^2 in order to select the best OLS estimator for Y^0_{1t} using j out of the J units in the donor pool, denoted by M(j)* for j=1, ..., T_0-4; then choose M(m)* from M(1)*, ..., M(T_0-4)* in terms of a model selection criterion (in our case AICc). Note that the key difference is that while we allowed models up to M(J)*, this is now modified to allow models up to M(T_0-4)*, with T_0-4<J, which allows for at least 3 degrees of freedom. This is implemented through the default value of nvmax, which is equal to J, or if not possible, to J-4. The user can of course override this default.
| ^
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64
Version: 1.1.2
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
pampe-internal.Rd: leaps
pampe.Rd: leaps
robustness.Rd: leaps
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.