-
Notifications
You must be signed in to change notification settings - Fork 32
/
Copy pathtransaction_cost_constraint.Rd
53 lines (45 loc) · 1.36 KB
/
transaction_cost_constraint.Rd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
\name{transaction_cost_constraint}
\alias{transaction_cost_constraint}
\title{constructor for transaction_cost_constraint}
\usage{
transaction_cost_constraint(type = "transaction_cost",
assets, ptc, enabled = TRUE, message = FALSE, ...)
}
\arguments{
\item{type}{character type of the constraint}
\item{assets}{number of assets, or optionally a named
vector of assets specifying initial weights}
\item{ptc}{proportional transaction cost value}
\item{enabled}{TRUE/FALSE}
\item{message}{TRUE/FALSE. The default is message=FALSE.
Display messages if TRUE.}
\item{\dots}{any other passthru parameters to specify box
and/or group constraints}
}
\value{
an object of class 'transaction_cost_constraint'
}
\description{
The transaction cost constraint specifies a proportional
cost value. This function is called by add.constraint
when type="transaction_cost" is specified, see
\code{\link{add.constraint}}.
}
\details{
Note that with the ROI solvers, proportional transaction
cost constraint is currently only supported for the
global minimum variance and quadratic utility problems
with ROI quadprog plugin.
}
\examples{
data(edhec)
ret <- edhec[, 1:4]
pspec <- portfolio.spec(assets=colnames(ret))
pspec <- add.constraint(portfolio=pspec, type="transaction_cost", ptc=0.01)
}
\author{
Ross Bennett
}
\seealso{
\code{\link{add.constraint}}
}