Closed m-grimes closed 5 years ago
Hi Mark. If this is still problematic, can you provide a more details for your test case. I can run the lines provided just fine and expand/collapse and move nodes around, no problems. But I don't know how to
go into other networks labelled "Network_N" and move one or more nodes. Or try to expand the group while in one of those windows
What exactly do you mean here? Can you provide code to run or steps to follow?
Alex
I'll reply by email since GitHub doesn't like .Rmd files. The code in the attached vignette now works perfectly. But if in Cytoscape any nodes are moved in subnetworks (Network; Network_1, etc.) the subsequent attempts to do any operations causes both R and Cytoscape to hang. Cytoscape won't even quit, has to be forced to quit. Can you reproduce this?
Thanks much,
Mark
University of Montana
On 30 Jun 2018, at 13:29, Alexander Pico wrote:
Hi Mark. If this is still problematic, can you provide a more details for your test case. I can run the lines provided just fine and expand/collapse and move nodes around, no problems. But I don't know how to
go into other networks labelled "Network_N" and move one or more nodes. Or try to expand the group while in one of those windows
What exactly do you mean here? Can you provide code to run or steps to follow?
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/cytoscape/RCy3/issues/29#issuecomment-401561450
This is working fine for me. I can get through the script, move nodes around (by click and drag) and then collapseGroup(). I expanded/collapsed and moved nodes a bunch of times in different orders and couldn't reproduce the error.
Try the latest version of RCy3 by running:
install.packages("BiocManager")
BiocManager::install("RCy3")
_You should see version RCy32.0.81 (skipped a few numbers on accident!)
Maybe there is a relevant fix?
Otherwise, we should confirm you Cytoscape version and then maybe disable apps you have installed. These (rarely) can cause odd bugs.
Did you try moving nodes in the sub-networks, not the main network?
Mark
University of Montana
On 2 Jul 2018, at 12:40, Alexander Pico wrote:
This is working fine for me. I can get through the script, move nodes around (by click and drag) and then collapseGroup(). I expanded/collapsed and moved nodes a bunch of times in different orders and couldn't reproduce the error.
Try the latest version of RCy3 by running:
install.packages("BiocManager") BiocManager::install("RCy3")
Maybe there is a relevant fix?
Otherwise, we should confirm you Cytoscape version and then maybe disable apps you have installed. These (rarely) can cause odd bugs.
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/cytoscape/RCy3/issues/29#issuecomment-401896391
Yes.
Ok. Last guess on this one... Go to Edit>Preferences>Group Preferences and UNCHECK "Show collapsed group nodes as Nested Networks". That is what generates the "Network_N" subnetworks and likely the cause of the errors. Nested networks is a feature that should have never existed in Cytoscape (in my opinion) and no good comes from using them. Try "Compound Node" view if you want to see the children nodes. See screenshot.
Alex
You have identified the problem: the nested networks makes for pretty grouped node icons but the nests can't be touched - some sort of java beehive is unleashed. I was able to reproduce the crash and avoid the crash by turning off "Show collapsed node as Nested Network." Enable attribute aggregation had no effect either way.
THanks!
Mark
On 13 Sep 2018, at 23:00, Alexander Pico wrote:
Ok. Last guess on this one... Go to Edit>Preferences>Group Preferences and UNCHECK "Show collapsed group nodes as Nested Networks". That is what generates the "Network_N" subnetworks and likely the cause of the errors. Nested networks is a feature that should have never existed in Cytoscape (in my opinion) and no good comes from using them. Try "Compound Node" view if you want to see the children nodes. See screenshot.
<img width="634" alt="screen shot 2018-09-13 at 9 57 05 pm" src="https://user-images.githubusercontent.com/1418193/45530609-71669a00-b7a0-11e8-8399-1717c1de78bb.png">
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/cytoscape/RCy3/issues/29#issuecomment-421231582
While testing the group functions I ran across this reproducible problem: if sub-networks are created using collapseGroup, and the nodes are rearranged in any way in those sub-networks, Cytoscape will hang if the expandGroup command is run. Here is what I did.
NOW go into other networks labelled "Network_N" and move one or more nodes. Or try to expand the group while in one of those windows. Sometimes this error shows up:
RCy3::commandsPOST, HTTP Error Code: 500 url=http://localhost:1234/v1/commands/group/expand body={ "groupList": "ALK,CTNND1,CTTN,IRS1,NPM1", "network": "SUID:173" } Error in commandsPOST(paste0("group expand groupList=\"", group.list, : java.lang.NullPointerException
OR: (after ESC):
Error in curl::curl_fetch_memory(url, handle = handle) : Operation was aborted by an application callback
. After that, try to do anything - Cytoscape is hung! Several pages of java errors show up on the Terminal console. I'll just paste the first and last few here:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Exception: null http://35.197.44.209 GpmlReaderFactoryImpl java.lang.NullPointerException at org.cytoscape.task.internal.group.AbstractGroupTask.getGroupSetString(AbstractGroupTask.java:145) at org.cytoscape.task.internal.group.CollapseGroupTask.lambda$getResults$0(CollapseGroupTask.java:120) .... at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:748)