Chromatin accessibility around transcription start sites (TSSs)
Chromatin accessibility around transcription start sites (TSSs)
Next, we’ll use two valr functions to expand the window of the reference point (bed_slop()
) and then break those windows into evenly spaced intervals (bed_makewindows()
).
# A tibble: 50,887 × 7
chrom start end name score strand .win_id
<chr> <int> <int> <chr> <chr> <chr> <int>
1 chrII 9800 9810 YBL107C . - 1
2 chrII 9810 9820 YBL107C . - 2
3 chrII 9820 9830 YBL107C . - 3
4 chrII 9830 9840 YBL107C . - 4
5 chrII 9840 9850 YBL107C . - 5
6 chrII 9850 9860 YBL107C . - 6
7 chrII 9860 9870 YBL107C . - 7
8 chrII 9870 9880 YBL107C . - 8
9 chrII 9880 9890 YBL107C . - 9
10 chrII 9890 9900 YBL107C . - 10
# ℹ 50,877 more rows
Chromatin accessibility around transcription start sites (TSSs)
At this point, we also address the fact that the TSS data are stranded. Can someone describe what the issue is here, based on the figure above?
Chromatin accessibility around transcription start sites (TSSs)
This next step uses valr bed_map()
, to calculate the total signal for each window by intersecting signals from the bigWig files.
Chromatin accessibility around transcription start sites (TSSs)
Once we have the values from bed_map()
, we can group by win_coord
and calculate a summary statistic for each window.
Remember that win_coord
is the same relative position for each TSS, so these numbers represent a composite signal a the same position across all TSS.