TOGA icon indicating copy to clipboard operation
TOGA copied to clipboard

old Java version on run_test.sh micro ValueError: Chain results file TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort

Open LinuxPersonEC opened this issue 1 year ago • 24 comments

Not really a bug but using an older version of Java results in the below. Perhaps a more graceful Java version detection and/or warning/error message? Newer Java of course works.

#### STEP 4: Classify chains using gradient boosting model

Classifying chains
classify_chains: loaded dataframe of size 0
classify_chains: total number of transcripts: 0
classify_chains: 0 rows with spanning chains
classify_chains: filtered dataset contains 0 records
classify_chains: omputing additional features...
classify_chains: WARNING! The final df for classification is empty
classify_chains: df for single-exon model contains 0 records
classify_chains: df for multi-exon model contains 0 records
classify_chains: loading models at /path/to/me/TOGA/./models/se_model.dat (SE) and /path/to/me/TOGA/./models/me_model.dat (ME)
classify_chains: applying models to SE and ME datasets...
classify_chains: applying -1.0 score to the spanning chains
classify_chains: applying -2.0 score to the processed pseudogene alignments
classify_chains: number of processed pseudogene alignments: 0
classify_chains: arranging the final output
classify_chains: classification result stats:
* orthologs: 0
* paralogs: 0
* spanning chains: 0
* processed pseudogenes: 0
classify_chains: using 0.5 as a threshold to separate orthologs from paralogs
classify_chains: combining results for 0 individual transcripts
classify_chains: saving the classification to /path/to/me/TOGA/micro_test_out/temp/trans_to_chain_classes.tsv
classify_chains: found no classifiable chains for 0 transcripts
classify_chains: saving these transcripts to: /path/to/me/TOGA/micro_test_out/temp/rejected/classify_chains_rejected.txt
Chain results file /path/to/me/TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort.
Traceback (most recent call last):
  File "/path/to/me/TOGA/./toga.py", line 1742, in <module>
    main()
  File "/path/to/me/TOGA/./toga.py", line 1738, in main
    toga_manager.run()
  File "/path/to/me/TOGA/./toga.py", line 621, in run
    self.__classify_chains()
  File "/path/to/me/TOGA/./toga.py", line 847, in __classify_chains
    check_chains_classified(self.chain_results_df)
  File "/path/to/me/TOGA/modules/sanity_check_functions.py", line 169, in check_chains_classified
    raise ValueError(msg)
ValueError: Chain results file /path/to/me/TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort

Edit: I do get this error message from the 2nd test on the page:

./toga.py test_input/hg38.mm10.chr11.chain test_input/hg38.genCode27.chr11.bed test_input/hg38.2bit test_input/mm10.2bit --kt --pn test -i supply/hg38.wgEncodeGencodeCompV34.isoforms.txt --nc /path/to/me/TOGA/nextflow_config_files --cb 3,5 --cjn 500 --u12 supply/hg38.U12sites.tsv --ms

#### STEP 4: Classify chains using gradient boosting model

Classifying chains
classify_chains: loaded dataframe of size 0
classify_chains: total number of transcripts: 0
classify_chains: 0 rows with spanning chains
classify_chains: filtered dataset contains 0 records
classify_chains: omputing additional features...
classify_chains: WARNING! The final df for classification is empty
classify_chains: df for single-exon model contains 0 records
classify_chains: df for multi-exon model contains 0 records
classify_chains: loading models at /path/to/me/TOGA/./models/se_model.dat (SE) and /path/to/me/TOGA/./models/me_model.dat (ME)
classify_chains: applying models to SE and ME datasets...
classify_chains: applying -1.0 score to the spanning chains
classify_chains: applying -2.0 score to the processed pseudogene alignments
classify_chains: number of processed pseudogene alignments: 0
classify_chains: arranging the final output
classify_chains: classification result stats:
* orthologs: 0
* paralogs: 0
* spanning chains: 0
* processed pseudogenes: 0
classify_chains: using 0.5 as a threshold to separate orthologs from paralogs
classify_chains: combining results for 0 individual transcripts
classify_chains: saving the classification to /path/to/me/TOGA/test/temp/trans_to_chain_classes.tsv
classify_chains: found no classifiable chains for 0 transcripts
classify_chains: saving these transcripts to: /path/to/me/TOGA/test/temp/rejected/classify_chains_rejected.txt
Chain results file /path/to/me/TOGA/test/temp/chain_results_df.tsv is empty! Abort.
Traceback (most recent call last):
  File "/path/to/me/TOGA/./toga.py", line 1742, in <module>
    main()
  File "/path/to/me/TOGA/./toga.py", line 1738, in main
    toga_manager.run()
  File "/path/to/me/TOGA/./toga.py", line 621, in run
    self.__classify_chains()
  File "/path/to/me/TOGA/./toga.py", line 847, in __classify_chains
    check_chains_classified(self.chain_results_df)
  File "/path/to/me/TOGA/modules/sanity_check_functions.py", line 169, in check_chains_classified
    raise ValueError(msg)
