|  | @@ -147,6 +147,23 @@ CALDER_sub_domains(intermediate_data_file,
 | 
	
		
			
				|  |  |  * log file storing the status and running time of each step
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | +## Output Structure
 | 
	
		
			
				|  |  | +The output of the workflow is stored in the folder specified by `--out_dir` ("results" by default) and will look like this:
 | 
	
		
			
				|  |  | +```
 | 
	
		
			
				|  |  | +results/
 | 
	
		
			
				|  |  | +└── HiC_sample_1
 | 
	
		
			
				|  |  | +    ├── 100000
 | 
	
		
			
				|  |  | +    │   └── KR
 | 
	
		
			
				|  |  | +    │       ├── chr1
 | 
	
		
			
				|  |  | +    │       │   ├── chr1_domain_boundaries.bed
 | 
	
		
			
				|  |  | +    │       │   ├── chr1_domain_hierachy.tsv
 | 
	
		
			
				|  |  | +    │       │   ├── chr1_log.txt
 | 
	
		
			
				|  |  | +    │       │   ├── chr1_nested_boundaries.bed
 | 
	
		
			
				|  |  | +    │       │   ├── chr1_sub_compartments.bed
 | 
	
		
			
				|  |  | +    │       │   └── chr1_sub_domains_log.txt
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +```
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  ### Runnig time:
 | 
	
		
			
				|  |  |  For the computational requirement, running CALDER on the GM12878 Hi-C dataset at bin size of 40kb took **36 minutes** to derive the chromatin domains and their hierarchy for all chromosomes (i.e., CALDER Step1 and Step2); **13 minutes** to derive the nested sub-domains (i.e., CALDER Step3). At the bin size of 10kb, it took **1 h 44 minutes and 55 minutes** correspondingly (server information: 40 cores, 64GB Ram, Intel(R) Xeon(R) Silver 4210 CPU @ 2.20GHz). The evaluation was done using a single core although CALDER can be run in a parallel manner.
 |