Groups
Groups
Sign in
Groups
Groups
PrediXcan/MetaXcan
Conversations
About
Send feedback
Help
SMulTiXcan - Unexpected error: nothing to repeat at position 0
76 views
Skip to first unread message
renatop...@live.com
unread,
May 3, 2021, 2:13:54 PM
5/3/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to PrediXcan/MetaXcan
Hello,
I'm having an issue with SMulTiXcan using the mashr models.
The error I get is "INFO - Unexpected error: nothing to repeat at position 0".
The GWAS file I'm using works fine with SPrediXcan.
Any suggestion is appreciated.
Thanks!
Hae Kyung Im
unread,
May 3, 2021, 2:20:08 PM
5/3/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to PrediXcan/MetaXcan
Posting in the mailing list while we investigate
--
You received this message because you are subscribed to the Google Groups "PrediXcan/MetaXcan" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
predixcanmetax...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/predixcanmetaxcan/53933210-5fb2-400d-879d-7b2f9ea211cfn%40googlegroups.com
.
renatop...@live.com
unread,
May 3, 2021, 5:53:49 PM
5/3/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to PrediXcan/MetaXcan
The issue was due to the unmatching of the --models_name_patter and the --metaxcan_file_name_parse_pattern.
Reply all
Reply to author
Forward
0 new messages