ValueError: Chain results file /path/to/me/TOGA/test/temp/chain_results_df.tsv is empty! Abort.

TOGA/test/temp/chain_results_df.tsv 
gene	gene_overs	chain	synt	gl_score	gl_exo	chain_len	exon_qlen	loc_exo	exon_cover	intr_cover	gene_len	ex_num	ex_fract	intr_fract	flank_cov

LinuxPersonEC avatar Dec 13 '23 20:12 LinuxPersonEC

Hi, I have a similar error of the chain_results_df.tsv

####` Initiating TOGA class ####
Version 1.1.6
Commit: affa067aaf3beeb8c06471fcddf1bb24deff5bc0
Branch: master

Calling cmd:
./modules/chain_score_filter test_input/align_micro_sample.chain 15000 > /nfs/users//TOGA/micro_test_out/temp/genome_alignment.chain

Command finished with exit code 0.
Continue without isoforms file: not provided
Found 1 sequences in /nfs/users//TOGA/test_input/hg38.micro_sample.2bit
Found 1 sequences in /nfs/users//TOGA/test_input/hg38.micro_sample.2bit
Found 2 sequences in /nfs/users//TOGA/test_input/q2bit_micro_sample.2bit
Saving output to /nfs/users//TOGA/micro_test_out
Arguments stored in /nfs/users//TOGA/micro_test_out/project_args.json


#### STEP 0: making chain and bed file indexes

Started chain indexing...
chain_bst_index: indexing 3 chains
chain_bst_index: Saved chain /nfs/users//TOGA/micro_test_out/temp/genome_alignment.chain index to /nfs/users//TOGA/micro_test_out/temp/genome_alignment.bst
Started bed file indexing...
bed_hdf5_index: indexed 3 transcripts


#### STEP 1: Generate extract chain features jobs

Calling cmd:
./split_chain_jobs.py /nfs/users//TOGA/micro_test_out/temp/genome_alignment.chain /nfs/users//TOGA/micro_test_out/temp/toga_filt_ref_annot.bed /nfs/users//TOGA/micro_test_out/temp/toga_filt_ref_annot.hdf5 --log_file /nfs/users//TOGA/micro_test_out/toga_2023_12_21_at_11_46.log --parallel_logs_dir /nfs/users//TOGA/micro_test_out/temp_logs --jobs_num 1 --jobs /nfs/users//TOGA/micro_test_out/temp/chain_classification_jobs --jobs_file /nfs/users//TOGA/micro_test_out/temp/chain_class_jobs_combined --results_dir /nfs/users//TOGA/micro_test_out/temp/chain_classification_results --rejected /nfs/users//TOGA/micro_test_out/temp/rejected/SPLIT_CHAIN_REJ.txt

split_chain_jobs: Use bed file /nfs/users//TOGA/micro_test_out/temp/toga_filt_ref_annot.bed and chain file /nfs/users//TOGA/micro_test_out/temp/genome_alignment.chain
split_chain jobs: the run data overview is:

* vv: False
* jobs: /nfs/users//TOGA/micro_test_out/temp/chain_classification_jobs
* results_dir: /nfs/users//TOGA/micro_test_out/temp/chain_classification_results
* errors_dir: None
* chain_file: /nfs/users//TOGA/micro_test_out/temp/genome_alignment.chain
* bed_file: /nfs/users//TOGA/micro_test_out/temp/toga_filt_ref_annot.bed
* index_file: /nfs/users//TOGA/micro_test_out/temp/genome_alignment.chain_ID_position
* job_size: None
* jobs_num: 1
* bed_index: /nfs/users//TOGA/micro_test_out/temp/toga_filt_ref_annot.hdf5
* jobs_file: /nfs/users//TOGA/micro_test_out/temp/chain_class_jobs_combined
* ref: hg38
* on_cluster: True
split_chain_jobs: searching for intersections between reference transcripts and chains
split_chain_jobs: chains-to-transcripts dict contains 2 records
split_chain_jobs: skipped 0 transcripts that do not intersect any chain
split_chain_jobs: preparing 2 commands
split_chain_jobs: command size of 3 for each cluster job
split_chain_jobs: results in 1 cluster jobs
split_chain_jobs: estimated time: 0:00:00.013618
Command finished with exit code 0.


