Jump to content

Wikipedia:Articles for deletion/One-pass algorithm

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by JPxG (talk | contribs) at 23:23, 15 April 2021. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
One-pass algorithm (edit | talk | history | protect | delete | links | watch | logs | views) – (View log)
(Find sources: Google (books · news · scholar · free images · WP refs· FENS · JSTOR · TWL)

Article has been unsourced since Jan 2007. Notability of topic is in question. Coin945 (talk) 05:49, 13 April 2021 (UTC)[reply]

Note: This discussion has been included in the list of Computing-related deletion discussions. Shellwood (talk) 09:14, 13 April 2021 (UTC)[reply]
  • Comment IMO the article should be kept and cleaned up. The distinction is important in CS, as a one-pass algorithm by definition can deal with arbitrarily large input with bounded memory. I no longer remember who wrote what, but the definition is clear and useful, and the term itself is clearly in use. To me, the fact that a lot of the references are in things like CS course notes tells me that a Wikipedia page on the topic would be useful, but I don't know where that lands us with Notability standards. The part on cluster representatives seems specific to database algorithms, so I'd be inclined to take it out. I'll see if I can dig up a few references and do a little cleanup --dmh
  • Keep I missed the link to streaming algorithm. With the text on cluster representatives removed, I think this article is about right: The full details, including the mechanics, are covered under streaming algorithm. This article just calls out that a one-pass algorithm is a particular kind of streaming algorithm, and gives examples of what you can and can't do in one pass. It adds an increment of value over streaming algorithm but mentions some specifics about one-pass algorithms in particular. The one area of improvement would be the examples. It would be good to call out a case that can be solved in more than one pass but not in one. As to notability, "one-pass" algorithm is definitely a term of art in CS. I think the hits for CS courses attest to this, but I don't think they need to be included in the article as references, since they only support notability and don't particularly add to the understanding beyond what's already in the article. --dmh. — Preceding undated comment added 15:45, 14 April 2021 (UTC)[reply]
  • Keep. This is an important subtopic of streaming algorithms. If it were stubbier, or the streaming algorithm article less broad, then a merge rather than deletion might be warranted, but as it is I think it works well enough as a stand-alone article. Googls Scholar has over 10k hits for "one pass" "streaming" and about the same number for "single pass" "streaming" so notability or availability of sourcing should not be an issue. —David Eppstein (talk) 20:38, 15 April 2021 (UTC)[reply]
  • Keep. The article needs some more work, but I have added some additional references, more are quite readily available (from searching "one-pass algorithm" or "single-pass algoritm") and it seems fine to me as a stub. jp×g 23:22, 15 April 2021 (UTC)[reply]