I get a 404 there.Still ugly but here's the first graph with the ceiling.
https://github.com/BlueTrin/diving_decompression/blob/master/buhlmann.ipynb
I think you need to make your repo public or invite me.
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
I get a 404 there.Still ugly but here's the first graph with the ceiling.
https://github.com/BlueTrin/diving_decompression/blob/master/buhlmann.ipynb
Just made it public, sorry !I get a 404 there.
I think you need to make your repo public or invite me.
The Buhlmann algorithm defines 16 theoretical compartments.
I literally have to re-read my own code to answer that. I think that GF hi applies at the surface and am certain that GF low applies at the first stop. How you decide that ascending is ok is sort of implementation dependant. You can choose to ascend when the ceiling is shallower than current depth OR ascend when the ceiling hits the next stop depth. The former is a dive computer centric plan, the later a planner centric plan.In this paper, Eric Baker interpolates GFHi and GFLo, but he seems to use the current stop to fix the GF for the next stop.
That means that GFHi is computed for 6m for example if your last stop is on 6m.
Is that correct ?
Here is an interactive version of my first implementation, you can click on the cells, then press CTRL+ENTER after editing the values to recompute the graph.
GitHub: BlueTrin/diving_decompression/master
disclaimer: don’t use this for any other purpose than testing, playing with it
It is ok, what I object to is the holding out of it as some kind of superior algorithm when really it is a very simple dissolved gas model with a very nasty kludge on top. Also it is often claimed to be an open standard, especially compared to the algorithms used by the majority of dive computer manufacturers, whereas really it has many gaps for the implementation to choose.Thank you.
About GF being a hack, I am quite pragmatic: the goal is to provide some margin and stay further away from the m-value lines.
And the GF methodology is achieving its goal in a fairly straightforward manner