Dear Sebastian,
Thank you for reporting this issue to our team! This issue is likely due to our recent platform update last week. We will let you know once we resolve this issue. Thank you for your patience!
Best regards,
Jin
From:
pen...@googlegroups.com <pen...@googlegroups.com> on behalf of Schoenherr Sebastian <sebastian....@i-med.ac.at>
Date: Wednesday, December 17, 2025 at 7:59 AM
To: pen...@googlegroups.com <pen...@googlegroups.com>
Subject: [External] PennPRS Question
|
You don't often get email from sebastian....@i-med.ac.at. Learn why this is important |
--
您收到此邮件是因为您订阅了Google群组上的“PennPRS”群组。
要退订此群组并停止接收此群组的电子邮件,请发送电子邮件到pennprs+u...@googlegroups.com。
如需查看此讨论,请访问
https://groups.google.com/d/msgid/pennprs/D2BAA904-F393-4813-A859-B30936F1BA99%40i-med.ac.at。
要查看更多选项,请访问https://groups.google.com/d/optout。
Dear Sebastian,
Our team has resolved the issue you reported. Please try again and let us know if you encounter additional issues.
Thanks!
Jin
On 18.12.2025, at 5:10 AM, Jin, Jin <Jin...@Pennmedicine.upenn.edu> wrote:
Hi Sebastian,
Thank you for reporting this issue! Our team has recently identified the same issue in another job, which is because the uploaded GWAS summary data file only contains SNPs from CHR 6 but not any other chromosome, while our code has a minor issue when handling such input datasets. We are currently working on updating our code and we will let you know as soon as our new code is online. Thank you again for your patience!
Best,
Jin
Hi Sebastian,
We have completed our code update. Please try to submit the job again and let us know if you encounter more issues. Please note that sometimes the user has to log out then log back in to use the latest version. Thank you for your patience!
Thanks!
Jin
Hi Sebatian,
Thanks for reporting the issue! Our team will look into this and get back to you.
Best,
Jin
Hi Sebastian,
You are correct – our code does not support an input P-value in the format “1e-622.587”. I believe the reason the syntax is not accepted is because in scientific notation, the exponent should be an integer not a decimal (e.g., 622.587). As a result, our R code recognizes this column as a column of characters.
I was wondering if there are some issues with columns “log10P” and “P” in the input data file. I checked one row corresponding to SNP rs56029582, where LOG10P column shows 2.71872e+00 and P column shows 1e-2.71872. I think the LOG10P column should be -LOG10P = 2.71872, i.e., LOG10P = 2.71872, and the P column should be 10^(-2.71872), not 1e-2.71872, which is not a format R can recognize.
Could you please try correcting the P-value column and rerunning the pipeline? I believe it should work then.
Thank you for reporting this issue due to the need for transforming the LOG10P output from REGENIE to p-values. We will discuss about the need to update our pipeline to account for this alternative input format and get back to you.
Thanks, and have a nice weekend!
Best regards,
Jin
Hi Sebastian,
Thanks for the update. Can you try the R code below which converted the LOG10P column into P? This should solve the problem in your data. Can you let me know how you got the “P” column? The as.numeric function in R cannot be used on the P column because the values in the current P column seem to be incorrect.
input_gwas_table = bigreadr::fread2(' output.tsv')
input_gwas_table$P = 10^(-input_gwas_table$LOG10P)
