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 think this issue is important.
If this issue is not resolved, Cytoscape users who want to import a local GPML (that has been slightly modified from Wikipathways) will have to create a new copy of the pathway on Wikipathways and update it.
And it causes confusion when the Wikipathways team curates it as a mysterious copy.
Hi Kozo, sorry about the confusion about the copied pathway at WikiPathways. This issue definitely needs to be resolved, but in your case I would recommend using the workaround solution, which doesn't involved WikiPathways at all. This works in Cytoscape 3.9, and also in the upcoming 3.10 version:
Import ANY pathway from WikiPathways using the WP app in Cytoscape.
Go to File > Import > Network from file and find your local gpml.
So as long as any pathway has been opened using the WP app, a local gpml can be opened without the import error. Let me know if you have any questions.
Thanks @khanspers (+ I'm sorry for the late replay...),
As you said, after step 1 and 2, I was able to import my local GPML into Cytoscape without any problems!
Note: This assumes that import of local gpmls is supposed to work, which it did previously.
Workflow:
From Task History:
Open any pathway from WikiPathways from Network Search tool, for example sandbox
File>Import Network from File, select gpml, choose "import as pathway". => pathway is imported successfully
Based on this, maybe there's a problem with finding the visual style, which is solved after a pathway is successfully imported from WP.org?
The text was updated successfully, but these errors were encountered: