Last updated on 2024-11-24 15:49:49 CET.
| Package | NOTE | OK |
|---|---|---|
| Binarize | 5 | 8 |
| BiTrinA | 5 | 8 |
| BoolNet | 10 | 3 |
| GiANT | 13 | |
| MOCCA | 13 | |
| ORION | 3 | 10 |
| TunePareto | 13 |
Current CRAN status: NOTE: 5, OK: 8
Version: 1.3.1
Check: compiled code
Result: NOTE
File ‘Binarize/libs/Binarize.so’:
Found non-API call to R: ‘SET_TYPEOF’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
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
Version: 1.3.1
Check: compiled code
Result: NOTE
File 'Binarize/libs/x64/Binarize.dll':
Found non-API call to R: 'SET_TYPEOF'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
Flavor: r-devel-windows-x86_64
Current CRAN status: NOTE: 5, OK: 8
Version: 1.3.1
Check: compiled code
Result: NOTE
File ‘BiTrinA/libs/BiTrinA.so’:
Found non-API call to R: ‘SET_TYPEOF’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
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
Version: 1.3.1
Check: compiled code
Result: NOTE
File 'BiTrinA/libs/x64/BiTrinA.dll':
Found non-API call to R: 'SET_TYPEOF'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
Flavor: r-devel-windows-x86_64
Current CRAN status: NOTE: 10, OK: 3
Version: 2.1.9
Check: Rd files
Result: NOTE
checkRd: (-1) getPathToAttractor.Rd:23: Lost braces; missing escapes or markup?
23 | Specifies whether the actual attractor states are included in the resulting table or not. If \code{includeAttractorStates = "all"} (which is the default behaviour), the sequence ends when the attractor was traversed once. If \code{includeAttractorStates = "first"}, only the first state of attractor is added to the sequence. This corresponds to the behaviour prior to \pkg{BoolNet} version 1.5. If {includeAttractorStates = "none"}, the sequence ends with the last non-attractor state. In this case, the sequence can be empty if the start state is an attractor state.
| ^
checkRd: (-1) plotSequence.Rd:42: Lost braces; missing escapes or markup?
42 | Specifies whether the actual attractor states are included in the plot or not (see also \code{\link{getPathToAttractor}}). If \code{includeAttractorStates = "all"} (which is the default behaviour), the sequence ends when the attractor was traversed once. If \code{includeAttractorStates = "first"}, only the first state of attractor is added to the sequence. If {includeAttractorStates = "none"}, the sequence ends with the last non-attractor state.
| ^
checkRd: (-1) sequenceToLaTeX.Rd:37: Lost braces; missing escapes or markup?
37 | Specifies whether the actual attractor states are included in the table or not (see also \code{\link{getPathToAttractor}}). If \code{includeAttractorStates = "all"} (which is the default behaviour), the sequence ends when the attractor was traversed once. If \code{includeAttractorStates = "first"}, only the first state of attractor is added to the sequence. If {includeAttractorStates = "none"}, the sequence ends with the last non-attractor state.
| ^
checkRd: (-1) simulateSymbolicModel.Rd:64: Lost braces in \itemize; meant \describe ?
checkRd: (-1) simulateSymbolicModel.Rd:66-70: Lost braces in \itemize; meant \describe ?
checkRd: (-1) simulateSymbolicModel.Rd:72-73: Lost braces in \itemize; meant \describe ?
checkRd: (-1) testNetworkProperties.Rd:131: Lost braces; missing escapes or markup?
131 | If {perturb="functions"} or \code{perturb="transitions"} and \code{accumulate=FALSE}, the function returns a vector of percentages of original attractors found in each of the perturbed copies of the original network. If \code{accumulate=TRUE}, the function returns the overall percentage of original attractors found in all perturbed copies.
| ^
checkRd: (-1) testNetworkProperties.Rd:140: Lost braces
140 | code{params} can hold parameters \code{numSamples, flipBits} corresponding to the parameters of \code{\link{perturbTrajectories}} that define how many initial states are drawn and how many bits are flipped.
| ^
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
Current CRAN status: OK: 13
Current CRAN status: OK: 13
Current CRAN status: NOTE: 3, OK: 10
Version: 1.0.3
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
predictionMap.Rd: generateCVRuns, tuneParetoClassifier
tunePareto.occ.Rd: tunePareto.knn, tuneParetoClassifier,
trainTuneParetoClassifier
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
Current CRAN status: OK: 13
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.