3 replies to this topic

[fisiodiver]

Alguem conhece este software, de planeamento de mergulho? é fiavel?

Cumps

Fica aqui uma decrição do que o gajo faz e suas caracteristicas:


# Description of values to use within Zplan or ZPlanner
# *****************************************************
#
# When using ZPlanner (from windows), the data in this file will
# be created automatically each time you press Calculate.
# The descriptions below will help with program usage, and
# parameter limits.
#
# When using ZPlan (from the command line), the data described
# here will need to created by you and placed in a file
# called "profile.dat".




# You can have blank lines and spaces anywhere you like.
# As you can see, comment lines must have a '#' at the beginning.
#
# UseMetric: y or n or Y or N. Use metric or imperial units.
# This entry needs to be the first one in this file. If it
# is not set, imperial will be assumed.
UseMetric: n

# Fresh or salt water. Defaults to salt, if not set. y or n or Y or N
SaltWater: y

# Set to y or n, to enable use of ZHL16b instead of ZHL16c
# "b" is a bit less conservative.
UseBValues: y

# Setting DebugLevel to anyting but zero (0) will cause an
# incredibly verbose stream of spoodge on your screen.
# It is for developer diagnostics. Mess with it at your
# own risk, or if you're bored. Debug levels are 0-2
DebugLevel: 0

# Altitude should be specified in feet or metres, depending
# on the UseMetric flag. Set to zero for sea-level, of course.
# This is the altitude where the dive is to be conducted. Remember
# to be extra conservative on altitude dives, as you are probably
# still off-gassing from your travel to altitude.
#
Altitude: 0

# Conservatism: allows you set a percentage of conservatism. 0-100.
# This forces the algorithm to tack on the stated percentage
# of additional time at each calculation waypoint for purposes
# of determining tissue loading.
# Increase conservatism for cold water and higher workload.
# A conservatism of zero represents the pure Buhlmann ZHL16c profile.
# Setting this higher will also have the side-effect of creating
# deeper stops, although not as deep as Pyle Stops.
Conservatism: 10

# Precision: This allows you to set the degree of optimization
# that the program will perform. Values are from 1 to 100, and
# represent the percentage of error from the absolute optimal
# decompression plan that can be generated. "optimal" means
# the shortest, most precise deco schedule. The program will
# run much faster if this value is set higher (say, 20), at
# the expense of stretching each individual deco stop by up to
# 20% longer (following the example). For relatively short
# deco profiles, it won't make much difference, since stop
# times are rounded up to the nearest minute anyway. For really
# long hangs, setting this to 2-5 can save you significant hang time,
# but the program will take significantly longer to run. The key
# here is the length of your 10 and 20ft (3-6m) stops. If you are pulling
# hour-long stops in this range, this value will make a big difference.
# For 10-15 minute stops, it won't matter much at all.
#
# If you're planning epic-length dives, you might try starting
# out with a value of 10-40 while you run what-if's, then when
# you've got the basic profile, set it back to 1, and go
# grab a cup of coffee, while it cranks out your optimal plan.
#
# A value of 5-10 is appropriate for most needs.
#
Precision: 5.0

# StopDistance: The interval you want between "normal" deco stops in feet
# or meters. By "normal", I mean non-Pyle stops, which are calculated
# via a different means.
#
StopDistance: 10

# LastStopDepth: The depth you want to pull your last stop at. Some
# people like to do the 10ft/3m stop at 15 or twenty feet (9m). On OC with
# a high o2 deco mix, this will add a safety factor, at the expense
# of additional CNS loading. If you're planning on doing your last
# stop deeper on a CCR, be sure you either set this value, or make
# an appropriate adjustment to your setpoint during deco. Otherwise,
# the lowered FO2 will put you at a higher risk of DCS.
#
LastStopDepth: 10

# OxyNarc determines whether or not you want Oxygen to be considered
# narcotic when calculating END's. Set to y or n.
OxyNarc: n


#
# DeepStops is used to enable the generation and type of
# deep decompression stops. Many people feel including
# deeper stops for deep dives significantly reduces the probability
# of subclinical DCS (post dive fatigue), as well as full-blown DCS,
# by eliminating microbubbles early in the deco profile.
#
# You have two choices of method. Richard Pyle style deep
# stops, or WKPP style deep stops. Set this value to
# 'P' or 'p' for Pyle Stops, 'w' or 'W' for WKPP-style stops,
# or 'n' to disable deep stop generation in your profile.
#
DeepStops: w

