You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that when you run getClockProbes(exampleBetas) in your Readme, or running it with custom betas after installing the package, the output says that the Knight clock has only 1 Total.probes.
However, this clock uses 148 CpGs. Internally, with get("Knight_CpGs") I can see that there are 148 CpGs. There seems to be a problem with the getClockProbes function, where you define totalProbes[i] <- length(currentCpGList), in the case of "Knight_CpGs", the currentCpGList object is a tibble with 1 column, and thus length is 1.
hope this helps
best
The text was updated successfully, but these errors were encountered:
rauldiul
changed the title
Number of stated Knight clock CpGs si 1, should be 148
Number of stated Knight clock CpGs is 1, should be 148
Apr 18, 2023
Hi! Thanks for your useful tool.
I've noticed that when you run
getClockProbes(exampleBetas)
in yourReadme
, or running it with custom betas after installing the package, the output says that the Knight clock has only 1Total.probes
.However, this clock uses 148 CpGs. Internally, with
get("Knight_CpGs")
I can see that there are 148 CpGs. There seems to be a problem with thegetClockProbes
function, where you definetotalProbes[i] <- length(currentCpGList)
, in the case of "Knight_CpGs", thecurrentCpGList
object is atibble
with 1 column, and thuslength
is1
.hope this helps
best
The text was updated successfully, but these errors were encountered: