Changements
Source :NEWS.md
motus 6.0.1
- Fix bug in
xxxRunsFilter()
functions resulting in the inability to correctly return the filter id
motus 6.0.0
Potential breaking change
- Changed internal method for loading SQLite databases. Now uses standard method with
DBI::dbConnect()
. Previously, users applyingDBI
functions to databases loaded withtagme()
had to use the$con
sub-element of the connection.$con
should no longer be used (it will result in an error).
Bug fixes
- fixed bug in
deprecateBatches()
which caused an error when removing deprecated batches from receivers.
Other
- Updated internal code for logging messages
- Now use simple wrappers for
DBI::dbExecute()
andDBI::dbGetQuery()
, usingglue::glue_sql()
to help construct statements.
motus 5.0.1
Bug fixes
- fixed bug in
deprecateBatches()
which caused an error when there were no batches to deprecate. - ensure new databases are fully up-to-date (without needing to immediately update).
motus 5.0.0
New features
- New
allruns
andallrunsGPS
views for quicker first passes of the data with large datasets - New field/column
attachment
intagDeps
table - New field/column
numGPSfix
inactivity
andactivityAll
tables - New field/columns
stationName
andstationID
inrecvDeps
tables -
gpsAll()
andactivityAll()
functions allow downloading complete records of GPS points and Activity - Deprecated batches are now returned to a new table
deprecated
ontagme()
-
deprecateBatches()
function to fetch and (optionally) remove deprecated batches from all relevant tables
Bug fixes
- fixed bug in
filterByActivity()
resulting inNA
probabilities - fixed bug in
getGPS()
which crashed ifts
had been converted to date/time format
motus 4.0.6
Bug fixes
- fixed bug resulting in missing metadata tables, and permission errors resulting from JSON formatting
- fixed bug where
forceMeta
did not force metadata download for previously downloaded tags - fixed warnings produced by
plotRouteMap()
on old versions of R
motus 4.0.2
Bug fixes
- fixed rounding error in
filterByActivity()
resulting in mismatchedhourBins
- fixed incorrect receiver types and model assignment for CTT receivers
motus 4.0.0
Small Changes
- Add
test
to metadata intagDeps
table to identify test deployments (tagDeployTest
inalltags
andalltagsGPS
views) - Add
age
andsex
to metadata intagDeps
table - For CTT SensorStation V2
- Add
lat_mean
,lon_mean
, andn_fixes
togps
table - Add
nodets
,firmware
,solarVolt
,solarCurrent
,solarCurrentCumul
,lat
, andlon
tonodeData
table - Add
validated
tohits
table
- Add
motus 3.0.1
Small Changes
- Receiver downloads now have similar progress messages to Project downloads
- Move GPS fields from
alltags
toalltagsGPS
- New function
getGPS()
adds GPS fields to data - Remove NOT NULL constraint on
motusTagID
s in ambiguous tag view
Bug fixes
- Receivers updating to the new version errored on the download start
- Allow renaming (if possible) of large databases on data updates
- Continue checking for activity/nodeData even if first batch returns 0
-
nodeDataId
is corrected tonodeDataID
- Warn users with custom views if they need to be removed prior to updating
motus 3.0.0 (2019-10-16)
Big Changes
- Switch to data version 2
- Includes new CTT antennas
- Includes
nodeData
andnodeDeps
tables for node related data and metadata.
motus 2.0.0 (2019-08-12)
New Features
- New function
activity()
adds hit activity for batches to a newactivity
table in the SQLite database. This is useful for detecting ‘noisy’ periods where hits may be unreliable. - New function
filterByActivity()
allows users to create custom filters using data from theactivity
table. - Added a
NEWS.md
file to track changes to the package - Added support for
httr
for server queries - Added
?motus
package documentation - Added unit testing
motus 1.0.0
2017 Sep 25
- tagme() / tellme() and supporting functions are now in the motusClient package, which is automatically installed from github the first time you do
library(motus)
after installing themotus
package. If automatic installation ofmotusClient
fails, you can install it directly like so:
install_github("motusWTS/motusClient")
2017 Jul 28
- tagme() - for updating local copies of receiver or tag project detection databases
- tellme() - for asking how much data will need to be transferred by the corresponding tagme() call
The latest version of the data server that works with this package is now running on a new box, but its database is only populated with data from 4 (!) receivers. Raw files from other receivers will be re-run with the latest version of the tag finder and added to this database. Only those users willing to wrestle with alpha code and not actually interested in getting their data should be using this package for now.