There is no erratic estimation. It is simply UNKNOWN because it depends on so much network stuff.
You can replace the estimation by a "approx" 1 minute timeout that's all. That is the internal timeout. Good luck with your other features. BR, Stefan On 23.06.2016 06:48, Prerna Kashyap wrote: > Hi all. > I am Prerna, a summer research intern at FU, Berlin and I'm currently > working on evaluation and implementation of additional features in Saros > like smoothing the erratic estimation of the remaining time during a Saros > session initiation. > Looking forward to contributing to the project. > Prerna > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > DPP-Devel mailing list > DPP-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dpp-devel ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
