HMS Conqueror (1773)

HMS Conqueror was a 74-gun third rate ship of the line of the Royal Navy, launched on 10 October 1773 at Plymouth.[1]

For other ships with the same name, see HMS Conqueror.

History
Great Britain
Name: HMS Conqueror
Ordered: 12 October 1768
Builder: Plymouth Dockyard
Laid down: October 1769
Launched: 10 October 1773
Fate: Broken up, 1794
General characteristics [1]
Class and type: Royal Oak-class ship of the line[2]
Tons burthen: 1606
Length: 168 ft 6 in (51.36 m) (gundeck)
Beam: 46 ft 9 in (14.25 m)
Depth of hold: 20 ft (6.1 m)
Propulsion: Sails
Sail plan: Full rigged ship
Armament:
  • 74 guns:
  • Gundeck: 28 × 32 pdrs
  • Upper gundeck: 28 × 18 pdrs
  • Quarterdeck: 14 × 9 pdrs
  • Forecastle: 4 × 9 pdrs

She was commanded by Captain George Balfour in the Battle of the Saintes, 1782.[3] Here she was fifth in line in the attack on the French fleet.[4]

She was broken up in 1794.[1]

Citations and notes
  1. Lavery, Ships of the Line vol. 1, p. 180.
  2. Winfield, British Warships.
  3. "Balfour". Dictionary of American Naval Fighting Ships. The Naval Historical Foundation. Retrieved 2 May 2012.
  4. Famous Fighters of the Fleet, Edward Fraser, 1904, p.106
gollark: Basically, if I want to run a search it just goes `SELECT * FROM page_tokens WHERE token = 'one token in search query'` or something like that, and it now has a list of pages with the right token, and SQLite can execute this query relatively fast.
gollark: I mean, as far as I can tell there isn't really a faster *and* more storage-efficient way to do search than the inverted-index page_tokens thing.
gollark: ```sqlCREATE TABLE crawl_queue ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, lockTime INTEGER, added INTEGER NOT NULL, referrer TEXT);CREATE TABLE pages ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, rawContent BLOB NOT NULL, rawFormat TEXT NOT NULL, textContent TEXT NOT NULL, updated INTEGER NOT NULL);CREATE TABLE page_tokens ( id INTEGER PRIMARY KEY, page INTEGER NOT NULL REFERENCES pages(id), token TEXT NOT NULL, weight REAL NOT NULL);CREATE TABLE links ( id INTEGER PRIMARY KEY, toURL TEXT NOT NULL, fromURL TEXT NOT NULL, lastSeen INTEGER NOT NULL, UNIQUE (toURL, fromURL))```Here is the database.
gollark: To be fair, the text content field isn't that necessary, as for search it uses the page_tokens table anyway and it can be rebuilt from the HTML if I need it.
gollark: The frequency of every word *must* be stored for quick (O(log n) time or something) search, the raw HTML or at least might be needed if I come up with a better way to weight frequency or something, the links are useful for (future) better search ranking algorithms.

References
  • Lavery, Brian (2003) The Ship of the Line - Volume 1: The development of the battlefleet 1650-1850. Conway Maritime Press. ISBN 0-85177-252-8.
  • Winfield, Rif (2007) British Warships of the Age of Sail 1714-1792: Design, Construction, Careers and Fates. Seaforth. ISBN 1-86176-295-X.

This article incorporates text from the public domain Dictionary of American Naval Fighting Ships.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.