17. Interpretation of Sectio
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
-<one line to give the program's name and a brief idea of what it does.>
-Copyright (C) <year> <name of author>
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation, either version 3 of the License, or
-(at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program. If not, see <http://www.gnu.org/licenses/>.<one line to give the program's name and a brief idea of what it does.>
+Copyright (C) <year> <name of author>
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see <http://www.gnu.org/licenses/>.Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
-<program> Copyright (C) <year> <name of author>
-This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
-This is free software, and you are welcome to redistribute it
-under certain conditions; type 'show c' for details.<program> Copyright (C) <year> <name of author>
+This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type 'show c' for details.The hypothetical commands show w and show c should show the appropriate parts of the General Public License. Of course, your program’s commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
@@ -283,7 +286,7 @@How to Apply These Terms
diff --git a/docs/articles/a1_data-prep.html b/docs/articles/a1_data-prep.html
index 311429b..6b84b20 100644
--- a/docs/articles/a1_data-prep.html
+++ b/docs/articles/a1_data-prep.html
@@ -1,367 +1,139 @@
-
-
-
+
-
-
-
-
-
-
-
-
-
-Formatting your data
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+Formatting your data • mort
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-
-Formatting your data
+
+
+
+
+
+
All mort functions rely on residence events. Residence events are
similar to detection data, but include a start time, an end time, and
duration. Before proceeding to explore your data and flag potential
mortalities in mort, detection data must be converted into residence
-events. This can be done within mort using the residences()
+events. This can be done within mort using the residences()
function, functions from other packages for acoustic telemetry data, or
manually.
-
-mort format
+
+mort format
+
Residence events are generated in morts from detection data, using
-the residences() function.
+the residences() function.
Detection data can be in any format and have any number of columns,
provided they have a datetime column, a location column, and an animal
ID column:
-
Formatting your data
+ +All mort functions rely on residence events. Residence events are
similar to detection data, but include a start time, an end time, and
duration. Before proceeding to explore your data and flag potential
mortalities in mort, detection data must be converted into residence
-events. This can be done within mort using the residences()
+events. This can be done within mort using the residences()
function, functions from other packages for acoustic telemetry data, or
manually.
mort format
+mort format +
Residence events are generated in morts from detection data, using
-the residences() function.
residences() function.
Detection data can be in any format and have any number of columns, provided they have a datetime column, a location column, and an animal ID column:
-