#### STEP 2: Extract chain features: parallel step

Extracting chain features, project name: chain_feats__micro_test_out_at_1703159205
Project path: ./nextflow_logs/chain_feats__micro_test_out_at_1703159205
Selected parallelization strategy: nextflow
Parallel manager: pushing job nextflow /nfs/users//TOGA/execute_joblist.nf --joblist /nfs/users//TOGA/micro_test_out/temp/chain_class_jobs_combined
Logs from individual chain runner jobs are show below


#### STEP 3: Merge step 2 output

Reading /nfs/users//TOGA/micro_test_out/temp/toga_filt_ref_annot.bed
merge_chains_output: got data for 3 transcripts
merge_chains_output: Loading the results...
merge_chains_output: There are 0 result files to combine
merge_chains_output: got 0 keys in chain_genes_data
merge_chains_output: got 0 keys in chain_raw_data
merge_chains_output: There were 0 transcript lines and 0 chain lines
merge_chains_output: chain_genes_data dict reverted, there are 0 keys now
merge_chains_output: Combining the data...
merge_chains_output: got combined dict with 0 keys
merge_chains_output: Writing output to /nfs/users//TOGA/micro_test_out/temp/chain_results_df.tsv
merge_chains_output: total runtime: 0:00:03.469617


#### STEP 4: Classify chains using gradient boosting model

Classifying chains
classify_chains: loaded dataframe of size 0
classify_chains: total number of transcripts: 0
classify_chains: 0 rows with spanning chains
classify_chains: filtered dataset contains 0 records
classify_chains: omputing additional features...
classify_chains: WARNING! The final df for classification is empty
classify_chains: df for single-exon model contains 0 records
classify_chains: df for multi-exon model contains 0 records
classify_chains: loading models at ./models/se_model.dat (SE) and ./models/me_model.dat (ME)
classify_chains: applying models to SE and ME datasets...
classify_chains: applying -1.0 score to the spanning chains
classify_chains: applying -2.0 score to the processed pseudogene alignments
classify_chains: number of processed pseudogene alignments: 0
classify_chains: arranging the final output
classify_chains: classification result stats:
* orthologs: 0
* paralogs: 0
* spanning chains: 0
* processed pseudogenes: 0
classify_chains: using 0.5 as a threshold to separate orthologs from paralogs
classify_chains: combining results for 0 individual transcripts
classify_chains: saving the classification to /nfs/users//TOGA/micro_test_out/temp/trans_to_chain_classes.tsv
classify_chains: found no classifiable chains for 0 transcripts
classify_chains: saving these transcripts to: /nfs/users//TOGA/micro_test_out/temp/rejected/classify_chains_rejected.txt
Chain results file /nfs/users//TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort.

I don't know if you figure out this issue? Thanks!

lynnyummy avatar Dec 21 '23 12:12 lynnyummy

I also have this problem. Do you know how to solve this?

guo-cheng avatar Dec 28 '23 00:12 guo-cheng

I also have this problem. Do you know how to solve this?

not yet.... have you sorted it out?

lynnyummy avatar Jan 09 '24 09:01 lynnyummy

@kirilenkobm Can you pls look into this? What I don't understand is what Java has to do with any of this, as TOGA doesn't use Java??

MichaelHiller avatar Jan 09 '24 10:01 MichaelHiller

@MichaelHiller @lynnyummy @SomePersonSomeWhereInTheWorld @guo-cheng The Chain results file /nfs/users//TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort. message is misleading -> in fact, nextflow does not even start the jobs. However, it does not return any non-0 error code, so TOGA crashes due to a bit general sanity check. Nextflow indeed requires Java, and, of course, some pairs of versions are incompatible :(. Please try downgrading nextflow. I'd recommend trying 23.10.0

kirilenkobm avatar Jan 12 '24 17:01 kirilenkobm

