I guess I >>REALLY<< don't understand the math and I will heed to your
advice and use 0.001 as a starting point.  At some point I'll study up to
better understand why that's a good idea.  Thanks

And I found the problem with the GUI.  I was entering .001, not 0.001.  THe
gui apparently needs that leading zero.

On Mon, May 11, 2015 at 4:36 AM, Thomas Eckardt <thomas.ecka...@thockar.com>
wrote:

> >Is there a practical difference between 0 and 0.001
>
> Yes - from the mathematical point of view a practical 'baysConf' range is
> between 0.000001 and 1
>
> >I'd think something like 0.1 would be a good starting point
>
> thought ? - calculated ? - this is a very very wild guess - with an ideal
> corpus norm of 1.00 a value of 0.1 for baysConf will lead in to over 90%
> low confidence detection
> The math (shown in the GUI) explains how the confidence value is
> calculated.
>
> Thomas
>
>
>
>
> Von:    K Post <nntp.p...@gmail.com>
> An:     ASSP development mailing list <assp-test@lists.sourceforge.net>
> Datum:  11.05.2015 04:28
> Betreff:        [Assp-test] baysConf invalid / and explanation please
>
>
>
> I'm starting to explore the possibilty of changing baysConf away from 0.
>
> First, I might have found a bug: I entered .001 to see what would happen,
> and also tried .005 but I get a javascript popup for both saying:
>
>      Invalid 'baysConf' - unchanged
>
>
> I've read the gui description, but I'm confused as to why .001 would be a
> good starting point.  Is there a practical difference between 0 and 0.001
> I'd think something like 0.1 would be a good starting point, only 10%
> certain vs .001 which would be 0.1% confident if I understand correctly.
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to