Skip to content
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

SearchGUI is successful but PeptideShaker is failing #481

Open
Bin-cc opened this issue Apr 1, 2022 · 2 comments
Open

SearchGUI is successful but PeptideShaker is failing #481

Bin-cc opened this issue Apr 1, 2022 · 2 comments
Assignees
Labels

Comments

@Bin-cc
Copy link

Bin-cc commented Apr 1, 2022

Hi,

Thank you for your such powerful tool. But I encountered a problem when I tried to use it to search my raw files with several engines (X!Tandem, MS-GF+, OMSSA, Comet). Each of them had ran successfully, however, they failed to be processed by PeptideShaker. I has not came up with any solutions. If you can give me some advice? The report file is attched and the PeptideShaker.log is as follows.

Best regards!

report.txt

PeptideShaker.log

Thu Mar 31 20:09:06 CST 2022: PeptideShaker version 2.2.6.
Memory given to the Java virtual machine: 4294967296.
Total amount of memory in the Java virtual machine: 134217728.
Free memory: 121876456.
Java version: 16.0.1.
com.esotericsoftware.kryo.KryoException: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
Serialization trace:
peptideAssumptionsMap (com.compomics.util.experiment.identification.matches.SpectrumMatch)
	at com.esotericsoftware.kryo.serializers.ReflectField.write(ReflectField.java:101)
	at com.esotericsoftware.kryo.serializers.FieldSerializer.write(FieldSerializer.java:108)
	at com.esotericsoftware.kryo.Kryo.writeObject(Kryo.java:627)
	at com.compomics.util.db.object.ObjectsCache.saveObjects(ObjectsCache.java:345)
	at com.compomics.util.db.object.ObjectsCache.updateCache(ObjectsCache.java:418)
	at com.compomics.util.db.object.ObjectsCache.addObject(ObjectsCache.java:204)
	at com.compomics.util.db.object.ObjectsDB.retrieveObject(ObjectsDB.java:480)
	at com.compomics.util.experiment.identification.Identification.retrieveObject(Identification.java:243)
	at com.compomics.util.experiment.identification.Identification.getSpectrumMatch(Identification.java:258)
	at eu.isas.peptideshaker.processing.PsmProcessorRunnable.processPsm(PsmProcessorRunnable.java:191)
	at eu.isas.peptideshaker.processing.PsmProcessorRunnable.run(PsmProcessorRunnable.java:151)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
	at java.base/java.lang.Thread.run(Thread.java:831)
@Bin-cc Bin-cc changed the title PeptideShaker processing canceled SearchGUI is successful but fail in PeptideShaker Apr 1, 2022
@Bin-cc Bin-cc changed the title SearchGUI is successful but fail in PeptideShaker SearchGUI is successful but PeptideShaker is failing Apr 1, 2022
@hbarsnes hbarsnes self-assigned this Apr 1, 2022
@hbarsnes hbarsnes added the bug label Apr 1, 2022
@hbarsnes
Copy link
Member

hbarsnes commented Apr 1, 2022

Hi! I'm afraid this is a known issue with our backend code that we have not yet been able to solve. In other words, it is not due to your input files (besides happening more often on larger datasets that use a lot of memory).

There are only two known fixes at the moment. The first option is to increase the amount of memory given to PeptideShaker. This you can do via the PeptideShaker Welcome dialog > Settings & Help > Settings > Java Settings > Memory.

The second option is to run the processing with only a single thread/core. However, this is significantly slower and should only be done if nothing else works. You can set the number of threads via the -threads option or in the New Project dialog when creating a new project.

@Bin-cc
Copy link
Author

Bin-cc commented Apr 1, 2022

Thank you so much. I will try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants