Last changes to x3

repo/pamguard/org/x3/2.2.0/_remote.repositories

@@ -1,4 +1,4 @@
 #NOTE: This is a Maven Resolver internal implementation file, its format can be changed without prior notice.
-#Fri Nov 11 13:13:18 GMT 2022
+#Mon Nov 14 09:57:39 GMT 2022
 x3-2.2.0.jar>=
 x3-2.2.0.pom>=

repo/pamguard/org/x3/2.2.0/m2e-lastUpdated.properties

@@ -0,0 +1,7 @@
+#Fri Nov 11 13:38:50 GMT 2022
+central|https\://repo1.maven.org/maven2|sources=1668173930657
+repo|file\:///Users/au671271/git/PAMGuard/repo|sources=1668173930657
+talan|https\://nexus.talanlabs.com/content/repositories/releases/|sources=1668173930657
+bintray-macster110-jtorch4pam|macster110|https\://dl.bintray.com/macster110/jtorch4pam|sources=1668173930657
+bedatadriven|https\://nexus.bedatadriven.com/content/groups/public/|sources=1668173930657
+unidata-all|https\://artifacts.unidata.ucar.edu/repository/unidata-all/|sources=1668173930657

repo/pamguard/org/x3/2.2.0/x3-2.2.0-sources.jar.lastUpdated

@@ -0,0 +1,14 @@
+#NOTE: This is a Maven Resolver internal implementation file, its format can be changed without prior notice.
+#Fri Nov 11 13:38:50 GMT 2022
+@default-talan-https\://nexus.talanlabs.com/content/repositories/releases/.lastUpdated=1668173930381
+https\://dl.bintray.com/macster110/jtorch4pam/.error=Could not transfer artifact pamguard.org\:x3\:jar\:sources\:2.2.0 from/to bintray-macster110-jtorch4pam (https\://dl.bintray.com/macster110/jtorch4pam)\: Remote host terminated the handshake
+https\://repo1.maven.org/maven2/.error=
+file\:///Users/au671271/git/PAMGuard/repo/.error=
+https\://nexus.bedatadriven.com/content/groups/public/.error=
+https\://artifacts.unidata.ucar.edu/repository/unidata-all/.error=
+https\://artifacts.unidata.ucar.edu/repository/unidata-all/.lastUpdated=1668173930064
+https\://repo1.maven.org/maven2/.lastUpdated=1668173930657
+https\://nexus.talanlabs.com/content/repositories/releases/.error=Could not transfer artifact pamguard.org\:x3\:jar\:sources\:2.2.0 from/to talan (https\://nexus.talanlabs.com/content/repositories/releases/)\: Access denied to https\://nexus.talanlabs.com/content/repositories/releases/pamguard/org/x3/2.2.0/x3-2.2.0-sources.jar. Error code 401, Unauthorized
+file\:///Users/au671271/git/PAMGuard/repo/.lastUpdated=1668173929099
+4d1f727a0c17e3b21ef2f6654eed0b3113a4db97@default-bintray-macster110-jtorch4pam-https\://dl.bintray.com/macster110/jtorch4pam/.lastUpdated=1668173929096
+https\://nexus.bedatadriven.com/content/groups/public/.lastUpdated=1668173930217

src/help/sound_processing/AcquisitionHelp/docs/sudfiles.html

@@ -18,6 +18,19 @@ SoundTrap recorders from
  <p>Inflating SUD files to WAV files generally required between 3 and 5 times as much disk space and could also take 
  a fair amount of time, so not inflating will save both!</p>
  
+ <h3>SUD Index Files</h3>
+ <p>To efficiently navigate SUD files, PAMGuard makes a map of each file and stores it in a new file in the same 
+ folder as the original SUD file. The index files have the same name as the original file, but end with .sudx. 
+ The index files are about 2.5% of the size of the original SUD files. When processing SUD files it is therefore 
+ important that a) the drive containing the SUD files is less than 95% full and b) that the system running PAMGuard has
+ write access to the folder containing the SUD files. </p>
+ 
+ <h3>SUD File Times</h3>
+ <p>The name of each SUD file contains the device serial number and a timestamp (data and time) in the form YYMMDDhhmmss. 
+ Note that these time stamps are in local time. When processing the file, PAMGuard will extract a UTC timestamp from within 
+ each SUD file and apply the UTC time to the data. you may therefore notice that the times of binary files and database
+ entries differ from the times in the file names. </p>
+ 
  <h3>Mixing SUD and WAV files</h3>
  <p>If a SUD file and a WAV file with the same name are in the same folder, then PAMGuard will ignore the SUD file
  and process the WAV file. Note that in this case, PAMGuard will be unable to extract any metadata from the SUD file