Entering edit mode
6.2 years ago
11707072
•
0
I used the Tailseeker-3.1.7 for the analysis of Tail-seq data. There is no error reported during runing. However it can not estimate the length of spike-ins rightly except spikein8 which maybe estimated by base-calling algorithm. BTW, I found that during the step of "process_signals
" , it generate null pos_tile.sigdists
. As a result, during the step of "calculate_optimal_parameters
", it can only get NaN value for the cutoff. Then, this may contribute to the final result incorrect. Do you ever met this problem? Is there any problem in my settings?
My Settings:
include:
- defaults.conf
run_id: "ts001"
sources:
- id: a
type: HiSeq-RapidV2
dir: "150421_SN7001146_0233_BC6APYACXX"
lane: 2
experimental_samples:
Ctrl1: ATCACG
Ctrl2: CGATGT
dcKO1: TTAGGC
dcKO2: TGACCA
reference_set:
_exp: GRCm38
spikein_samples:
spk8: ACTTGA
spk16: CTTGTA
spk32: CGCTAA
spk64: TCTGCT
spikein_lengths:
spk8: 8
spk16: 16
spk32: 32
spk64: 64
read_cycles:
R5: [1, 100, 1]
Ri: [101, 106, 2]
R3: [110, 209, 3]
dupcheck_regions:
_exp: [[21, 35], [110, 124]]
analysis_level: 1
performance:
enable_gsnap: yes
third_party_basecaller:
R5: AYB