8ceea19db110700c4b6612ce4f30ce0b08da7d81
max
  Mon Sep 14 07:34:15 2026 -0700
hg38 Fiber-seq makeDoc: record where the nucleosome hold-back landed, refs #36210

The commit that holds it, 75e82896028, is titled "uniprot otto: the miniprot
cluster job needs absolute paths": two sessions were committing in the same
working copy and the other one took these files out of the shared index first.
It is pushed, so note it in the makeDoc rather than rewrite shared history.

diff --git src/hg/makeDb/doc/hg38/fiberSeq.txt src/hg/makeDb/doc/hg38/fiberSeq.txt
index 7abb25d631e..e9ba3dc578c 100644
--- src/hg/makeDb/doc/hg38/fiberSeq.txt
+++ src/hg/makeDb/doc/hg38/fiberSeq.txt
@@ -131,31 +131,41 @@
 # The lab then asked us to hold the display back while they settle internally
 # on how they want nucleosomes shown, and to keep the track set on FIRE peaks
 # and CpG methylation.  So the files are mirrored and checked but no subtrack
 # is generated: INCLUDE_NUC in fiberSeqTrackDb.py is False.  Setting it True and
 # regenerating is the whole of turning it on, no download needed.
 #
 # What that flag builds, when the lab comes back: it is read depth, not a
 # percentage, which makes it the one wiggle here that cannot take fixed
 # viewLimits.  The genome-wide mean runs from 25 (PS00971) to 142 (PM00001) with
 # sequencing depth, and single loci reach 1.7e5, so it is drawn with autoScale
 # on and the axis is comparable within a sample but not between samples.
 #
 # The flag also moves the per-sample priorities, which is why they are assigned
 # from a running counter rather than a fixed index per data type.  With the flag
 # off the generated fiberSeq.ra is byte-identical to the version before the
-# nucleosome work, which is the check that the counter renumbers correctly.
+# nucleosome work, and with it on to the version that added it, which is the
+# check that the counter renumbers correctly either way.
+#
+# Where to find this change in git: the commits are
+#   d07356d7640  the PM00001 reissue and the nucleosome track
+#   75e82896028  this hold-back
+# The second one reads "uniprot otto: the miniprot cluster job needs absolute
+# paths".  Two sessions were committing in the same working copy at the same
+# time, and the other one picked up these four files out of the shared index
+# before its own commit.  It was pushed that way, so the message stands; go by
+# the file list, not the subject, when reading back through the log here.
 
 ~/kent/src/hg/makeDb/scripts/fiberSeq/fiberSeqCheck.sh /hive/data/genomes/hg38/bed/fiberSeq
 # no lines: all 492 files present, parsing and non-empty
 
 # ---------------------------------------------------------------------------
 # Rebuild the FIRE peak bigBeds
 # ---------------------------------------------------------------------------
 
 # The peak files carry narrowPeak data and even embed the narrowPeak autoSql,
 # but their bigBed header records a field count of 3:
 bigBedInfo -as PM00001/fire-peaks.bb | head -25
 #   fieldCount: 3
 #   definedFieldCount: 3
 #   extraFieldCount: 0
 #   as: table fire_peaks ... 10 columns ...