@MichaelHiller @lynnyummy @SomePersonSomeWhereInTheWorld @guo-cheng The Chain results file /nfs/users//TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort. message is misleading -> in fact, nextflow does not even start the jobs. However, it does not return any non-0 error code, so TOGA crashes due to a bit general sanity check. Nextflow indeed requires Java, and, of course, some pairs of versions are incompatible :(. Please try downgrading nextflow. I'd recommend trying 23.10.0

Already using that:

nextflow -v
nextflow version 23.10.0.5889

Same results:

classify_chains: using 0.5 as a threshold to separate orthologs from paralogs
classify_chains: combining results for 0 individual transcripts
classify_chains: saving the classification to /path/to/me/TOGA/test/temp/trans_to_chain_classes.tsv
classify_chains: found no classifiable chains for 0 transcripts
classify_chains: saving these transcripts to: /path/to/me/TOGA/test/temp/rejected/classify_chains_rejected.txt
Chain results file /path/to/me/TOGA/test/temp/chain_results_df.tsv is empty! Abort.
Traceback (most recent call last):
  File "/path/to/me/TOGA/toga.py", line 1742, in <module>
    main()
  File "/path/to/me/TOGA/toga.py", line 1738, in main
    toga_manager.run()
  File "/path/to/me/TOGA/toga.py", line 621, in run
    self.__classify_chains()
  File "/path/to/me/TOGA/toga.py", line 847, in __classify_chains
    check_chains_classified(self.chain_results_df)
  File "/path/to/me/TOGA/modules/sanity_check_functions.py", line 169, in check_chains_classified
    raise ValueError(msg)
ValueError: Chain results file /path/to/me/TOGA/test/temp/chain_results_df.tsv is empty! Abort.
rk3199@g029:~/TOGA$ ls  /path/to/me/TOGA/test/temp/chain_results_df.tsv
/path/to/me/TOGA/test/temp/chain_results_df.tsv

the .tsv file does have:

chain_results_df.tsv
gene	gene_overs	chain	synt	gl_score	gl_exo	chain_len	exon_qlen	loc_exo	exon_cover	intr_cover	gene_len	ex_num	ex_fract	intr_fract	flank_cov
java --version
java 20.0.1 2023-04-18

LinuxPersonEC avatar Jan 12 '24 17:01 LinuxPersonEC

@MichaelHiller @lynnyummy @SomePersonSomeWhereInTheWorld @guo-cheng The Chain results file /nfs/users//TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort. message is misleading -> in fact, nextflow does not even start the jobs. However, it does not return any non-0 error code, so TOGA crashes due to a bit general sanity check. Nextflow indeed requires Java, and, of course, some pairs of versions are incompatible :(. Please try downgrading nextflow. I'd recommend trying 23.10.0

Hi, I've checked my Nextflow is 23.10.0 and the Java is openjdk 21-internal 2023-09-19.

I checked those error files again, I think probably it is not enough memory for Java, N E X T F L O W ~ version 23.10.0 There is insufficient memory for the Java Runtime Environment to continue. Native memory allocation (malloc) failed to allocate 1424 bytes for AllocateHeap

Can we modify the run_test.sh and specify Java in the script? any suggestion?

thanks!

lynnyummy avatar Jan 17 '24 16:01 lynnyummy

@lynnyummy

The error message is quite misleading - it appears that the problem might be related to Java's heap memory settings rather than a lack of physical memory (it failed to allocate just 1424 bytes, it's nothing). Pls try to increase Java heap size by doing export NXF_OPTS='-Xms1g -Xmx4g'

kirilenkobm avatar Jan 17 '24 20:01 kirilenkobm

export NXF_OPTS='-Xms1g -Xmx4g

Hi, I tried to put this at the end of the command, but still failed and reported the same error. TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort.

lynnyummy avatar Jan 18 '24 11:01 lynnyummy

Seems like I should give this a push https://github.com/hillerlab/TOGA/issues/104 so that nextflow logs are carefully arranged and we can analyse what exactly is going on

kirilenkobm avatar Jan 19 '24 22:01 kirilenkobm

@lynnyummy

The error message is quite misleading - it appears that the problem might be related to Java's heap memory settings rather than a lack of physical memory (it failed to allocate just 1424 bytes, it's nothing). Pls try to increase Java heap size by doing export NXF_OPTS='-Xms1g -Xmx4g'

I sorted out this issue, just specify the memory in my own script.

lynnyummy avatar Mar 04 '24 11:03 lynnyummy

