Job ID = 1299184 sra ファイルのダウンロード中... Read layout: PAIRED fastq に変換中... 2019-06-03T09:01:13 fasterq-dump.2.9.6 sys: error unknown while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed : NET - Reading information from the socket failed ) 2019-06-03T09:01:13 fasterq-dump.2.9.6 sys: error unknown while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed : NET - Reading information from the socket failed ) 2019-06-03T09:01:13 fasterq-dump.2.9.6 sys: error unknown while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed : NET - Reading information from the socket failed ) 2019-06-03T09:13:42 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:13:42 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:29:00 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:33:19 fasterq-dump.2.9.6 sys: error unknown while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:35:05 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:35:05 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:36:02 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:36:02 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:37:54 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:39:19 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:39:19 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:39:48 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:41:07 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:41:38 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) 2019-06-03T09:48:54 fasterq-dump.2.9.6 sys: timeout exhausted while reading file within network system module - mbedtls_ssl_read returned -76 ( NET - Reading information from the socket failed ) spots read : 51,779,886 reads read : 103,559,772 reads written : 103,559,772 rm: cannot remove ‘[DSE]RR*’: No such file or directory rm: cannot remove ‘fastqDump_tmp*’: No such file or directory fastq に変換しました。 bowtie でマッピング中... Time loading reference: 00:00:00 Time loading forward index: 00:00:00 Time loading mirror index: 00:00:00 Multiseed full-index search: 01:40:07 51779886 reads; of these: 51779886 (100.00%) were paired; of these: 5456809 (10.54%) aligned concordantly 0 times 36868110 (71.20%) aligned concordantly exactly 1 time 9454967 (18.26%) aligned concordantly >1 times ---- 5456809 pairs aligned concordantly 0 times; of these: 518997 (9.51%) aligned discordantly 1 time ---- 4937812 pairs aligned 0 times concordantly or discordantly; of these: 9875624 mates make up the pairs; of these: 8422567 (85.29%) aligned 0 times 1036553 (10.50%) aligned exactly 1 time 416504 (4.22%) aligned >1 times 91.87% overall alignment rate Time searching: 01:40:07 Overall time: 01:40:07 マッピングが完了しました。 samtools でBAM に変換中... [samopen] SAM header is present: 15 sequences. [bam_sort_core] merging from 40 files... [bam_rmdup_core] processing reference chr2L... [bam_rmdup_core] processing reference chr2LHet... [bam_rmdup_core] processing reference chr2R... [bam_rmdup_core] processing reference chr2RHet... [bam_rmdup_core] processing reference chr3L... [bam_rmdup_core] processing reference chr3LHet... [bam_rmdup_core] processing reference chr3R... [bam_rmdup_core] processing reference chr3RHet... [bam_rmdup_core] processing reference chr4... [bam_rmdup_core] processing reference chrM... [bam_rmdup_core] processing reference chrU... [bam_rmdup_core] processing reference chrUextra... [bam_rmdup_core] processing reference chrX... [bam_rmdup_core] processing reference chrXHet... [bam_rmdup_core] processing reference chrYHet... [bam_rmdup_core] 12012277 / 46773920 = 0.2568 in library ' ' BAM に変換しました。 Bed ファイルを作成中... BedGraph に変換中... INFO @ Mon, 03 Jun 2019 21:09:28: # Command line: callpeak -t /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.bam -f BAM -g dm -n /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.10 -q 1e-10 # ARGUMENTS LIST: # name = /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.10 # format = BAM # ChIP-seq file = ['/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.bam'] # control file = None # effective genome size = 1.20e+08 # band width = 300 # model fold = [5, 50] # qvalue cutoff = 1.00e-10 # Larger dataset will be scaled towards smaller dataset. # Range for calculating regional lambda is: 10000 bps # Broad region calling is off # Paired-End mode is off INFO @ Mon, 03 Jun 2019 21:09:28: #1 read tag files... INFO @ Mon, 03 Jun 2019 21:09:28: #1 read treatment tags... INFO @ Mon, 03 Jun 2019 21:09:28: # Command line: callpeak -t /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.bam -f BAM -g dm -n /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.05 -q 1e-05 # ARGUMENTS LIST: # name = /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.05 # format = BAM # ChIP-seq file = ['/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.bam'] # control file = None # effective genome size = 1.20e+08 # band width = 300 # model fold = [5, 50] # qvalue cutoff = 1.00e-05 # Larger dataset will be scaled towards smaller dataset. # Range for calculating regional lambda is: 10000 bps # Broad region calling is off # Paired-End mode is off INFO @ Mon, 03 Jun 2019 21:09:28: #1 read tag files... INFO @ Mon, 03 Jun 2019 21:09:28: #1 read treatment tags... INFO @ Mon, 03 Jun 2019 21:09:28: # Command line: callpeak -t /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.bam -f BAM -g dm -n /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.20 -q 1e-20 # ARGUMENTS LIST: # name = /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.20 # format = BAM # ChIP-seq file = ['/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.bam'] # control file = None # effective genome size = 1.20e+08 # band width = 300 # model fold = [5, 50] # qvalue cutoff = 1.00e-20 # Larger dataset will be scaled towards smaller dataset. # Range for calculating regional lambda is: 10000 bps # Broad region calling is off # Paired-End mode is off INFO @ Mon, 03 Jun 2019 21:09:28: #1 read tag files... INFO @ Mon, 03 Jun 2019 21:09:28: #1 read treatment tags... INFO @ Mon, 03 Jun 2019 21:09:37: 1000000 INFO @ Mon, 03 Jun 2019 21:09:37: 1000000 INFO @ Mon, 03 Jun 2019 21:09:38: 1000000 INFO @ Mon, 03 Jun 2019 21:09:45: 2000000 INFO @ Mon, 03 Jun 2019 21:09:46: 2000000 INFO @ Mon, 03 Jun 2019 21:09:48: 2000000 INFO @ Mon, 03 Jun 2019 21:09:53: 3000000 INFO @ Mon, 03 Jun 2019 21:09:54: 3000000 INFO @ Mon, 03 Jun 2019 21:09:57: 3000000 INFO @ Mon, 03 Jun 2019 21:10:01: 4000000 INFO @ Mon, 03 Jun 2019 21:10:02: 4000000 INFO @ Mon, 03 Jun 2019 21:10:07: 4000000 INFO @ Mon, 03 Jun 2019 21:10:08: 5000000 INFO @ Mon, 03 Jun 2019 21:10:11: 5000000 INFO @ Mon, 03 Jun 2019 21:10:16: 6000000 INFO @ Mon, 03 Jun 2019 21:10:16: 5000000 INFO @ Mon, 03 Jun 2019 21:10:19: 6000000 INFO @ Mon, 03 Jun 2019 21:10:23: 7000000 INFO @ Mon, 03 Jun 2019 21:10:26: 6000000 INFO @ Mon, 03 Jun 2019 21:10:27: 7000000 INFO @ Mon, 03 Jun 2019 21:10:31: 8000000 INFO @ Mon, 03 Jun 2019 21:10:35: 7000000 INFO @ Mon, 03 Jun 2019 21:10:36: 8000000 INFO @ Mon, 03 Jun 2019 21:10:38: 9000000 INFO @ Mon, 03 Jun 2019 21:10:44: 9000000 INFO @ Mon, 03 Jun 2019 21:10:45: 8000000 INFO @ Mon, 03 Jun 2019 21:10:46: 10000000 INFO @ Mon, 03 Jun 2019 21:10:52: 10000000 INFO @ Mon, 03 Jun 2019 21:10:53: 11000000 INFO @ Mon, 03 Jun 2019 21:10:54: 9000000 INFO @ Mon, 03 Jun 2019 21:11:01: 11000000 INFO @ Mon, 03 Jun 2019 21:11:01: 12000000 INFO @ Mon, 03 Jun 2019 21:11:04: 10000000 INFO @ Mon, 03 Jun 2019 21:11:09: 13000000 INFO @ Mon, 03 Jun 2019 21:11:09: 12000000 INFO @ Mon, 03 Jun 2019 21:11:13: 11000000 INFO @ Mon, 03 Jun 2019 21:11:17: 14000000 INFO @ Mon, 03 Jun 2019 21:11:17: 13000000 INFO @ Mon, 03 Jun 2019 21:11:23: 12000000 INFO @ Mon, 03 Jun 2019 21:11:24: 15000000 INFO @ Mon, 03 Jun 2019 21:11:26: 14000000 INFO @ Mon, 03 Jun 2019 21:11:31: 16000000 INFO @ Mon, 03 Jun 2019 21:11:32: 13000000 INFO @ Mon, 03 Jun 2019 21:11:34: 15000000 INFO @ Mon, 03 Jun 2019 21:11:39: 17000000 INFO @ Mon, 03 Jun 2019 21:11:42: 16000000 INFO @ Mon, 03 Jun 2019 21:11:42: 14000000 INFO @ Mon, 03 Jun 2019 21:11:46: 18000000 INFO @ Mon, 03 Jun 2019 21:11:50: 17000000 INFO @ Mon, 03 Jun 2019 21:11:51: 15000000 INFO @ Mon, 03 Jun 2019 21:11:54: 19000000 INFO @ Mon, 03 Jun 2019 21:11:57: 18000000 INFO @ Mon, 03 Jun 2019 21:12:00: 16000000 INFO @ Mon, 03 Jun 2019 21:12:01: 20000000 INFO @ Mon, 03 Jun 2019 21:12:05: 19000000 INFO @ Mon, 03 Jun 2019 21:12:08: 21000000 INFO @ Mon, 03 Jun 2019 21:12:09: 17000000 INFO @ Mon, 03 Jun 2019 21:12:13: 20000000 INFO @ Mon, 03 Jun 2019 21:12:15: 22000000 INFO @ Mon, 03 Jun 2019 21:12:18: 18000000 INFO @ Mon, 03 Jun 2019 21:12:21: 21000000 INFO @ Mon, 03 Jun 2019 21:12:23: 23000000 INFO @ Mon, 03 Jun 2019 21:12:27: 19000000 INFO @ Mon, 03 Jun 2019 21:12:29: 22000000 INFO @ Mon, 03 Jun 2019 21:12:30: 24000000 INFO @ Mon, 03 Jun 2019 21:12:36: 20000000 INFO @ Mon, 03 Jun 2019 21:12:37: 23000000 INFO @ Mon, 03 Jun 2019 21:12:37: 25000000 INFO @ Mon, 03 Jun 2019 21:12:45: 26000000 INFO @ Mon, 03 Jun 2019 21:12:45: 24000000 INFO @ Mon, 03 Jun 2019 21:12:45: 21000000 INFO @ Mon, 03 Jun 2019 21:12:52: 27000000 INFO @ Mon, 03 Jun 2019 21:12:53: 25000000 INFO @ Mon, 03 Jun 2019 21:12:55: 22000000 INFO @ Mon, 03 Jun 2019 21:12:59: 28000000 INFO @ Mon, 03 Jun 2019 21:13:01: 26000000 INFO @ Mon, 03 Jun 2019 21:13:04: 23000000 INFO @ Mon, 03 Jun 2019 21:13:07: 29000000 INFO @ Mon, 03 Jun 2019 21:13:09: 27000000 INFO @ Mon, 03 Jun 2019 21:13:13: 24000000 INFO @ Mon, 03 Jun 2019 21:13:14: 30000000 INFO @ Mon, 03 Jun 2019 21:13:16: 28000000 INFO @ Mon, 03 Jun 2019 21:13:21: 31000000 INFO @ Mon, 03 Jun 2019 21:13:23: 25000000 INFO @ Mon, 03 Jun 2019 21:13:24: 29000000 INFO @ Mon, 03 Jun 2019 21:13:29: 32000000 INFO @ Mon, 03 Jun 2019 21:13:33: 26000000 INFO @ Mon, 03 Jun 2019 21:13:33: 30000000 INFO @ Mon, 03 Jun 2019 21:13:37: 33000000 INFO @ Mon, 03 Jun 2019 21:13:41: 31000000 INFO @ Mon, 03 Jun 2019 21:13:43: 27000000 INFO @ Mon, 03 Jun 2019 21:13:44: 34000000 INFO @ Mon, 03 Jun 2019 21:13:48: 32000000 INFO @ Mon, 03 Jun 2019 21:13:51: 35000000 INFO @ Mon, 03 Jun 2019 21:13:52: 28000000 INFO @ Mon, 03 Jun 2019 21:13:56: 33000000 INFO @ Mon, 03 Jun 2019 21:13:58: 36000000 INFO @ Mon, 03 Jun 2019 21:14:02: 29000000 INFO @ Mon, 03 Jun 2019 21:14:04: 34000000 INFO @ Mon, 03 Jun 2019 21:14:05: 37000000 INFO @ Mon, 03 Jun 2019 21:14:11: 38000000 INFO @ Mon, 03 Jun 2019 21:14:12: 30000000 INFO @ Mon, 03 Jun 2019 21:14:12: 35000000 INFO @ Mon, 03 Jun 2019 21:14:18: 39000000 INFO @ Mon, 03 Jun 2019 21:14:19: 36000000 INFO @ Mon, 03 Jun 2019 21:14:21: 31000000 INFO @ Mon, 03 Jun 2019 21:14:25: 40000000 INFO @ Mon, 03 Jun 2019 21:14:27: 37000000 INFO @ Mon, 03 Jun 2019 21:14:30: 32000000 INFO @ Mon, 03 Jun 2019 21:14:31: 41000000 INFO @ Mon, 03 Jun 2019 21:14:35: 38000000 INFO @ Mon, 03 Jun 2019 21:14:38: 42000000 INFO @ Mon, 03 Jun 2019 21:14:39: 33000000 INFO @ Mon, 03 Jun 2019 21:14:42: 39000000 INFO @ Mon, 03 Jun 2019 21:14:45: 43000000 INFO @ Mon, 03 Jun 2019 21:14:48: 34000000 INFO @ Mon, 03 Jun 2019 21:14:50: 40000000 INFO @ Mon, 03 Jun 2019 21:14:52: 44000000 INFO @ Mon, 03 Jun 2019 21:14:58: 41000000 INFO @ Mon, 03 Jun 2019 21:14:58: 35000000 INFO @ Mon, 03 Jun 2019 21:14:58: 45000000 INFO @ Mon, 03 Jun 2019 21:15:05: 46000000 INFO @ Mon, 03 Jun 2019 21:15:06: 42000000 INFO @ Mon, 03 Jun 2019 21:15:08: 36000000 INFO @ Mon, 03 Jun 2019 21:15:12: 47000000 INFO @ Mon, 03 Jun 2019 21:15:13: 43000000 INFO @ Mon, 03 Jun 2019 21:15:18: 37000000 INFO @ Mon, 03 Jun 2019 21:15:18: 48000000 INFO @ Mon, 03 Jun 2019 21:15:21: 44000000 INFO @ Mon, 03 Jun 2019 21:15:25: 49000000 INFO @ Mon, 03 Jun 2019 21:15:28: 38000000 INFO @ Mon, 03 Jun 2019 21:15:29: 45000000 INFO @ Mon, 03 Jun 2019 21:15:32: 50000000 INFO @ Mon, 03 Jun 2019 21:15:37: 46000000 INFO @ Mon, 03 Jun 2019 21:15:39: 39000000 INFO @ Mon, 03 Jun 2019 21:15:39: 51000000 INFO @ Mon, 03 Jun 2019 21:15:45: 47000000 INFO @ Mon, 03 Jun 2019 21:15:47: 52000000 INFO @ Mon, 03 Jun 2019 21:15:49: 40000000 INFO @ Mon, 03 Jun 2019 21:15:53: 48000000 INFO @ Mon, 03 Jun 2019 21:15:54: 53000000 INFO @ Mon, 03 Jun 2019 21:16:00: 41000000 INFO @ Mon, 03 Jun 2019 21:16:02: 54000000 INFO @ Mon, 03 Jun 2019 21:16:02: 49000000 INFO @ Mon, 03 Jun 2019 21:16:09: 55000000 INFO @ Mon, 03 Jun 2019 21:16:10: 50000000 INFO @ Mon, 03 Jun 2019 21:16:11: 42000000 INFO @ Mon, 03 Jun 2019 21:16:17: 56000000 INFO @ Mon, 03 Jun 2019 21:16:19: 51000000 INFO @ Mon, 03 Jun 2019 21:16:21: 43000000 INFO @ Mon, 03 Jun 2019 21:16:24: 57000000 INFO @ Mon, 03 Jun 2019 21:16:27: 52000000 INFO @ Mon, 03 Jun 2019 21:16:32: 58000000 INFO @ Mon, 03 Jun 2019 21:16:32: 44000000 INFO @ Mon, 03 Jun 2019 21:16:36: 53000000 INFO @ Mon, 03 Jun 2019 21:16:39: 59000000 INFO @ Mon, 03 Jun 2019 21:16:43: 45000000 INFO @ Mon, 03 Jun 2019 21:16:45: 54000000 INFO @ Mon, 03 Jun 2019 21:16:47: 60000000 INFO @ Mon, 03 Jun 2019 21:16:53: 55000000 INFO @ Mon, 03 Jun 2019 21:16:54: 46000000 INFO @ Mon, 03 Jun 2019 21:16:54: 61000000 INFO @ Mon, 03 Jun 2019 21:17:02: 56000000 INFO @ Mon, 03 Jun 2019 21:17:02: 62000000 INFO @ Mon, 03 Jun 2019 21:17:05: 47000000 INFO @ Mon, 03 Jun 2019 21:17:09: 63000000 INFO @ Mon, 03 Jun 2019 21:17:10: 57000000 INFO @ Mon, 03 Jun 2019 21:17:15: 48000000 INFO @ Mon, 03 Jun 2019 21:17:17: 64000000 INFO @ Mon, 03 Jun 2019 21:17:19: 58000000 INFO @ Mon, 03 Jun 2019 21:17:24: 65000000 INFO @ Mon, 03 Jun 2019 21:17:26: 49000000 INFO @ Mon, 03 Jun 2019 21:17:27: 59000000 INFO @ Mon, 03 Jun 2019 21:17:32: 66000000 INFO @ Mon, 03 Jun 2019 21:17:36: 60000000 INFO @ Mon, 03 Jun 2019 21:17:37: 50000000 INFO @ Mon, 03 Jun 2019 21:17:39: 67000000 INFO @ Mon, 03 Jun 2019 21:17:45: 61000000 INFO @ Mon, 03 Jun 2019 21:17:47: 68000000 INFO @ Mon, 03 Jun 2019 21:17:48: 51000000 INFO @ Mon, 03 Jun 2019 21:17:53: 62000000 INFO @ Mon, 03 Jun 2019 21:17:55: 69000000 INFO @ Mon, 03 Jun 2019 21:17:59: 52000000 INFO @ Mon, 03 Jun 2019 21:18:02: 63000000 INFO @ Mon, 03 Jun 2019 21:18:02: 70000000 INFO @ Mon, 03 Jun 2019 21:18:10: 53000000 INFO @ Mon, 03 Jun 2019 21:18:10: 71000000 INFO @ Mon, 03 Jun 2019 21:18:10: 64000000 INFO @ Mon, 03 Jun 2019 21:18:11: #1 tag size is determined as 50 bps INFO @ Mon, 03 Jun 2019 21:18:11: #1 tag size = 50 INFO @ Mon, 03 Jun 2019 21:18:11: #1 total tags in treatment: 34374973 INFO @ Mon, 03 Jun 2019 21:18:11: #1 user defined the maximum tags... INFO @ Mon, 03 Jun 2019 21:18:11: #1 filter out redundant tags at the same location and the same strand by allowing at most 1 tag(s) INFO @ Mon, 03 Jun 2019 21:18:12: #1 tags after filtering in treatment: 25459236 INFO @ Mon, 03 Jun 2019 21:18:12: #1 Redundant rate of treatment: 0.26 INFO @ Mon, 03 Jun 2019 21:18:12: #1 finished! INFO @ Mon, 03 Jun 2019 21:18:12: #2 Build Peak Model... INFO @ Mon, 03 Jun 2019 21:18:12: #2 looking for paired plus/minus strand peaks... INFO @ Mon, 03 Jun 2019 21:18:14: #2 number of paired peaks: 2 WARNING @ Mon, 03 Jun 2019 21:18:14: Too few paired peaks (2) so I can not build the model! Broader your MFOLD range parameter may erase this error. If it still can't build the model, we suggest to use --nomodel and --extsize 147 or other fixed number instead. WARNING @ Mon, 03 Jun 2019 21:18:14: Process for pairing-model is terminated! cut: /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.05_peaks.narrowPeak: No such file or directory pass1 - making usageList (0 chroms): 1 millis needLargeMem: trying to allocate 0 bytes (limit: 17179869184) rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.05_model.r’: No such file or directory rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.05_*.xls’: No such file or directory rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.05_peaks.narrowPeak’: No such file or directory CompletedMACS2peakCalling INFO @ Mon, 03 Jun 2019 21:18:19: 65000000 INFO @ Mon, 03 Jun 2019 21:18:20: 54000000 INFO @ Mon, 03 Jun 2019 21:18:27: 66000000 INFO @ Mon, 03 Jun 2019 21:18:31: 55000000 INFO @ Mon, 03 Jun 2019 21:18:35: 67000000 INFO @ Mon, 03 Jun 2019 21:18:42: 56000000 INFO @ Mon, 03 Jun 2019 21:18:44: 68000000 INFO @ Mon, 03 Jun 2019 21:18:53: 57000000 INFO @ Mon, 03 Jun 2019 21:18:53: 69000000 INFO @ Mon, 03 Jun 2019 21:19:02: 70000000 INFO @ Mon, 03 Jun 2019 21:19:04: 58000000 INFO @ Mon, 03 Jun 2019 21:19:10: 71000000 INFO @ Mon, 03 Jun 2019 21:19:12: #1 tag size is determined as 50 bps INFO @ Mon, 03 Jun 2019 21:19:12: #1 tag size = 50 INFO @ Mon, 03 Jun 2019 21:19:12: #1 total tags in treatment: 34374973 INFO @ Mon, 03 Jun 2019 21:19:12: #1 user defined the maximum tags... INFO @ Mon, 03 Jun 2019 21:19:12: #1 filter out redundant tags at the same location and the same strand by allowing at most 1 tag(s) INFO @ Mon, 03 Jun 2019 21:19:12: #1 tags after filtering in treatment: 25459236 INFO @ Mon, 03 Jun 2019 21:19:12: #1 Redundant rate of treatment: 0.26 INFO @ Mon, 03 Jun 2019 21:19:12: #1 finished! INFO @ Mon, 03 Jun 2019 21:19:12: #2 Build Peak Model... INFO @ Mon, 03 Jun 2019 21:19:12: #2 looking for paired plus/minus strand peaks... INFO @ Mon, 03 Jun 2019 21:19:14: 59000000 INFO @ Mon, 03 Jun 2019 21:19:15: #2 number of paired peaks: 2 WARNING @ Mon, 03 Jun 2019 21:19:15: Too few paired peaks (2) so I can not build the model! Broader your MFOLD range parameter may erase this error. If it still can't build the model, we suggest to use --nomodel and --extsize 147 or other fixed number instead. WARNING @ Mon, 03 Jun 2019 21:19:15: Process for pairing-model is terminated! cut: /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.10_peaks.narrowPeak: No such file or directory pass1 - making usageList (0 chroms): 1 millis needLargeMem: trying to allocate 0 bytes (limit: 17179869184) rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.10_model.r’: No such file or directory rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.10_*.xls’: No such file or directory rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.10_peaks.narrowPeak’: No such file or directory CompletedMACS2peakCalling INFO @ Mon, 03 Jun 2019 21:19:25: 60000000 INFO @ Mon, 03 Jun 2019 21:19:36: 61000000 INFO @ Mon, 03 Jun 2019 21:19:46: 62000000 INFO @ Mon, 03 Jun 2019 21:19:57: 63000000 INFO @ Mon, 03 Jun 2019 21:20:06: 64000000 INFO @ Mon, 03 Jun 2019 21:20:16: 65000000 INFO @ Mon, 03 Jun 2019 21:20:25: 66000000 INFO @ Mon, 03 Jun 2019 21:20:34: 67000000 INFO @ Mon, 03 Jun 2019 21:20:43: 68000000 INFO @ Mon, 03 Jun 2019 21:20:53: 69000000 INFO @ Mon, 03 Jun 2019 21:21:02: 70000000 INFO @ Mon, 03 Jun 2019 21:21:11: 71000000 INFO @ Mon, 03 Jun 2019 21:21:12: #1 tag size is determined as 50 bps INFO @ Mon, 03 Jun 2019 21:21:12: #1 tag size = 50 INFO @ Mon, 03 Jun 2019 21:21:12: #1 total tags in treatment: 34374973 INFO @ Mon, 03 Jun 2019 21:21:12: #1 user defined the maximum tags... INFO @ Mon, 03 Jun 2019 21:21:12: #1 filter out redundant tags at the same location and the same strand by allowing at most 1 tag(s) INFO @ Mon, 03 Jun 2019 21:21:13: #1 tags after filtering in treatment: 25459236 INFO @ Mon, 03 Jun 2019 21:21:13: #1 Redundant rate of treatment: 0.26 INFO @ Mon, 03 Jun 2019 21:21:13: #1 finished! INFO @ Mon, 03 Jun 2019 21:21:13: #2 Build Peak Model... INFO @ Mon, 03 Jun 2019 21:21:13: #2 looking for paired plus/minus strand peaks... INFO @ Mon, 03 Jun 2019 21:21:15: #2 number of paired peaks: 2 WARNING @ Mon, 03 Jun 2019 21:21:15: Too few paired peaks (2) so I can not build the model! Broader your MFOLD range parameter may erase this error. If it still can't build the model, we suggest to use --nomodel and --extsize 147 or other fixed number instead. WARNING @ Mon, 03 Jun 2019 21:21:15: Process for pairing-model is terminated! cut: /home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.20_peaks.narrowPeak: No such file or directory pass1 - making usageList (0 chroms): 2 millis needLargeMem: trying to allocate 0 bytes (limit: 17179869184) rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.20_model.r’: No such file or directory rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.20_*.xls’: No such file or directory rm: cannot remove ‘/home/okishinya/chipatlas/results/dm3/SRX474565/SRX474565.20_peaks.narrowPeak’: No such file or directory CompletedMACS2peakCalling BedGraph に変換しました。 BigWig に変換中... BigWig に変換しました。