Hi,

I just pushed a branch to Github: 
https://github.com/atdotde/subsurface/tree/latest_update

One of the patches is supposed to fix an error that made our desaturation 
artificially fast. Now, the deco times are slightly more conservative. But it 
seems they are too conservative for the benchmark.

I guess Rick did the benchmark (I don’t have it here). Rick, could you please 
look into the source of the benchmark what the assumptions on the 
saturation/desaturation rates are there and why the computed times differ so 
much?

Thanks
Robert

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to