Problem Space: negatives or only positives
"Trever L. Adams" <[email protected]>
| Newsgroups | gmane.mail.spam.crm114 |
|---|---|
| Message-ID | <[email protected]> |
Thank you all who have helped me so far. I am still collecting
information but getting ready to actually code (C and crm114).
My problem space is a strange one (code will be GPL 2, 2+ or 3, I
haven't decided and will be based on other F/OSS projects which I don't
control). I am working on categorizing web pages. So, things may fit
into multiple categories, they may only fit one. They may not fit any
(as this is access control/filtering not exhaustive).
Some texts I have seen suggest to me I want hyperspace or OSBF.
Hyperspace is faster and uses less memory which fits what I am after.
OSBF can be (some texts suggest they trade places) more accurate than
Hyperspace. Any suggestions?
Finally, I have seen code from CRM114 Revealed that suggests I want:
{
isolate (:stats:)
classify <osb unique microgroom> (A B C) (:stats:)
output /:*:stats:/
}
However, this doesn't allow for negatives. I am not sure I need or want
negatives. However, I am sure it ups the accuracy, but slows it down.
Is it possible to do ((A | nA) (B | nB) ...) where nX is notWhatever?
Is it possible to do something like (A B C) | D?
Which would be the recommended way of handling this? I am afraid the
answer is going to be to use negatives. The question is, based on
people's experience, which is best.
Thank you,
Trever Adams
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Crm114-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crm114-general
signature.asc
(application/pgp-signature, 259 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkg14LsACgkQTmpiivh5HXPuZgCeLn855LxginZDBb/eouAvt0B0 JFYAn0eIi0HrcjXvRFEJfjJIdt57OL4g =avU3 -----END PGP SIGNATURE-----