Hi I got the same error for the second test with the human and mouse datasets. I checked the log file, and indicated that `Mar-05 15:41:35.927 [Task submitter] ERROR nextflow.processor.TaskProcessor - Error executing process > 'execute_jobs (2)'

Caused by: java.io.IOException: Cannot run program "sbatch" (in directory "~/TOGA/nextflow_logs/work/15/f2b3a7ba56330223cecf3946904a73"): error=2, No such file or directory

Command executed:

sbatch .command.run

Command exit status:

Command output: (empty)

Work dir: ~/TOGA/nextflow_logs/work/15/f2b3a7ba56330223cecf3946904a73

Tip: when you have fixed the problem you can continue the execution adding the option -resume to the run command line Mar-05 15:41:35.928 [Task submitter] DEBUG nextflow.Session - Session aborted -- Cause: Error submitting process 'execute_jobs (2)' for execution Mar-05 15:41:35.944 [main] DEBUG nextflow.Session - Session await > all processes finished Mar-05 15:41:35.944 [main] DEBUG nextflow.Session - Session await > all barriers passed Mar-05 15:41:35.945 [Task monitor] DEBUG n.processor.TaskPollingMonitor - <<< barrier arrives (monitor: slurm) - terminating tasks monitor poll loop Mar-05 15:41:35.949 [main] DEBUG n.trace.WorkflowStatsObserver - Workflow completed > WorkflowStats[succeededCount=0; failedCount=217; ignoredCount=0; cachedCount=0; pendingCount=317; submittedCount=0; runningCount=-217; retriesCount=217; abortedCount=0; succeedDuration=0ms; failedDuration=0ms; cachedDuration=0ms;loadCpus=-217; loadMemory=0; peakRunning=0; peakCpus=0; peakMemory=0; ] Mar-05 15:41:36.158 [main] DEBUG nextflow.cache.CacheDB - Closing CacheDB done Mar-05 15:41:36.174 [main] DEBUG nextflow.script.ScriptRunner - > Execution complete -- Goodbye`

Seems like I should give this a push #104 so that nextflow logs are carefully arranged and we can analyse what exactly is going on

It can still generate the file genome_alignment.chain, but not chain_results_df.tsv. Can you help to check the issue?

lynnyummy avatar Mar 05 '24 16:03 lynnyummy

Sorry, but where does the Java come from? TOGA is not based on any Java code. If the resume is problematic, could you try a fresh run from the start, providing enough memory? @kirilenkobm Could you pls have a look? Apparently it is problematic to get TOGA running on the Sanger compute system.

Thx !!!

MichaelHiller avatar Mar 07 '24 11:03 MichaelHiller

This problem still persists. Has anyone found a workaround?

Thanks!

jackslinde35 avatar Jun 12 '24 21:06 jackslinde35

font{
    line-height: 1.6;
}
ul,ol{
    padding-left: 20px;
    list-style-position: inside;
}



Hi all,Because I can’t use snakemake in our cluster system. You can check the log file and run the `#### STEP 2: Extract chain features: parallel step` alone. It works for me.Best,Guo-Cheng Li

  

    
                
        
            
                
                        
                            
                        
                        
                            guochengli666
                        
                
                    
                        
                                ***@***.***
                        
                    
            
        
    
    





