The paper reports all the ages, predictions and model errors in months, are you sure the model isn't built on (and outputs) months rather than years? (I admit after a very quick check this was not clear in the methodology) (another thing that you may encounter when dealing with clocks is that the outputted age is transformed, for example the model predicts log(age) instead of age).
However since we are dealing with mices I dont know which direction to take.. also the model rightfully states everything in months but since that I just applied the same system as to humans (except the last function) I was expecting the result in years.
If we state the result as months (sigma_DNAmPhenoAge = 6.238126) and take approximately 4.34812141 weeks in a month we get 27.12413 weeks; and if we apply the last function it gives 151.0006
I had the same difficulty, however the coefficients that are available at the paper also were indexed as chromosome number instead of CpG's, what I did was (couldn't find a better solution) match every coefficient chromosome to the correspondent beta chromosome and then remove the duplicate values so that they only pair once, after that I just did the summation
That would explain why you got different results. 1) In the paper you linked, both of the available clocks (in sup. tables 1 and 2) do have unique coordinates: look at the Chromosome and the Coordinate columns in the table. If you paste them together (e.g. "chr1_9967422") you will have unique columns. You can do the same for your own data (GSM2465621) by pasting the chr and start or end columns (they are the same) and thus select your CpGs and match them to the clock's coefficients.
2) If not all of the CpGs of the clock are in your data matrix CpGs (GSM2465621), do not ignore those coefficients. It is better if you input them with some values (such as 0% meth) and use them in the summation.
3) Finally, in the summation do not forget to add the Intercept coefficient (it is the first one in the provided clock files). That coefficient does not multiply any methylation value.
Hello, In my project, I need to correlate single-cell RNAseq marker genes (after clustering) with specific pathways, for example [metabolism][1] and the immune system in …
Hi, I'm trying to perform RNA sequencing analysis using data download from NCBI: https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE184199 I'm following this workflow: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4934518/ These are the commands I've done …
Hi all. Now, I’m trying to get an assembly stat with reference to table S1 and figure S1 in this paper. > [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7266049/][1] I used …
Found here: https://www.ncbi.nlm.nih.gov/dbvar/content/tools/entrez/ I get KeyError Traceback (most recent call last) <ipython-input-35-be9c80362590> in <module> ----> 1 for ds in dsdocs['eSummaryResult']['DocumentSummarySet']['DocumentSummary']: 2 for p in ds['dbVarPlacementList']['dbVarPlacement']: …
I am having trouble identifying/locating the MBP promoter sequence for Mus musculus (mouse). According to [this article][1] the promoter is 1.3kb in length. However, I …
I'm trying to generate a heatmap for almost 15,000 genes expression data across different samples. But they are grouped into clusters based on their similar …
The paper reports all the ages, predictions and model errors in months, are you sure the model isn't built on (and outputs) months rather than years? (I admit after a very quick check this was not clear in the methodology) (another thing that you may encounter when dealing with clocks is that the outputted age is transformed, for example the model predicts log(age) instead of age).
However since we are dealing with mices I dont know which direction to take.. also the model rightfully states everything in months but since that I just applied the same system as to humans (except the last function) I was expecting the result in years. If we state the result as months (
sigma_DNAmPhenoAge = 6.238126) and take approximately 4.34812141 weeks in a month we get 27.12413 weeks; and if we apply the last function it gives 151.0006For the moment I have checked the first part of your code:
And it leads to your CpGs being named with non-unique names:
So I don't know how you can match each CpG with each coefficient.
I had the same difficulty, however the coefficients that are available at the paper also were indexed as chromosome number instead of CpG's, what I did was (couldn't find a better solution) match every coefficient chromosome to the correspondent beta chromosome and then remove the duplicate values so that they only pair once, after that I just did the summation
That would explain why you got different results. 1) In the paper you linked, both of the available clocks (in sup. tables 1 and 2) do have unique coordinates: look at the Chromosome and the Coordinate columns in the table. If you paste them together (e.g. "chr1_9967422") you will have unique columns. You can do the same for your own data (GSM2465621) by pasting the chr and start or end columns (they are the same) and thus select your CpGs and match them to the clock's coefficients. 2) If not all of the CpGs of the clock are in your data matrix CpGs (GSM2465621), do not ignore those coefficients. It is better if you input them with some values (such as 0% meth) and use them in the summation. 3) Finally, in the summation do not forget to add the Intercept coefficient (it is the first one in the provided clock files). That coefficient does not multiply any methylation value.