diff --git a/src/help/JavaHelpSearch/DOCS b/src/help/JavaHelpSearch/DOCS index aa2227fe..9ef95fd3 100644 Binary files a/src/help/JavaHelpSearch/DOCS and b/src/help/JavaHelpSearch/DOCS differ diff --git a/src/help/JavaHelpSearch/DOCS.TAB b/src/help/JavaHelpSearch/DOCS.TAB index ad72b66e..6dd679ba 100644 Binary files a/src/help/JavaHelpSearch/DOCS.TAB and b/src/help/JavaHelpSearch/DOCS.TAB differ diff --git a/src/help/JavaHelpSearch/OFFSETS b/src/help/JavaHelpSearch/OFFSETS index 8a7b9b88..a181bc16 100644 Binary files a/src/help/JavaHelpSearch/OFFSETS and b/src/help/JavaHelpSearch/OFFSETS differ diff --git a/src/help/JavaHelpSearch/POSITIONS b/src/help/JavaHelpSearch/POSITIONS index 91375b46..ce64fcb8 100644 Binary files a/src/help/JavaHelpSearch/POSITIONS and b/src/help/JavaHelpSearch/POSITIONS differ diff --git a/src/help/JavaHelpSearch/SCHEMA b/src/help/JavaHelpSearch/SCHEMA index 0de6873b..b7978b92 100644 --- a/src/help/JavaHelpSearch/SCHEMA +++ b/src/help/JavaHelpSearch/SCHEMA @@ -1,2 +1,2 @@ JavaSearch 1.0 -TMAP bs=2048 rt=1 fl=-1 id1=6709 id2=1 +TMAP bs=2048 rt=1 fl=-1 id1=6727 id2=1 diff --git a/src/help/JavaHelpSearch/TMAP b/src/help/JavaHelpSearch/TMAP index a083f8e0..ea69fd11 100644 Binary files a/src/help/JavaHelpSearch/TMAP and b/src/help/JavaHelpSearch/TMAP differ diff --git a/src/help/Map.jhm b/src/help/Map.jhm index a3886c8c..d96912ac 100644 --- a/src/help/Map.jhm +++ b/src/help/Map.jhm @@ -276,6 +276,8 @@ + + diff --git a/src/help/PAMGUARDTOC.xml b/src/help/PAMGUARDTOC.xml index e1eeb6dc..12209a10 100644 --- a/src/help/PAMGUARDTOC.xml +++ b/src/help/PAMGUARDTOC.xml @@ -198,6 +198,8 @@ + + diff --git a/src/help/utilities/tethys/docs/images/TethysGUI_1.png b/src/help/utilities/tethys/docs/images/TethysGUI_1.png new file mode 100644 index 00000000..4a6f1adc Binary files /dev/null and b/src/help/utilities/tethys/docs/images/TethysGUI_1.png differ diff --git a/src/help/utilities/tethys/docs/images/calibration_information.png b/src/help/utilities/tethys/docs/images/calibration_information.png new file mode 100644 index 00000000..234ff348 Binary files /dev/null and b/src/help/utilities/tethys/docs/images/calibration_information.png differ diff --git a/src/help/utilities/tethys/docs/images/deploymentspanel.png b/src/help/utilities/tethys/docs/images/deploymentspanel.png new file mode 100644 index 00000000..8516c96b Binary files /dev/null and b/src/help/utilities/tethys/docs/images/deploymentspanel.png differ diff --git a/src/help/utilities/tethys/docs/tethys_overview.html b/src/help/utilities/tethys/docs/tethys_overview.html index da30d095..9419fe10 100644 --- a/src/help/utilities/tethys/docs/tethys_overview.html +++ b/src/help/utilities/tethys/docs/tethys_overview.html @@ -43,9 +43,8 @@ img { areas as well.

-

PAMGuard is compatible with Tethys 3.0, released early in 2024.

-

The Tethys database is not a replacement for the existing - +

PAMGuard is compatible with Tethys 3.0 or above, released early in 2024.

+

The Tethys database is not a replacement for the existing PAMGuard Database. Where the PAMGuard database only contains data from a single instrument or cruise, the Tethys database contains data from many cruises and projects and can be used to hold a summary of all data @@ -60,8 +59,7 @@ img {

- Next: Configuring the Tethys - Module + Next: Quick Start



diff --git a/src/help/utilities/tethys/docs/tethys_quickstart.html b/src/help/utilities/tethys/docs/tethys_quickstart.html new file mode 100644 index 00000000..d492f5a6 --- /dev/null +++ b/src/help/utilities/tethys/docs/tethys_quickstart.html @@ -0,0 +1,80 @@ + + + +Tethys + + + +

Tethys Quick Start

+ +

This 'Quick Start' guide is aimed at people who are already familiar with both Tethys and PAMGuard

+

The Tethys database is only used in + PAMGUard Viewer mode and is only used to archive project data to a single + centralised database. + It is NOT a replacement for the existing PAMGuard database.

+ +

PAMGuard Tethys Module

+

Launch PAMGuard in Viewer Mode with an existing set of data.

+

Add a Tethys module to PAMGuard from the File / Add Modules / Utilities menu.

+

A new tab panel will show the Tethys interface

+
+

The tab shows a number of panels for the connection to the server and the various types + of data that will be output to the database. Some of these should summary information on what's in the + current PAMGuard dataset (consisting of your PAMGuard database and binary store), others may be empty until you start to + export to Tethys.

+ + + +

Tethys Server

+

Make sure you have a Tethys Server running. The PAMGuard interface will + only work with Tethys 3.

+

Check the server connection. If PAMGuard has correctly connected to the Tethys server, the top panel of the display will be a normal + grey colour. If the connection cannot be made, the panel will be orange.

+

If required, change the server settings using the "Select Sever" button

+ + +

Project and Instrument Information

+

Either select an existing "Project", or create a new one.

+

You also need to give Tethys more information about the instrument(s) or arrays you've deployed than in previous PAMGuard versions. Again, select an + existing instrument, or set up a new one. You'll notice that this information is held with the rest of the PAMGuard array management information.

+ +

Data Export

+

It's best to export data in the sequence the panels are laid out in on the PAMGuard display, i.e. Calibrations, then Deployments, and finally Detections.

+ +

Calibrations

+

To export the calibration data, press the "Export..." button at the top of the "Instrument Calibration Information" panel. +

Most of the calibration data is taken from the array manager and from the sound acquisition module. However, PAMGuard will ask a few questions about + HOW the instrument was calibrated, when it was done and who is responsible. Fill in as much information as you can! + IF the export is successful, a record will show for each hydrophone (or sensor) in your instrument array in the calibration information table:

+ +
+ +

Deployments

+

PAMGuard will have done it's best to work out the temporal extent of your data by looking in the + PAMGuard database and + binary Store. Where data were collected on a regular duty + cycle, or continuously, there should be a single record in the table of recording periods. If data were collected on a more + "ad-hoc" basis, for instance during a boat based survey, there might be many different records in the table. + Occasionally, there may be short recording periods (e.g. while you were testing kit on deck) that you don't want to export. Either select + individual rows that you want to export, or right click on the table and "Select All".

+ +

Press the "Export..." button and work through the questions to provide additional information about your data, why it was collected, etc.

+

Once the document(s) have been exported, the document names will be shown alongside each PAMGuard deployment period

+
+ +

Detections

+

The bottom left panel shows a list of different types of PAMGuard data that can be exported and should also show the total numbers of each type of data that are available + within the PAMGuard storage systems. Select the datablock you want to export from and press "Export...".

+

You really don't want to try to export zillions of data to Tethys , in the options that will appear you can opt to just export certain types of detections + or summary counts.

+ +
+
+ + +
+
+
+ + diff --git a/src/help/utilities/tethys/docs/tethys_server.html b/src/help/utilities/tethys/docs/tethys_server.html index 50a61a06..b9330ed2 100644 --- a/src/help/utilities/tethys/docs/tethys_server.html +++ b/src/help/utilities/tethys/docs/tethys_server.html @@ -26,7 +26,7 @@

- +