Hi Graham,
(Assuming your talking about Dive Log Manager/DT here, not Dive Log).
1) If setting the "main tank" as "double" it seems to be impossible to have the second tank as a single ...
You're right - very confusing! Thanks for pointing out this bug. Will get this fixed ASAP for the next release.
2) the calculated SAC rate does not seem to take into account gas usage in the additional tank/s.
Well, we *think* we do. Perhaps this bug is getting in the way somehow, but you should see a per tank SAC rate. The exception is that if we don't have profile information for the pressure values and depth on the 2nd tank, we can't do a calculation. So let's say you have the main tank and Tank 1. When calculating the SAC for the main tank, we exclude all the samples found in the profile from Tank 1 and do the same (exclude main tank) when calculating for Tank 1. If there is no main tank profile data, then you can enter an "average depth" for SAC calculation purposes, but we don't have a way for users to enter "average depth" for additional tanks like Tank 1.
Few dive computers support the concept of "tank switch" and so depending on how the information got into the application means that maybe we don't have enough information. If we can take a look at one of your example dives, that might help. You could create a new logbook and just import the indicating dive and send it off to us and we could take a look.
And a suggestion- if loading a dive profile that contains temperatures, is it possible to populate the air and water temperatures with values from the surface and deepest parts of the dive?
Certainly possible. Although this is a bit of a philosophical question. So far, we have only populated these fields with information from the dive computer itself, or let the user enter it. Since we believe the dive computer is "the truth", we do not like to modify any information it has without the user's knowledge. So we left it empty on purpose if we didn't know how to read it from the dive computer or if the dive computer didn't have it. We could fill it in with our own calculated data if that was the case, but for all the different diving in the world, it's hard to know what to do. For example the surface water temperature is not necessarily indicative of the air temperature and people have different beliefs on what single number to use for water temperature based on thermal clines and personal experience on the dive. We just figure that if the dive computer doesn't have an opinion, then we should punt and let the user decide what it should be
Right now though, for Suunto computers, we don't "read" what the dive computer thinks the water temperature is. So if the dive computer has a temperature profile, we'll calculate the average and put that value in there. We had a lot of feedback from Suunto users that they wanted this so we did it. So things can change too with user feedback like this
Cheers,
Janice