Closed sneumann closed 8 years ago
That's really interesting. On a first quick glance, I could not find the problem. I'll have a look tomorrow and fix it asap.
Indeed, my fault. When trying to create a minimal standalone example, I could not reproduce the issue. Case closed :-)
library(IPO)
library(faahKO)
library(RUnit)
xsg <- group(faahko)
retcorGroupParameters <- getDefaultRetGroupStartingParams(retcorMethod="loess")
retcorGroupParameters$profStep <- 1
retcorGroupParameters$missing <- 0
retcorGroupParameters$extra <- 0
retcorGroupParameters$minfrac <- 0.75
retcorGroupParameters$max <- 50
resultRetcorGroup <- optimizeRetGroup(xset=xsg, params=retcorGroupParameters, nSlaves=1, subdir="rsmDirectory")
checkEquals(resultRetcorGroup$best_settings$retcorMethod, "loess")
So the issue is still persisting?
In a subsequent step writeRScript(paramsPP, resultRetcorGroup$best_settings, 1)
I had left out the $best_settings
, and that mislead me to thinking that something
was wrong with "loess". Sorry for the confusion.
No worries. It's good to hear, that optimizeRetGroup
correctly recognizes the method for retention time correction.
Hi, it seems that
optimizeRetGroup()
is somehow still usingmethod="obiwarp"
even if the retcorGroupParameters were created withgetDefaultRetGroupStartingParams(retcorMethod="loess")
results in:
Yours, Steffen