-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PTHR24031 sum3 ! chromosome segregation PAINT_REF:24031 #1322
Comments
Very large family: 2800 members. Postpone this fix. |
Removed annotations manually. |
I thought you were now able to open the large families. Is this still an On Thu, Oct 20, 2016 at 12:59 AM, pgaudet notifications@github.com wrote:
|
Yes it's still a problem. The largest Marc and I were able to open since we On Tue, Oct 25, 2016 at 8:12 PM, Suzanna Lewis notifications@github.com
|
Opening large families doesn't seem to be a problem for me. Earlier this summer, on 5/6/16, I opened the family below with over 1500 sequences in order to make some corrections brought to our attention by an MGI user: PTHR24249 (1642 sequences)
Based on file creation dates, I think I was probably using beta 2.18 (I save new versions of PAINT into new directories rather than overwriting and it's been a while since I deleted an old version.) I have just opened it again (using an instance of PAINT 2.25 that had previously opened another family) and it didn't take that long to open, max of 30 minutes, probably less as I wasn't paying that much attention to how long it took since I left in the background while I did other stuff. -Karen Note: I was not at home and based on ping times of google.com, my internet connection was not as fast or consistent as I get at home. |
I can also open PTHR24031. This time it was the first family I loaded into a newly launched instance of PAINT and I was at home with a fast, reliable connection. It took 7-8 minutes to load. |
Ouch, 30 minutes! OK, we should be able to massively reduce this. @selewis, does the current release version of PAINT have sufficient On 25 Oct 2016, at 23:32, Karen R Christie wrote:
|
I wasn't saying that this took 30 minutes to load, only that it loaded within 30 minutes, having taken no time points between starting it and looking at it 30 minutes later to see that it had actually loaded, in comparison to what Pascale reports that she can't load large families at all, and I selected this family because I knew I had opened it previously with a version of PAINT2. For one I actually timed (at home on my normal, good connection), see my other comment about loading PTHR24031, which is huge with over 2800 sequences. That one took 7-8 minutes to load and was the first family loaded into a newly opened instance of PAINT, which always takes longer. For me personally, it's not a priority to make the loading faster. The loading speed is not a show stopper for me, in contrast to some other things which cause me to lose work (geneontology/paint#15). I know that the first load is always much slower than subsequent loads of other families, so on days I plan to do PAINT, I start one loading early while I'm still reading my email. I also generally run two instances of PAINT so that when it's time to load a new family into one instance, I switch to the second one which will have finished loading in the time I was working on something in the first one. I posted into this thread to provide additional info to try to help narrow down where the problem is occurring for Pascale and Mark. |
Trying to open 24031 since more than 1h30. Still nothing. Data get lost somewhere in the Atlantic Ocean !! |
Hi Chris, If there is anything you can do that would make me very happy. I managed to annotate about 10 small families this week, but I need to try to open each family about 10 times before getting one to open. The last message on the terminal is always: (the length varies slightly at each time I try) What is this? Could it be the taxon constraints ? I don't think it's a memory issue on my end - increasing the memory allocation in java when I launch paint (with the -Xmx command) does not help at all. Thanks, |
@krchristie - sounds like you have a workaround (though this quite involved!) @pgaudet and @marcfeuermann thanks for the data points and the log messages. I have asked for some more detailed logging (see #24). Unfortunately what we have now is not much to go on, but I'm going to make some guesses.
This is just the output for the elk reasoner, which is called on ontology loading. It's normally not informative. However, I expect this to be done in <1s. The fact it took 24s leads to speculate that there is something not right in your memory settings. I don't see anything on https://github.com/geneontology/paint about memory settings or minimum memory requirements, so I'm not sure what your protocol is on assigning more memory, I will try and find out more.
This is frustratingly almost infortmative! If only we knew what it was attempting to retrieve (it's nothing to do with the line above, it just happens to follow it). It can't be the ontology, as it must have that for the reasoning step. It could be either family data, or it could be a golr query... until we do #24 it's hard to tell! |
@pgaudet Oh I just realized you said you set the memory using |
OK, I spoke to @selewis and she told me that "IOException Unexpected end of file from server has been returned while sending and receiving information from server" is coming from the PantherService. I check the code and this is definitely the case. Progress, we have a firm diagnosis! We'll also add something to make the logging more informative, and to give more information on how long the service call was running. It seems the issue is worst for you @pgaudet . I'm wondering if this is some network or firewall peculiarity. Do you have VPN software you can use for some tests? |
Hi Chris, I use the command line to do something like Java - jar Xmx#### I started with Xmx2048 (as far as I recall) and went up to 16384 (by I hope this gives you enough information to dig a little further. Thanks, Pascale Le 28 oct. 2016 12:14 AM, "Chris Mungall" notifications@github.com a
|
Hi Chris, What VPN software should I use for what tests? Thanks, Pascale Le 28 oct. 2016 12:31 AM, "Chris Mungall" notifications@github.com a
|
emailed u a few suggestions also - any correlation between family size and time taken? Can you give a few example family IDs just so we can be sure we're comparing like with like? |
Hi Chris, Several points:
Maybe with one exception, I had to try multiple times loading the family
Thanks, Pascale On Fri, Oct 28, 2016 at 12:45 AM, Chris Mungall notifications@github.com
|
Another thing:
Thanks Pascale On Fri, Oct 28, 2016 at 10:40 AM, Pascale Gaudet pgaudet1@gmail.com wrote:
|
Hello again, I seem to have found a way to get PAINT to work: This is much more memory than I thought I needed ! I also tried to double it, but I am not sure that made a difference. I cannot load 1000-members families, for example PTHR23050 crashed twice already. Pascale |
Last update for today: I was very happy to be able to annotate a few Thanks, On Fri, Oct 28, 2016 at 10:46 AM, Pascale Gaudet pgaudet1@gmail.com wrote:
|
Hey Pascale, Do you ever check the speed/consistency of your connection? When I have issues, I often check my connection using the ping command in a terminal window. I usually ping google, but have also pinged yahoo. From where I am, I usually get 20ms - 200ms with either, and slightly faster times with google, but only by a little. ping google.com If I try to use PAINT somewhere where my connection times get really slow (over 1000ms for sure, though high hundreds can be problematic too) or erratic (some pings with very long response times or no response at all), it just stalls. I've had this happen when I had been doing PAINT from home, and then needed to work in a coffee shop for a couple hours while one of my kids was at an appointment, and the coffee shop wifi connection was really terrible and I couldn't load anything in PAINT at all. I don't think PAINT had gone down that day either. -Karen |
Note these are two separate steps.
|
@krchristie - this is helpful, thanks I had @pgaudet do a speedtest and her connection seems fine. It seems most likely the machine is underpowered, it's operating near it's limits when it makes the panther service call, this will increase the probability of a timeout on a 5 minute translatlantic API call. |
@krchristie and @marcfeuermann - how much memory do you both allocate (and how much is available on your machine - I know it's 16G for you Marc)? Do you use the startup script that is available from the releases on github? @pgaudet can you let us know whether you are using your 4G machine or your 8G Machine each time you provide a data point? Also, are you sure this is the command you use?
Note that
|
I have 16 G memory. I have never done anything to change the memory allocation, so I have no idea. I no longer remember how to even check this. I generally run two copies of PAINT at the same time (and sometimes other Java apps, e.g. OBO-Edit too) I launch command line from the terminal window with ./launchPAINT.sh |
OK, this is interesting.
The exact behavior of this may be dependent on system, but I have never seen the memory specified after the jar before. On my mac this has the effect of ignoring the memory setting, and default memory will be used. I don't know if this is the same on your mac. It may be setting the memory to 16G. Or it may be ignoring it and using whatever your system default is for java. |
So it sounds like it's hanging. Can you show what is that the tail of your log when you do this? |
I am currently using 2.25, and my version of launchPAINT.sh (I usually just copy from previous PAINT directories) has this: java -jar paint-all.jar -Xmx1600m |
@pgaudet and @marcfeuermann |
sum3 is a translation initiation factor. Roles in translation (or possibly splicing?)
chromosome segregation is way too indirect:
PomBase SPCC1795.11 sum3 GO:0007059 PAINT_REF:24031 IEA PANTHER:PTN000619593 P translation initiation RNA helicase Sum3 moc2|slh3|ded1 protein taxon:4896 20150318 GO_Central
The text was updated successfully, but these errors were encountered: