Errors during Trinity run
This is an indicator that the process ran out of available RAM. If you have more RAM resources to make available to Trinity, then simply rerun your original Trinity command with the altered resources allocated and it should resume approximately where it left off.
If you are resource limited, please consider running Trinity here. If you want to continue to try to run Trinity given your available resources, you can reduce the total RAM requirements by running Trinity with parameter '--min_kmer_cov 2'. Although the assembly should still be of high quality and require less RAM, lowly expressed transcripts may be more highly fragmented in the assembly.
There are a couple reasons why this error message might creep up.
-
all memory has been consumed on the machine. Each butterfly process wants to reserve 10G of maximum heap space. If there's less than 10G of free memory on the machine per butterfly (--CPU setting), then java may not be able to initialize (depends on your OS configuration). Try reducing the --CPU setting and rerunning your Trinity command. It should resume where it left off.
-
Your server might be configured to allow only limited numbers of processes per user. Check your hardware configuration like so:
% cat /etc/security/limits.conf
soft memlock unlimited
hard memlock unlimited
soft stack unlimited
hard stack unlimited
- nofile 131072
soft nproc unlimited
hard nproc unlimited
There are various ways to deal with restricted settings (Google can help).
- NUMA architecture: one of our users found that the java invocation required: -XX:ParallelGCThreads=, otherwise it would try to use too many threads.
A great way to share your data with the Trinity developers is through: https://mega.nz/ as, a command-line interface can be used to easily download data from there.
Alternatively, google drive or dropbox can be used.
Get the Trinity developers direct email address, rather than posting links to your data on the google forum for privacy concerns. Trinity developers will not share your data, so no worries!
- Trinity Wiki Home
- Installing Trinity
- Running Trinity
- Trinity process and resource monitoring
- Output of Trinity Assembly
- Assembly Quality Assessment
- Downstream Analyses
- Miscellaneous additional functionality that may be of interest
- Contributing code
- Trinity Tidbits
- Frequently Asked Questions (FAQ)
- There are too many transcripts! What do I do?
- How to minimize RAM usage
- How do I use reads I downloaded from SRA
- How do I identify the specific reads that were incorporated into the transcript assemblies?
- How can I perform cross-species analysis?
- How do I combine PE and SE reads?
- How can I run this in parallel on a computing grid?
- Computing and Time requirements
- Errors during Trinity run
- Killing Trinity
- Contact us