Question Zhl-16c questions

Please register or login

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

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

@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 🙏
Search ScubaBoard and you will find many discussions of Mark Powell's quote. The issue is that a "deco dive" to MOST people means one with mandatory decompression stops. So, yes, all dives involve decompression, but only some dives involve mandatory decompressions stops. Your training and experience and dives do NOT involve mandatory decompressions stops; they are NDL dives.
 
@Mobulai I seldom use python(once per years),and I am not a coder. As a result, I disagree that this is not due to my lack of ability. However, it must be due to my lack of sleeping, I forgot that arduino is using c? Or c++? Anyway, thank you for sharing your valuable insights and experiences in your industry. Thank you very much indeed🙏🙏
 
@Mobulai I seldom use python(once per years),and I am not a coder. As a result, I disagree that this is not due to my lack of ability. However, it must be due to my lack of sleeping, I forgot that arduino is using c? Or c++? Anyway, thank you for sharing your valuable insights and experiences in your industry. Thank you very much indeed🙏🙏
If you are new to both coding and deco models, I recommend you go with something a bit more established like:

Or, start from scratch but validate everything (ideally against a commercially available dive computer) or running the code you develop against subsurface in planning mode
(Would be very educational which is good also)
 
@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 the target CPU that is the question. On arduino you might want to skip the pythons and go straight to its native IDE, on an ARM (like RasPi), python won't be problem performance-wise. It has other problems for an actual dive computer-type application, but for a computer or cellphone-based dive planner it'll do just fine.
 
@Mobulai Since my English is not good, do you mean using my own code to spawn a Deco plan and compare with the commercial available computer's result? Thank you very much indeed 🙏🙏
 
@dmaziuk thank you very much indeed for your valuable support and guidance. Do you mean the arduino ide is the one that I can download from its website? Thank you very much indeed🙏🙏
 
@Mobulai Since my English is not good, do you mean using my own code to spawn a Deco plan and compare with the commercial available computer's result? Thank you very much indeed 🙏🙏
Yes, to be sure that your code is doing the correct calculations
Like in this thread:

Another option is to compare with subsurface planner (but that’s more work, and python will help generate the results needed to do so)
 
It's the target CPU that is the question. On arduino you might want to skip the pythons and go straight to its native IDE, on an ARM (like RasPi), python won't be problem performance-wise. It has other problems for an actual dive computer-type application, but for a computer or cellphone-based dive planner it'll do just fine.
Agreed, but (even tho I haven’t tried python for such a project so can’t estimate the comp. Load) python is quite lacking in memory management so I’d avoid it in fear of eventually running into memory overflow/heap allocation
Gotta love c++ for that
I wouldn’t want a dive computer to crash mid dive 😅
Probably I’m too biased/hyperbole here given my mostly ECU based code experience; the only python code that handled RT system I worked on ran on an Intel linux industrial gateway with 32gb ram so that also had more than sufficient resources
 
Agreed, but (even tho I haven’t tried python for such a project so can’t estimate the comp. Load) python is quite lacking in memory management so I’d avoid it in fear of eventually running into memory overflow/heap allocation
Gotta love c++ for that

:rofl3: C++? Dead Languages 'R Us, COBOL FTW!

@Hihihello I meant the arduino "native" kit that comes with some sort of C++-like wrapper on top of C.

(I'd use it an as excuse to learn rust, myself.)
 

Back
Top Bottom