search

4dsoftware / pride-toolsuite

Automatically exported from code.google.com/p/pride-toolsuite
0 stars 0 forks source link

Pride inspector does not start #7

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi guys!

We have a rather strange configuration here for our pcs, the Desktop is somehow 
mapped to our network and it seems to confuse your PrideInspectorBootstrap.java.
The tool starts from the command line so I guess it is a path specification 
issue. Not a big issue on my side but thought you might want to be aware of it 
in case other users complain :)
Also, note that the log stays empty.

Best regards!

Marc

Original issue reported on code.google.com by mvau...@gmail.com on 3 Jun 2013 at 9:38

GoogleCodeExporter commented 8 years ago 
Hello!

another issue all my colleagues are encountering, seems to be related to your 
bootstrap again so i post it here:
1- default memory setting is too low to open most datasets
2- with increased memory settings the tool does not start anymore
3- the tool starts when using the command line: java -jar PrideInspector

Can it be that you use the java 32 bits by default on 64 bits machines? Again, 
did not find any log...

Btw would be cool to be able to edit memory settings from the GUI :) Especially 
since we have to "hide" pride inspector deep in the file system due to the 
above reported issue.

Original comment by mvau...@gmail.com on 6 Jun 2013 at 10:03

GoogleCodeExporter commented 8 years ago 
Hi Marc,

Thank you for reporting the problem. 

I have build a version of the Inspector with debugging switched on, would you 
mind to rerun what you did and send me the log file? 

You can download it from: http://www.ebi.ac.uk/~rwang/pride-inspector-1.3.0.zip

Many thanks,
Rui

Original comment by harry.r....@gmail.com on 6 Jun 2013 at 1:14