-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Assigned data dfdc.final[[x]] - dfdc.final[[y]]
must be compatible with existing data
#190
Comments
Hi @jfertaj
which means that, for example, for your condition
you should have these ones instead
And same thing for all the other conditions. And once you have ready the new keys file, you will have to run the Quantification step again and use the new results files with that new notation. Next version of Hope it helps |
Hi David, I have corrected the keys.txt file and then I realised than my version of artMS was outdated so I have updated to version v1.10.2. However when running
Any idea why? |
Hi, I guess you are referring to this issue. I thought that the issue was resolved. It was not only the wrong notation for conditions and bioreplicates, but also bioreplicates must be unique, and then the |
Hi David, I have tried with your version but the error is still there, here is the full output
Sorry for bothering so much |
Also, I have created a new keys.txt from scratch, loaded in R and test for unique values like this
The number of unique elements is equals to 90, the original number of samples. I need to remove one after QC but just to do it from scratch I have re-run it with the whole datase |
Hi there, Remember the important rules: Condition: The conditions names must follow these rules:
BioReplicate: biological replicate number. It is based on the condition name. Use as prefix the corresponding Condition name, and add as suffix dash (-) plus the biological replicate number. For example, if condition H1N1_06H has too biological replicates, name them H1N1_06H-1 and H1N1_06H-2 Have you tried the keys files that I included in my previuos response? |
Hi David,
Yes, I have tried with the key file you share but still have the same
problem. I am going to share with you the folder where I have all the files
so you can see if you are able to recreate the error.
Thanks for your help. Regards
Juan
Here is the link:
https://www.dropbox.com/sh/btt8yalaqvuo530/AABsxiOW58LPowy_hnZuFCSRa?dl=0
…On Mon, Sep 13, 2021 at 11:47 PM David JM ***@***.***> wrote:
Hi there,
Remember the important rules:
Condition: The conditions names must follow these rules:
- Use only letters (A - Z, both uppercase and lowercase) and numbers
(0 - 9). The only special character allowed is underscore (_).
- *Very important*: A condition name cannot begin with a number (R
limitation). @jfertaj <https://github.com/jfertaj> *You are not
showing the condition names, but if they match the bioreplicates, you are
breaking this rule.*
BioReplicate: biological replicate number. It is based on the condition
name. Use as prefix the corresponding Condition name, and add as suffix
dash (-) plus the biological replicate number. For example, if condition
H1N1_06H has too biological replicates, name them H1N1_06H-1 and H1N1_06H-2
Have you tried the keys files that I included in my previuos response?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJH3NBWTO2NHDG6JOJNTFDUBZWORANCNFSM5D6EIALA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Thanks! I'll take a look and get back to you soon |
Hi David,
Sorry for bothering you again and on Sunday. Did you have time to see if
you were able to replicate my problem?
Thanks a lot
Juan
…On Tue, Sep 14, 2021 at 6:08 PM David JM ***@***.***> wrote:
Thanks! I'll take a look and get back to you soon
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJH3NATHXAKXBOA4RU5AGTUB5XO5ANCNFSM5D6EIALA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hi Juan, sorry for the late response. I've been carefully debugging the issue and I am sorry to report that this is not an artMS issue, but rather an MSstats/data.table one. According to the error message:
and based on similar errors found on the internet, the error could be solved if the I strongly encourage you to report this error in the MSstats google group. Specifically, it fails when running this MSstats function (normalization step):
However, let me point something out. It is truly remarkable the low number of proteins identified: In the evidence file:
After contaminants and protein group removal:
barely 308 proteins. Is this expected? did you search with the right database? You should include this when asking in the msstats group Please, let us know how it goes. Thanks! |
Hi Juan and David, I just met the same issue as Juan, also I have a relative small dataset (~300 proteins) for this set of data. I'm wondering did you find a solution for it? Actually I realized this error just happened after the message of "--- Number of +/- INF values: 344 ", which I think should happened during the imputeMissingValue and merge the original log2FC to the impute steps, here is the full error: I'm wondering is it possible we can separate the imputation and stats steps? Then maybe we can skip the imputing errors and direct feed the imputed data to perform the stats with MSstats. Looking forward for your response. Really appreciate it! Best, |
Hi,
I am trying to run a quantification analyses using artMS and get the following error:
Error: Assigned data `dfdc.final[[x]] - dfdc.final[[y]]` must be compatible with existing data
The chunk of my code that triggers the error is this:
my SessionInfo is the following
My keys.txt is attached
Thanks a lot
Juan
keys.txt
The text was updated successfully, but these errors were encountered: