This the paper he self-published in "World Divers"
Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.
Benefits of registering include
My summary of that paper: the DCIEM algorithm should be the gold standard for repetitive, mandatory stop diving and any computer using any other algorithm should state it is different from DCIEM. (Somehow, that seems obvious to me. If I wanted a DCIEM computer, I would have bought one.)This the paper he self-published in "World Divers"
Strange indeed.ETA: It was also strange that they evaluated computers using anything other than ZHL-16C-GF at their default conservatism, but somehow they didn't do that for those using it. Who does mandatory stop dives (repetitive or not) at 90/90?? It's certainly not the default conservatism setting for any computers with which I am familiar.
Strange indeed.
Do you mean that when appointed by the Shell oil company when building ZHL16 he was'nt reliable too ?He also in same period was terribly excited about a new UWATEC computer he was involved in
@cerich
Since the beginning of this thread, I have been trying to give you hints that I saw through your game. It does not seem that you understand my gentle hints that you are not fooling us. You are leaving me with no choice but to write this message.
Your arguments are obviously biased.
Your first message on this thread (#5) suggests that we would present fake data.
Because digging into how BW started to slog about his invented dive history database to try and save RGBM when it started to fall apart would have just been a distraction from this.All of our tests are accompanied with pictures at different points in the test protocols. You can cross reference any information we display using these pictures to match dive time, depth, stop time, TAT, even time of the day for the models that display it in dive mode. It would be doable to spot an error in our data, and quite easy to demonstrate that it is an error. Yet, when @Peralman asks you for some pointers about which data is fake, you remain silent, and have not brought the subject back on since.
Sigh, you are lacking reading comprehension and paranoid.This visibly looks like an unsupported claim. You can of course prove me wrong by giving one single specific example of such fake data.
In messages #12, #24 and #30, you have been saying that our tests are out of scope for the intended use case of some dive computers, without ever bringing any proof to support your statement. I have asked for this multiple times, yet you do not deliver. I took it a step further, doing it your way, quoting manuals to support our claim that we are indeed in the intended scope. You have not denied these proofs, neither have you brought evidence that you were asked for in your response message, #39. We have reviewed the computers we tested and never have we found any mention saying that we were out of the intended use scope, in manuals, websites or any communication from manufacturers. You can of course prove me wrong by giving one specific quote from a manual that supports your claims.
You keep cherry picking on the fact that the "right-left shunt" term for the lungs makes no sense. I have tried to explain why such term is used, yet you don't seem to understand. I can understand that my explaining isn't perfect, but @Duke Dive Medicine explained it in a way that makes perfect sense in post #32. Yet, you still deny the words of Pr A. A. Bühlmann. You presented an argument to why you deny it in post #39, and this is where it gets interesting.
You are saying that the UWATEC lawsuit is Pr Bühlmann's fault. The recalled computer (CPSC, UWATEC AG Announce Recall of 1995 Aladin Air X NitrOx Dive Computers) is the Aladin Air X NitrOx, which was released more than a year after Pr Bühlmann passing away. The error was specific to nitrox diving (Did Uwatec conceal a known computer flaw?). The prototype computer that was tested for the UHMS workshop was the Aladin Air X, which didn't have nitrox capabilities. There is no way Pr Bühlmann could possibly identify the fault with the prototype he had then.
In conclusion, your arguments are not only biased, they are obviously selected and filtered to serve your purpose. You mention the Aladin Air X NitrOx lawsuit, because you can use it to serve your point, without specifying any of the details, which go against it.
Sigh, I never hid who i was, you didn't even look when I started to reply in this thread? That says something. Bühlmann made many iterations, I said very clearly he was brilliant and added to safety. Yeah, I think he went down wrong road for a bit in the early 90's, work since has built upon his earlier foundational work than the stuff he was doing at the end. When I said we would have to have a clear conflict of interest policy, you obviously took that to mean you.. that is silly, I meant everyone, including me. I can only speculate why that triggered you it seems, and be amused.I believe you are being emotional about the fact that we question ZH-L16 C implementations. You are Chief Diving Officer at Deep Six, which sells a dive watch, the Deep 6 Excursion Dive Computer. Remind me, what algorithm does it run again? If you are so doubtful about Pr Bühlmann's work, why do you sell a computer that uses his algorithm? There is obviously a conflict of interest here. You are the one in a conflict of interest.
Dive safe, don't set 90/90, NOBODY thinks that is a good idea, except some dude screaming it's default when it isn't it seemsNow that this is out of the way, I believe the situation is fit to answer the questions that actually serve the debate. Yet, this post is already long enough, so, to be continued.
Best regards,
Eric Frasquet,
Deeply Safe Labs.
My summary of that paper: the DCIEM algorithm should be the gold standard for repetitive, mandatory stop diving and any computer using any other algorithm should state it is different from DCIEM. (Somehow, that seems obvious to me. If I wanted a DCIEM computer, I would have bought one.)
There is always a balance to be found between stop time and safety. If this had been submitted to a peer-reviewed journal, I'm quite certain it would have been rejected with the admonishment to incorporate data backing up the author's contention.
ETA: It was also strange that they evaluated computers using anything other than ZHL-16C-GF at their default conservatism, but somehow they didn't do that for those using it. Who does mandatory stop dives (repetitive or not) at 90/90?? It's certainly not the default conservatism setting for any computers with which I am familiar.
Spending more time on decompression is generally safer than less time, but we’re always trying to balance Total Decompression Time (TDT) against the probability of DCS (pDCS).The Deeply Safe Labs website is the most recent version of the tests. It includes more GF settings, including manufacturer default settings.
Greetings divers,
The results show that some dive computers, specifically these that implement ZH-L16 C, compute significantly lower decompression times than other computers.... Some of them simply confirmed that absence of additional procedures, without bringing any argument to why they are not taking into account aggravating factors, like the right-left pulmonary shunt.