Question Zhl-16c questions

[Hihihello]

@tursiops I am trying to develop a computer to be an alternative way to calculate my decompression obligations as an ow diver to prevent decompression, rather than only using a g shock, a pressure gauge ,and a table to verify the result from a peregrine. I hope this can reduce the possibility of becoming a patient of Dcs. I fully understand that using diy equipment is absolutely dangerous and may cause severe problems. Thanks for your warning indeed.

 

[Hihihello]

@inquis Thanks for your recommendation indeed. I have tried already but due to my lack of ability in computer science, I don't know how to use c. I hope to use python and would like to use my own knowledge to verify other code suitability. However, once again thank you very much indeed.

 

[tursiops]

@tursiops I am trying to develop a computer to be an alternative way to calculate my decompression obligations as an ow diver to prevent decompression, rather than only using a g shock, a pressure gauge ,and a table to verify the result from a peregrine. I hope this can reduce the possibility of becoming a patient of Dcs. I fully understand that using diy equipment is absolutely dangerous and may cause severe problems. Thanks for your warning indeed.

You don't really need to "verify" the results from the Peregrine. If you have a table, that is your absolute backup. Apparently you are trying to stay within NDL limits. Your proposed 30 mins at 30m will break those limits.
I understand your desire to learn more about Buhlmann, but perhaps you should first understand more what your limitations are as new OW diver. You speak of decompression obligations; you do not have any. Zero.

Your reasoning makes as much sense as saying you wish to make your own watch because you don't trust your G-Shock.

 

[Hihihello]

@tursiops I truly understand that I need to be limited by no decompression limits, but I would like to ask if I do not have any decompression obligations, why can't I ascent in 30m/s excluding the factor that I might collide with a boat? Thank you very much indeed. As I know a little bit only.
Regarding the question that I am not trusting my gshock, I would like to apologize for the inconvenience I have caused due to my bad expression. I would like to clarify that I hope to have 2 verification tools to help me reduce my decompression obligations in a scientific way that follows the probability theory. Once again, sorry for my bad English, and thank you very much indeed for answering my questions.

 

[Mobulai]

@inquis Thanks for your recommendation indeed. I have tried already but due to my lack of ability in computer science, I don't know how to use c. I hope to use python and would like to use my own knowledge to verify other code suitability. However, once again thank you very much indeed.

Python is extremely slow and unfit for embedded systems
I recommend you look into DiveIno repo on github

 

[Hihihello]

@tursiops Regarding the 21m 30min problem, I must express that this is my problem. I did not consider ndl. I hope to use this as an example for professionals to explain the theory easier. Thank you very much indeed

 

[tursiops]

@tursiops I truly understand that I need to be limited by no decompression limits, but I would like to ask if I do not have any decompression obligations, why can't I ascent in 30m/s excluding the factor that I might collide with a boat? Thank you very much indeed. As I know a little bit only.
Regarding the question that I am not trusting my gshock, I would like to apologize for the inconvenience I have caused due to my bad expression. I would like to clarify that I hope to have 2 verification tools to help me reduce my decompression obligations in a scientific way that follows the probability theory. Once again, sorry for my bad English, and thank you very much indeed for answering my questions.

Even if you are able to calculate your own version of Buhlmann, you will NOT find why an ascent rate of 30m/min (NOT 30 m/s) is a bad idea. That is external information that is input to Buhlmann, and does not derive from any calculation within Buhlmann.
Before learning how to calculate Buhlmann, you should first study at least these two books for the background information and answers to your questions about things like ascent rate:
"Deco for Divers" by Mark Powell
"Deep into Deco: the Diver's Decompression Textbook" by Asser Salama

 

[Hihihello]

@Mobulai thank you very much indeed for your precious suggestions. I didn't notice that python is slow due to my lack of ability. Thanks for warning me

 

[Hihihello]

@tursiops Thank you very much indeed for your recommendation. According to Deco for divers p.133/p.688, "
NO-STOP DIVES
A no-stop-dive, also known erroneously as a no-decompression dive, is a dive in which no decompression stops are required. It is defined as a dive in which the diver can ascend directly to the surface at the recommended ascent rate without any of the tissue compartments exceeding their M-Values and hence without needing to do a decompression stop.
The term no-decompression dive is a misleading name. As we have seen every dive involves a degree of on-gassing and every ascent involves a degree of off-gassing and so decompression of some sort is required on every dive. The tissues may decompress enough on the ascent so that no additional stops are required but that does not mean they are not decompressing."
Sorry for quoting Mr Mark Powell's master piece, if you have any opinions, I would delete it immediately. Thank you very much indeed.
I do agree that the reason for having a wrong concept is that my English is not really good to understand the aforementioned paragraph. @tursiops Would you mind sharing your thoughts on your understanding on the aforementioned quote? Thank you very much indeed

 

[Mobulai]

@Mobulai thank you very much indeed for your precious suggestions. I didn't notice that python is slow due to my lack of ability. Thanks for warning me

It’s not a lack of ability, only EXTREMELY heavy computations would make it show

But in essence, python actually runs on a C backend engine (especially for math libs); so translations cost some comp. power

But I think there are libs out there that enable compiling python scripts into embedded compatible C/C++ code; not that I used any — in case you really wanna avoid writing in C