The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
This version introduces a new flow method, but also comes with several breaking changes.
RPhosFate
now utilises the terra
instead
of the raster
package.img2tif()
function can be used to convert all
ERDAS IMAGINE raster files in a directory and its
subdirectories into GeoTIFF raster files.DEMrelatedInput()
function changes:
ns_cha
argument: allows for specifying the
minimum D8 flow accumulation determining a channel.ls_mD8
argument: allows for mimicking D8
flow directions by rounding the D-infinity flow directions to the
nearest multiple of 45 degrees. Please note that this treatment is
always applied to channel cells independently of this argument.cs_wgs
and cs_dir
arguments: These input data are no longer supported for the time
being.SpatRaster
and
SpatVector
classes from the terra
package
instead of the RasterLayer
class from the
raster
and the Spatial*DataFrame
classes from
the sp
packages.is_ths
argument to the RPhosFate()
and catchment()
constructors: allows for specifying the
number of threads to use for processing, where applicable.transport()
method. This implies that the
transportPrerequisites()
method does not save it to disk
any longer.transportCalcOrder()
method, as the
determination of the cell transport calculation order is now integrated
into the transport()
method. This implies that the
firstRun()
as well as subsequentRun()
methods
do not call it and the saveState()
method does not save it
to disk any longer.calibrationQuality()
method now returns its return
value invisibly.RPhosFateHelpers
class.spatstat.geom
from the imported packages list
(utilised functionality is now also provided by
terra
).hydroGOF
from the imported packages list
(maptools
is retiring and hydroGOF
depends on
it via hydroTSM
). Thanks to Roger Bivand for raising this
issue (#17).rgdal
from the suggested packages list and set
the minimum required version of the raster
package to ≥
3.6.3 (rgdal
is retiring and raster
≥ 3.6.3
does not depend on it any longer). Thanks to Roger Bivand for raising
this issue (#17).autoCalibrate2()
method: allows for calibrating
the overland and channel deposition rate in one go.DEMrelatedInput()
function can handle multiple
catchment outlets now and so does the calibrationQuality()
method.DEMrelatedInput()
function now returns the breached
DEM with reversed stream burning if applicable instead of the original
one.DEMrelatedInput()
function now calculates “correct”
slopes even if the channels used for stream burning contain gaps.RPhosFate
now makes sure that the x- and y-coordinates
of gauges used for calibration lie within the extent of the river
catchment object."inChannelRetention"
output of the
calibrationQuality()
method to
"inChannelRetentionRatio"
.RPhosFate
requires R ≥ 3.5.0 now.subsequentRun()
method, which allow for calling the respective methods:
erosionPrerequisites
erosion
emission
transportPrerequisites
transportCalcOrder
cv_MCl
argument to the RPhosFate()
and catchment()
constructors: allows for specifying the
names of the layers, which shall be written to disk with the associated
Monte Carlo iteration in their filenames upon calling the appropriate
methods.calibrationQuality()
method is
now prettier.RPhosFate
now depends on the spatstat.geom
instead of the spatstat
package.whitebox
package (≥ 2.0.0).DEMrelatedInput()
function.DEMrelatedInput()
function now calculates the
slopes from the breached DEM (stream burning is undone beforehand).cs_fex
argument to the
DEMrelatedInput()
function: allows for using ERDAS
IMAGINE raster files for backward compatibility.cs_dir
argument to the
DEMrelatedInput()
function: allows for utilising an
existing D8 flow directions raster using ArcGIS codes.demoProject()
function providing training
data.tinytest
package.covr
.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.