| Name | Last modified | Size | Description | |
|---|---|---|---|---|
| Parent Directory | - | |||
| README.html | 08-May-2012 04:27 | 2.7K | ||
| opendeco.pdf | 24-May-2009 09:48 | 2.0M | ||
| opendeco.tgz | 24-May-2009 09:54 | 3.0M | ||
Copy of the post:
Hi all, In 2007 I wrote did some research on the VPM-B algorithm for my BSc in Applied Physics thesis. As part of this research I wrote an implementation of VPM-B in the Python programming language. At that time I was planning to launch an open source project called OpenDeco to create an open implementation that could be used and audited by anyone with knowledge of the mechanics behind VPM-B. Unfortunately after graduation I have been extremely busy and I didn't even have much time for diving. I'm currently living in Beijing which is also not the best place to get wet. Instead of letting this information sit on my hard drive awaiting a moment I will have time to polish up the code and thesis for publication, I decided to post it here as is in case it is useful to you. The code is released under the GNU LGPL license, I will release the documentation with its LaTeX sources under a license that allows modification once I find a proper license for that (suggestions are welcome). A word of warning: 1) This is not a nice usable graphical decompression planner that you can use to plan you dives. It's a library other programmers could use to build one. 2) This implementation has not received much peer review yet, so DO NOT DIVE THE GENERATED SCHEDULES. The generated schedules vary slightly from both V-Planner and Erik Baker's code and might even be rubbish in extreme cases. So why care? 1) It is open source, anyone can improve on it. 2) It's more readable than Fortran code. 3) The way it's constructed allows for easy plotting of all kinds of parameters that might be interesting if you want to get a better feeling for how VPM-B works unlike other planners that are only focusing on spitting out a runtime table. 4) The thesis tries to give a good overview of how VPM works and is more comprehensive than many documents that are scattered across the internet. 5) The thesis documents the code with references to the actual code the theory is implemented in. You can find it at http://home.wojas.nl/opendeco/ I hope it's useful to you. Cheers, Konrad