failed to verify signature for macports source

#Failed to verify signature for macports source install
#Failed to verify signature for macports source archive

Timing tests on shuffled FIMO datasets suggest the impact from having to allocate space for buffers at runtime is very minimal.

Switched compile-time, stack-allocated char arrays to runtime, heap-based pointers.

Added -unique ( -u) and -duplicates ( -d) options to only print unique and duplicate in sorted output, to mimic the behavior of sort -u and uniq -d Unix tools.

The unstarch binary implements the character length constants of ID and remainder strings, specific to the build-time settings in the Makefile and in the app-wide constants.

More stringent memory management and stricter adherance to BEDOPS-wide constants, to help reduce likelihood of pointer access out of bounds and incidence of segfaults.

(These constants are specific to the build-time settings in the Makefile and in the app-wide constants.) This follows up on issue 195. The starch binary does more stringent input checks for the character lengths of ID and remainder strings, which must be no larger than 2 ID_EXPONENT - 1 and 2 REST_EXPONENT - 1 characters in length.This limitation is now removed, and a single chromosome (when compressed in a Starch archive) can be up to UINT64_MAX bytes in size.

#Failed to verify signature for macports source archive

Previously, a chromosome record in a Starch archive would result in corrupted metadata, if the chromosome is larger than UINT32_MAX bytes (~4.3GB) in size when compressed.

Errors are no longer reported when error checking is enabled and running in non-fast mode, when a fully-nested element is detected.

The Darwin-specific Makefiles have been fixed to resolve this build issue, so that all OS X BEDOPS binaries should now be able to compile in the correct megarow-specific settings. These binaries rely on wider suite-wide constants and data types that the megarow build variety specifies. These applications specifically were affected: bedextract, bedmap, and convert2bed.

Some applications packaged in the OS X installer or compiled via the OS X command-line developer toolkit lacked megarow build support, despite those flags being specified in the parent Makefile.It is recommended that this build be used only if analyses require a higher level of precision than what the double type allows. This build will use more memory to store floating-point values with higher precision, and processing those data will require more computation time.At this time, “megarow” support is not enabled with higher precision floats. This build type combines support for quadruple, 128-bit precision floats with the typical build type for handling “typical” BED4+ style line lengths.

#Failed to verify signature for macports source install

Please use make float128 & make install_float128 to install this build type.Please refer to the article on double precision for more technical detail. For comparison, the current “non-float128” typical and megarow builds allow measurements on values from approximately ±5e−324 to ±5e324 (subnormal) or ☒.23e-308 to ☒.23e308 (normal).The article on quadruple precision can be useful for technical review.

This build includes support for measurements on values ranging from approximately ☖.48e−4966 to ☖.48e4966 ( subnormal), or ☑.19e-4932 to ☑.19e4932 (normal), which enables bedmap to handle, for example, lower p-values without log- or other transformation preprocessing steps.

A new build type adds support for long double or 128-bit floating point operations on measurement values in bedmap, such as is used with score operators like: -min, -max, -min-element, -max-element, -mean, and so on.

New build type (128-bit precision floating point arithmetic, float128).

Tests are available via source distribution in $/tests and can be run by entering make in this directory.

Begun work on a comprehensive test suite for BEDOPS applications.

Reduced warning: zero as null pointer constant compiler warnings via Clang.

The -min/max-element operators will give results as before (the empty string).

Resolved an issue preventing use of a bash process substitution or Unix named pipe in the reference position: i.e., bedmap -options option, where replaces the empty string output of -echo-map* operations when there are no mapped elements.