# If Pyle Stops are enabled, the amount of time in minutes that will
# be spent at each system-generated deep stop. A value of
# 1-4 is typical. The WKPP method determines stop times for
# you, so PyleStopTime will be ignored if DeepStops is set to 'w'
#
PyleStopTime: 2.0

# TissueFile will be read to get your load values,
# and can be updated before planning the next dive.
# Leave blank if you don't want repetetive dives.
# The tissue file will only be updated if you run the program with
# a -s option. This way, you can do what-if's, and when you're happy
# with a profile and/or know your minimum surface interval, you can
# save the tissue loading values.
#
TissueFile: tissue.dat

# SurfaceInterval: is used in conjunction with TissueFile for
# calculating repetetive dives. Format: HHH:MM or just HH
# If this is the first dive after a long break, and your tissues
# are totally clear, just set the value to something like 900:00
# Be sure to update it before planning your second and each subsequent
# dive.
#
SurfaceInterval: 900:00

# PlanFile is generated, and contains your deco profile. If you
# want to print it out, go for it. Or just bring it up in Notepad
# and transcribe it. Change this to save to a different file besides plan.out
#
PlanFile: plan.out

# Rmv: is your Respitory Minute Volume in Cubic Feet or liters per minute.
# This is used for open circuit gas consumption calculations.
# If you don't know your RMV, you should measure it.
# DecoRmv allows you to set a different breathing rate for
# decompression, because you are likely to be more at
# rest while hanging on the deco line, trying not to get bored.
#
Rmv: 0.6
DecoRmv: 0.6

# SlideRate is in PO2 per minute. How much O2 do you
# burn off in one minute during a Scamahorn Slide.
#
SlideRate: 0.1

# This is for selection of deco gasses on open circuit.
# Just leave it blank or comment it out if you are doing Closed Circuit deco.
# The values are the percentage of o2 in the Nitrox mix. If you don't use
# any deco gasses, the last bottom mix will be assumed.
# You can list as many gasses as you need, just don't forget the commas.
# Set UseOCDeco to y if you want to enable the use of the
# gasses specified by OcDecoGas, or N to disable them.
UseOCDeco: y
OcDecoGas: 21, 32, 50, 100

# OcDecoMaxPO2: is the max PO2 allowed for any OC deco gas. It
# is used to autoselect the proper deco gas for a given depth.
# The program will always pick the deco gas for a given depth
# that has the highest PO2 without exceeding the value of OcDecoMaxPO2
# or your chosen MaxEND.
# To lower your overall CNS exposure (at the expense of a longer deco),
# tune down this value.
# NOTE: if you want to use 100% O2 at your 20ft. stop,
# set OcDecoMaxPO2: 1.6
#
OcDecoMaxPO2: 1.55

# MaxEND: is used when the program autoselects deco gasses. It
# won't pick a deco gas with and END higher than your max, unless
# you don't give it a choice (meaning you have no deco gasses, and
# the END of your bottom mix exceeds MaxEND during deco).
# Specified in ft or meters.
MaxEND: 130

# These values select your ascent and descent rates. You can
# add as many lines as you like, just make sure there's no
# big overlaps or *any* gaps in the ranges, or I'm not sure
# exactly what will happen.
# Ranges are in feet or meters, rates are fpm or mpm. Also, list the ranges
# from shallowest (first) to deepest (last) for descent, and deepest
# to shallowest for ascent, or you'll really screw up the program.
# Format is depth1-depth2 (ft or meters), feet/meters per minute.
#
DescentRate: 0-100, 60
DescentRate: 101-200, 60
DescentRate: 201-300, 60
DescentRate: 301-1000, 60
AscentRate: 1000-200, 50
AscentRate: 200-100, 30
AscentRate: 100-20, 30
AscentRate: 20-0, 30

