Hi
@cerich ,
Votre Français n'est pas si médiocre.
However, with some consideration to the other users of this forum, let's keep this in English. Our writing may not be perfect, but it is good enough to avoid any missunderstanding. If we have trouble understanding someone, we would be asking questions anyway. There is no need to worry on this side.
Salut Eric,
Pourquoi pensez-vous que les ordinateurs devraient prendre en compte des facteurs physiologiques tels qu'un shunt droite-gauche ?
Certes, un shunt est un facteur de risque supplémentaire de DCS (Peppas et al, 2023), mais c'est aussi un problÚme physiologique présent chez environ 25 % de la population générale. Pourquoi est-ce que c'est aux fabricants d'ordinateurs de tenir compte de l'aptitude à la plongée plutÎt qu'à l'aspect médical ?
L'industrie de la plongĂ©e ne veut pas exclure un quart de sa base de consommateurs potentiels, mais Peppas et al soulignent certainement que le shunt droite-gauche est bien trop bien reprĂ©sentĂ© chez ceux qui obtiennent le DCS. Cela me semble plus prĂ©occupant que les choix de conception faits dans les ordinateurs de plongĂ©e qui se rapportent Ă l'utilisation conçue et prĂ©vue. Ne tient pas compte des facteurs aggravants (il existe bien plus quâun simple shunt droite gauche Ă des degrĂ©s divers). Le problĂšme vient donc des ordinateurs de plongĂ©e, ou d'une industrie, y compris des organisations qui ont codifiĂ© les examens mĂ©dicaux de plongĂ©e pour la plongĂ©e rĂ©crĂ©ative (RSTC, UHMS et DAN), qui savent qu'un shunt droit-gauche peut constituer un risque grave (RSTC Medical, instructions au mĂ©decin, 2020), mais ne nĂ©cessite-t-il pas de tests pour exclure ?
Ma prĂ©occupation est que l'extrapolation de tous les facteurs susceptibles d'augmenter le risque pour un plongeur dans la conception d'un ordinateur aboutirait Ă un ordinateur de plongĂ©e qui conseille "Ne plongez pas". AprĂšs tout, mis Ă part les problĂšmes physiologiques, la visibilitĂ© de lâeau, la tempĂ©rature, lâexpĂ©rience, le poids, etc. sont tous des facteurs bien Ă©tablis qui contribuent Ă de mauvais rĂ©sultats. Bien qu'en thĂ©orie, vous puissiez concevoir un ordinateur de plongĂ©e pour mesurer et prendre en compte tous ces Ă©lĂ©ments (avec des capteurs appropriĂ©s, une saisie utilisateur et une capacitĂ© de calcul), il semble beaucoup d'efforts pour proposer "Ne plongez pas".
View attachment 833564
Are you refering to the article named "Right-to-Left Shunt in Divers with Neurological Decompression Sickness: A Systematic Review and Meta-Analysis"?
There seem to be some kind of missunderstanding here. This study focuses on the patent foramen ovale (PFO), as one of the contributing factors to what is generally refered as right to left shunt (RLS). I suppose that is why you mention 25% of the population, but the article clearly talks only about PFO:
[...] PFO is common in the general population, with an estimated prevalence of 25â30%.
What we are talking about is specifically the right-left
pulmonary shunt, which is described briefly in the introduction of the article you mention:
[...] the supersaturation of tissues with dissolved gas that overwhelms pulmonary filtration capacity [...]
You are asking why we believe this right-left pulmonary shunt should be accounted for in dive computers. What we do or don't believe does not matter. What seems more important is what Pr. A. A. BĂŒhlmann wrote:
Experimental dives and statistics (DAN, BSAC) confirm a higher risk of decompression sickness for repetitive dives. Microbubbles in the venous blood obstructing a part of the lung capillaries produce ventilation-perfusion trouble, a right-left shunt well known in lung physiology. The arterial nitrogen pressure is for a few hours distinctly higher than the nitrogen pressure in the inspired air. Therefore the nitrogen elimination by respiration is retarded.
The algorithm ZH-L8 ADT takes into consideration this risk in extreme repetitive dives [...]
The algorithm ZH-L8 ADT is not only a needed modification, it is an essential improvement.
Source: Albert A. BĂŒhlmann, Behavior of dive computer algorithms in repetitive dives : experience and needed modifications, in Hamilton R.W. edition, UHMS Workshop 81, 6-1-1994, Undersea and Hyperbaric Medical Society.
sure, but like him, having been involved in dive computers at the manufs level, I know that a LOT of thought goes into it, and the intended use for the computer is an important factor in implementation decisions. Much of what he is doing is going WELL outside the design use case for many units and ignoring what the actual manuals say. His argument that it's a valid means to test/expose is.. wrong. There are many good reasons why that is, some algorithm, some programming, some hardware, and some design decisions. But, push some units far past design envelope and if the manuf didn't choose to just lock them out, you will see..exactly what he found. Is the problem the computer or the user not using as designed? If I try and do all the aerobatics in a Cessna 150 that a 150 aerobat can do, when the wings fold on me it's my fault, no matter how much I scream on the way down "BUT OTHER CESSNA 150's CAN DO IT, why didn't this one?"
I'm ok with him doing that, IF he CLEARLY annotated with what the manufs recommended use for the unit was, and any specific things regards settings from the manuals. Plus, having like you read many, many papers on deco, some of what he is claiming is.. cherry picking at best and some is just wrong. So, supply references or don't make unsupported claims.
I have trouble understanding how the lack of source invalidates our claims. Let me take an example, with this conference:
At 15:00,
@Dr Simon Mitchell talks about the inverse correlation between decompression time and DCS risk, however he never gives any source to back that up. Does that mean that Dr Mitchell is not a scientist? Does that mean that his claim is wrong? I don't think so, it probably just means that he is simplifying his speech for the sake of his audience.
Now, let's be constructive and leave these petty arguments behind us. You seem to disagree with us, and that's fine, but please make your point clearly:
Which claims exactly are you denying? Why?
Do you have a specific example of a computer that, in its manual, makes a mention of a scope of use that we would have breached?
Best regards,
Eric Frasquet,
Deeply Safe Labs.
Edit:
There seems to be a problem with embedding the youtube video. Here's a direct link:
https://www.youtube.com/live/jR0Fu20zlYQ?si=fo-K0X2OiaPVy0F0&t=900