Re: No-fly in Subsurface?
On 07/27/2016 01:44 PM, Lutz Vieweg wrote: > One additional reason for "yet more safety margin" could be > that "loss of cabin pressure" is, albeight seldom, an event > that can actually happen on a flight. > Question is: Is loss of cabin pressure likely enough to > justify calculating with a much lower ambient pressure > (for the period of time the plane requires to descend to > 2400m) for decompression? > > Regards, > > Lutz Vieweg Interesting article for scuba diving pilots at https://www.faa.gov/pilots/safety/pilotsafetybrochures/media/dcs.pdf This event http://www.ncbi.nlm.nih.gov/pubmed/20377149 The fact that it is rapid is further concern http://www.avmed.in/2011/10/cabin-pressurisation-%E2%80%93-hazards-of-rapid-decompression/ Note: Most of this is about the pilot who also dives. I know that an hour at 10,000 feet (3,000m) will give me a deep headache and slowed response time -- even when I haven't been diving recently. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [PATCH 3/2] gas model: add polynomials for Z factors of oxygen/nitrogen/helium
On 03/02/2016 07:58 PM, Linus Torvalds wrote: > On Mar 2, 2016 7:34 PM, "Steve"wrote: >> >> SMB: Would be interesting to see if a polynomial of 21% of the oxygen >> factors and 79% of nitrogen factors comes close (enough) to the air >> specific one. > > See some of my "Google is great at graphing" emails. Yup. That was the next email after the one I posted. Note to self. Really should read all outstanding emails first. Really. > > Short version: yes, the linear mixing seems to give extremely good > results at least for air (which is the only one we have independent > tables for). There are bigger differences just between the air tables > on Wikipedia and baue. > > In fact, if you plot the baue air polynomial and the "air mix" > polynomial at the same time, you get an almost *perfect* match to 300 > bar. That would agree with chemistry theory about gas partial pressures. > > After that it diverges a bit, but that seems to be because the oxygen > polynomial really ends up being bad at 300+ bar. > > You can trivially test yourself: just paste this into google: > > y = > 0.9994355774568318-0.00035668306234655186*x+0.0218474273138185*x^2+5.8403793405e-9*x^3-2.780101081e-11*x^4+3.144563e-14*x^5, > y = > 0.21*(1.0002231211532653-0.0007471497056767194*x+0.0200444854807816*x^2+2.91501995188e-9*x^3-4.48294663e-12*x^4-6.11529e-15*x^5)+ > > 0.79*(1.0001898816185364-0.00030793319362077315*x+0.0327557417347714*x^2-1.93872574476e-9*x^3-2.7732353e-12*x^4-2.8921e-16*x^5) > from 0 to 500 > > where that first "y=" is the polynomial from the "air" table at baue, > the second "y=" is the "air mix" from the polynomials for oxygen and > nitrogen. > > They are literally on top of each other. > > In fact, it's *such* a perfect match up to 275 bar that I wonder if > the baue numbers aren't based on a linear mix. <> That would be a more "perfect" explanation. Each fall my professor would say "What we taught you last year is just an approximation. This year we'll explain how it really works." I suspect they same thing to the master and doctoral candidates. > > In other words, it's possible that one or more of the the baue tables > aren't entirely experimental. Mayeb the baue pure gas tables are > experimental, and the air table is from a linear mix of those? > > Regardless, the linear mix looks really good. When you compare it to > the Wikipedia numbers, it's still pretty close. So everything lines up > pretty well. > >Linus > ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [PATCH 3/2] gas model: add polynomials for Z factors of oxygen/nitrogen/helium
On 03/02/2016 07:34 PM, Steve wrote: > > > > > Sent from my Verizon Wireless 4G LTE smartphone > Original message > From: Linus Torvalds> Date: 3/2/2016 16:39 (GMT-08:00) > To: Dirk Hohndel > Cc: Subsurface Mailing List > Subject: [PATCH 3/2] gas model: add polynomials for Z factors of > oxygen/nitrogen/helium > > > From: Linus Torvalds > Date: Wed, 2 Mar 2016 16:30:24 -0800 > Subject: [PATCH 3/2] gas model: add polynomials for Z factors of > oxygen/nitrogen/helium > > .. and use a linear mix of them for arbitrary gas mixes. > > For the special case of air, we continue to use the air-specific > polynomial. > > > SMB: Would be interesting to see if a polynomial of 21% of the oxygen > factors and 79% of nitrogen factors comes close (enough) to the air > specific one. > You already did. I'm just not catching up fast enough! ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Eon Steel on Ubuntu 15.04
On 08/23/2015 08:52 PM, Linus Torvalds wrote: On Sun, Aug 23, 2015 at 6:29 PM, Steve Butler kg...@comcast.net wrote: Anybody on the list using Subsurface on Ubuntu 15.04 and downloading from an Eon Steel? If so, how did you get around the permission denied message? Better yet, what /dev/ are you using to do the download? I'm not on Ubuntu, but the udev rules shouldn't be that different. So I have something like this: [torvalds@i7$ cat /lib/udev/rules.d/91-suunto-eonsteel.rules SUBSYSTEM==usb,ATTR{idVendor}==1493,ATTR{idProduct}==0030, MODE=0666 SUBSYSTEM==usb,ATTR{idVendor}==1493,ATTR{idProduct}==0031, MODE=0666 which should make the device accessible (the 0031 device is what happens when you do a firmware update, you don't need it). And you don't need to give any device node for the EON Steel, since we just end up using libusb and picking it by device ID. Thank you. Running late tonight but I did copy/paste from the other email the following: echo 'SUBSYSTEM==usb,ATTR{idVendor}==1493,ATTR{idProduct}==0030, MODE=0666' | sudo tee /etc/udev/rules.d/99-cobalt.rules Too late to fiddle with the DC and USB cable (they are current back in their box) tonight. I should have more time tomorrow evening to take the next step. Again, thanks for the info. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Re. subsurface: FTBFS in experimental
On 08/25/2015 05:10 PM, Christoph Anton Mitterer wrote: Hey. How saddening to see such a nice program for divers being basically destroyed by a stupid and arrogant upstream (and while some may consider this impolite, I guess it's simply the truth). Humph. The daily PPA works fine for me on Ubuntu. These guys have been a wonderful help to me. A lot better than that DM5 I'm forced to use on a Windows box to update the firmware on the DC. You sound a little like my grandkids last month when picking my grapes. I told them they should wait a month and the grapes wouldn't be so sour. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Eon Steel on Ubuntu 15.04
Anybody on the list using Subsurface on Ubuntu 15.04 and downloading from an Eon Steel? If so, how did you get around the permission denied message? Better yet, what /dev/ are you using to do the download? Part of dmesg output: [ 13.505232] wlan0: associated [ 167.332583] usb 1-1: new full-speed USB device number 5 using xhci_hcd [ 167.462795] usb 1-1: New USB device found, idVendor=1493, idProduct=0030 [ 167.462804] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 167.462808] usb 1-1: Product: GURU [ 167.462812] usb 1-1: Manufacturer: Suunto [ 167.462815] usb 1-1: SerialNumber: [ 167.479650] hid-generic 0003:1493:0030.0003: hiddev0,hidraw2: USB HID v1.01 Device [Suunto GURU] on usb-:00:14.0-1/input0 steve@SteveLaptop:/dev$ ls -l *usb* total 0 crw--- 1 root root 180, 0 Aug 23 18:09 hiddev0 crw--- 1 root root 180, 1 Aug 23 18:12 hiddev1 steve@SteveLaptop:/dev$ lsusb Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 1bcf:28ac Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 06cb:0af8 Synaptics, Inc. Bus 001 Device 005: ID 1493:0030 Suunto Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub steve@SteveLaptop:/dev$ l hid* hidraw0 hidraw1 hidraw2 steve@SteveLaptop:/dev$ l hiddev* ls: cannot access hiddev*: No such file or directory -- Stephen M Butler, PMP, PSM kg...@comcast.net kg...@arrl.net ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ubuntu 15.04 compile Subsurface from source
On 07/02/2015 09:42 PM, Miika Turkia wrote: check out INSTALL file under the sources and install the Ubuntu dependencies listed there miika Thanks Miika for reminding me that I needed to go back to the basics after the O/S upgrade. I ran the apt-get as listed there and everything except libcurl was up-to-date. It did install the new package libcurl4-openssl-dev. Compiled fine but attempting to run the local version give: install-root/bin/subsurface: error while loading shared libraries: libGrantlee_Templates.so.5: cannot open shared object file: No such file or directory Went back and redid the apt-get (see below). Should there be an entry for libGrantlee in that list? sudo apt-get install git g++ make autoconf libtool cmake pkg-config \ libxml2-dev libxslt1-dev libzip-dev libsqlite3-dev \ libusb-1.0-0-dev libgit2-dev \ qt5-default qt5-qmake qtchooser qttools5-dev-tools libqt5svg5-dev \ libqt5webkit5-dev libqt5qml5 libqt5quick5 libqt5declarative5 \ qtscript5-dev libssh2-1-dev libcurl4-openssl-dev qttools5-dev [sudo] password for steve: Reading package lists... Done Building dependency tree Reading state information... Done autoconf is already the newest version. cmake is already the newest version. g++ is already the newest version. git is already the newest version. libqt5qml5 is already the newest version. libqt5quick5 is already the newest version. libqt5svg5-dev is already the newest version. libqt5webkit5-dev is already the newest version. libsqlite3-dev is already the newest version. libtool is already the newest version. libusb-1.0-0-dev is already the newest version. libxml2-dev is already the newest version. libxslt1-dev is already the newest version. make is already the newest version. pkg-config is already the newest version. qtchooser is already the newest version. qtscript5-dev is already the newest version. qttools5-dev is already the newest version. qttools5-dev-tools is already the newest version. libgit2-dev is already the newest version. libqt5declarative5 is already the newest version. libssh2-1-dev is already the newest version. libzip-dev is already the newest version. libcurl4-openssl-dev is already the newest version. qt5-default is already the newest version. qt5-qmake is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ubuntu 15.04 compile Subsurface from source
On 07/03/2015 12:37 PM, Linus Torvalds wrote: On Fri, Jul 3, 2015 at 12:29 PM, Steve Butler kg...@comcast.net wrote: Compiled fine but attempting to run the local version give: install-root/bin/subsurface: error while loading shared libraries: libGrantlee_Templates.so.5: cannot open shared object file: No such file or directory Yeah, subsurface uses a shared library for its private grantlee link, Ah. Private. That explains why having Software Center locate and install one just got me deeper in trouble. Let me see if I can back out from here. which is kind of annoying, but some libraries really want to be shared, whether it makes sense or not. And since the library is in a non-standard place, the system doesn't find it. You can work around it by doing something like sudo ldconfig full-path-to/install-root/lib Will try that once I back out the two items I just installed. to run stuff in place (or by just installing it all, but you'll still need to then run ldconfig to let the system know about the new library). Linus -- Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Ubuntu 15.04 compile Subsurface from source
On 07/03/2015 12:49 PM, Steve Butler wrote: On 07/03/2015 12:37 PM, Linus Torvalds wrote: You can work around it by doing something like sudo ldconfig full-path-to/install-root/lib Will try that once I back out the two items I just installed. Success. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Pressure line missing on dive profile
On 07/02/2015 06:18 AM, Dirk Hohndel wrote: On Thu, Jul 02, 2015 at 05:49:54AM -0700, Dirk Hohndel wrote: On Thu, Jul 02, 2015 at 01:35:04PM +0200, Jef Driesen wrote: And I don't believe Subsurface has been updated to take that into consideration... we use DC_FIELD_TANK to get the size of the tank, but we don't appear to get any beginning/end pressure from it. This shouldn't be too hard to fix. Any volunteers? Actually, I looked at this and it's trivial. Silly that this slipped through. Steve, I think you're on Ubuntu, compiling from source, right? I'll push my fix into master, would you mind rebuilding the latest master and giving it a try? Easiest way to do this would be to create a new logbook and Ubuntu 15.04 (took the plunge from 14.10 a week ago). I haven't been compiling since the move to cmake. Haven't kept my copy of source up to date either. So I just wiped it all out and following the instructions on the build page. Just pulled down a new clone. Did not set the checkout (I presume this leaves it pointing at the latest entry). The build script is running now. Pseudo life that pays for this real diving life keeps getting in the way. Not to mention this ear infection that has kept me out of the water for the last two weeks (last dive on the 15th). Then on Monday, Wanita and I are taking the Norwegian Sun to Alaska (week long cruise up the inland passage) with some friends from Phoenix -- he also dives. So, no diving for the next two weeks either! download from the dive computer. Once this is confirmed we could try the force download and prefer data from dive computer switches which I am sure no one has used in years... but they were implemented exactly for this case where we fix something in a parser and you can get more / better information from the dive computer but don't want to lose everything else that you've already entered... But first I'd like for you to test my fix with a new divelog as that removes possible other things that could be going wrong when merging the data into the existing log. While I was typing the script got to this point -- suspect I need to go lookup again how to checkout the tip top of master. Now, where did I put the git manual? May need to leave this until I get home tonight. Pseudo work needs to happen today!! Cloning into 'grantlee'... fatal: unable to access 'https://gitorious.org/grantlee/grantlee.git/': Could not resolve host: gitorious.org ./subsurface/scripts/build.sh: line 165: cd: grantlee: No such file or directory fatal: Not a git repository (or any parent up to mount point /home/steve) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). can't check out v5.0.0 of grantlee -- giving up ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Ubuntu 15.04 compile Subsurface from source
I suspect this morning's attempt was foiled by work's rogue external WiFi dropping in the middle of downloading one of the modules. The attempt here at home went further/faster. Apparently libcurl isn't part of 15.04. -- checking for module 'libcurl' -- package 'libcurl' not found CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:345 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:399 (_pkg_check_modules_internal) cmake/Modules/pkgconfig_helper.cmake:2 (pkg_check_modules) CMakeLists.txt:74 (pkg_config_library) Will have to chase this one down tomorrow. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Pressure line missing on dive profile
On 07/02/2015 08:24 AM, Steve Butler wrote: While I was typing the script got to this point -- suspect I need to go lookup again how to checkout the tip top of master. Now, where did I put the git manual? May need to leave this until I get home tonight. Pseudo work needs to happen today!! Cloning into 'grantlee'... fatal: unable to access 'https://gitorious.org/grantlee/grantlee.git/': Could not resolve host: gitorious.org ./subsurface/scripts/build.sh: line 165: cd: grantlee: No such file or directory fatal: Not a git repository (or any parent up to mount point /home/steve) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). can't check out v5.0.0 of grantlee -- giving up Dirk, Can you push out to the daily? I just saw 4.4.2-995 and updated to it this morning. Not able to compile on my box. Will need to be home tonight to grab the DC to download again. (Someone said we could use the dump file to simulate the DC. How is that done? I do have the dump file I attached to an earlier email. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Pressure line missing on dive profile
On 07/02/2015 11:34 AM, Dirk Hohndel wrote: On Thu, Jul 02, 2015 at 10:47:58AM -0700, Steve Butler wrote: On 07/02/2015 08:24 AM, Steve Butler wrote: While I was typing the script got to this point -- suspect I need to go lookup again how to checkout the tip top of master. Now, where did I put the git manual? May need to leave this until I get home tonight. Pseudo work needs to happen today!! Cloning into 'grantlee'... fatal: unable to access 'https://gitorious.org/grantlee/grantlee.git/': Could not resolve host: gitorious.org ./subsurface/scripts/build.sh: line 165: cd: grantlee: No such file or directory fatal: Not a git repository (or any parent up to mount point /home/steve) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). can't check out v5.0.0 of grantlee -- giving up Dirk, Can you push out to the daily? I just saw 4.4.2-995 and updated to it this morning. Not able to compile on my box. I did. 955 (not 995) is on Launchpad and contains the fix. Your eyes are better than mine. Confirmed 955 was downloaded Will need to be home tonight to grab the DC to download again. (Someone said we could use the dump file to simulate the DC. How is that done? I do have the dump file I attached to an earlier email. It's somewhat non-trivial. And I seem to remember that Jef has only posted binaries to do so, not sources, so I'm not sure you can do this on Ubuntu. There are Linux binaries so it's worth a try. Details at http://www.libdivecomputer.org/simulator.html Waiting for big honking SQL to finish against the Oracle database so took a look. OK. I'm not that good at Linux. :-) All set to try from home tonight. Thanks Dirk. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Pressure line missing on dive profile
On 07/01/2015 06:51 AM, Dirk Hohndel wrote: On Tue, Jun 30, 2015 at 09:49:28PM -0700, Steve Butler wrote: On 06/30/2015 09:41 PM, Steve Butler wrote: Subsurface: 4.4.2-292 DC: Suunto Cobra Dive 69: Downloaded March 8 (or soon thereafter) has pressure line and the P: entries on the Information block. Dive 70: Dive for June 15 downloaded June 30 (today). Does not have either. I don't remember changing any preferences and can't locate one to make the switch. What else do I need to include to help locate what happened? It is always possible that it is PEBKAC. --Steve This may help. Perhaps the pressure didn't get downloaded from the DC for #70. dive number=69 date=2015-03-08 time=12:13:00 duration=23:10 mincylinder size=14.383 l workpressure=237.318 bar description=HP119 o2=31.0% start=222.0 bar end=126.0 bar/divecomputer model=Suunto Cobra deviceid=04e6459b diveid=f8d87d3ddepth max=14.021 m mean=8.94 m/temperature air=9.0 C water=8.0 C/ dive number=70 date=2015-06-15 time=18:30:00 duration=27:30 minnotesLast Rescue dive./notescylinder size=14.383 l workpressure=237.318 bar description=HP119 o2=30.0%/weightsystem weight=13.608 kg description=integrated/weightsystem weight=4.536 kg description=pockets/weightsystem weight=0.907 kg description=ankle/divecomputer model=Suunto Cobra deviceid=04e6459b diveid=b1b300e2depth max=24.994 m mean=14.289 m/temperature water=11.0 C/ I'm not familiar with the Cobra. But from looking at pictures it should be hose based and air integrated? Then the pressure in the cylinder entry comes from the pressure delivered in the samples. So the question is... if you look at the samples, are there pressure values in the older dives and not in the newer dives? /D Hose/air-integrated. I closed my logbook and created a new one by downloading all dives from the DC. None of them had pressure information. Based on what I saw from Suuto's DM, and how it appears to be stored in the DC menus, I suspect the pressure start/end are stored in some sort of header. I don't see profile based pressure points (may be there but not that I can detect). Dumped the log file but find I don't know how to read the data lines being recorded. Then did both the log and dump file. The 2nd log was bigger than the first and appears to be reading 4 more bytes per sample record. Also looks like 2 extra bytes are written for each read. Attached: -- subsurface.log (log file from 1st log run) -- subsurface2.log (log file from 2nd log run with dump file also being generated) -- subsurface2.bin (dump file from 2nd log run). How do you read the dump file? INFO: Open: name=/dev/ttyUSB0 INFO: Configure: baudrate=2400, databits=8, parity=2, stopbits=1, flowcontrol=0 INFO: Timeout: value=1000 INFO: DTR: value=1 INFO: Sleep: value=100 INFO: Flush: queue=3, input=0, output=0 INFO: Sleep: value=500 INFO: RTS: value=1 INFO: Write: size=5, data=0500161407 INFO: Sleep: value=200 INFO: Flush: queue=1, input=0, output=0 INFO: RTS: value=0 INFO: Read: size=25, data=050016140001A11C3F12094200600C210E5A0C35FD Event: model=12 (0x000c), firmware=33 (0x0021), serial=14901253 (0x00e36005) INFO: Sleep: value=500 INFO: RTS: value=1 INFO: Write: size=3, data=08A5AD INFO: Sleep: value=200 INFO: Flush: queue=1, input=0, output=0 INFO: RTS: value=0 INFO: Read: size=2, data=0820 INFO: Read: size=33, data=022C0D0D807D7DFF7D01FB7D090A130F060F0D1E86 INFO: Read: size=2, data=0807 INFO: Read: size=8, data=1E2D000A02000B3F INFO: Read: size=0, data= INFO: Sleep: value=500 INFO: RTS: value=1 INFO: Write: size=3, data=09A5AC INFO: Sleep: value=200 INFO: Flush: queue=1, input=0, output=0 INFO: RTS: value=0 INFO: Read: size=2, data=0920 INFO: Read: size=33, data=022E0C0B807DFCFFFD00FFFF000100FF0001FE INFO: Read: size=2, data=0920 INFO: Read: size=33, data=00FDFEFFFEFEFDFDFEFEFF00FF0001FCFFFE29 INFO: Read: size=2, data=0920 INFO: Read: size=33, data=FFFEFE000100FDFF00FFFEFF2B INFO: Read: size=2, data=0920 INFO: Read: size=33, data=00FD0001FF0001FF01FF01020202FF010001FF000200010101002A INFO: Read: size=2, data=0920 INFO: Read: size=33, data=00020301FF0200010302020102030302050303020401050100020100D2 INFO: Read: size=2, data=0919 INFO: Read: size=26, data=0105040101007D00051E120F060F11001E74000A0112 INFO: Read: size=0, data= INFO: Sleep: value=500 INFO: RTS: value=1 INFO: Write: size=3, data=09A5AC INFO: Sleep: value=200 INFO: Flush: queue=1, input=0, output=0 INFO: RTS: value=0 INFO: Read: size=2, data=0920 INFO: Read: size=33, data=023F0808807DFF7D0001F77D7A00FF010100010401FA7DF97AFB7AFF01001A INFO: Read: size=2, data=0920 INFO: Read: size=33, data=03040503F9FC7AFEFF000201FF00FBFDFEFFFD0202FF00FE51 INFO: Read: size=2, data=0920 INFO: Read: size=33, data=7C0101FF01FEFF00FF00FF01FF0100FF01FE00FFAA INFO: Read: size
Re: [PATCH] Planner - change timestep to 2 seconds
On 06/21/2015 04:40 PM, Rick Walsh wrote: Steve, On 22 June 2015 at 08:48, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: On 06/21/2015 03:23 PM, Rick Walsh wrote: On 22 Jun 2015 8:16 am, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: On 06/20/2015 06:25 PM, Rick Walsh wrote:On 21 Jun 2015 11:19 am, Dirk Hohndel d...@hohndel.org mailto:d...@hohndel.org wrote: On Sat, Jun 20, 2015 at 11:17:28AM +1000, Rick Walsh wrote: But what about me? I like SI units and whole decimals. Don't worry, 2 s timesteps fit nicely when using 10 m/s ascent rate (18 s between stops). snip Also my DC records every 10s. One of the DCs i'm looking at does 5s intervals. How would this work comparing the pre-dive plan with the post-dive profile? The change has nothing to do with setting or limiting an ascent rate. Currently the ascent to the next stop is done in 3 second increments. If you ascend at 30ft/min (Subsurface default, which matches most DCs) it should take 20s to ascend 10ft. But in 3s increments it is bumped out to 21s. No huge issue but it makes the calculated plan have some odd runtimes. So that would be 10 calculations (one every 2s) between stops. If you slid the other way and went every 4s then its 5 calculations up to the next stop. Any concerns with snappiness (performance) on slower machines? I have an 8 year old laptop, and calculations appear immediate, so I don't think it's too intensive. Changing from 3s to 2s means we do 10 calculations rather than 7, which isn't that dramatic. Changing to 4s is ok for a 30ft (9m) /min ascent rate, but for 20ft (6m) /min ascent (also common), a stop should take 30s but that becomes 32s. 5s is ok for 20ft/min or 30ft/min but isn't good for 5 m/min or 10 m/min. You are right, it isn't all that efficient. I tried setting it to the time it takes to ascend to the next stop (do the ascent in one jump), which I thought should work. And to quote a great of modern philosophy, 60 percent of the time it worked every time. Occasionally, it would just break a ceiling. R To paraphrase another great thinker -- Efficiency is over-rated. Or, To err is human. To really mess things up you need a computer. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Cloud storage and web view
On 06/20/2015 04:40 PM, Dirk Hohndel wrote: On Jun 20, 2015, at 4:00 PM, Salvador Cuñat salvador.cu...@gmail.com mailto:salvador.cu...@gmail.com wrote: 2015-06-20 23:13 GMT+02:00 Dirk Hohndel d...@hohndel.org mailto:d...@hohndel.org: BTW I can only test tomorrow, as on monday I'll be in a family trip to Mauritius (expecting to have a little diving, off course). On the good side, I hope to get back with a bunch of new dive locations and gps fixes to test. I think we can all agree (except for Lubomir and, sadly, Robert) that collecting more data is the best part of our hobby :-) Have a great trip to Mauritius. I was hoping to gather a couple dives worth this morning at Sund Rock (Hood Canal). But an outer ear infection showed up yesterday morning and put a stop to any such thoughts. Mauritius looks like an interesting destination. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [PATCH] Planner - change timestep to 2 seconds
On 06/21/2015 03:23 PM, Rick Walsh wrote: On 22 Jun 2015 8:16 am, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: On 06/20/2015 06:25 PM, Rick Walsh wrote:On 21 Jun 2015 11:19 am, Dirk Hohndel d...@hohndel.org mailto:d...@hohndel.org wrote: On Sat, Jun 20, 2015 at 11:17:28AM +1000, Rick Walsh wrote: But what about me? I like SI units and whole decimals. Don't worry, 2 s timesteps fit nicely when using 10 m/s ascent rate (18 s between stops). snip Also my DC records every 10s. One of the DCs i'm looking at does 5s intervals. How would this work comparing the pre-dive plan with the post-dive profile? The change has nothing to do with setting or limiting an ascent rate. Currently the ascent to the next stop is done in 3 second increments. If you ascend at 30ft/min (Subsurface default, which matches most DCs) it should take 20s to ascend 10ft. But in 3s increments it is bumped out to 21s. No huge issue but it makes the calculated plan have some odd runtimes. So that would be 10 calculations (one every 2s) between stops. If you slid the other way and went every 4s then its 5 calculations up to the next stop. Any concerns with snappiness (performance) on slower machines? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Recreational mode, Add 3min stop
On 04/02/2015 01:54 AM, Robert Helling wrote: Hi, On 02.04.2015, at 10:01, Joakim Bygdell j.bygd...@gmail.com mailto:j.bygd...@gmail.com wrote: This builds ontop of Roberts patch and adds a 3min stop @5m, these fixes #839 #840. these two again build on top of Joakim’s patch: The first adds a checkbox for the safety stop while the second disables the safety stop for dives of less than 10m max depth (which is what for example Suunto computers do). I don’t have a strong opinion on weather we should do the safety stop also in the trail ascent. If we did, the NDL would be longer but on the other hand this would make the safety stop mandatory. What do you people think? I'd like the option to pick either at run time. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: segfault adding images + problems with locations
On 03/16/2015 10:15 AM, Dirk Hohndel wrote: On Mon, Mar 16, 2015 at 05:11:13PM +, Pedro Neves wrote: Hi all: Using Subsurface version 4.4.1-225-g0d77b921eb11 I have a segfault when adding images to my dive. I select a dive, then load images: - I get an error message on the load image dialog saying that not all images have timestamps between 30 minutes before the start and 30 minutes after the end of any selected dive, although they have. Yes, there's definitely something wrong with the logic there. I'm waiting to hear back from Jan on this one. - If I shift the image times (e.g. 1 hour later and then back to 0:00) the error message disapears. - when I press ok, Subsurface crashes with a segfault That sucks. Any chance you can run this under a debugger and get us a back trace? Also, after I download a dive from my dive computer (Uwatec Tec 2G), I'm trying to insert the information for the dive site. I write the name of the site and press manage. On the divesite dialog, all fields are empty. I insert the information (name and coordinates) When I press Apply changes. I get back to the notes tab. The location field has the name of my dive site (in yellow). I press Apply changes changes, but the divesite doesn't show up on the map, and if I select another dive, the location I've just inserted disapears. This hasn't been implemented, yet. Sorry. The current development version is not all that useful for actual work - which is why I haven't made another daily build... AHA. And I spent last night trying to figure out what was wrong with my PPA setup! :-) Good to know that the answer is: Nothing! /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Off Topic -- slightly. Dive Computers
On 03/07/2015 03:36 AM, Anton Lundin wrote: On 06 March, 2015 - Steve Butler wrote: Any updates to Linus' Dive Computer ramblings regarding the Cobalt2 and/or Eon Steel? Other color, air-integrated DCs folks would recommend? Wanita and I have been using Cobras for the last three years. But we can't see the backlight at depth (or in our living rooms) and shining a dive light on it produces a lot of glare unless the angle is just right. We've both had cataract surgery and I've had a detached retina repaired (yes, the surgeon specifically agreed I could dive). Then there is something about four and three score orbits of Sol. Definitely want color and lighted. Our experience at 120' last Sunday while narced convinced me we'll never dive deep with the Cobra as the primary DC again. I'm even debating if I want to allow it as the secondary (note, I don't have a secondary now). --Steve PS We'll finish our deep specialty after the new DC is tested out. I'd thought i dump out some thoughts about DC's to. I started out diving with a Suunto Vyper as my one and only DC, and it worked pretty well. I like the big clear numbers on the display, and it got a awesome battery time. But i don't like that you need to push a button to get the backlight on and trying to do deco diving on it is just plain stupid. Its actually pretty resonable up to 10 mins of deco, and past that it just shoots away. We did some wreck penetration training and doing gas sharing exits passing restrictions we got a bit delayed, and the Vyper showed 65 min of deco. Subsurface calculates the TTS based on the same dive to 15 min. (One of the reasons i wrote that TTS/NDL code was actually to compare it with the numbers from my Vyper) I've only seen extensive use of Suunto Vyper/Vytec-series computers and i haven't seen any of them fail for any other reason than the owner botching a battery change and thus drowning the device. I still carry that Vyper in my dry suite pocket as a backup computer in Gauge mode. Its battery life is great for that. I'll probably leave the Cobra attached when adding in the new DC. At least until I purchase a 2nd new DC. (one hose; one non-hose). As my main computer i use a OSTC3 nowadays. I've saw a bunch of them fail to begin with but now with the replaced and fixed versions all the ones in my diving team works like a charm. I did look at it and wondered if the optical port could be hacked to feed tank pressure. Would require a mod to the firmware. Maybe a two-wire SPI interface from a pressure transducer down the arm with an optical conversion to feed into the optical port. Yup. Want (need) air-integration. It got great readability and i love how compact it is. I also like the mecanical push-buttons better than the piezoelectric ones in the OSTC2 and predator/petrel. It doesn't do air-integration. It would be fun to have the pressure-sensor data in subsurface for analysis but i don't care for it during my dive. I don't mind unclipping my spg from my left hip and looking at it to verify my mental model of what pressure I'm at. I like it all in one spot. Anybody have information about Liquid Vision? My instructor said it was just a BT. I've done quite a bit of diving with the OSTC2N, and too is a great computer, but i like the OSTC3 better. The layouts on the OSTC3 is better and the menus are easier to comprehend. I also got a OSTC Sport laying next to me here. Its almost the same hardware as the OSTC3, but with a constrained firmware. I haven't had time to test it in the water yet. One big upside with HW computers is the HW team them self. They are just awesome and have great support for their gear. One other manufacturer to mention is Shearwater. In my dive team its a 30/70 split between Shearwater computers and HW computers. The Predator was a great computer and the Petrel is a even better one. Its bulkier than the OSTC3, and it has piezoelectric buttons. One upside is that you can get them with fisher-connectors to run as your rebreather monitoring device, which is way more hassle with the OSTC3. I've seen some weird failure modes on Petrel's. One stopped accepting any input at all, but looked fine in surface mode, and another lost half of its menus. The support from Shearwater was just great, having there English distributor over night ship a replacement device to Malta so my mate could continue to dive was just great. It was kinda a show-stopper when his Petrel died becase he was using that as his way of monitoring his mCCR. That kinda sums it up for me. I do technical diving, and don't care about air integration so here's my 2 ören: Rec diver just now breaking the 100' level. Did a deco dive in college for NAUI certification (with the old yellow horseshoe collar and CO2 bottles to inflate it). Then didn't dive for a few decades. If i where in for a cheap option i would probably by a second-hand OSTC2. There's a lot of them out there on the market and you
Off Topic -- slightly. Dive Computers
Any updates to Linus' Dive Computer ramblings regarding the Cobalt2 and/or Eon Steel? Other color, air-integrated DCs folks would recommend? Wanita and I have been using Cobras for the last three years. But we can't see the backlight at depth (or in our living rooms) and shining a dive light on it produces a lot of glare unless the angle is just right. We've both had cataract surgery and I've had a detached retina repaired (yes, the surgeon specifically agreed I could dive). Then there is something about four and three score orbits of Sol. Definitely want color and lighted. Our experience at 120' last Sunday while narced convinced me we'll never dive deep with the Cobra as the primary DC again. I'm even debating if I want to allow it as the secondary (note, I don't have a secondary now). --Steve PS We'll finish our deep specialty after the new DC is tested out. -- Stephen M Butler, PMP, PSM kg...@comcast.net kg...@arrl.net ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Off Topic -- slightly. Dive Computers
On 03/06/2015 09:02 AM, Linus Torvalds wrote: On Mar 6, 2015 8:51 AM, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: Any updates to Linus' Dive Computer ramblings regarding the Cobalt2 and/or Eon Steel? Other color, air-integrated DCs folks would recommend? I updated my ramblings by adding the A300CS (do *not* buy) and the EON Steel (I like it, but wish it was thinner and lighter). See http://subsurface-divelog.org/misc/dive-computer-ramblings/linus-dive-computer-ramblings/ I read it in detail last night on the train home. I've heard that in the water the EON doesn't feel that heavy. Wanita may not want something that big on her arm (she's around 5' tall) but it would fit me fine (I'm 6'3 and a lot overweight). For the current version. Dirk has his own ramblings too I don't have anything new on the Cobalt, since I still haven't actually used it on a dive. But I haven't heard anything bad about it, and if you like the hose based approach and don't mind that it's a bit bulky, it's definitely one of the top choices. It's easy to use and very readable. Your thoughts on carrying a 2nd on each dive? I've been tempted to sell the Cobra and buy both the EON and COBAL2 (not in same year). Linus Thank you for the feedback. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Off Topic -- slightly. Dive Computers
On 03/06/2015 09:06 AM, Davide DB wrote: Hi Steve, IMHO IMHO right now, one of the best gadget out there is the Shearwater petrel. One of the best display (size and colors), amazing overall features plus a rock solid customer service. Right now I have a Xdeep Black bottom timer (you can buy nitrox or trimix DC version but the hardware it's the same). I'm satisfied with it but I would not suggest :) Few months ago I wrote a small review/open letter of its pro and cons that I copy here. I have this BT and it's really one of the nicest gadget I ever had but after nearly three months of diving with it I can give here a small recap on its cons. and maybe some suggestion to them. Now, the latest update has solved everything was previously reported. Maybe their temp compensation algorithm still needs some refinement. the CPU used is so powerful that is capable to heat the device giving false values. They implemented a sw temperature correction that works. Actually I still get slightly different values from my Sensus Ultra. Buttons: they get pressed accidentally, continuosly. You have to put the device exactly in the middle of your arm otherwise when you bend your arm for whatever reason the get pushed and you find your display on another screen. Nothing dramatic but really annoying. Now I'm diving with a pscr and on the same arm I have the O2 monitor so it's really a PITA. I should try the latest sw feature added: you can disable the button underwater. I did not try but I need to be in control for stopwatch and average depth. KeyPressing combinations: I think the the Liquivision Xen way is far more efficient. To reset the timer/avg. depth you have: - short press of left button to bring the menu - one or two short press of right button to choose the reset timer option - one long press fo right button to confirm. It's really too long. Layout/fonts: disclaimer - My eye sight is 11/10 but I'm in the forties so size matters. Layout and fonts are really nice but some info are really too small. It's all about size now! If I don't have to change out the 1.65 for 2.50 in the bottom of the mask, that would be preferable! You can set a custom color for everything on screen through some very counterintuitive menu. There's no way to move things around (custom layout) or changing dimensions. You have to stick with three layouts: full - simple - minimum. Unfortunately for (us) tech divers we would like having full because it's the only one with timer and average depth. In this layout I find that these info are displayed really too small. IMHO their error was to rely only on the wonderful screen resolution. Unfortunately even if your display resolution permits to draw 1 mm letters it doesn't mean they are eye readable. Moreover in this layout they WASTE a lot of space for their state-of-the art VSI indicator (ascent/descent speed indicator) that it's completely useless for tech dives. Same apply for the runtime. By default the large central timer start with the runtime. As you reset the timer, the runtime is displayed on the upper right corner with the same font as average depth. Too little to me. On the reatime log screen you have average depth and temperature. Both are (maybe) smaller that the main screen. Guys you hate me!!! Regarding the difficult task to insert color hex values via two buttons... Why don't you rely on a CSV file as for compass bearing? You already have the feature to read one CSV user file from the flash memory. You could do the same for setting color. You simply give the user one table with a numeric code for each object on screen so I can assign the RGB hex value in a file like this: 01;ff 02;ffa500 03;... PS Maybe a greater attention to their customer too. Same question as I asked Linus -- thoughts on carrying a backup DC on all dives. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Plan Dive -- thoughts
On 03/02/2015 12:22 PM, Joakim Bygdell wrote: On 02 Mar 2015, at 5:51, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: On 02/27/2015 10:54 PM, Joakim Bygdell wrote: On 27 Feb 2015, at 21:23, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: Now, as an OC rec diver (soon to have access to the 100-130 depths) I would not want to enter the ascent segments separate from spending time at a level on the way up in order to indicate to ascend at best rate. Take this scenario: Drop to 130 and hang there for 6 minutes (28% O2). Rise at 30'/m to 70 and hang there for 8 minutes on the ledge. Ascend at 30'/m to 40 (no wait as it is a transition to an upslope. Spend 5 minutes swimming the upslope to 15. Spend the standard 3 minute stop at 15. As this is a multilevel dive you have to do some calculation on your own, i.e transition times between the levels. That is what I was hoping to avoid. Especially as we entice more newly certified OW and AOW divers to use Subsurface. Use of the printed dive planner and the eRDP both assume the transition time is included in the level time. That is because they assume that each level is represented by a square profile. If we take your example dive in reverse creating a dive your students might be called upon to do. Assuming you start from shore with a 7 min slow descent to 70’, spend 7 min @ 70’ followed by 5 min swim upslope to 15'. How do you plan such a dive on the tools you mentioned? Do you ignore the time not spent @ 70’ or do you calculate the average depth for those 12 min and use a square profile as a representation? If you use subsurface in your classes, teach the students to use it properly the way it was designed, do not try to imitate how the eRDP works because subsurface can do a lot more. In which case the check to drop to first depth (which combines the first two lines) is really not that useful at best and possibly misleading when looking at what was entered. It led to my losing the 130 depth on a dive with a 70' ledge on the way up. Entered (with check box off) 130 7 70 2 70 10 Noticed the profile and saw that I'd failed to check the drop box. So clicked that first box and got: 70 9 70 10 Now, if I enter the original list with that box already checked and then uncheck it I get: 130 2 130 4 70 2 70 10 Which is what I should have entered in the first place (though I would have done 130 5 on the 2nd line). Which makes me think that if we're going to enforce entering all way points, then the drop to first depth box really isn't that useful and in my case, while I an learning the interface, caused me to lose my initial depth line. Final DepthDurationRuntime 13022descend 13068level 70210ascend 70616level 15521swim upslope 15324stop When you do that the ascent rates that you can set tin the lower left cornet of the planner will not be used. The descent rate will be used only if you check “Drop to first depth”. And in this case it will replace the first two lines with this. 13088 Containing both the descent time and the time spent at 130’. This is what the OW rec diver expects to enter. See above. Oh, and option to pick between 15 or 20'. I noticed only 20' was set as the last stop. That is because the planner used 10’ increments in its internal calculations. And the planner will only calculate what reamins on the ascent after your last waypoint. OK. How about another check box to include 3 min safety stop at 15 feet at the end of the dive. At least that is what is being taught in PADI. That might not be to hard to implement. Compare how the planner works on your example vs. a blue water ascent profile. The only thing entered into the planner is this line with “Drop to first depth” checked. Final DepthDurationRuntime 1301313 In this case the planner will tell you that the calculated ascent from 130ft, using the defined ascent rates, will take 7minutes. Multilevel dives you have to define all waypoints for all the levels, until the start of the ascent that contains your safety stop. In the first example if the upslope didn’t exist your last waypoint would be @ 70’ and the planner would calculate the ascent time to the surface. Since you don’t have any deco obligation it will tell you that you can ascend to the surface using the defined ascent rates over a time of 4min. Would still want the option to add 15' 3 min safe stop without having to calculate the ascent times. /Jocke --Steve /Jocke ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Dive Location
4.4.1-175 (Ubuntu 14.10 via PPA daily) appears to have lost ability to add/update the Location. I tried entering 'Ditman Mill Pond, Tacoma, WA' directly into the field and then clicked on Apply Changes. However it didn't show up in the dive list panel. When I navigated away from the dive and came back it went missing from the location field. Then saw the Manage button and tried that route. Same end result. This was two new dives downloaded from Suuntu Cobra. Closed the file (saving the changes). Reopened and tried it again. Almost same results. This time when typing into the Location field it offered up the description entered on the prior dive (closed Subsurface in the meantime). However, still didn't stick in the location field. Nor did it show up in the dive list panel. -- Stephen M Butler, PMP, PSM kg...@comcast.net kg...@arrl.net ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Dive Location
4.4.1-189 has same problem. --Steve On 02/22/2015 07:08 PM, Steve Butler wrote: 4.4.1-175 (Ubuntu 14.10 via PPA daily) appears to have lost ability to add/update the Location. I tried entering 'Ditman Mill Pond, Tacoma, WA' directly into the field and then clicked on Apply Changes. However it didn't show up in the dive list panel. When I navigated away from the dive and came back it went missing from the location field. Then saw the Manage button and tried that route. Same end result. This was two new dives downloaded from Suuntu Cobra. Closed the file (saving the changes). Reopened and tried it again. Almost same results. This time when typing into the Location field it offered up the description entered on the prior dive (closed Subsurface in the meantime). However, still didn't stick in the location field. Nor did it show up in the dive list panel. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Installing dunce cap and facing corner
I re-cloned subsurface (per email for somebody else to build from source) with -b v4.4-branch. Compiled to version 4.4.0-56-g554b652d25d9 and then compared to latest daily build via distro which was 4.4.0-67. Did a 'get checkout master' and redid the build script. Same version as the v4.4-branch (4.4.0-56-g554b652d25d9). How is it that the latest source code has an earlier version? [Hence the dunce cap pre-installed and facing corner.] For what it is worth -- script works on Ubuntu 14.10. At least I got an executable out of it. -- Stephen M Butler, PMP, PSM kg...@comcast.net kg...@arrl.net ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Merging Dives (P.S. -- multiple email addresses)
My wife's DC recorded 4 separate dives (pool work for her Rescue Diver class) on Sunday Jan 29th. She wanted them all merged into a single dive. Her version of Subsurface will merge only 2 dives and then stops merging. v4.3.0.0 Once she merges the Dives 12 from the 29th it won't let her merge any more. Not even the 2 pool dives (make up work) from Thursday Feb 5th. I haven't stayed up with the current master but do have v4.4.0-67. Created a new log book and started downloading from her DC. Cancelled after a bit (didn't want all her dives) and selected just the 4 dives from Jan 29th and the 2 from Feb 5th. Attached as Wanita1.xml. I was able to merge the two dives from Feb 5th and then able to merge dives 34 from Jan 29th (working from most recent to oldest -- if I start with the oldest I can only merge the first two dives on Jan 29th and nothing more). After renumbering the dives, saving out as Wanita2.xml and opening it back up I was only able to merge dive 2 into the merger of original dives 3/4. Could not get dive 1 included. Attached as Wanita3.xml Note: Both of us tried to highlight all 4 dives and merge them in one pass but it only merged the first two and then stopped merging. Questions: 1. Should we be able to merge more than two dives in a single pass? 2. Why do we have to renumber/save/close/open to get the second merge to work when working from oldest to newest (but not when working newest to oldest)? [my version]. 3. Should we be doing something else? [I do need to go prune the grape vines.] --Steve PS Can my account have more than one email address? Try as I do, my Ubuntu box and my phone don't seem to agree on which mail box emails are sent from. I suspect the one from my phone hangs up until the moderator releases it. The phone email comes from kg...@comcast.net Thunderbird claims this email is from kg...@comcast.net with a reply-to of kg...@arrl.net I think I registered with kg...@arrl.net Now I'm confused -- but if I could have both addresses I'm sure the phone emails won't hang waiting for the moderator. -- Stephen M Butler, PMP, PSM kg...@comcast.net kg...@arrl.net divelog program='subsurface' version='2' settings /settings dives dive number='1' date='2015-01-29' time='22:09:00' duration='15:30 min' cylinder size='14.383 l' workpressure='237.318 bar' description='HP119' start='200.0 bar' end='170.0 bar' / divecomputer model='Suunto Cobra' deviceid='caef9227' diveid='9d4e4e00' depth max='3.048 m' mean='2.687 m' / temperature air='27.0 C' water='27.0 C' / event time='9:20 min' type='3' name='ascent' / sample time='0:00 min' depth='0.0 m' / sample time='0:10 min' depth='1.524 m' / sample time='0:20 min' depth='1.829 m' / sample time='0:30 min' depth='2.438 m' / sample time='0:40 min' depth='2.438 m' / sample time='0:50 min' depth='2.134 m' / sample time='1:00 min' depth='2.743 m' / sample time='1:10 min' depth='1.829 m' / sample time='1:20 min' depth='2.438 m' / sample time='1:30 min' depth='2.438 m' / sample time='1:40 min' depth='3.048 m' temp='27.0 C' / sample time='1:50 min' depth='3.048 m' / sample time='2:00 min' depth='3.048 m' / sample time='2:10 min' depth='3.048 m' / sample time='2:20 min' depth='3.048 m' / sample time='2:30 min' depth='3.048 m' / sample time='2:40 min' depth='3.048 m' / sample time='2:50 min' depth='2.743 m' / sample time='3:00 min' depth='2.743 m' / sample time='3:10 min' depth='3.048 m' / sample time='3:20 min' depth='3.048 m' / sample time='3:30 min' depth='2.743 m' / sample time='3:40 min' depth='2.438 m' / sample time='3:50 min' depth='2.743 m' / sample time='4:00 min' depth='2.743 m' / sample time='4:10 min' depth='2.743 m' / sample time='4:20 min' depth='2.743 m' / sample time='4:30 min' depth='2.743 m' / sample time='4:40 min' depth='2.743 m' / sample time='4:50 min' depth='2.743 m' / sample time='5:00 min' depth='2.743 m' / sample time='5:10 min' depth='2.743 m' / sample time='5:20 min' depth='2.743 m' / sample time='5:30 min' depth='2.743 m' / sample time='5:40 min' depth='2.743 m' / sample time='5:50 min' depth='2.743 m' / sample time='6:00 min' depth='2.743 m' / sample time='6:10 min' depth='2.743 m' / sample time='6:20 min' depth='2.743 m' / sample time='6:30 min' depth='2.743 m' / sample time='6:40 min' depth='2.743 m' / sample time='6:50 min' depth='2.743 m' / sample time='7:00 min' depth='2.743 m' / sample time='7:10 min' depth='2.743 m' / sample time='7:20 min' depth='2.743 m' / sample time='7:30 min' depth='2.743 m' / sample time='7:40 min' depth='2.743 m' / sample time='7:50 min' depth='2.743 m' / sample time='8:00 min' depth='2.743 m' / sample time='8:10 min' depth='2.743 m' / sample time='8:20 min' depth='2.743 m' / sample time='8:30 min' depth='2.743 m' / sample time='8:40 min' depth='2.743 m' / sample time='8:50 min' depth='2.743 m' / sample time='9:00 min'
Re: Merging Dives (P.S. -- multiple email addresses)
On 02/15/2015 05:41 PM, Dirk Hohndel wrote: On Sun, Feb 15, 2015 at 03:06:48PM -0800, Steve Butler wrote: My wife's DC recorded 4 separate dives (pool work for her Rescue Diver class) on Sunday Jan 29th. She wanted them all merged into a single dive. . But for every pair of dives it's supposed to merge it calls can_merge() and that only succeeds if there's less than 30 minutes between the dives... One of these days I'll read the manual. Last time I read a manual though, I ended up in a timed 4-hour test. That's an arbitrary threshold, of course. It seemed to make sense to us... if you have more than 30 minutes surface interval, it really doesn't seem to be the same dive anymore... snip You should ask yourself why you want to merge these dives to begin with... the idea behind merging was if you did a dive but for some reason had to come to the surface and the silly computer decides to start a new dive, whereas in reality you are just continuing the dive. 30 minutes on the surface seems not to fit that pattern. Since we were in the water all 5 hours (she on one AL-64), she wanted them all combined. Now we know and she'll live with what we did manage to merge. As for me, I'm going to delete the pool dives and keep only the paper copy the instructor signs! The two OW dives last Sunday ended up being all surface scenarios. Final three ocean dives next Sunday. Then we'll both be rescue diver certified. PS Can my account have more than one email address? Try as I do, my Ubuntu box and my phone don't seem to agree on which mail box emails are sent from. I suspect the one from my phone hangs up until the moderator releases it. The phone email comes from kg...@comcast.net Thunderbird claims this email is from kg...@comcast.net with a reply-to of kg...@arrl.net I think I registered with kg...@arrl.net Both of these emails are accepted for posting. And I don't see anything from you in the moderation queue. I think it happened last week and you may have fixed it be default then. Thanks. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Merging Dives (P.S. -- multiple email addresses)
On 02/15/2015 05:46 PM, Dirk Hohndel wrote: On Sun, Feb 15, 2015 at 05:41:13PM -0800, Dirk Hohndel wrote: I see... because of the rules for merging dives dive 1 and 2 can't be merged - more than 30 minutes between the end of the first and the beginning of the second. Then dives 2 and 3 get merged successfully. And then we seem to have a bug because the duration of that merged dive is now incorrect. It claims a duration of 850 seconds - a little over 14 minutes, which is the sum of the two durations, but not the sum duration from beginning to end of the dive - we don't account for the surface interval. And therefore a calculated end time is about ten minutes to early and with that the merge fails. Ah I see what bites us. We calculate duration from the samples. And at some point we decided that we don't want to include surface intervals in the duration (because that messes with the SAC rate calculation). But of course that also means that when+duration isn't the end time of the dive. So we need a dive duration and a total time field. I don't have the time to implement this right now, but at least I understand the bug now. /D No hurry from here. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: [PATCH] Need to warn about some more characters on CSV import
On 01/08/2015 07:38 AM, Robert Helling wrote: When the apostroph is used as a field separator and it appears inside the cell, it is just repeated. I have no idea how general are these rules (wikipedia says quotation repetition is in an RFC) but maybe we should support them. That is standard practice in *NIX world and in the Oracle database engine. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Input requested [was: [PATCH] Use proper gas names in the divelist.]
On 01/06/2015 08:40 PM, Dirk Hohndel wrote: On Tue, Jan 06, 2015 at 07:50:13PM -0800, Steve Butler wrote: On Tue, Jan 6, 2015 at 6:35 PM, Anton Lundin gla...@acc.umu.se wrote: The same goes when discussing Nitrox vs. Advanced Nitrox diving. Diving a 32% vs a dive with 32..100 are usually a bit different. Could the tec divers provide a little education for this rec diver? What is the difference between EAN32, 32% and 32..100? EAN32 is a common way to describe a Nitrox gas with 32% O₂. 32% is a short way of referring to that. And in our nomenclature 32..100 means that you used more than one Nitrox mixture, the lowest being 32%, the highest 100%. /D Thank you. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Input requested [was: [PATCH] Use proper gas names in the divelist.]
On Tue, Jan 6, 2015 at 6:35 PM, Anton Lundin gla...@acc.umu.se wrote: The same goes when discussing Nitrox vs. Advanced Nitrox diving. Diving a 32% vs a dive with 32..100 are usually a bit different. Could the tec divers provide a little education for this rec diver? What is the difference between EAN32, 32% and 32..100? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Input requested [was: [PATCH] Use proper gas names in the divelist.]
On 01/06/2015 08:21 AM, Miika Turkia wrote: Rec diver so current implementation is more than enough for me. Don't care about the extras... miika Under PADI, I'm limited to 100' so usually use EAN32 or air. I suspect in about 6 weeks I'll have the shop mix me some EAN28 and get me another 32'. But only one tank strapped to the back per dive. Miika, on the first read my brain picked up 'wreck' and I had to go back and re-read it!! --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Prev/Next DC
On 12/23/2014 03:35 AM, Tomaz Canabrava wrote: Deivide, On Tue, Dec 23, 2014 at 9:09 AM, Davide DB dbdav...@gmail.com mailto:dbdav...@gmail.com wrote: On Tue, Dec 23, 2014 at 12:03 PM, Miika Turkia miika.tur...@gmail.com mailto:miika.tur...@gmail.com wrote: On Tue, Dec 23, 2014 at 1:01 PM, Davide DB dbdav...@gmail.com mailto:dbdav...@gmail.com wrote: Is there any keyboard shortcut for: Prev DC - Switch to next dive computer. PREV = NEXT ??? Left arrow/cursor Next DC - Switch to previous dive computer. NEXT = PREV ??? Right arrow/cursor Hummm On Windows it doesn't seem to work. Moreover on the menu there's no hint. I'm trying to compare two computers but without shortcut is alittle PITA Wow. I was trying to think my way through this but now my head hurts. Must be out of my mind since everybody else seems to understand! Shouldn't it be: Left arrow = Prev DC = Switch to previous dive computer Right arrow = Next DC = Switch to next dive computer Or is my English all messed up again. English 101 in college was too long ago. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Prev/Next DC
On 12/23/2014 02:03 PM, Davide DB wrote: Uh oh! Simple typo Aha! Those I understand. It's clearing up now. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: daily builds for Ubuntu
On 12/02/2014 01:29 PM, Dirk Hohndel wrote: So this is an experiment... but maybe it's useful for some? I have created a current daily build for Trusty and Utopic (with lots, and lots, and LOTS of help from Miika). I'd appreciate if people could test this as it is quite different from the official builds - it statically links against the Subsurface-testing branch of libdivecomputer and a compatible version of libgit2 (btw - tip of master of libgit2 is already incompatible again with Subsurface... what is WRONG with these people?). If this is useful for people I'll experiment with including our own marble library in the package as well and more importantly with switching the whole thing to Qt5 (marble-dev on Ubuntu is linked against Qt4). One thing that's ironic about this is that I don't actually have a client system running Ubuntu, so I can't test what I'm uploading :-) To quote the launchpad page: You can update your system with unsupported packages from this untrusted PPA by adding ppa:subsurface/subsurface-daily to your system's Software Sources. https://launchpad.net/~subsurface/+archive/ubuntu/subsurface-daily /D Added the ppa. Software Center found the correct version of the daily build (4.2.90.76-1) but reported this: The following packages have unmet dependencies: subsurface: Depends: libmarblewidget18 (= 4:4.10.80) but it is not going to be installed Depends: libqt4-network (= 4:4.8.0) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: libqt4-svg (= 4:4.5.3) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: libqtcore4 (= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: libqtgui4 (= 4:4.8.0) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: zlib1g (= 1:1.1.4) but 1:1.2.8.dfsg-1ubuntu1 is to be installed It is the libmarblewidget18 that it is baulking on. --Steve (Ubuntu 14.10) ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: daily builds for Ubuntu
On 12/02/2014 03:57 PM, Dirk Hohndel wrote: On Tue, Dec 02, 2014 at 03:50:07PM -0800, Steve Butler wrote: Added the ppa. Software Center found the correct version of the daily build (4.2.90.76-1) but reported this: The following packages have unmet dependencies: subsurface: Depends: libmarblewidget18 (= 4:4.10.80) but it is not going to be installed If it depends on it, why isn't it being installed? I have a theory! Depends: libqt4-network (= 4:4.8.0) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed That seems fine... 4:4.8.6... should be = 4:4.8.0, right? Depends: libqt4-svg (= 4:4.5.3) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: libqtcore4 (= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: libqtgui4 (= 4:4.8.0) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: zlib1g (= 1:1.1.4) but 1:1.2.8.dfsg-1ubuntu1 is to be installed Same for the rest of those... It is the libmarblewidget18 that it is baulking on. Odd. I know almost nothing about how all this is supposed to work. Miika copied the binaries over for 14.10 - but I don't think he was able to test that, either. You are in a better position than I, but I'm digging. I checked software center and it claims I have 4:4.14.1-0ubuntu2 installed. So, looks like in my messing around with Marble I ended up with a more current version. That's my current theory! I'm in the process of including marble as well (and removing that dependency), but real work is interfering with progress :-/ I ended up staying in bed most of the day. Still have a vice across the temples. So far mainly in the head but I feel it drifting downward. But work intruded several times since my DBA is on vacation and Q4 work still needs to be finished before 1/1/2015. /D --Steve PS I don't recommend this method of skipping out of work. :-( ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Recompile Marble and Subsurface -- still undefined reference
On 11/26/2014 02:17 AM, Lubomir I. Ivanov wrote: hello, On 26 November 2014 at 06:08, Steve Butler kg...@comcast.net wrote: -- Found Qt4: /usr/bin/qmake-qt4 (found version 4.8.6) snip * Qt4 , cross-platform application framework , http://qt.digia.com/ core framework marble is basically saying it found Qt4.8.6 installed on your system and will be built using it. earlier you've mentioned that your 'qmake' version is 5.x, which could mean that you have both Qt5 and Qt4 installed on your system. that's not really a bad thing, it's just not that easy to handle. Another mystery for my learning curve. Thanks for pointing these out for me. snip if you go back to step one and use qmake from Qt4 (e.g. qmake-qt4) with the Ubuntu packages you may be just able to built subsurface with marble support. Yes! Stumbled on that last night while thinking what if. now, if you want to built both marble and subsurface with Qt5 you need Nope! Now that you confirmed my experimental results I'll simplify and use the standard Ubuntu 14.10 version of Marble. In fact, I think I managed to toss all Marble off my box last night and reinstall the package. to find a way to tell marble to use Qt5 and then use the standard 'qmake' command (given --version shows Using Qt version 5.x). hope that clarifies things a little. :-) lubomir -- The mud is much thinner now. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Happy T-Day
Thank all of you for your patience as I come up to speed. Enjoy tomorrow and be sure that the bird isn't the only one stuffed at the table! :-) --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: INSTALL file
On 11/24/2014 06:08 AM, Lubomir I. Ivanov wrote: On 24 November 2014 at 03:20, Steve Butler kg...@comcast.net wrote: On 11/22/2014 11:46 PM, Miika Turkia wrote: On Sun, Nov 23, 2014 at 8:51 AM, Steve Butler kg...@comcast.net wrote: On 11/17/2014 01:56 PM, Lubomir I. Ivanov wrote: On 17 November 2014 23:53, Lubomir I. Ivanov neolit...@gmail.com wrote: On 17 November 2014 23:49, Steve Butler kg...@comcast.net wrote: Looks like I need to find a non-Canonical source to update. Is there another PPA to which I can point for a later version? that should be it: https://marble.kde.org/sources.php but perhaps it would be best to remove all marble related packages first. not the exact answer to the question, i admit. perhaps there are alternative and compatible PPA, if not, you may have to built from the sources which is a bit of task. Built from source. Now need the qmake command to include Marble again. I thought a simple 'qmake' might do that. But it is still disabled at build time. I wonder if you are missing libmarble-dev. If everything is available, qmake should pick up Marble. Just to make sure, the Ubuntu packages I have uploaded to our PPA (subusrface-beta has the 4.2.90 beta release along with latest master of libdivecomputer) have the following dependencies: It is present but Lubomir thinks it was compiled with an older version of qt than I'm using. I was getting: .obj/moc_globe.o:(.data.rel.ro._ZTV8GlobeGPS[_ZTV8GlobeGPS]+0x60): undefined reference to `Marble::MarbleWidget::connectNotify(QMetaMethod const)' .obj/moc_globe.o:(.data.rel.ro._ZTV8GlobeGPS[_ZTV8GlobeGPS]+0x68): undefined reference to `Marble::MarbleWidget::disconnectNotify(QMetaMethod const)' Lubomir had me turn off Marble with: qmake DEFINES += NO_MARBLE make clean make I pulled down latest Marble (or thought I did) and compiled on my box. Need to go buy Qmake for Dummies so I can reverse the above and see if what I did fixed my problem. make sure you have marble installed sudo make install. https://marble.kde.org/sources.php but something to note here; this: ... -DCMAKE_BUILD_TYPE=Debug ... will build a 'debug' version of marble which means that you need to build subsurface with make debug, unless you have also have built a 'release' version of marble in which case you can also build subsurface using 'make release'. the idea behind 'make release' and 'make debug' is that on runtime subsurface will look for different shared libraries between the two. in the case of 'debug' those are inflated with special debug symbols that are useful for finding the exact problematic line of code. to redo the qmake configuration just run: qmake make clean make [debug] if you get errors post them here. lubomir -- Sorry for the delayed response. I'll use the Life comment I've seen from others. If you want the detailed litany just PM me grin. I'm back to square one: .obj/moc_globe.o:(.data.rel.ro._ZTV8GlobeGPS[_ZTV8GlobeGPS]+0x60): undefined reference to `Marble::MarbleWidget::connectNotify(QMetaMethod const)' .obj/moc_globe.o:(.data.rel.ro._ZTV8GlobeGPS[_ZTV8GlobeGPS]+0x68): undefined reference to `Marble::MarbleWidget::disconnectNotify(QMetaMethod const)' collect2: error: ld returned 1 exit status Makefile:523: recipe for target 'subsurface' failed make: *** [subsurface] Error 1 Maybe my compile and install of Marble didn't do what I thought it did. I'm thinking of firing up Software Center and removing all incarnations of Marble I can find and then do a find /usr -name '*marble*' and see what is left. Hope I don't destroy my box in the process. I'll try to refrain from: cd / sudo rm -rf * huge frown --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Recompile Marble and Subsurface -- still undefined reference
On 11/25/2014 08:08 PM, Steve Butler wrote: I'm obviously missing something. But it is too obvious for me. duh. Really so obvious that only curiosity found it. It's even on the build instructions. qmake-qt4 instead of qmake! I thought if qmake worked then qmake-qt4 wouldn't. My bad. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Temps from Suunto Cobra
On 11/24/2014 06:55 AM, Dirk Hohndel wrote: On Sat, Nov 22, 2014 at 08:19:00PM -0800, Steve Butler wrote: Subsurface (or maybe libdiv) takes the first temp and calls it the Air temp. DM3 calls it Start of Dive. Looking at the values for that day I'm surmising the temp is of the DC as it cools down in the water. Air temp that day was in low 80s. DM3 recorded 63 for the start, 54 for max depth and 55 for end of dive. Looking at the profile from DM3 looks like 63 is from the first 10 second recording. Nothing in the DM3 profile until max depth. 54 temp repeated for every entry at max depth. Then nothing until the last entry at depth (7 feet) which showed 55. Yes, that's how many Suunto dive computers operate. This is indeed Subsurface mis-labeling the temperatures we're getting from libdivecomputer. But the thing is, for many other dive computers this works just as we use it... the first temperature were closely matches the surface temperature... /D Surface air or surface water? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Temps from Suunto Cobra
On 11/24/2014 02:04 PM, Linus Torvalds wrote: On Nov 24, 2014 1:24 PM, Steve Butler kg...@comcast.net mailto:kg...@comcast.net wrote: Surface air or surface water? Usually surface air, mostly because the temperature sensor is really really slow to register. So the first sample - if it has a temperature at all, of course - is usually ambient temperature of the dive computer before the dive started. Now, is it air? If you keep your dive computer in a camera easter bucket like some people, obviously not. And if you are on the surface for a long enough time, then the slow temperature sensor will basically give you surface water temperature. But normally? Air temperature is likely the closest description. Certainly not guaranteed, but then, it would usually be even worse to call it water temperature.. Linus It has always bothered me that that my Cobra reports several degrees (as much as 20) below the air and also several degrees above the water. Would be nice if the DC would grab the temp when first turned on and checking the tank pressure. But, that's something we don't have control over. I'll have to live with this as is.At least DM3 didn't try to call it one or the other (just 'Start of dive', 'Max Depth', 'End of Dive'). Let the user determine whether it's air (like to see that at max depth!) or water. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Weights
On 11/23/2014 07:01 AM, Dirk Hohndel wrote: On Nov 22, 2014, at 11:43 PM, Steve Butler kg...@comcast.net wrote: On last dive that was imported -- the weights had to be added back in. [Of course!!!] But, when I added each line it picked up the weight from the prior dive. The downside is I had to add all three lines. * ankles 2 # * integrated pockets 30# * BC Pockets 8# [Yup, I'm a big guy but down from 69 # I carried three years ago.] If we are going to copy from the last dive, why not copy all the lines and save the user some entry time. They can always edit. At this point I don't see the weight pattern changing much from dive to dive for me. I'd like an option where the weights from the last previously saved dive auto-copy to all the new dives as they download. So we have the Copy Paste option where you can do just that. Download your new dives. Go to the last dive that was similar and then copy the data that you want to keep and just paste it on all the new dives. What we do remember is the last weight VALUE. So the last time you used ankle weights, they were 2#. But for those who often change where they dive (that would include myself), I don’t really want to have it fill in the data from my last dive… Backplate, V-bar for cold tech dives and integrated weights for recreational dives… I don’t see an advantage in just assuming that the last dive was like this dive. Now that I write this, I guess I could come up with an algorithm that might usually make sense. If the user uses auto-trip and the last dive /in this trip/ has weights, then maybe it mike sense to just copy them. What do you think? /D Have to admit it was weighing heavy on my mind as I went to sleep after sending that. Then it hit me that when I go on vacation with the wetsuit I'd hate to have to edit those multiple dives that assumed was still using the dry suit and more weight. So, you and I have arrived at the same place. Forgot about the copy/paste. But had thought maybe just a button (really small) next to the + sign to copy weights from last dive. At least it wouldn't happen automatically and be a hassle for divers who switch up their equipment. But for divers like me who dive OC/Dry/Nitrox/same weights for most of the year it would be nice to flag a set of fields that could be copied at one click under control of the user. --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Missing Default tank on DC import
On 11/23/2014 07:34 PM, Steve Butler wrote: On 11/23/2014 07:34 AM, Dirk Hohndel wrote: On Sat, Nov 22, 2014 at 11:30:33PM -0800, Steve Butler wrote: Deleted last dive so I could import from DC. It came in without the default tank from my preferences (HP119). In addition, when I selected HP119, the cu ft is not 123 (the manufacturer of my XL-119 tanks claims they have 123 cu ft at 3442 #). I have verified that all occurrences of HP119 in my dives have been modified to show 123. Is there some other place I should change? What's the wet volume of that tank? It's possible that the manufacturer gives the gas volume based on the ideal gas law (i.e., wet volume multiplied with the pressure in bar). But air doesn't behave like an ideal gas at higher pressures. We try to calculate an approximation of the real behavior of air (look at surface_volume_multiplier() in dive.c) which gives a lower gas volume at higher pressures as you would assume by simply using the ideal gas laws. /D The specs are: http://www.xsscuba.com/tank_steel_specs.html The Nominal Capacity at http://www.xsscuba.com/tank_steel_specs_metric.html is what we need. 15.3 liters should be 0.54 cuft. @230 Bar the ideal gas is 124.34. The Z-factor for air at 250 bar and 300 K (little warm for room temp) is 1.0669. The Z-factor at 200 bar/300K is 1.0326. I'd estimate the Z-factor around 1.05 for 230 bar. Just an eyeball would put the real around 119. sigh and here I wanted to believe the manufacturer especially since their 120 tank is listed as having 120 cu ft and costs $25 more at my LDS. --Steve So I'm guessing the True Volume from the first web page is the ideal gas calculation. However that implies to me that the actual capacity is 116 cu ft (124.34/1.0669=116.55). However, we are not at 250 bar so looking down at 200 bar with a Z factor of Been a long day. Obviously that lower part was supposed to have been removed. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: SAVE for OPEN
Thought I had done a git pull. Must have goofed on a step then. On 11/22/2014 09:50 PM, Dirk Hohndel wrote: I'm resonantly certain that's not the latest master. That one has a custom dialog that will do none of these things. You are describing the state as of 24h ago. Is it possible that you are taking about the latest daily build? I'll do a new one tonight /D On November 22, 2014 8:08:27 PM Steve Butler kg...@comcast.net wrote: Playing with the latest master to get the Cobra serial number, I made an export of my data in order to work with that. When I close, then open the dialogue box wants me to Save a file. Tried to give a non-existent name. It became obvious that it wanted to read the file. So, gave it the copied export file and it complained that the file already existed and did I want to overwrite. Being brave (it was a clone!) I said sure and everything worked out OK. But, sure was a strange dialogue to open an existing file. --Steve -- Stephen M Butler, PMP, PSM kg...@comcast.net kg...@arrl.net ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
CANCEL changes -- next option of CANCEL not intuitive
On 11/22/2014 10:52 PM, Dirk Hohndel wrote: I’d appreciate if you could play with the dialogs and see if you can trip them up into something stupid. I allowed multiple file selection (I think). You can enter file names that don’t exist. Etc. It would be good to make sure that none of this causes more issues. Thanks /D Not sure if this in stupid but it isn't intuitive. Start to change a dive. Then hit CANCEL. This pops a dialogue box with two options: 1. Close without saving. 2. Cancel Hmm. Since I pressed Cancel should I keep going down that path (introspective question). I'm not really Closing anything. I think it is the wording that struck me as odd. Since the description in the box above the two buttons is You are about to discard your changes perhaps the two buttons should be: 1. Discard changes. 2. Keep Changes. Note, pressing CANCEL after pressing CANCEL does indeed CANCEL the CANCEL. And if you followed that on the first pass -- well, I'm needing to head to bed on this thought! --Steve ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Missing Default tank on DC import
Deleted last dive so I could import from DC. It came in without the default tank from my preferences (HP119). In addition, when I selected HP119, the cu ft is not 123 (the manufacturer of my XL-119 tanks claims they have 123 cu ft at 3442 #). I have verified that all occurrences of HP119 in my dives have been modified to show 123. Is there some other place I should change? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: INSTALL file
On 11/16/2014 10:29 PM, Dirk Hohndel wrote: Could some of you who build from source on various flavors of Linux and Mac check the INSTALL file and make sure it's still accurate / send updates? Thanks, that would really help me. Still learning c++ and git. In other words a greenhorn. But still unable to build from source. The make step fails. In 6-8 months I should be more helpful. In the meantime, gasping for air! Anybody else using Ubuntu 14.10? Did: -git status On branch master Your branch is behind 'origin/master' by 20 commits, and can be fast-forwarded. (use git pull to update your local branch) nothing to commit, working directory clean -git pull First, rewinding head to replay your work on top of it... Fast-forwarded master to 25072b60ce6407044820dba043f07247f5acf226. -qmake -make | tee -a ~/steve.txt see attached for full listing linking subsurface .obj/moc_globe.o:(.data.rel.ro._ZTV8GlobeGPS[_ZTV8GlobeGPS]+0x60): undefined reference to `Marble::MarbleWidget::connectNotify(QMetaMethod const)' .obj/moc_globe.o:(.data.rel.ro._ZTV8GlobeGPS[_ZTV8GlobeGPS]+0x68): undefined reference to `Marble::MarbleWidget::disconnectNotify(QMetaMethod const)' collect2: error: ld returned 1 exit status make: *** [subsurface] Error 1 Makefile:523: recipe for target 'subsurface' failed /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_source.ts -qm translations/subsurface_source.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_source.qm'... Generated 0 translation(s) (0 finished and 0 unfinished) Ignored 1227 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_bg_BG.ts -qm translations/subsurface_bg_BG.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_bg_BG.qm'... Generated 1217 translation(s) (1217 finished and 0 unfinished) Ignored 10 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_da_DK.ts -qm translations/subsurface_da_DK.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_da_DK.qm'... Generated 1016 translation(s) (1016 finished and 0 unfinished) Ignored 211 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_de_CH.ts -qm translations/subsurface_de_CH.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_de_CH.qm'... Generated 945 translation(s) (945 finished and 0 unfinished) Ignored 282 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_de_DE.ts -qm translations/subsurface_de_DE.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_de_DE.qm'... Generated 1214 translation(s) (1214 finished and 0 unfinished) Ignored 13 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_el_GR.ts -qm translations/subsurface_el_GR.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_el_GR.qm'... Generated 543 translation(s) (543 finished and 0 unfinished) Ignored 684 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_en_GB.ts -qm translations/subsurface_en_GB.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_en_GB.qm'... Generated 1216 translation(s) (1216 finished and 0 unfinished) Ignored 11 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_es_ES.ts -qm translations/subsurface_es_ES.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_es_ES.qm'... Generated 1217 translation(s) (1217 finished and 0 unfinished) Ignored 10 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_et_EE.ts -qm translations/subsurface_et_EE.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_et_EE.qm'... Generated 942 translation(s) (942 finished and 0 unfinished) Ignored 285 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_fi_FI.ts -qm translations/subsurface_fi_FI.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_fi_FI.qm'... Generated 1208 translation(s) (1208 finished and 0 unfinished) Ignored 19 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_fr_FR.ts -qm translations/subsurface_fr_FR.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_fr_FR.qm'... Generated 1149 translation(s) (1149 finished and 0 unfinished) Ignored 78 untranslated source text(s) /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease translations/subsurface_he.ts -qm translations/subsurface_he.qm Warning: ignoring defaultcodec element Updating 'translations/subsurface_he.qm'... Generated 502 translation(s) (502 finished and 0 unfinished)
Re: INSTALL file
On 11/17/2014 01:45 PM, Lubomir I. Ivanov wrote: qmake DEFINES += NO_MARBLE make clean make Yes, that did work. Sounds like a newer version of qtCreator is needed on my box. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: extra data display
On 11/07/2014 02:08 PM, Dirk Hohndel wrote: So byte your tongue. Or even “bite” it… :-) Just take two nibbles. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: messing with the gas / tank handling
G Once my EON Steel arrives we'll need to drive up to Hoodsport and do some data collection... :-)? As in Hood Canal, WA? Somehow I thought you were located in Europe. Guess I need to be more curious in the future! --Steve (Enumclaw, WA -- OC mostly at Redondo) PS Looks like I'll need to pick up a modern language like C to add to my ancient language list (COBOL, Fortran, PL/SQL, etc). Become more useful here. ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface