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 get the below error. I rerun with "allow.cartesian=TRUE", but the error persists.
Any advice on this? Attached is my annotation file. annotation_towers.txt
Help appreciated.
GPR
Error in vecseq(f__, len__, if (allow.cartesian || notjoin || !anyDuplicated(f__, : Join results in 1854844 rows; more than 1650276 = nrow(x)+nrow(i). Check for duplicate key values in i each of which join to the same group in x over and over again. If that's ok, try by=.EACHI to run j for each group to avoid the large allocation. If you are sure you wish to proceed, rerun with allow.cartesian=TRUE. Otherwise, please search for this error message in the FAQ, Wiki, Stack Overflow and data.table issue tracker for advice.
The text was updated successfully, but these errors were encountered:
I think what is happening here is a mismatch between your annotation and MaxQ output, but it is hard to tell with just the annotation file. Can you post a subset of you MaxQ output?
Hi, when running:
MaxQtoMSstatsTMTFormat(evidence = raw.mq, proteinGroups = proteinGroups.mq, annotation = annotation.mq,allow.cartesian=TRUE)
I get the below error. I rerun with "allow.cartesian=TRUE", but the error persists.
Any advice on this? Attached is my annotation file.
annotation_towers.txt
Help appreciated.
GPR
Error in vecseq(f__, len__, if (allow.cartesian || notjoin || !anyDuplicated(f__, : Join results in 1854844 rows; more than 1650276 = nrow(x)+nrow(i). Check for duplicate key values in i each of which join to the same group in x over and over again. If that's ok, try by=.EACHI to run j for each group to avoid the large allocation. If you are sure you wish to proceed, rerun with allow.cartesian=TRUE. Otherwise, please search for this error message in the FAQ, Wiki, Stack Overflow and data.table issue tracker for advice.
The text was updated successfully, but these errors were encountered: