Invalid dives
Dirk Hohndel
dirk at hohndel.org
Sun Mar 17 09:28:30 PDT 2013
On Mar 16, 2013, at 9:40 PM, Ďoďo wrote:
> Dirk,
>
> because my "Invalid dives" were dives I was swimming and freediving with my dive computer. So I was checking how deep water was on different places.
>
> Another cases are during the dive courses, actually during OWD mainly.
>
> 1. Swimming pool: I do not count for me swimming pool lessons as a real dives. But I track them - yes, I am too lazy to write it on paper.
> 2. Till you really start some dive with group of beginners it takes sometimes few "invalid" short dives. Again, I do not want to have them displayed as real dive, but I wanna keep them.
>
> is it enough?
I understand that you want them to be a special type of dives that you can somehow exclude. I'm not sure why you'd want to keep them, but of course "the user is always right".
This of course opens a huge can of worms. How are these dives treated in statistics? How are they handled when it comes to dive numbering? What happens if a dive is tagged as "invalid" (why "invalid", btw? Shouldn't that be "ignored"?) and then re-downloaded / re-imported from a different source (say you are like me and dive with four or five dive computers)?
This adds a lot more questions than your first implementation addressed.
> I did not use boolean - I did consider - because SHORT allows to distinguish between different type of invalid dives - if once needed.
I actually agree with that. If we really want to go that route than this should be just a dive type that is multi-valued. We could basically add an arbitrary number of tags to a dive. Things like "shore", "boat", "ice", "training", "ignored" and then have a UI that allows you to pick and choose which tags you want to exclude or include… that seems much more useful.
/D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4130 bytes
Desc: not available
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20130317/e5f75046/attachment-0001.bin>
More information about the subsurface
mailing list