Dive Planner custom SAC per dive segment.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files or tests are named. Start by locating the dive planner point table and the existing general and per-leg SAC handling, then determine how a segment-specific value would affect planning calculations. Done means each dive leg can use its own SAC while defaulting to the general bottom SAC.
Written by the indexing model from the issue text.
Description
Describe the issue:
- Bug
- Change request
- [ x] New feature request
- [ x] Discussion request
Issue long description:
Wile planning a dive ususally we know our SAC, it is totally different while fighting a current or making some work, than when relaxed making a deco stop holding a line for example. My suggestion is to create a SAC field in the dive planner point table that will by default place the bottom SAC placed on the general field. But that can be manually changed for that specific leg to whatever value we want. This would make the planer so much better.
Operating system:
All Operating systems.
Current behavior:
Only Two possible SAC values are assigned for all the dive legs.
Expected behavior:
Be able to assign different SAC values for different legs.
- Dominant language
- C++
- Stars
- 3.2k
- Forks
- 601
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 29
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from subsurface/subsurface
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
subsurface/subsurface#4970 · 3 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
subsurface/subsurface#4969 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
subsurface/subsurface#4950 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
subsurface/subsurface#4946 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
subsurface/subsurface#4941 · 3 comments ·
All issues in subsurface/subsurface
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·