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
Error in .rowNamesDF<-(x, value = value) :
duplicate 'row.names' are not allowed
Calls: ... row.names<- -> row.names<-.data.frame -> .rowNamesDF<-
In addition: Warning message:
non-unique value when setting 'row.names': ‘entry withdrawn’
Execution halted
I have attached a tar.gz file with two dataframes as examples. One dataframe works (="df_working.Rda") while the other does not (="df_not_working.Rda) with quantiseq.
I would be glad if you could have a look at these files and check what is going wrong with them.
The text was updated successfully, but these errors were encountered:
Hello @suhuanhou
I've seen that the version number in the description file of the package was not updated. Nevertheless, it should still be the right version. We were well aware of that bug, but it has not been fixed.
You can check #146, specifically this answer, and see if the suggested solution works
The error message says:
Error in .rowNamesDF<-(x, value = value) :
duplicate 'row.names' are not allowed
Calls: ... row.names<- -> row.names<-.data.frame -> .rowNamesDF<-
In addition: Warning message:
non-unique value when setting 'row.names': ‘entry withdrawn’
Execution halted
However, I have double checked the input dataframes. There are no duplicates concerning the HUGO gene symbols in the input data.
I also tried converting the HUGO symbols to ENSEMBL, removing duplicate entries again and back transforming it to HUGO symbols (see https://bioinformatics.stackexchange.com/questions/19584/error-of-duplicated-rownames-although-there-are-no-duplicates for explanation).
However, I still get the same error for many samples.
I have attached a tar.gz file with two dataframes as examples. One dataframe works (="df_working.Rda") while the other does not (="df_not_working.Rda) with quantiseq.
I would be glad if you could have a look at these files and check what is going wrong with them.
The text was updated successfully, but these errors were encountered: