High-Performance Open-Source Archive
fputk() gains a na_as_string argument.
When TRUE, an NA in any key component is
preserved as the literal string "NA" produced by
paste() instead of being restored to
NA_character_. This enables round-trip lookups against
formats built via fmap(paste(..., sep = "|"), values),
where the stored keys themselves contain "NA". Default
FALSE preserves existing behavior (NA →
.missing / keep_na).finputk() — composite-label wrapper around INVALUE
lookup, mirroring fputk() on the reverse direction.
Supports the same sep and na_as_string
arguments and dispatches on the stored invalue’s
target_type.paste()-built keys
contain the literal string "NA" for NA inputs,
shows the incorrect result with the default
na_as_string = FALSE, and demonstrates the correct
round-trip with na_as_string = TRUE using a clinical LB
PARAMCD derivation scenario.finputk() — basic two-column reverse lookup and
na_as_string = TRUE usage with NA key
components.examples/CompositeKeyNA.R — runnable companion script
for both examples.stratified_range —
combines a discrete stratum (study arm, subject id, composite key, …)
with per-stratum numeric / Date / POSIXct range buckets. Apply with
fputk(), passing the stratum column(s) first and the value
column last.fmap_strata(stratum, low, high, label, inc_low, inc_high, sep)
— produces a ks_fmap ready for
fnew(..., type = "stratified_range"). The chosen separator
is carried as an attribute and picked up automatically by
fnew().fmap_ranges(low, high, label, inc_low, inc_high) —
convenience helper that turns parallel vectors of numeric / Date /
POSIXct bounds and labels into canonical range keys, removing the need
to hand-craft "low,high,inc_low,inc_high" strings.fparse() / fexport() support the new type
via the
VALUE name (stratified_range, range_subtype: numeric|date|datetime, strata_sep: |)
block syntax. Both canonical
"STRATUM|low,high,inc_low,inc_high" keys and the friendly
"STRATUM"|[low, high) interval form are accepted, including
per-stratum .missing|STRATUM / .other|STRATUM
directives.print.ks_format() renders stratified formats grouped
under Stratum "X": headers.fputk() — programmatic and text-based
construction, date subtype with per-subject windows, per-stratum and
global .other fallbacks, and
fexport()/fparse() roundtrip.fmap_ranges() — builds a numeric age-band format
without hand-crafted canonical keys.examples/StratifiedRanges.R — runnable companion
script.date_range and datetime_range types:
fiscal-year bucketing, fparse() with ISO bounds,
LOW/HIGH open-ended arms,
fput_all() multilabel overlapping windows, auto-detection,
fexport()/fparse() roundtrip, and
datetime_range shift bucketing.examples/DateRanges.R — a self-contained runnable
script with the same scenarios for quick interactive exploration.date_range and datetime_range format
types: bucket Date or POSIXct values into character labels using
interval bounds written as ISO date/datetime strings. Both types reuse
the numeric range-table fast path (sorted-disjoint ranges hit
findInterval() in C).fnew() accepts type = "date_range" /
"datetime_range" and a new optional
date_format argument for parsing custom bound strings.fparse() accepts interval notation with date/datetime
bounds, e.g. [2024-01-01, 2025-01-01) = "FY24" and
[2024-01-01 08:00, 2024-01-01 16:00) = "Day". The type is
auto-detected when no explicit subtype is given.fexport() renders date/datetime range bounds as ISO
strings, enabling full roundtrip through fparse().LOW / HIGH keywords
(rendered as -Inf / +Inf and emitted back as
LOW / HIGH on export) and exclusive
( / ) brackets.ks_format objects now carry a
pre-built range_table field. Range keys are parsed once at
format-creation time (in fnew(), fparse(),
fimport()) rather than on every fput()
call.findInterval() fast path in fput():
sorted, non-overlapping numeric ranges with standard
[low, high) semantics now use R’s built-in
findInterval() (O(n log k) in C), giving a ~10–14× speedup
over the previous per-range R loop on large inputs (benchmarked at 1M
rows).skip_discrete optimisation in fput(): pure
numeric-range formats (no discrete keys) with numeric input now skip the
as.character() + match() step entirely.is_missing(): removed a redundant is.nan()
pass on numeric vectors — is.na() already returns
TRUE for NaN..build_range_table(): ranges defined out-of-order are
now sorted by (low, high) before storage, so the
findInterval fast path triggers regardless of definition
order..build_range_table(): removed a dead
attr<- loop that silently had no effect (subsetting a
character vector creates a copy, stripping any attribute set on the
subset).franges(): extracts all range entries from a
ks_format object as a tidy data.frame with
columns low, high, inc_low,
inc_high, and label. Accepts either a
ks_format object or a registered format name.fmap_to_ranges(): reverse-looks up range bounds
by label — given a vector of coded values that match range labels in a
format, returns the corresponding low / high
bounds (and inclusivity flags) per element.fput() (and fputk()) losing the
tzone attribute when returning POSIXct values
from a value-type format. The result vector was seeded from a tzone-less
NA, so values were silently displayed in the local timezone instead of
the source timezone (e.g. UTC), causing an apparent time-shift. The
tzone attribute of the mapped values is now propagated to
the result.format_library_app() Shiny browser for the global
format library, including filters by name/object type, per-object
details, and mapping table rendering for both ks_format and
ks_invalue entries.format_library_app() from the
Addins menu..missing, .other) in structured form.format_library_app() docs and package index
references.fputk() examples (basic
composite key, fmap() data-driven Date lookup,
fparse() text-defined Date lookup), added
fmap() to the Function Reference table, and rearranged
layout to fit landscape page.fparse()
and fputk()” — character lookup, native Date lookup with
fmap(), and round-trip via
fexport()/fparse().fnew() no longer accepts the reverse
parameter. Use fmap(keys, values) instead of
setNames(values, keys) with reverse = FALSE to
create data-driven formats consistently for all types.fmap(keys, values) helper creates a key-value
mapping that tells fnew() to use the natural direction
(keys → values) without reversal. Works identically for character,
numeric, Date, POSIXct, and logical formats.fmap()” — demonstrates how fmap(keys, values)
replaces the old setNames() + reverse = FALSE
pattern.fmap().reverse = FALSE to the character format created with
setNames(), which caused all lookups to return “NOT
FOUND”.fnew() gains a reverse parameter for
explicit control over named-vector direction. Set
reverse = FALSE to use the natural
setNames(values, keys) convention consistently for all
format types — character, numeric, Date, POSIXct, and logical. The
default (NULL) preserves backward-compatible
auto-detection: reversal for character/numeric, no reversal for value
types.reverse” — demonstrates how to build lookup formats from
data frames using the same setNames() pattern for all
output types.fnew() documentation with detailed explanation
of the named-vector reversal convention and the new reverse
parameter.
Need mirroring services?
Contact our team at info@vpspulse.com.
Mirror powered by VPSpulse
Infrastructure sponsored by VPSPulse & Secure Payments by ArionPay.