FS#21 - FLPar functionality
Attached to Project:
FLR
Opened by Laurie Kell (ltkell) - Wednesday, 28 October 2009, 10:48 GMT+2
Last edited by Iago Mosqueira (imosqueira) - Thursday, 07 January 2010, 12:24 GMT+2
Opened by Laurie Kell (ltkell) - Wednesday, 28 October 2009, 10:48 GMT+2
Last edited by Iago Mosqueira (imosqueira) - Thursday, 07 January 2010, 12:24 GMT+2
|
DetailsThere are a few things in FLPar that are either features or bugs e.g.
# 1) dims(FLPar) returns iters 1st and params 2nd, which is in the wrong order and only show 2 dims dims(FLPar(rnorm(100),dimnames=list(params=c("a","b"),scen=1:2,iter=1:100))) # 2) When there are multiple iters in objects like FLPar, it would be easier if they were displayed in the same way as multiple iters in FLQuant. FLPar(rnorm(100),params=c("a","b"),iter=1:100) # 3) Shouldn´t FLPar constructor have iters by default FLPar(NA,dimnames=list(scen=1:4,period=c(70,90),param=c("a","b"))) # 4) Is this legal, i.e. putting params 3rd in order of dims srPar<-FLPar(NA,dimnames=list(scen=1:4,period=c(70,90),param=c("a","b"),iter=1:2)) # 5) Why does this have two elements for params srPar[1,1,"a",] # 5) Why doesn´t assignment work srPar[1,1,,]<-srPar[1,1,,] |
This task depends upon
> 1) dims(FLPar) returns iters 1st and params 2nd, which is in the wrong order and only show 2 dims
The information returned by dims is right now no different from dimnames, so maybe we should just use dimnames: it will return the list in the right order automatically.
> 2) When there are multiple iters in objects like FLPar, it would be easier if they were displayed in the same way as multiple iters in FLQuant.
Fixed now with a show method for FLPar, at branch IM_FLCore_20091106_fix_for_R2100
> 3) Shouldn´t FLPar constructor have iters by default
> 4) Is this legal, i.e. putting params 3rd in order of dims
This needs to be declared in the validity and forced in the constructor. TODO