---- Replied Message ----



  
    
     From 
    
    
        ***@***.***>
        
    
  
  
    
     Date 
    
    
    06/13/2024 05:18
    
  
  
    
     To 
    
    
     
      
        ***@***.***>
        
      
    
  
  
    
     Cc 
    
    
      
        ***@***.***>
        ,
      
      
        ***@***.***>
        
      
    
  
  
    
     Subject 
    
    
          Re: [hillerlab/TOGA] old Java version on run_test.sh micro ValueError: Chain results file TOGA/micro_test_out/temp/chain_results_df.tsv is empty! Abort (Issue #131)

This problem still persists. Has anyone found a workaround? Thanks!

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

guo-cheng avatar Jun 13 '24 00:06 guo-cheng

Hi, I had the same error. With lots of help from chatGPT I discovered that the problem was that I did not have the command "sbatch" from the "slurm" workload manager. To solve it I did the following:

  1. Created a file in the TOGA directory with: nano nextflow.config
  2. Wrote this in the new file: process { executor = 'local' cpus = 2 memory = '4 GB' }

I then confirmed that everything worked ok with this test: nextflow run /home/guest/TOGA/execute_joblist.nf --joblist /home/guest/TOGA/test/temp/chain_class_jobs_combined -c nextflow.config

I think this works, though I am now stuck in step 8.

Blumina avatar Aug 24 '24 04:08 Blumina

I didn't know that a Slurm installation would lack the sbatch command, which submits jobs. Thanks for reporting this and the workaround

MichaelHiller avatar Aug 24 '24 07:08 MichaelHiller

Sorry, I expressed myself incorrectly. I don't have the Slurm package manager installed either.

Using the local configuration resolved the issue in step 2, but now I have the problem in steps 7 and 8 that is reported in this issue:

https://github.com/hillerlab/TOGA/issues/175

Could the solution to both issues involve Slurm?

Is it possible to use TOGA without slurm? I've been trying to install it in my computer without success. The fact that I am using a single computer (with Ubuntu 22.04.3) and not a cluster may be a problem?

Blumina avatar Aug 24 '24 20:08 Blumina

For a normal-sized genome (say mammal), you typically need a compute cluster (with a scheduler). But our upcoming TOGA 2.0 seems to be so fast that a workstation (maybe even laptop) is sufficient.

MichaelHiller avatar Aug 26 '24 05:08 MichaelHiller

This is excellent news. Might I inquire as to the projected release date for TOGA 2.0?

Blumina avatar Aug 26 '24 16:08 Blumina

I was able to run ./run_test.sh micro successfully. However, when I attempted the final test, I received the following mishap. The program runs, but it isn't populating the chain_results_df.tsv. The "Final test" section specifies that this should run for approximately 20 mins, so I imagine that the results_df.tsv file should not be empty. Since the issue seems to be similar to the one with the ./run_test.sh micro, I placed it here. I can also open a new issue, if you would prefer that.

./toga.py test_input/hg38.mm10.chr11.chain test_input/hg38.genCode27.chr11.bed hg38.2bit mm10.2bit --kt --pn test -i supply/hg38.wgEncodeGencodeCompV34.isoforms.txt --nc nextflow_config_files/ --cb 3,5 --cjn 500 --u12 supply/hg38.U12sites.tsv --ms.

classify_chains: found no classifiable chains for 0 transcripts Chain results file TOGA/test/temp/chain_results_df.tsv is empty! Abort.

What is strange is that the files are populated and should be fine.

Writing isoforms data for 3674 transcripts. Found 455 sequences in TOGA/hg38.2bit Found 455 sequences in TOGA/hg38.2bit Found 66 sequences in TOGA/mm10.2bit

Perhaps the issue is here? #### STEP 3: Merge step 2 output merge_chains_output: got data for 3674 transcripts merge_chains_output: Loading the results... merge_chains_output: There are 0 result files to combine merge_chains_output: got 0 keys in chain_genes_data merge_chains_output: got 0 keys in chain_raw_data

GLagunas-Robles avatar Oct 02 '24 15:10 GLagunas-Robles

Hi Glagoonas,

interesting case. I haven't seen this error before.

I assume something is wrong with the nextflow configuration, as the micro test (without nextflow) runs. Could you pls check if you find a tip here https://github.com/hillerlab/TOGA/blob/master/TroubleShooting.md Having the right nextflow and python version is important.

Another test could be to run it sequentially, without the nextflow parameters. To avoid long runtimes, pls only take say ~10 transcripts in the input bed file. Then run it with and without nextflow.

@kirilenkobm If you have any ideas on why the mini test doesn't run, pls add.

Thx a lot Michael

MichaelHiller avatar Oct 04 '24 19:10 MichaelHiller

@Blumina Hi, could you help me, please, with some details about the answer that you provided?:

...
To solve it I did the following:

    Created a file in the TOGA directory with: nano nextflow.config
    Wrote this in the new file:
    process { executor = 'local' cpus = 2 memory = '4 GB' }

I then confirmed that everything worked ok with this test:
nextflow run /home/guest/TOGA/execute_joblist.nf --joblist /home/guest/TOGA/test/temp/chain_class_jobs_combined -c nextflow.config
...

Does your nexflow.config file only contains those lines that you provided? You did not add lines like withName {} I'm trying to use your solution but I got only errors. Could you give more details about it? Any help is welcome!

MauriAndresMU1313 avatar Oct 28 '24 18:10 MauriAndresMU1313

I had the same exact issue, and solved it by just putting the absolute path to the nextflow_config_files directory instead of the relative path. Hope this can help :)

MaximePolicarpo avatar Jan 20 '25 18:01 MaximePolicarpo