<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 1 Nov 2014, at 10:57, Miika Turkia <<a href="mailto:miika.turkia@gmail.com">miika.turkia@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote class="gmail_quote" style="font-family: GillSans; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Together they give enough information to know what the diver was breathing at any time.<br></blockquote><div style="font-family: GillSans; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br></div><div style="font-family: GillSans; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Thanks, this gives me something to work on. The current Shearwater import is indeed quite limited in this regard. And of course the whole CCR concept was not there when I wrote the transformation.<span class="Apple-converted-space"> </span></div></blockquote><br></div><div>Indeed, and I think we’re going to find things rather fluid as we decide what’s useful information to have from a CCR dive. Willem’s building a road with the Poseidon work he’s doing, but it’s quite an esoteric rebreather, so I think we’ll find some concepts map well to others, and some won’t.</div><div><br></div><div><blockquote class="gmail_quote" style="font-family: GillSans; margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"></blockquote><blockquote type="cite"><blockquote class="gmail_quote" style="font-family: GillSans; margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">The CSV import has no options for Gasses, Setpoints, OC/CC mode, ppO2 Sensors, all of which are in this file. I agree the dialog is a limiting factor here. I think there is also a problem with how these concepts map into the Subsurface XML.<br><br>Fields are named similarly to the XML.<br><br></blockquote><div style="font-family: GillSans;">I am thinking of 3 different options for this:<br></div><div style="font-family: GillSans;">1) just keep it as it is and hope that CCR divers have better import option than the CSV<br></div><div style="font-family: GillSans;">2) Implement the setpoints and other info under the hood with no configuration options for users<br></div><div style="font-family: GillSans;">3) Make a new tab for CCR import<br><br></div><div style="font-family: GillSans;">Personally I would of course prefer something that does not include GUI work, but overall I kinda like the third approach. At minimum, implement another tab for the CCR import and possibly cimplify the current CSV import for recreational divers. I just wonder if tech divers will need all the fields in current CSV import when diving OC.<br><br></div><div style="font-family: GillSans;">Any comments on these? Anton, what is your opinion?</div></blockquote><br></div><div>CSV is nice to have as a fall back. There’s always going to be a computer / rebreather that we don’t support, and having CSV available gives a user a fighting chance. Even if it’s a limited set of info. If you’ve got a better method for a particular device (e.g. XML, or a specific format of CSV) you’re going to do that.</div><div><br></div><div>My opinion is that for the configurable CSV import it has to be limited, otherwise you’ll be on a never ending quest to try to build in more flexibility.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Time</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Depth</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Water Temp</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>ppO2 (Single Value - CCR/SCR)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>CC/OC (CCR)</div><div> Stop Depth</div><div><br></div><div>…and then it’s a manual process to enter gasses / switch depths.</div><div><br></div><div>(I’ve dropped off NDL, CNS, TTS, & pressure from the current list. CNS is calculable. NDL & TTS aren’t that important if you’ve got the ceiling IMHO. Pressure I assume is cylinder pressure - How many do you want? Possibly just 1, but no more)</div><div><br></div><div>Things like multiple sensor readings, or multiple gasses probably need to be limited to known vendors. There’s just too many ways they could be represented. </div><div><br></div><div> - Is an O2 sensor reading in bar or millivolts? </div><div> - Is a breathing gas a number into a gas table, an fO2/fHe, or a ppO2/ppHe? </div><div> - Is a set point column boolean Hi/Lo, or a value?</div><div><br></div><div>Any dialog box that deals with all of that is going to be huge. So I’d keep the options low (as present, maybe trimming a couple), and add a couple more for CCR/SCR. Then have predefined schemes which are able to do more under the hood (e.g. APD, Seabear, etc)</div><div><br></div><div>My 2p.</div><div><br></div><div>Paul</div></body></html>