# DecoSetpoint is for Closed Circuit. It allows you to plan a
# setpoint change at different depths during deco.
# Add as many lines as you like. The program will assume
# you are using the setpoint of your last waypoint up to
# whatever the depth you choose here. If you disable
# DecoSetpoint, your last waypoint PO2 will be used.
# If you want to go OC for deco at a given range, just
# put a 0 for the setpoint, and make sure your OcDecoGas
# parameters are set up with the proper ranges and O2 mixes.
# If there is overlap in the ranges for OC and CC deco, the program
# will assume you will use CC in the overlap zone.
# Set UseDecoSetpoint to y to use the DecoSetpoint values,
# or n to disable them.
UseDecoSetpoint: n
DecoSetpoint: 80-30, 1.4
DecoSetpoint: 29-0, 1.2

# This section contains your dive profile. You can have as many
# waypoints as you wish. Depth is in meters or feet. Time is in minutes.
# The gas selection is either o2% or o2/He. The "/He" portion
# is optional. The percentage of Nitrogen is always assumed to
# be whatever is left over after o2 and He. Setpoint is in PO2, of course.
# If you're doing open circuit, just leave the setpoint field empty (with
# no comma after the gas selection). To do a Scamahorn Slide, add a
# dash "-" after the setpoint, then put in the max slide value.
# Make sure you have a comma between values.
#
# Note that if you make a gas switch, the program assumes that
# for waypoints during descent, you will make the switch upon
# leaving the previous waypoint, and on ascent, gas switches
# are made upon arriving at the shallower waypoint. It's OK to put
# a time of 0 in for switches on the fly. If this not immediately
# inutitive, take a look at the examples below. You'll notice that
# it takes very few waypoints to specify a complex multi-gas dive.
#
# The columns are:
# depth, time, o2(/He)(, Setpoint(-slide))
#
# Examples:
#
# Dive1 (basic open circuit trimix dive):
# 130, 3, 21
# 250, 15, 10/44
#
# The first line says to descend to 130fsw on air and swim for three minutes.
# The second line says descend to 250ft after switching to trimix 10/44 and
# spend 15 minutes, then begin final ascent. The program assumes you
# switched to mix at the end of your 3 minute swim at 130fsw. See, pretty
# powerful for entering six values, eh?
#
# Note that the program assumes you want to start the final ascent after
# your last waypoint.
#
# Dive2 (Closed circuit Heliox dive with a diluent switch):
# 155, 0, 21, 1.2 - Descend on air, 1.2 setpoint. Switch to HeOx 8 at 155fsw.
# 450, 15, 8/92, 1.2-1.6 - drop to 450fsw for 15 minutes, using a slide.
# 155, 0, 21, 1.2 - switch back to air diluent at 155fsw.
#
# Once again, the columns are:
#
# depth, time, o2(/He)(, Setpoint(-slide))
#
130, 1, 21
250, 20, 10/44

[Culdagor!]

Tal como diz o disclaimer, esse software pode matar-te.

Tal como qq software seja ele o V-Planner o GAP ou o que for. Software de descompressão serve para integrar um algoritmo (ou varios) numa forma user friendly e com o maximo de hipoteses possiveis.

Podem fazer desde interpolações polinomiais de tabelas a calculos integrais, mas são todos baseados num algoritmo de descompressão.

A pergunta mais pertinente será "Qual o algoritmo de descompressão em que confio mais?"


Buhlman? Qual deles?

RGBM?

VPM?

Vais ver se utilizares vários que dão valores muito proximos com o mesmo tipo de settings selecionado. Ouvi dizer que o da GUE é mais "rápido" mas ainda não vi ninguem a pronunciar-se sobre isso.

[Culdagor!]

Já agora respondendo á pergunta, o Z-Planner é mais conservador que qq outro software.

Dá-te mais tempo de patamar que o GAP, ou o V-Planner.

Se é fiavél?

Bem em termos de software não tem bugs que eu tenha dado por isso, a sua fiabilidade enquanto modelo descompressivo é igual a todas a outras em minha opinião.

Ou seja pode num dia qq falhar horrivelmente.

[tramorwr]

Z is the precurser to V if I not very much mistaken. If you can get hold of V then do so as it has been 'developed'.

I used to dive Z and found that I suffered from high levels of subclinical DCS, I tried more conservative pofiles but moved quickly on to V (but now use proplanner/VR3).

F