Menu
▾
▴
pamguard-developer — Mail list for PAMGUARD developers
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(4) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2011 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2018 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Douglas G. <dg...@st...> - 2022-01-02 16:16:00
|
Happy New Year PAMGuard Developers. To keep up (or catch up) with the times, we're moving PAMGuard from a SVN repository on Sourceforge to a GIT repo on Github. I plan to only migrate the current working branch (NOAA), since the SVN repo is what can be best described as a 'right mess', so will NOT be moving over much of the history. Once migrated, I will lock the SVN repository, allowing no further commits, though I will leave the Sourceforge site in place for the foreseeable future so that code history is available to anyone needing it. This and other mailing lists associated with the Sourceforge site will also become obsolete and will be deleted. I've set up an organisational Github account https://github.com/PAMGuard. I've also created a single 'core' team which people can join of they want to (to replace this email list). If you think you should have write access or admin access to this account, please email me. My feelings though are that, since GIT is a distributed system, very few will have write access, instead, you should clone the repository and we'll pull any code changes from your clone once you're done. If you're currently in the middle of a development, with lots of uncommitted code, then please get in touch asap so that we can discuss how best to handle this. If necessary, we can continue to merge in changes from SVN for a short period, though I have a strong preference to make a clean break with SVN and NOT to have to do this. I'm going to start migrating over some of the plugin modules in the next days, so some repo's will start to appear on Github quite soon. All going well, I hope to have PAMGuard across by mid January. I confess to being new to GIT and not an expert, to please be patient ! Yours, Douglas. ========================== Douglas Gillespie Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Twitter: @_SMRU_ In line with Scottish government guidelines I am working from home, I should be available on email, Skype for Business or Microsoft Teams during normal office hours. The University of St Andrews is a charity registered in Scotland : No SC013532 |
|
From: Angus H. <afh...@gm...> - 2021-11-26 04:33:54
|
Hi All, Has anyone had luck receiving a NMEA feed from a Garmin Montana 700+ in PamGuard? I can get my old garmin to receive the NMEA feed fine, but i can't get the new one to work. PamGaurd won't give me a serial port option, the little drop down box is empty, when normally it has at least 1 option, 2 if the NMEA feed is working. The garmin is on the Garmin Spanner setting, as per the manual. https://www8.garmin.com/manuals/webhelp/GUID-20A50E5B-3DFB-42C7-A3B4-8D55519B532C/EN-US/Montana_7xx_OM_EN-US.pdf Also any recommendations for newer GPS units that talk very well with Pamguard for future projects needing new gear. Probably something that is fairly high power, or has an external antenna, for indoor use, at sea on a large vessel. Thanks, Angus |
|
From: Michael O. <m2o...@gm...> - 2021-09-20 10:17:04
|
Hi everyone. Just a quick note to let you know that we are moving future PAMGuard development to the NOAA branch on Sourceforge. All of the changes from the Java16 branch have been merged, up to and including Friday Sept 17 2021. If you have been doing any development work in the Java16Maven branch that has not been committed to the SVN, please do that soon. I'll monitor the Java16Maven branch and sync any commits into the NOAA branch over the next few weeks. Thanks so much, and please let us know if you have any questions or concerns. Michael |
|
From: Douglas G. <dg...@st...> - 2021-04-15 13:45:59
|
Hi All, I've had a bit of a clean up of the sourceforge Developer list. There were many names in there of people I didn't know, or know that they are not currently involved in PAMGuard development, so I've removed them. If you think that you should still be on the PAMGuard developers list on Sourceforge, please contact me and I'll reinstate you. Remember that if you only want to check out versions of the code as it's developed and are not planning to check anything back in, you can do that anonymously. Sorry if I causeed anyone any inconvenience. Douglas. ========================== Douglas Gillespie Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Twitter: @_SMRU_ In line with Scottish government guidelines I am working from home, I should be available on email, Skype for Business or Microsoft Teams during normal office hours. The University of St Andrews is a charity registered in Scotland : No SC013532 |
|
From: Brian M. <Bri...@aw...> - 2021-01-18 02:50:50
|
Hi Fabio,
Thanks for your interest in my work, and for your interesting question.
I don't have any experience running Pamguard without a user interface, but I think that it might be possible. A while back there was a project to run Pamguard in 'network' mode with control and display of data were done over a (wireless) network. I don't remember hearing much about this recently, but the Pamguard developers, copied here, should be able to provide a definitive answer on the status of these features.
Just out of curiosity, why do you want to run Pamguard without a user interface?
Cheers,
Brian
From: FABIO CASSIANO <fab...@en...>
Sent: Monday, 18 January 2021 00:10
To: Brian Miller <Bri...@aa...>
Subject: Question about PAMGUARD [SEC=OFFICIAL] appended Classification
Hello Brian,
I'm a PhD Student, and I'm working on the detection of sperm whale, supervised by Flore SAMARAN. I was reading your PhD thesis, and I saw that you had work with PAMGUARD.
I would like to know if there is a possibility to run PAMGUARD without the user interface ?
Best regards,
Fabio CASSIANO
PhD Student CIFRE with Fondation des mers australes
Lab-STICC (UMR 6285)
ENSTA-Bretagne - Pôle STIC/SISO
-----------------------------------------
2 rue François Verny
29806 Brest Cedex 9
+33(0)2 98 34 89 92
[cid:image002.png@01D6ED9A.48025FF0] [cid:image004.jpg@01D6ED9A.48025FF0]
___________________________________________________________________________
Australian Antarctic Division - Commonwealth of Australia
IMPORTANT: This transmission is intended for the addressee only. If you are not the
intended recipient, you are notified that use or dissemination of this communication is
strictly prohibited by Commonwealth law. If you have received this transmission in error,
please notify the sender immediately by e-mail or by telephoning +61 3 6232 3209 and
DELETE the message.
Visit our web site at http://www.antarctica.gov.au/
___________________________________________________________________________
|
|
From: Michael O. <m2o...@gm...> - 2020-11-03 22:54:00
|
Hi everyone. Just wanted to drop a quick note to say that we are moving all development from the Java12 branch on the PAMGuard Sourceforge SVN to the Java12Maven branch. They are essentially the same, but the Java12Maven branch uses Maven to handle the dependencies (just in case you didn't already guess that) I will keep the two branches synchronized for a few weeks in case anyone is currently doing any development in the Java12 branch. If you need more time, please let me know. If you interested in more information, I have a document which describes setting up Eclipse projects for the Java12Maven branch. Email back to mo...@st... and let me know if you'd like me to send it to you. If you're getting this email and you have no idea what I'm talking about, then let me know that as well and I can take you off the mailing list. Michael |
|
From: Michael O. <m2o...@gm...> - 2020-10-23 22:18:27
|
Hi everyone. We have a new PAMGuard release for you - something to look forward to when you get back to the office/lab/covid-friendly workspace on Monday. A lot of bug fixes and some upgrades that you will be interested in. The new version number is 2.01.05. Remember that this version does not require a separate installation of Java! Java 13 is bundled with the installer so you won't need to worry about it. Because of that, though, this version will only work on 64-bit machines. If you have a 32-bit machine, please download the older version 2.00.20 instead. All of these are available on the PAMGuard website, www.pamguard.org. Bug Fixes 1. Bug 474. Click Detector Classifier fails when trying to use amplitude range for classification. 2. Bug 476. Array Manager dialog throws exception if there is only 1 hydrophone. 3. Bug 478. Ishmael Detector auto-scaling graphics does not work well. 4. Bug 479. Increase number of characters in fixed landmark module from 50 to 256. 5. Bug 481. Depending on Windows Security settings, PAMGuard may not be able to access dll library (such as NMEA). 6. Bug 482. Concurrency problem when hydrophone interpolation method is not set to "Use Latest Value". 7. Bug 483. Radar display loses it's params when new modules are added. 8. Bug 484. Datagram Display error. 9. Bug 485. 3D Group Localiser limited by millisecond times when dealing with closely-spaced hydrophones. 10. Bug 486. UDF tables not getting copied over to new database properly. 11. Bug 487. Database module not working with newer version of MySQL 12. Bug 488. Incorrect 0-peak and peak-peak calculations in Filtered Noise Measurement module. Upgrades 1. Speed up adding subdetections to superdetections. 2. Added new system of scrolling to data in Spectrogram, using CTRL+arrow keys to move to previous/next displayed data unit. 3. Implemented new Effort Monitoring System to track on/off-effort information 4. Added ability to receive NMEA over UDP multicast in addition to UDP broadcast 5. Added logger form annotation to Spectrogram Annotation module. 6. Better auto-scaling in Ishmael Detector graphics window. 7. Change to Windows temporary folder location, to get around Windows Security settings that were preventing some modules from working properly. As always, if you have any problems please don't hesitate to send us an email at su...@pa.... Include as much information as you can, including text from the black DOS console window with error messages if possible. Thanks, and enjoy! |
|
From: Michael O. <m2o...@gm...> - 2020-08-17 12:59:41
|
Hi everyone. We may have been stuck at home for the last few months, but we've kept busy! Here is a new PAMGuard release for you, full of bug fixes and upgrades. This is version 2.01.04 and, like the previous release, this is bundled with the freely-available and open-source Java implementation OpenJDK 13 (version 13.0.1). If you are upgrading from a PAMGuard Core release (1.15.xx), PAMGuard Version 2 contains major updates. You should read and understand the notes listed in the README file for Beta Version 2.00.10 before running this version. Don't worry - this will install into a different location than 1.15.xx, so you won't lose the old program. Also, 2.01.04 will open up your psf file, but upon saving it will convert it to a newer-format psfx file when you exit PAMGuard. If you are upgrading from a Java 8 PAMGuard Beta release (2.00.xx), this will install into a different location so you won't lose the old program. Your psfx files are compatible with this version and vice-versa (i.e. you can switch back and forth to 2.00.xx if you need to). Drop by www.pamguard.org <https://l.facebook.com/l.php?u=http%3A%2F%2Fwww.pamguard.org%2F%3Ffbclid%3DIwAR1sceoH-S3Q4dhV0yoRebQahgIbTaqkmRa5uWSMPWOzU7JUbtQ7QfOI5aY&h=AT2ph8o9-h3l2Vuwu3yW92YPXCkPe7SPVj0QahvL7A7JPp_6KBUTLFfGSOMa8Z1Kp09KKyLcaX3wZg_oEROVL4JcqZJ3oqXOipDMXS_cuYbfuXMh8OuX26GlOGbx5Q24v4j_0Tj4RwjC5TuSRQ&__tn__=-UK-R&c[0]=AT3S3gXOlvdI5bMZ85YGHYBboKWKqSqFeVgp2aZtGj2saaxorfdiXlTeGYo6lgicu6649y-RdUlDbUcCMENd-UI4NONtVIE5yRmdgJNarKUp65oMyrfAojJrX46yIsgQLiwXur_wbBfilLbtJjB8kzzkUBiiaWbPavYKC3c> and check it out! Bug Fixes 1. Bug 451. Small time offset was being applied when post-processing wav files. 2. Bug 453. Adding a new spectrogram display causes PAMGuard to throw exception 3. Bug 455. Cepstrum creating data units using channels it should not be using 4. Bug 456. Under certain conditions, the Ishmael detection plugin that is shown at the bottom of the spectrogram can disappear about 500 msec behind the current time. 5. Bug 457. PAMGuard throws exception in Viewer mode when trying to load a data unit that has more than 1 annotation 6. Bug 458. Contour lines on map disappear when user zooms in 7. Bug 459. Rocca does not save wav clip properly when WMD is source 8. Bug 460. Click Detector BT Display vertical axis shows all zeroes when zooming out 9. Bug 461. Fix pam symbol drawing - bit of a mix up between width and right edge 10. Bug 462. Fix time offset bug in Decimator. Was putting data times a chunk out of synch. 11. Bug 463. Changed start sample in the data unit to be actual start sample and not the end sample. 12. Bug 464. Click Train Detector multiplying instead of dividing for long tracks. 13. Bug 465. Matched click classifier peak search was not working. 14. Bug 466. Bug in IIR filter which was not correctly handling odd numbered band pass or band stop filters. 15. Bug 467. Fix bug in triggered recordings that was messing up the amount of time. 16. Bug 468. User Display tab does not disappear when the module is removed. 17. Bug 469. Mark Observers may not work properly in TD Displays 18. Bug 470. Datagram not displaying colours properly, hanging while scrolling. 19. Bug 471. Beamformer, LTSA and Cepstrum data not displaying data properly in Spectrogram. 20. Bug 472. Viewer mode crashing when generating a Datagram from very large binary files. 21. Bug 473. ReportGenerator throwing exception when trying to generate report. Upgrades 1. Add functionality for bluetooth headsets. 2. Add user-facing option to adjust the startup delay for the time-correction (Global Time module). This provides a workaround to speed up analysis of thousands of wav files (i.e. by setting startup delay to 0 instead of default value of 2000 ms). 3. Add support for RS Aqua time format. 4. Add 15 minute data load option to viewer mode. 5. Add 3D map for target motion module. 6. Add option to alarm module to attach screenshots of all frames to email alerts. 7. Add Beamformer and Bearing Localiser modules 8. Added Global Medium Manager, to switch between air and water mediums 9. Added global hotkeys to Logger module. 10. Added channel display to noise one band measurement display. 11. Added Azigram module, to work in conjunction with Difar. 12. Added beaked whale to sim sounds 13. Added ctrl-p hotkey to print-screen button. 14. Update simulated daq so that it generates new random noise correctly on each call rather then recycling old data. Makes the output more spectrally flat. 15. Changes to FX Display to make it more intuitive - menu options, button placement, etc. |
|
From: Ying Xu <yi...@we...> - 2020-07-29 03:40:58
|
Dear whom it may concern This is Ying Xu from Western Sydney University. I am a postdoc working on the neuromorphic auditory systems and applications. We developed a pair of a real-time nonlinear cochlear model in both software and hardware, and we have tested it for a 2D sound localisation experiment in our real office. We have seen with the nonlinear cochlea, the sound localisation system can achieve outstanding accuracy in the reverberant environment. I have two questions : 1. Would you be interested in us developing a cochlea module and processing for localisation and identification? 2. If you are aware of a database we can test it on? Please find the link of my work : Xu, Y., Afshar, S., Singh, R. K., Wang, R., van Schaik, A., & Hamilton, T. J. (2019). A binaural sound localization system using deep convolutional neural networks. Proceedings - IEEE International Symposium on Circuits and Systems. https://doi.org/10.1109/ISCAS.2019.8702345 and the details in my thesis : https://search.proquest.com/docview/2290954353?pq-origsite=gscholar&fromopenview=true Kind Regards, Ying |
|
From: Michael O. <m2o...@gm...> - 2020-01-20 12:50:10
|
Hi everyone. I wanted to write a quick note to say that we will very shortly stop working on the current PAMGuard 'Core' version, and switch to the Java12 branch that is found on the PAMGuard Sourceforge SVN. The Java12 branch is a duplicate of the UIDBranch (the current 'Beta' version), but modified to work with Java version 9 and up. There is also a Java12Maven branch which is the same as Java12 but uses Maven to handle dependencies. This isn't quite ready yet, but eventually this one will become the branch of choice for all development work. If you interested in more information, I have two documents which describe setting up Eclipse projects for both of the branches. Email back to mo...@st... and let me know if you'd like me to send them to you. If you're getting this email and you have no idea what I'm talking about, then let me know that as well and I can take you off the mailing list. Michael |
|
From: Michael O. <m2o...@gm...> - 2019-07-17 13:08:38
|
Hi everyone. We've just released an installer for the Beta branch version of PAMGuard, but with Java 12 bundled instead of Java 8. The Java 12 development is occurring in a different branch (called 'UID Java 12', because I couldn't come up with anything more clever). We are keeping the regular beta branch (SMRU_UID) and this branch synchronized, so development can happen in either. However, we'd like to transition to just the Java 12 branch in the autumn sometime, and only update SMRU_UID when required. If you haven't already worked with Java 12, it's probably a good time to start. For the most part you probably won't notice a difference. One major issue, though, is that Java 12 no longer bundles JavaFX. So you will need to download JavaFX separately and add it as a library to your build path. Download the Java 12 JDK here: https://jdk.java.net/12/ Download the JavaFX 12 JDK here: https://gluonhq.com/products/javafx/ This page has good information about using JavaFX in an IDE: https://openjfx.io/openjfx-docs/#introduction look at the menu along the left for info on installing into your IDE of choice. Send us an email if you have any problems or need help setting up. Michael |
|
From: Michael O. <m2o...@gm...> - 2019-06-27 11:01:16
|
Hi everyone. Another release today, just in time for the summer. The new Core version is 1.15.17, and the new Beta version is 2.00.17. Just a couple bug fixes in Core. More changes in the Beta version, including the new Gebco netCDF map file compatibility. Download now from www.pamguard.org. Remember that even though the Core download is the default, you really need to be switching over to the Beta version. We're also updating the API's (it's been awhile, sorry about that). Find the links under the Developer menu on the website. Here is a list of the changes: Bug Fixes 1. Bug 427. Soundtrap import not closing binary files properly if BCL files do not contain off-effort 'E' line (Beta only) 2. Bug 428. Decimator crashing in viewer mode (Beta only) 3. Bug 429. Click Bearings at 180 degrees (both) 4. Bug 430. Rocca calculates inflection point parameters incorrectly (both) 5. Bug 431. Error when trying to mark section of spectrogram to send to Bearing Calculator module (Beta only) 6. Bug 432. MySQL database interface - connection problems (Beta only) Upgrades (Beta Only) 1. New display for Gebco Netcdf bathymetry maps. 2. Difar enhancements based on recent field testing. 3. Click Train Detector upgrades, including localisation capabilities. 4. Updates to the Ishmael detectors. |
|
From: Michael O. <m2o...@gm...> - 2019-05-06 10:19:50
|
Hi everyone. Big release today - new versions for both Core (1.15.16) and Beta (2.00.16). Lots of bug fixes and upgrades for both, so please download and try it out. One important thing: these installers have the Java run-time engine bundled up with them. This means that the download is about 100Mb larger (sorry) but more importantly no more issues with having no/incorrect versions of java on your computer. This is the first new Core release in almost a year. A lot of the bug fixes are old ones, having been incorporated into the Beta version a long time ago. Which brings us to a point we've mentioned many times - there is no new development happing in Core, and very soon we will no longer be offering the Core version at all. If you haven't already upgraded to Beta, PLEASE DO IT! There are so many new features, from better displays to new and updated modules. You can use your old psf files in Beta, and they will be converted to psfx (the type of settings file that Beta uses) so you don't have to worry about losing your old configurations. Database and binary files will be upgraded to include the new UID column, so make copies of those if you want to keep originals. Here is a list of the changes in the new versions: Bug Fixes 1. Bug 391. Click Detector not registering change in multi-threading option. (Core) 2. Bug 392. Click Detector throwing exception if multi-threading is turned off and the Basic Sweep Classifier is testing the amplitude range. (Core) 3. Bug 393. Rocca module not calculating energy, duty cycle, and windowRMS values when manually picking contour points. (Core) 4. Bug 403. Seismic Veto throwing ClassCastException when downstream of a Signal Amplifier and the multithreading options are changed. Fixed. (Core) 5. Bug 413. Binary file crashing during load, after a system failure. Failure could cause the file to become corrupt, which caused a crash during subsequent load (Beta) 6. Bug 414. Whistle Classifier module may not classify properly when analyzing multiple audio files. (Beta) 7. Bug 415. Click Detector could throw an Out Of Memory error when processing a large dataset. (Beta) 8. Bug 416. Bearing Localiser was not using the FFT information from it's Source, as it should have been. (Beta) 9. Bug 418. Rocca module was not classifying clicks properly when in Viewer mode. (Both) 10. Bug 419. Radar display not showing correct symbol in key. (Beta) 11. Bug 420. The Click Classifier set was not getting updated properly in Viewer mode. (Beta) 12. Bug 421. Alarm module resetting the simple count too quickly (Both) 13. Bug 422. Soundtrap import causing memory problems with large datasets. (Beta) 14. Bug 423. TD display FX scrolls extremely slowed when super detections were present. (Beta) 15. Bug 424. Pamguard would occasionally freeze when processing offline files. (Both) 16. Bug 425. Rocca crashing if Click Detector is used as source but the Click Classifier is not configured properly. (Both) 17. Bug 426. Clip Generator could cause memory issues when a large number of files were being analyzed. (Beta) Upgrades 1. Upgrades to the Group Localiser, including better error estimation. (Beta) 2. Click Train Detector upgrades, including ability to import time chunks from csv file for batch processing. (Beta) 3. Better display of microseconds in dialogs. (Both) 4. Added adaptive noise filter to Ishmael Detectors. (Beta) 5. Many upgrades to the Sound Playback module, including a high-pass filter, gain control, and the ability to mix wavefrom and envelope data together to listen to high-frequency clicks and dolphin whistles at the same time. (Beta) 6. New Analog Array Sensors module, to read data from 3-axis accelerometers. (Beta) 7. Send Email option added to Alarm module. (Beta) 8. Added ability to scale the PAMGuard display (go to Help > Set Display Scaling Factor to adjust the scale). This, in conjunction with the built-in Windows Display Scaling feature, will hopefully help with issues sometimes found when using 4k/UHD/high-DPI displays. At the moment this does not fix the JavaFX components, but we're working on that. (Both) |
|
From: Michael O. <m2o...@gm...> - 2019-01-30 13:15:02
|
Hi everyone. Another new Beta release, version 2.00.15. A few new features, and a few bug fixes. Simply go to our website, www.pamguard.org <https://l.facebook.com/l.php?u=http%3A%2F%2Fwww.pamguard.org%2F%3Ffbclid%3DIwAR1mNMTd-zB9j30hXc5uZsF7e7L9kDJOS_Ice6khWlqNAtTnohwpXVeaOyc&h=AT31rh9EyFTlbMzJIRgTuxEsUF214Y6xQjQUH1S7DWTsagEeKj31cUYXa_XHcv8Um8VwllsfuFSQ0soMn9F23Mc7j7ZndtD2NhAYSQkhYDkONdKBSd5rUlG1ewJbKqwfuIGIDTDaCSKUYVJ2deaxcEk-PzO8FjlVpA6ZdZnpDsOCIEEIhOhJeJTpLF4JVcm7wRX0AY6_CQiZiU8M6BABR6j9YMrp5M6kyTVqeQ_GfBxZQPi1buqc1N0L1DIQE1KqJBjtd4lxMzK-0wPxw9Zt334ctU-c0mz0AhQJtUDW0wrnajPfXeNj4EiqLE3HZw7iyK5DbQ2f1wUNVwE9lPXFsFFprR55aXbTJ364QBn-QzTHL26laqD-KAkXvidQp2VLzktBysCFeGXpDrpc14RsXV2wLYSmVitQc38BedF7sE-BmChKHEHy1onpHTWKSrZH-C52YO1x_19pUjyyffbjjTnqxGvBUZRKwUYQCJNGeFGnWO-tD51K0NJsz_mywTMVOV1TzEMbQWhl9NG356igety-axUTI18VvC7SkhjOICLKsYNzbbpzLqz-qcaB7kOlNOr00suJ24YQax0e2sfrIn9iIhCQPgMse4BkSunnSgQbiQe96HOFh7C30ElGVboi-CojbgqeQwUYa89DirdU-3zgxlMLbZ1hMxE>, click on the Download > Pamguard Software link, fill in the info to get the download page, and select 'Beta Release 2.00.15' from the Pamguard Version drop-down list. Here are the changes in this release: Bug Fixes 1. Bug 401. AIS graphics in Viewer crashing. 2. Bug 402. Fixed problem with data from old access database not importing correctly 3. Bug 403. Seismic Veto throwing ClassCastException when downstream of a Signal Amplifier and the multithreading options are changed. Fixed. 4. Bug 406. Pamguard resetting UID values in binary files. 5. Bug 408. Map Key icon not updated when colouring by channel. Fixed. 6. Bug 409. Fixed Click Detector not showing the correct input source in the dialog 7. Bug 410. Bug in Difar module, manually editing sonobuoy compass corrections. 8. Bug 411. Incorrect matching of GPS data sources for calibration in Difar module. 9. Bug 412. Fixed problem with ship always centering on map. Upgrades 1. Improvement to Range Rings in Map display. 2. Improvement in click train detector speed. 3. Added table of compass calibration to the Sonobuoy Manager, and option to use magnetic variation as initial calibration. 4. Matched template classifier extended to handle multiple templates. 5. New methods for handling and logging time offsets from the PC clock based either on GPS NMEA data or on pings of an NTP time server. 6. Improvements to Difar module graphics - easier reading, better visibility at night. 7. Added print screen button to capture/save all PAMGuard screens to file and log the information to the database. 8. Updates to the Ishmael module. 9. Added option to the WarnOnce dialog to hide a warning for the current PAMGuard session, but not forever. As always, if you have any problems or find other bugs, please let us know. Thanks! Michael |
|
From: Michael O. <m2o...@gm...> - 2018-10-31 12:12:42
|
Hi everyone. We have a new Beta release, version 2.00.14c, with a few important bug fixes. The Click Detector, FFT Engine and Filter modules were losing their source setting during startup if the source was something other than the first Sound Acquisition module. This could cause a lot of confusion if not noticed, so we highly encourage anyone using 2.00.14 to update to this version. Simply go to our website, www.pamguard.org <http://www.pamguard.org/?fbclid=IwAR0XpzMYYA1joTXku5OGE6uXy1GaUvlAcheexMNJlQuntYJoC6Xq63mL1SM>, click on the Download > Pamguard Software link, fill in the info to get the download page, and select 'Beta Release 2.00.14c' from the Pamguard Version drop-down list. There are a few other bug fixes and upgrades as well: Bug Fixes 1. Bug 338. Problem displaying coastlines and bathymetric contours around the dateline (+/- 180 longitude) in the map. 2. Bug 397. Clip Generator not able to find raw data when clips were taken from many channels. 3. Bugs 398 and 399. Click Detector, FFT Engine and Filter modules were losing source during startup, if the source selected was not the first raw data source in the list. 4. Bug 400. Spectrogram display running out of memory. Upgrades 1. Added decimal degrees option to latitude/longitude dialog. 2. Added option in the Click Delay parameters to restrict the number of initial samples used in the calculation. This can be useful for cleaning up delays in the presence of echoes and small time delays. 3. Increased upsampling to 2, 3 or 4 times. 4. Can now change units and scale type in level meter display. As always, if you have any problems or find other bugs, please let us know. Thanks! Michael |
|
From: Michael O. <m2o...@gm...> - 2018-09-06 12:47:27
|
Hi everyone. It took a little longer than expected, but here is the long-awaited update to Pamguard Beta. This is release 2.00.14, and is available for download on our website www.pamguard.org. <https://l.facebook.com/l.php?u=http%3A%2F%2Fwww.pamguard.org%2F&h=AT3jveP0xOKito4LnVFzVrXHCbq0KDzOMup_RdjNv3mYucAvF54GBqAZnDQ_JnilUbH9OIALJuqO5N7fxwtQ4zV488my-wD7XhaU6LgIoZ0FxSlXePcSBLquhhGAOs5BZ_iy0L_JjYAdUK7lCWSM9DX4EcQfQy-oYcfIdeIAePkEMGw96QCsXdOOEYI0gaUDXB5SdtCmgbMSrC-7DoA8HKb7YgYYvAn9VpL6mRT3f79NiyVl543Eodxvhd-uLvBuI-cem2PfVhNxSti7eVbg3gCv6XKhaWCVM8lfU9vSCEo2z6e-SwwqB7xlNVLK4etiYk8xIBK0_KcuvYyso9ZiiaqGc-u-Xmt958HonDdZiN_CKrrF_cnOlGrb97OsDFP_NP6lgLAxT9vu_hx1> We still list the Core version as the default, so when you get to the downloads page click on the Pamguard Version drop-down box on the right-hand side of the screen and select this Beta version. Lots of bug fixes and upgrades on this release (see below). One that I'd like to highlight is the change from psf settings files to psfx settings files. The settings files between the Core and Beta versions are fundamentally different, and once you open a psf file in Pamguard Beta it was upgraded and no longer accessible by Pamguard Core. Beginning with this release, Pamguard Beta now uses the psfx extension for it's settings files. If you start Pamguard Beta with a psf file it will automatically save it as a psfx file when you exit, and not modify the psf. That will still allow you to open the old psf file in the Core version, if you need to (but why would you need to? Are you still using Core? What's wrong? The Beta version is not scary, I promise) As always, feedback is greatly appreciated. Enjoy! Bug Fixes 1. Bug 381. Logger form loses controls when the order is changed. 2. Bug 382. Click species check boxes get cleared in toolbar when the Click Classification dialog is closed 3. Bug 383. Spectrogram max frequency resetting to incorrect value the first time the spectrogram dialog is opened. 4. Bug 385. Bug in offline toolbar which will crash if the classifier dialog is opened and then closed with no classifiers specified. 5. Bug 386. Click Detector Sweep Classifier sometimes keeping changed settings even when user tries to cancel or discard changes 6. Bug 387. Map was stopping displaying data based on the start time of data units. Have changed this to last updated time so that click events will display if they have been recently modified. Otherwise, long events get lost from the display. 7. Bug 388. Spectrogram annotations not working properly in beta branch. Would make and store mark, but not store snr or notes. Both now fixed for both online and offline operations. Have also added some options controlling SNR measurement period. 8. Bug 389. Multiple annotations of the same class would not be stored to the database if they had the same class. This was affecting the Spectrogram Annotation module which has now been given two text type annotations. 9. Bug 391. Click Detector not registering change in multi-threading option. 10. Bug 392. Click Detector throwing exception if multi-threading is turned off and the Basic Sweep Classifier is testing the amplitude range. 11. Bug 393. Rocca module not calculating energy, duty cycle, and windowRMS values when manually picking contour points. 12. Bug 394. Occasional divide-by-0 error in Spectrogram Display time scale. 13. Bug 395. Problem with hydrophone locator was resulting in an incorrect x position for hydrophone 0. Upgrades 1. Better way of coupling scrollers in User Display panels - see new options in main menu. 2. Added Matched Template Click Classifier. Classifies clicks based on an ideal template to match and a template to reject. An example of this is to classify beaked whale clicks in an environment with dolphin clicks. 3. Added zoom in/out to Raw Data plugin display in spectrogram. 4. Added ability to read differential GPS data. 5. Added check for duplicate settings in the psf file when exiting Pamguard. If duplicate settings are found, user is given the option to leave them in the psf or get rid of them. Duplicate settings are ignored by Pamguard, but can cause the psf file to grow large over time. 6. New features in PAMGuard Beta mean that psf files created with new versions are not compatible wth earlier versions and all configuration data may be lost if an attempt is made to open newly created psf files with older versions. We have therefore changed the file extension of psf files to .psfx in new Beta releases. Beta releases will still load the older psf files, but when the configuration is saved, the original psf file will remain untouched and data will be written to a psfx file with the same directory and name. Michael |
|
From: Michael O. <m2o...@gm...> - 2018-03-08 14:22:57
|
Hi Everyone. It's that time again - another update. We have just released new versions of both Pamguard Core (1.15.13d), and Pamguard Beta (2.00.12c). No new modules, but quite a few bug fixes. You can download them from our website, www.pamguard.org. <http://www.pamguard.org/> Note that the core release 1.15.13d shows up as the default download. If you are interested in the beta version, you can find it in the Pamguard Version drop-down box on the right - it's labelled Beta Release 2.00.12c. As always, feedback is greatly appreciated! Bug Fixes: 1. Bug 355. Pamguard crashed when database module was present and Rocca tried to load classifier 2. Bug 356. Ishmael Localiser losing raw audio before it had time to localise 3. Bug 357. Difar storing Tracked Group latitude in both GroupLatitude and GroupLongitude database columns 4. Bug 358. Clip Generator not storing overlapping detections properly 5. Bug 359. Pamguard crashes when selecting auto-scale option in Noise Monitor module 6. Bug 360. LTSA not loading in viewer mode 7. Bug 362. Bug in maximum likelihood bearing estimator grid search 8. Bug 363. Rocca throwing exception if user boxes a whistle close to the beginning of a file 9. Bug 364. LTSA bug - get correct fft length and hop into datablock and output stream 10. Bug 365. Lose spectrogram settings when converting data from Core to Beta versions 11. Bug 366. Rocca manual whistle contour extraction throws error when trying to classify a boxed whistle Upgrades 1. During conversion from Core to Beta versions, if there are any problems matching database units to binary store units the UID values will now be set to negative numbers instead of leaving them null. The user is warned about this and encouraged to manually fix the database. |
|
From: Michael O. <m2o...@gm...> - 2018-01-12 14:10:44
|
Hi Everyone. It's been a couple of months, but we have just released new versions of both Pamguard Core (1.15.13), and Pamguard Beta (2.00.12). No new modules, but quite a few bug fixes. You can download them from our website, www.pamguard.org. Note that the core release 1.15.13 shows up as the default download. If you are interested in the beta version, you can find it in the Pamguard Version drop-down box on the right - it's labelled Beta Release 2.00.12. As always, feedback is greatly appreciated! Bug Fixes Bug 341. Temporary objects created in the Rocca module were not being discarded, and could cause memory issues in large datasets. Bug 342. Rocca was not properly loading a previously-saved EncounterStats file. Bug 343. Fixed threading issue between Rocca and Click Detector. Bug 344. Database subtable items were being duplicated when running offline batch processing. (Beta version only) Bug 345. Offline Click Event reporting twice as many clicks as there actually were. (Beta version only) Bug 346. Click Classifier not properly checking frequency ranges for invalid entries. Bug 347. Pamguard crashes when loading a Sound Acquisition module when Java 7 is installed on computer. Caused by JFLAC library, which has been recompiled to correct issue. Bug 348. Map plot overlay menu not updating. Bug 349. Clip Generator overlay graphics sometimes crashing on map. Bug 352. Click Detector event marking was not correctly removing clicks from the events tables in the database. (Beta version only) Bug 353. Data load information dialog was not updating correctly, particularly when grouped data was relinked to super detections. (Beta version only) Bug 354. Whistle Classifier was crashing if user accidentally entered invalid parameters. Have added diagnostics to prevent this. Upgrades Can now add echoes to simulated sound acquisition. (Beta version only) |
|
From: Michael O. <mo...@st...> - 2017-06-06 11:19:26
|
Hi Everyone. We're very excited to announce the newest Pamguard beta release, version 2.00.10! You can download it from our website, www.pamguard.org. Note that since this is a beta release, it will not show up as the default download. Follow the download link at the top of the page, enter your details and hit Download. Then find the correct version in the Pamguard Version drop-down box on the right - it's labelled Beta Release 2.00.10. As always, feedback is greatly appreciated. Bug reports can be sent to su...@pa.... Thanks! ========================== Michael Oswald Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Twitter: @_SMRU_ The University of St Andrews is a charity registered in Scotland : No SC013532 Latest Beta Version 2.00.10 June 2017 PAMGuard Version 2 contains major updates. You should read and understand these notes before proceeding with installation and use of this version. These changes have been funded under contract to NOAA Fisheries, contract no. WE-133F-16-SE-1126. Binary File Structural Changes The Binary File structure has changed to accommodate additional information for each unit of data stored. This means that any data generated with PAMGuard Version 2.00.00 and above will not be compatible with older versions of PAMGuard. If you open older data sets with the PAMGuard Viewer the older data will be converted to the new format (see below for details). The most significant change in the binary file format is the addition of a Unique Data Identifier (UID) to each unit of data. This is intended to aid in offline analysis by making it easier for the user to link what they are seeing on different PAMGuard displays and also to link with any data post processed in Matlab or other custom analysis software. UID’s are also added to PAMGuard database tables. Converting Old Data If old data are opened with the PAMGuard viewer they will automatically be converted. For safety, the original binary files will not be overwritten and the new data will be placed in a new folder on your computer with the same path as the old data, but suffixed with ‘_WithUID’, e.g. if your binary data were previously stored in the folder C:\MySurvey\binarydata the new data will be written to C:\MySurvey\binarydata_WithUID. The additional UID column will be added to all database tables and populated with unique values. For data which are stored in both the binary files and in database tables, the same UID’s will be used in both data stores. New Displays A new time based scrolling display has been added to PAMGuard which can display multiple types of data on the same time axis. It can for instance be used to display bearings to whistles on a bearing-time type display similar to that commonly used in the click detector. Composite display graphs containing data from more than one detector are also possible. For details, see the PAMGuard help file (Displays / Time Display FX). Note that this display is only available if you are running Java 8 or later. Event Marking and the Detection Group Localiser A new system of event marking which can be used both online and offline has been added to PAMGuard. Details are in the PAMGuard help file (Displays/Display Marking). Data can be selected on the Map, the Spectrogram Display and the new Time Display FX in a similar way and sent to other PAMGuard modules. The new marking and data selection system works with the new Detection Group Localiser. The Detection Group Localiser extends the functionality which always existed in the click detector to other types of data (e.g. Whistles) so that they can be grouped and tracked using target motion analysis in a similar way. Details of the Detection Group Localiser are in the PAMGuard help files (Localisation/Detection Group Localiser). Display Colours A new system for handling display colours has been implemented across all PAMGuard displays. This gives greater flexibility to the user to control how data units are shown. For instance, you might simply want to show clicks in blue and whistles in green. However, for clicks and whistles that have been assigned to a Detection Group, you may want to colour them by the colour assigned to the group. Using Old PAMGuard Configurations Old PAMGuard configurations will work with the new version. However please note the following: 1. New classes will be added to the configuration files, so they will no longer work with older PAMGuard versions. 2. Display colour options will be lost and most data displayed on the map may default to black. This is due to the above changes to how colours are managed. Changing back to the colours of your choice is relatively simple through the PAMGuard GUI. |
|
From: Michael O. <mo...@st...> - 2017-05-10 13:32:15
|
Hi everyone. There is a new version of Pamguard now available on the pamguard.org website. Version 1.15.11 fixes a couple of important bugs: problems reading Soundtrap files and problems reading click events from a database when the events include target motion analysis data. Both issues are resolved with this release, along with some upgrades and bug fixes in the Difar and Rocca modules. A list of recent versions is shown below.. As always, any feedback would be appreciated. Bug reports can be sent to su...@pa.... Thanks! Michael ========================== Michael Oswald Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Twitter: @_SMRU_ The University of St Andrews is a charity registered in Scotland : No SC013532 Latest Version 1.15.11 May 2017 *Bug Fixes* 1. Bug 317. Rocca Module Data Purging. The ROCCA module was not performing data purging when using classifiers developed for Hawaii/Temperate Pacific/North Atlantic datasets. This has been corrected. 2. Bug 320. Pamguard stopped reading Click Detector Event data from database when target motion analysis information was encountered. Corrected. 3. Bug 321. Problem reading Soundtrap 4 files. Fixed. *Upgrades* 1. Added Copy-to-Clipboard button to Warning dialogs, to store error messages and stack trace information on the Windows clipboard. This information can then be easily pasted into emails, text documents, etc when contacting Pamguard support. 2. Enhancements and bug fixes made to Difar module during 2017 ACE voyage. 3. Rocca Module: added StartHr, ProportionWhists and ProportionClicks parameters to Event classifier 4. The installer now allows the user to enter command line switches/parameters to be included in *.ini files. Version 1.15.10 March 2017 *Bug Fixes* 1. Bug 308. Map Overlay Control. Storage of data saying what get's plotted on each map and for how long became corrupted and the list grew to a ridiculous size. Code has been put in place to a) stop it happening again and b) to repair any configuration files which are corrupted. Corrupted files will be slow to load, slow to save and will be > several megabytes in size. It may be necessary to delete the PamguardSettings table in any databases since these too may have become oversized which will slow down viewer mode PAMGuard start-up. 2. Bug 309. Rocca would crash when the user would press the classify button after the contour was recalculated. This has been corrected. 3. Bug 310. When exiting Viewer mode, PAMGuard queries the user whether they are sure they want to exit without saving even though they selected *Save and Exit*. Corrected, and added an *Exit without Save* option. 4. Bug 311. When double-clicking on a psf file to start PAMGuard, the working directory is set as the location of the psf and not as the installation folder. The library subfolder (\lib or \lib64) uses a relative path from the working folder, and therefore is set incorrectly. This has been fixed. 5. Bug 314. If PAMGuard is started by double-clicking on a psf, nothing happens when the user selects save as new configuration. This has been fixed. 6. Bug 315. code searched for file in working folder, which is the installation folder when starting PAMGuard using a shortcut link. But when double-clicking on a psf, the working folder is the location of the psf. This has been fixed. 7. Bug 316. Another error reading metadata for Dtag and SoundTrap files has occurred due to a format change in dTag metadata. This has been fixed. Version 1.15.09 January 2017 *BugFixes* 1. Bug 306. Certain methods have been querying AcousticDataUnit.getDuration and expecting to receive a response in milliseconds. However, getDuration actually returns the number of samples. This has been corrected. *Plug-Ins* A major change in this version of PAMGuard is how plug-ins are managed. PAMGuard now has the ability to dynamically load plug-in modules (saved as jar files) at runtime. This will greatly simplify the process of testing and distributing newly developed modules, since only a small jar file will be required rather than a new bespoke PAMGuard installation. Module code development remains largely unchanged, in most cases simply requiring the addition of an interface class. Instructions for the development of new modules utilizing the plug-in scheme can be found here <http://www.pamguard.org/16_HowtomakePlug-Ins.html>. Plug-in modules can be downloaded from the PAMGuard website here, but developers are encouraged to host and maintain their own modules. Modules of interest to the general PAM community will remain as part of the core PAMGuard installation. However, specialized modules which are useful to only a small number of users have been removed and are available as a separate download. The following modules have been removed: 1. Resource Monitor 2. WILD ArcGIS Interface 3. Workshop Demo Detector 4. Echo Detector and IPI Demo (bundled together, due to dependencies) *Other Changes* The installer has been updated to handle both 64 bit and 32 bit installations. PAMGuard psf files are now registered in the Windows Registry, so double-clicking on a psf file should run PAMGuard in normal mode (as opposed to Viewer or Mixed modes). Note that the Windows Registry can only hold a single executable reference for psf files; therefore, for users with multiple installations of PAMGuard, double-clicking on a psf will run the most-recently installed version of PAMGuard on the system. Version 1.15.08 November 2016 This release contains one bug fix. *Bug Fixes* 1. Bug 307. Unpacker for Sound trap dwv files was not working correctly. This is now fixed. Version 1.15.07 November 2016 This release contains two bug fixes. *Bug Fixes* 1. Bug 303. Some ASIO sound cards not working with either ASIO system in PAMGuard. For the PAMGuard ASIO system, this was due to a data format used by some sound cards never being properly implemented. For the “New ASIO system” which is based on jAsioHost, the unpacking of that format contained a bug which returned incorrect numbers, so data were swamped with noise. Both systems are now fixed. By preference, users should use the PAMGuard ASIO system since the JAsioHost based system seems to drop samples when many channels are running at high sample rate. 2. Bug 305. Date and Time not being correctly extracted from wav files created using SoundTrap recorders. Fixed by correctly finding and unpacking information in the accompanying xml log files that come with SoundTrap files. |
|
From: Michael O. <mo...@st...> - 2017-03-23 13:33:10
|
Dear all, We are releasing a new version of PAMGuard. Just a few bug fixes, with details below. As always, if you find bugs, please report them. Bug reports should be sent to su...@pa.... Yours, Michael ========================== Michael Oswald Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Twitter: @_SMRU_ The University of St Andrews is a charity registered in Scotland : No SC013532 Latest Version 1.15.10 March 2017 *Bug Fixes* 1. Bug 308. Map Overlay Control. Storage of data saying what get's plotted on each map and for how long became corrupted and the list grew to a ridiculous size. Code has been put in place to a) stop it happening again and b) to repair any configuration files which are corrupted. Corrupted files will be slow to load, slow to save and will be > several megabytes in size. It may be necessary to delete the PamguardSettings table in any databases since these too may have become oversized which will slow down viewer mode PAMGuard start-up. 2. Bug 309. Rocca would crash when the user would press the classify button after the contour was recalculated. This has been corrected. 3. Bug 310. When exiting Viewer mode, PAMGuard queries the user whether they are sure they want to exit without saving even though they selected *Save and Exit*. Corrected, and added an *Exit without Save* option. 4. Bug 311. When double-clicking on a psf file to start PAMGuard, the working directory is set as the location of the psf and not as the installation folder. The library subfolder (\lib or \lib64) uses a relative path from the working folder, and therefore is set incorrectly. This has been fixed. 5. Bug 314. If PAMGuard is started by double-clicking on a psf, nothing happens when the user selects save as new configuration. This has been fixed. 6. Bug 315. code searched for file in working folder, which is the installation folder when starting PAMGuard using a shortcut link. But when double-clicking on a psf, the working folder is the location of the psf. This has been fixed. 7. Bug 316. Another error reading metadata for Dtag and SoundTrap files has occurred due to a format change in dTag metadata. This has been fixed. Version 1.15.09 January 2017 *BugFixes* 1. Bug 306. Certain methods have been querying AcousticDataUnit.getDuration and expecting to receive a response in milliseconds. However, getDuration actually returns the number of samples. This has been corrected. *Plug-Ins* A major change in this version of PAMGuard is how plug-ins are managed. PAMGuard now has the ability to dynamically load plug-in modules (saved as jar files) at runtime. This will greatly simplify the process of testing and distributing newly developed modules, since only a small jar file will be required rather than a new bespoke PAMGuard installation. Module code development remains largely unchanged, in most cases simply requiring the addition of an interface class. Instructions for the development of new modules utilizing the plug-in scheme can be found here <http://www.pamguard.org/16_HowtomakePlug-Ins.html>. Plug-in modules can be downloaded from the PAMGuard website here, but developers are encouraged to host and maintain their own modules. Modules of interest to the general PAM community will remain as part of the core PAMGuard installation. However, specialized modules which are useful to only a small number of users have been removed and are available as a separate download. The following modules have been removed: 1. Resource Monitor 2. WILD ArcGIS Interface 3. Workshop Demo Detector 4. Echo Detector and IPI Demo (bundled together, due to dependencies) *Other Changes* The installer has been updated to handle both 64 bit and 32 bit installations. PAMGuard psf files are now registered in the Windows Registry, so double-clicking on a psf file should run PAMGuard in normal mode (as opposed to Viewer or Mixed modes). Note that the Windows Registry can only hold a single executable reference for psf files; therefore, for users with multiple installations of PAMGuard, double-clicking on a psf will run the most-recently installed version of PAMGuard on the system. Version 1.15.08 November 2016 This release contains one bug fix. *Bug Fixes* 1. Bug 307. Unpacker for Sound trap dwv files was not working correctly. This is now fixed. Version 1.15.07 November 2016 This release contains two bug fixes. *Bug Fixes* 1. Bug 303. Some ASIO sound cards not working with either ASIO system in PAMGuard. For the PAMGuard ASIO system, this was due to a data format used by some sound cards never being properly implemented. For the “New ASIO system” which is based on jAsioHost, the unpacking of that format contained a bug which returned incorrect numbers, so data were swamped with noise. Both systems are now fixed. By preference, users should use the PAMGuard ASIO system since the JAsioHost based system seems to drop samples when many channels are running at high sample rate. 2. Bug 305. Date and Time not being correctly extracted from wav files created using SoundTrap recorders. Fixed by correctly finding and unpacking information in the accompanying xml log files that come with SoundTrap files. Version 1.15.06 November 2016 This release contains bug fixes from release 1.15.05, mostly concerning the new target motion analysis methods. Bugs were found in several places in the system, affecting calculations using all three methods: Least Squares, 2D Simplex and 3D Simplex. To the best of our knowledge, all issues are now resolved. *Bug Fixes* 1. Bug 291. Click Detector Click Classifier: If this is set to "none" the click detector will freeze / crash and will put the psf file into a state where it will never load again. Incredibly, this bug seems to have been in place for several years and no one has come across it until now. It's fixed. 2. Bug 292. Incorrect labels on Target Motion panel in viewer - 3D algorithm was labelled as 2D.Fixed 3. Bug 293. Errors displayed in the click detector target motion panel were wrong in the graphics for the Simplex localisers and wrong in the tabulated data for the least square model. Both fixed. 4. Bug 294. Click classifier was crashing when the �min amplitude� option was used. This is fixed. 5. Bug 295. If a click has a total length of a single sample, the code attempting to estimate the time delay between channels would crash. This is now fixed. This could only occur if both pre sample and post sample were set to 0 in the click detector, which is generally not a good idea, so this bug may have been there for some time, it's just that no one noticed before. Fixed 6. Bug 296. Context menu popping up in click detector when marking clicks in Viewer mode. This has been fixed so that in viewer mode, the menu will only appear when you right click on the display. 7. Bug 297. Airgun display was not correctly showing itself at fixed locations, but always following the vessel track. This is now fixed. 8. Bug 299. Threading Hydrophone locator. Bug found in hydrophone heading calculation has been fixed. 9. Bug 300. GUI Tab panel selections were not being restored correctly when PAMGuard displays were split across multiple frames. Fixed. 10. Bug 301. Multiple errors in the target motion module have been fixed. 11. Bug 302. Target motion calculations taking too long when many clicks are included in a track. Mostly a problem when using automatic click train id. Fixed by setting an optional maximum number of clicks to use in a track. |
|
From: Douglas G. <dg...@st...> - 2016-11-30 10:56:22
|
Dear PAMGuard developers, We're in the process of rationalising some of the class inheritance in PAMGuard, particularly within the chain of subclasses PamDataUnit AcousticDataUnit PamDetection GroupDetection There are two drivers for this. * Firstly, we're rationalising the structure of the binary files so that there is a much more standardised way of storing common data for each data unit (e.g. channel maps, sample numbers, time delays, etc) * Secondly, we're finding that there is some functionality in PamDetction and GroupDetection which we need to use with non-acoustic data. Having thought about this hard, we've decided to do the following: 1. Move all data and functionality currently in AcouticDataUnit and PamDetection down into PamDataUnit 2. Remove AcousticDataUnit and PamDetection from PAMGuard, so that anything that did subclass either of them will now subclass PamDataUnit. 3. A lot of the actual data members of PamDataUnit are moving to PamDataUnitBaseData which is included in each PamDataUnit (this is needed for reading and writing binary files more efficiently). 4. Break out the functionality of things like amplitude calculations and data list management from PamDataUnit and PamDataBlock into separate classes with logically coherent sets of functions and have these classes of functions as separate members of PamDataBlock. This will a) neaten up the code and b) make it easier for developers pick and mix what they want to do (by overriding specific sections of that functionality). We're currently working on this in a separate branch so nothing will happen to the main code for a couple of months at least. Well then handle the merge back into the main SMRU development branch, making changes to anyone's data structures as required. We'll send out another email prior to doing this. If you're working in a separate development branch, then you'll need to merge back from SMRU into that branch to get these changes. I hope everyone is happy with this change. Please get in touch if you think this affects your work in any way. To the user it shouldn't even be noticed. Yours, Doug Gillespie and Mike Oswald. ========================== Douglas Gillespie Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Twitter: @_SMRU_ The University of St Andrews is a charity registered in Scotland : No SC013532 |
|
From: Douglas G. <dg...@st...> - 2016-09-16 09:30:46
|
Hi All, I've just developed a new warning message system for PAMGuard in PamView.dialog.warn.WarnOnce.java. Basically, it allows you to display OK and OK/Cancel type message dialogs which are similar to those from JOptionsPane, but with an additional "Don't show this warning message again" checkbox. I've used it in a couple of places and encourage others to do so. The list of warning not to be shown can be cleared from a new "Reset Hidden Warning" item in the file menu. Douglas. ========================== Douglas Gillespie Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, KY16 8LB Scotland. Tel: +44 (0)1334 462663 Twitter: @_SMRU_ The University of St Andrews is a charity registered in Scotland : No SC013532 |
|
From: Douglas G. <dg...@st...> - 2016-09-08 08:42:56
|
Dear PAMGuard users and developers. Anyone got feedback on this document regarding new data identification systems ? If so, please send be the weekend so that I can take on board any feedback and start working on this next week. Thanks, Douglas. From: Douglas Gillespie Sent: 29 August 2016 12:41 To: 'pam...@li...' <pam...@li...>; 'pam...@li...' <pam...@li...> Subject: Feedback Wanted: PAMGuard modification to data identification system. Dear All, As part of a program of work funded by NOAA fisheries, we are looking at ways of improving how data are uniquely identified within PAMGuard. An improved system of Unique Identifiers (UID's) will be of particular use to those who use PAMGuard for more complex analysis tasks involving additional software written in Matlab or R. An initial discussion document has been placed on the PAMGuard website at http://www.pamguard.org/downloads.php?cat_id=2. We welcome feedback from any user or developer of PAMGuard as to the various options laid out in the document, or indeed any totally new ideas which we may have overlooked. This will lead to a program of work being carried out later this year. This consultation period will remain open for two weeks, ending on 9 September, 2016. Feedback should be sent directly to me, Douglas Gillespie dg...@st...<mailto:dg...@st...>. I'll circulate a summary of all feedback and if there are strong differences of opinion either contract people individually or organize a group call in order to finalise a decision on how we should move forward. Yours, Douglas Gillespie ========================== Douglas Gillespie Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, St Andrews, KY16 8LB Scotland. The University of St Andrews is a charity registered in Scotland : No SC013532 |
|
From: Douglas G. <dg...@st...> - 2016-08-29 11:46:02
|
Dear All, As part of a program of work funded by NOAA fisheries, we are looking at ways of improving how data are uniquely identified within PAMGuard. An improved system of Unique Identifiers (UID's) will be of particular use to those who use PAMGuard for more complex analysis tasks involving additional software written in Matlab or R. An initial discussion document has been placed on the PAMGuard website at http://www.pamguard.org/downloads.php?cat_id=2. We welcome feedback from any user or developer of PAMGuard as to the various options laid out in the document, or indeed any totally new ideas which we may have overlooked. This will lead to a program of work being carried out later this year. This consultation period will remain open for two weeks, ending on 9 September, 2016. Feedback should be sent directly to me, Douglas Gillespie dg...@st...<mailto:dg...@st...>. I'll circulate a summary of all feedback and if there are strong differences of opinion either contract people individually or organize a group call in order to finalise a decision on how we should move forward. Yours, Douglas Gillespie Ps. Apologies if you got this twice ========================== Douglas Gillespie Sea Mammal Research Unit, Scottish Oceans Institute, University of St Andrews, St Andrews, KY16 8LB Scotland. Tel: +44 1334 462663 Fax: +44 1334 463443 The University of St Andrews is a charity registered in Scotland : No SC013532 |
8 messages has been excluded from this view by a project administrator.
