Dear Andy,
We had used DANPOS3 a few months back and had run both the dpos and dtriple functions. We observed differences in the number of nuclesome positions called when using these functions. We tried to find the reason for this and came up with the following explanation:
We checked the commands of the dpos and dtriple runs and all the default parameters that would have been applied in the runs. We observed that the dpos and dtriple function defaults for two parameters (--height and --pheight ) were different although as per danpos documentation they should be the same. The dpos default for the --height and --pheight parameters were 5 and 0 respectively, and this is reflected in the danpos dpos documentation.
https://sites.google.com/site/danposdoc/b-documentation/1-dpos/parameters?authuser=0
The dtriple default for --height and --pheight parameters were 0 and 1e-10 respectively, and these are the defaults for running dpeak and dregion functions
https://sites.google.com/site/danposdoc/b-documentation/2-dpeak/parameters?authuser=0
There is no separate danpos documentation for dtriple; it simply refers the reader to dpos/dpeak/dregion parameters. The definitions of --height and --pheight as per the danpos dpos documentation is as follows:
-p , --pheight occupancy (reads density) P value cutoff for defining individual protein binding position. Setting to a value 0 will disable this parameter and use the parameter -q or --height as an instead (default: 0)
-q , --height occupancy (reads density) cutoff for defining individual protein binding position. Setting to a value 0 will disable this parameter and use the parameter -p or --pheight as an instead (default: 5)