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 tried SBGNview with a custom SBGN file and supplied my user-provided mapping table. Because I made the mapping table manually in an excel-file it coincidentally occurred, that the column for the parameter gene.id.type was not the first column but the second column and the first column was the parameter sbgn.gene.id.type. When I tried running it, it was not able to map any IDs. After some troubleshooting I tried creating a mini-mapping table in R (with the reverse column order), which had previously worked on a different SBGN file and it worked. After changing the column order it also worked with the actual file I was trying to visualize. This makes me think, that some part of the mapping refers to columns not (only) by name but (also) by order. For my understanding, this is not clearly indicated in the documentation of the function arguments. I would also personally prefer the function not to depend on column order if I am already indicating it by the name, but I think it would be okay if this is clearly indicated in the documentation.
Best,
Micha
The text was updated successfully, but these errors were encountered:
Hi,
I tried SBGNview with a custom SBGN file and supplied my user-provided mapping table. Because I made the mapping table manually in an excel-file it coincidentally occurred, that the column for the parameter gene.id.type was not the first column but the second column and the first column was the parameter sbgn.gene.id.type. When I tried running it, it was not able to map any IDs. After some troubleshooting I tried creating a mini-mapping table in R (with the reverse column order), which had previously worked on a different SBGN file and it worked. After changing the column order it also worked with the actual file I was trying to visualize. This makes me think, that some part of the mapping refers to columns not (only) by name but (also) by order. For my understanding, this is not clearly indicated in the documentation of the function arguments. I would also personally prefer the function not to depend on column order if I am already indicating it by the name, but I think it would be okay if this is clearly indicated in the documentation.
Best,
Micha
The text was updated successfully, but these errors were encountered: