Closed whatever closed 12 years ago
converting the name "relogit" to "Relogit" because otherwise we have like... 3 objects that all do different things labeled "relogit"
working on the "Relogit2" type of fitted model now. This supports upper/lower bounds on the prediction via the tau
parameter
Relogit2
needs its own sim
method. It does non-standard work with the param
generic, and that is no longer supported within Zelig core.
Relogit2
(issue with specifying upper and lower bounds for the tau
parameter) still exists. Standard relogit models operate fine.
Relogit
relogit
model needs a patch, and should probably be placed in ZeligMisc