On 01 Jun 2014, at 15:23, Robert C. Helling <[email protected]> wrote:
> > >> Am 01.06.2014 um 14:54 schrieb Henrik Brautaset Aronsen >> <[email protected]>: >> >> Agreed, it really makes sense to force these values to be in whole minutes. >> At least that's what GUE Deco Planner and Multideco/VPlanner does. > > Will take care of this. Could you guys provide me with an example with what > your favourite runtime table would look like (in ASCII text)? Do you really > want transition times given the ascent rate is determined by the depth? > Currently the output look like this. Transition to 40 m in 2:00 min - runtime 2:00 on EAN27 Stay at 40 m for 28:00 min - runtime 30:00 on EAN27 Transition to 21 m in 2:34 min - runtime 32:34 on EAN27 Switch gas to EAN50 Transition to 12.0 m in 1:30 min - runtime 34:04 on EAN50 Stay at 12.0 m for 1:00 min - runtime 35:04 on EAN50 Transition to 9.0 m in 0:30 min - runtime 35:34 on EAN50 Stay at 9.0 m for 2:00 min - runtime 37:34 on EAN50 Transition to 6.0 m in 0:30 min - runtime 38:04 on EAN50 Stay at 6.0 m for 2:00 min - runtime 40:04 on EAN50 Transition to 3.0 m in 3:08 min - runtime 43:12 on EAN50 Stay at 3.0 m for 6:00 min - runtime 49:12 on EAN50 Transition to 0.0 m in 3:08 min - runtime 52:20 on EAN50 Gas consumption: 2877l of EAN27 454l of EAN50 That is way to crowded. A minimalistic table would look something loke this. Showing only depth and time/action. There really is no point in showing ascent speeds/transition times. Depth Time 40m 30min 21m EAN50 12m 1min 9m 2min 6m 2min 3m 6min > Best > Robert > From the beer garden of the world's oldest brewery > _______________________________________________ > subsurface mailing list > [email protected] > http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface _______________________________________________ subsurface mailing list [email protected] http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
