TU8G

The TU8G (ТУ8Г) is a Soviet, later Russian diesel locomotive for track gauge 750 mm (2 ft 5 12 in).

TU8G
Kambarka engineering plant, Russia
Type and origin
Power typeDiesel
BuilderKambarka Engineering Works
Build date1988 - today
Specifications
Configuration:
  UICB'B'
Gauge750 mm (2 ft 5 12 in) to
1,067 mm (3 ft 6 in)
Wheel diameter600 mm (23.62 in)
Minimum curve40 m (131.23 ft)
Length9,010 mm (29 ft 6 34 in)
Width2,550 mm (8 ft 4 38 in)
Height3,495 mm (11 ft 5 58 in)
Axle load4 t (3.9 long tons; 4.4 short tons)(?)
Loco weight16 t (15.7 long tons; 17.6 short tons)
Fuel typeDiesel
Prime moverЯМЗ-236М
Engine typeV-shaped
Transmissionmechanical
Performance figures
Maximum speed50 km/h (31 mph)
Power output180 hp
Career
Class RUS - TU8G / (ТУ8Г)
 Belarus - TU8G / (ТУ8Г)
 Ukraine - TU8G / (ТУ8Г)
 Guinea - TU8GE / (ТУ8ГЭ)

History

TU8G-0017, Ukraine

The diesel locomotive TU8G (ТУ8Г) is designed for loading and unloading and also general purpose locomotive for Narrow gauge railways. The TU8G was developed in 1987 - 1988 at the Kambarka Engineering Works to replace the aging locomotive classes TU6D (ТУ6Д). The TU8G was designed to be used on any gauge from 750 mm (2 ft 5 12 in)1,067 mm (3 ft 6 in). The cab is equipped with heat-system, refrigerator, radio-set and air conditioning.[1] TU8G № 0022 - 0027 made on the 1,067 mm (3 ft 6 in) for the Sakhalin Railway.[2]

Additional specifications

  • Carrying capacity of motor-car platform - 29.4 kN (6,600 lbf) (3.0 t or 3.0 long tons or 3.3 short tons)
  • Crane - hydraulic with moving remote control
  • Carrying capacity - 9.8 kN (2,200 lbf) (1.0 t or 0.98 long tons or 1.1 short tons)
  • Angle of rotation (of crane) - 360°
  • Max. boom-out (of crane) - 6.0 m (19.69 ft)
  • Number of seats in the cabin - 6
  • Distance between bogies - 4,000 mm (157.48 in)
  • Base of bogies - 1,400 mm (55.12 in)
gollark: ```nonlocality=# EXPLAIN ANALYZE SELECT url, ts_rank(fts, query), ts_headline(fts::text, query, 'MaxWords=60') AS rank FROM pages, websearch_to_tsquery('bee') query WHERE fts @@ query ORDER BY rank LIMIT 1; QUERY PLAN ------------------------------------------------------------------------------------------------------------------------------------------------- Limit (cost=860.92..860.92 rows=1 width=96) (actual time=8506.425..8506.427 rows=1 loops=1) -> Sort (cost=860.92..861.05 rows=52 width=96) (actual time=8506.423..8506.425 rows=1 loops=1) Sort Key: (ts_headline((pages.fts)::text, query.query, 'MaxWords=60'::text)) Sort Method: top-N heapsort Memory: 25kB -> Nested Loop (cost=688.65..860.66 rows=52 width=96) (actual time=1.362..8505.403 rows=348 loops=1) -> Function Scan on websearch_to_tsquery query (cost=0.25..0.26 rows=1 width=32) (actual time=0.023..0.025 rows=1 loops=1) -> Bitmap Heap Scan on pages (cost=688.40..846.49 rows=52 width=142) (actual time=0.353..1.502 rows=348 loops=1) Recheck Cond: (fts @@ query.query) Heap Blocks: exact=231 -> Bitmap Index Scan on page_search_index (cost=0.00..688.39 rows=52 width=0) (actual time=0.320..0.320 rows=387 loops=1) Index Cond: (fts @@ query.query) Planning Time: 0.190 ms Execution Time: 8506.463 ms(13 rows)```
gollark: It's not a condition, it's an extra row on the output, and I can see exactly what it does via `EXPLAIN ANALYZE`.
gollark: Maybe I need a better full text search backend?!
gollark: This is apioform.
gollark: So it works in about 30ms - perfectly okay - *without* the ts_headline, but takes about 30 seconds *with* it.

See also

References


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