Skip to content

v1.0.1 (CRAN)

Latest
Compare
Choose a tag to compare
@mcol mcol released this 07 Mar 16:56
· 1 commit to master since this release
v1.0.1
4884ccb

Changes in version 1.0.1 (2025-03-07)

Bugfixes

analyse_baSAR()

  • The number of aliquots used was only partially reported if no aliquots
    were removed, resulting in an incomplete message in the output to the
    terminal.

analyse_FadingMeasurement()

  • The function now checks that an input object generated from an XSYG
    file contains irradiation steps and returns an error if none are
    available, instead of producing an unhelpful output (#588).

  • A regression in plot_RLum.Analysis() caused part of the plot of the
    luminescence curves to be garbled (#589).

  • The function crashed on a file generated by read_XSYG2R() if the
    number of curves available after removal of the irradiation step was
    not enough for the the fading measurement to be analysed (#603).

analyse_pIRIRSequence()

  • The check on the minimum device plot size used to fail if only one
    dimension was below our minimum threshold, and when it was incorrectly
    triggered by the floating point values computed by
    grDevices::dev.size(), which sometimes could be spuriously just
    below threshold. We also changed the minimum device size from 18 to 16
    inches (#593).

calc_CosmicDoseRate()

  • The function crashed if the number of depths provided exceeded that of
    the densities and the latter contained more than one value (#595).

calc_FadingCorr()

  • The function sporadically returned an implausibly large error estimate
    if any of the Monte Carlo simulations produced an outlier solution
    (#597).

  • The function now allocates only as much memory as required if the user
    specifies a value for n.MC other than "auto", which brings a small
    speed-up if fewer than 10 million samples are requested.

  • Input arguments are now more thoroughly checked to avoid warnings or
    unhelpful messages (#599).

calc_FastRatio()

  • The function crashed if the input was an RLum.Analysis object (#586).

plot_AbanicoPlot()

  • The xlim, ylim and zlim parameters are now better validated to
    avoid possible crashes if misspecified (#581).

plot_RLum.Analysis()

  • The function reset incorrectly the graphical parameters for the case
    plot_singlePanels = TRUE. This caused a regression in the plot
    output from analyse_FadingMeasurement() (#589).

sort_RLum()

  • The function doesn’t crash when multiple fields are specified,
    although the actual sort at the moment occurs only on the first field
    (#606).

  • Attempting to sort an empty object returns the object itself instead
    of crashing (#608).

What's Changed

  • Validate xlim, ylim and zlim in plot_AbanicoPlot() by @mcol in #582
  • Complete coverage for calc_CosmicDoseRate.R by @mcol in #583
  • Replace sapply(x, length) and similar with lengths() by @mcol in #585
  • Fix crash in calc_FastRatio() on RLum.Analysis objects by @mcol in #587
  • Check that irradiation steps are available if the originator is read_XSYG2R by @mcol in #590
  • Fix regression in plot generated by analyse_FadingMeasurement() by @mcol in #591
  • Fix the minimum device plot size checks in analyse_pIRIRSequence() by @mcol in #594
  • Tighten checks on inputs and consolidate code in calc_CosmicDoseRate() by @mcol in #596
  • Tighten the outlier threshold in calc_FadingCorr() by @mcol in #598
  • Improve validation and documentation of calc_FadingCorr() arguments by @mcol in #600
  • Improve validation against a character vector by @mcol in #602
  • Fix crash in analyse_FadingMeasurement() if not enough curves are available by @mcol in #604
  • Fix crashes in sort_RLum() if more than one field is specified by @mcol in #607
  • Don't crash when sorting an empty RLum.Analysis object by @mcol in #609

Full Changelog: v1.0.0...v1.0.1