text:
Megavoltage X-rays

Megavoltage X-rays are produced by linear accelerators ("linacs") operating at voltages in excess of 1000 kV (1 MV) range, and therefore have an energy in the MeV range. The voltage in this case refers to the voltage used to accelerate electrons in the linear accelerator and indicates the maximum possible energy of the photons which are subsequently produced. They are used in medicine in external beam radiotherapy to treat neoplasms, cancer and tumors. Beams with a voltage range of 4-25 MV are used to treat deeply buried cancers because radiation oncologists find that they penetrate well to deep sites within the body. Lower energy x-rays, called orthovoltage X-rays, are used to treat cancers closer to the surface.

Megavoltage x-rays are preferred for the treatment of deep lying tumours as they are attenuated less than lower energy photons, and will penetrate further, with a lower skin dose. Megavoltage X-rays also have lower relative biological effectiveness than orthovoltage x-rays. These properties help to make megavoltage x-rays the most common beam energies typically used for radiotherapy in modern techniques such as IMRT.

History
The Use of megavoltage x-rays for treatment first became widespread with the use of Cobalt-60 machines in the 1950s. However prior to this other devices had been capable of producing megavoltage radiation, including the 1930s Van de Graaff generator and betatron.

title: Megavoltage X-rays


text:
Saab 35 Draken

The Saab 35 Draken (The Kite, ambiguous with The Dragon) is a Swedish fighter-interceptor developed and manufactured by Svenska Aeroplan Aktiebolaget (SAAB) between 1955 and 1974. Development of the Saab 35 Draken started in 1948 as the Swedish air force future replacement for the then also in development Saab 29 Tunnan dayfighter and Saab 32B Lansen night fighter. It featured an innovative but unproven double delta wing, which led to the creation of a sub-scale test aircraft, the Saab 210, which was produced and flown to test this previously-unexplored aerodynamic feature. The full-scale production version entered service with frontline squadrons of the Swedish Air Force on 8 March 1960. It was produced in several variants and types, most commonly as a fighter-interceptor.

The Saab 35 Draken is known for, among other things, its many "firsts" within aviation. It was the first Western European-built combat aircraft with true supersonic capability to enter service and the first fully supersonic aircraft to be deployed in Western Europe. Designwise it was one of, if not the first, combat aircraft designed with double delta wings, being drawn up by early 1950. The unconventional wing design also had the side effect of making it the first known aircraft to be capable of and perform the Cobra maneuver. It was also one of the first Western-European-built aircraft to exceed Mach 2 in level flight, reaching it on 14 January 1960.

The Draken functioned as an effective supersonic fighter aircraft of the Cold War period, although it was never used in conflict. Even though the type was designed and intended as an interceptor, it was considered to be a very capable dogfighter for the era. In Swedish service, it underwent several upgrades, the ultimate of these being the J 35J model. By the mid-1980s, the SAF's Drakens had largely been replaced by the more advanced JA 37 Viggen fighter, while the introduction of the more capable Saab JAS 39 Gripen fighter was expected in service within a decade, although delayed. As a consequence of cutbacks and high maintenance costs, the SAF opted to retire the Draken during December 1999. The type was also exported to the air forces of Austria, Denmark and Finland. Danish aircraft have been exported, post-service, to the United States where they have seen use as training aircraft for test pilots.

Naming
The Swedish word "Draken" has a double meaning, translating either as “The Dragon” or “The Kite”. It is said that the name was derived from the appearance of the prototype, like a paper kite, when seen from above.

The number "35" comes from the aircraft's Swedish Air Force-designation: "flygplan 35" (fpl 35), meaning “aeroplane 35”. Depending on the given role, the aircraft received a prefix to indicate its type, the most common being "J 35" to indicate "jaktflygplan" (pursuit-aircraft), the Swedish term for fighter aircraft.

Development
As jet fighter technology developed after World War II, Sweden foresaw a need for a supersonic fighter that could intercept bombers at high altitude as well as engage other fighters. During September 1949, the Swedish Air Force, via the Swedish Defence Materiel Administration, released its recently formulated requirement for a cutting-edge interceptor aircraft that was envisioned to be capable of attacking hostile bomber aircraft in the transonic speed range. The original requirement specified a top speed of Mach 1.4 to 1.5, but this was revised upwards in 1956 to Mach 1.7 to 1.8 and then again in 1959 to Mach 2.0.

It had to be flown by a single pilot, yet be capable of conducting combat operations under all weather conditions, night or day, while operating from relatively austere airstrips, carrying all equipment needed to neutralize modern jet bombers. Although other interceptors like the US Air Force's F-104 Starfighter were being conceived at the time, this fighter would have to undertake a role unique to Sweden; the ability to operate from reinforced public roads, which were to be used as part of wartime airbases. The aircraft also needed to be refueled and rearmed in no more than ten minutes by conscripts with minimal training.

SAAB commenced work on producing an aircraft to meet these requirements. Preliminary studies found that the majority of critical issues posed by these requirements could be met with a delta wing configuration. However, to obtain an aerodynamically desirable location, the forward fuselage needed to be extended, making the aircraft too heavy. The optimum solution was thought to be a double delta wing. However, this wing configuration was new and untested, so SAAB's design staff, headed by aircraft engineer Erik Bratt, and a team of more than 500 technicians, constructed a small test aircraft to explore the behaviour of the new wing.

A sub-scale test aircraft constructed in Sweden, the Saab 210 (formally flygplan 210, "aircraft 210"), unofficially nicknamed "Lilldraken" (the little dragon), comprised a test of the double delta wing, and performed its first flight on 21 January 1952. Results produced by these test flights led to an order for three full-size Draken prototypes. On 25 October 1955, the first of these prototypes, not fitted with an afterburner, conducted its maiden flight. According to aircraft publication Flight International, an atypically intensive flight test program was conducted to define and test the type's exceptional speed, range, and complicated systems. The second prototype, equipped with an afterburner, unintentionally broke the sound barrier during its first flight while climbing.

During 1956, the first operational version of the Draken, designated as the J 35A, was ordered into quantity production and the first production aircraft flew for the first time on February 15, 1958. Mach 2 was reached on January 14, 1960 with test pilot Erik Dahlström at the controls of the J 35B prototype. The engine used was a slightly modified British made Rolls-Royce Avon Mk.48A (Swedish designation RM6BE), engine number 3459.

Design
The Saab 35 Draken is a fighter aircraft, equipped with a distinctive double delta wing. According to Flight International, it is difficult to differentiate between the fuselage and the wing. The design anticipates what would later be known as a ‘blended wing-body’. The fuselage has a circular section, and the inboard portion of the wing is a large-chord surface which extended almost to the engine intakes. It was possible to dispense with a tailplane, resulting in a clean, simple overall design. The leading edge of the inner wing was swept back 80° for high-speed performance, and the outer wing 60° for good performance at low speeds.

The cockpit of the Draken featured mostly Swedish-sourced instrumentation. Successive models introduced various improvements to the cockpit fittings, such as the revised canopy and new avionics. For export customers, the Draken was outfitted with a Ferranti-built Airpass II fire-control radar, which was effective for acquiring various air-to-air or air-to-surface targets, along with a ground-mapping mode working in conjunction with the aircraft's navigation systems. Typically, two separate radio units would be installed, along with a high-speed data link and two navigation systems. As there is no natural feedback placed upon the stick, artificial forces were generated by a q-feel system. The Draken was also fitted with a three-axis autopilot. The fuselage of the Draken consisted of two sections, front and rear, joined by bolts. The forward section, which was integral with the intake ducts and neighbouring wing structure, accommodates the fire-control radar, cockpit, nose undercarriage, integral fuel tanks and various systems. The rear portion, which was manufactured as a single piece alongside the rest of the inner wing, contained the engine and afterburner, bag-type fuel tanks, armament, main landing gear, and other systems. The flight control surfaces consisted of a rudder, along with inboard and outboard elevons, the outer sections being fitted with mass-balance weights. Each surface was operated by a tandem hydraulic jack, which was connected to separate circuits. As a weight-saving measure, the hydraulic systems would operate at a line pressure of 210 kp/cm2 (20.6 MPa), which would be greater than double the pressure used in the earlier Saab 29 Tunnan.

Propulsion was provided by a single Svenska Flygmotor RM6B/C turbojet engine, a licence-built model of the Rolls-Royce Avon 200/300 engine (also known as Avon Mk.48A and Mk.60). A ram turbine, positioned under the aircraft's nose, provided emergency power, while the engine also featured a built-in emergency starter unit. In order to reduce its landing distance when required, the Draken was equipped with a drogue parachute. The principal armament was carried externally, up to four AIM-9 Sidewinder air-to-air missiles were carried on hard points beneath the wings and fuselage; alternative payloads include a variety of bombs and rockets, along with provisions for the installation of a pair of 30 mm cannons, located within each of the inboard wing panels. In place of the cannons, additional fuel tanks could be fitted in the same space. For aerial reconnaissance missions, a variety of camera pods could be carried underneath the fuselage.

Instability
Due to a lack of knowledge regarding the then historically unproven design of the J 35's tailless double delta wing configuration, the plane encountered problems at the start of its service life. The unstable design of the double delta wing made it difficult to land early versions of the J 35 as they had to be manually stabilized during landing. The design also allowed the plane to enter a "super stall"; which can be described as an uncontrollable stall affecting aircraft with specific wing configurations when experiencing high alpha numbers. Due to this, J 35 pilots were trained to prevent super stalls, and this training led to the development of the cobra maneuver. The cobra is performed by entering into a controlled super stall state, gaining high alpha and then quickly negating the angle of attack to counter the stall. This forces the airframe to act as an air brake for a few seconds, which rapidly reduces the speed.

The Swedish Air Force is the first air force to have discovered and developed the cobra maneuver. The Swedish named it kort parad (short parry) after the fencing maneuver of the same name, in English known as ‘beat parry’. Initially it was used during training to teach pilots how to counter super stalls, however it also saw secondary use as a combat maneuver which would cause a pursuing enemy fighter overshoot, allowing the pilot to riposte.

Operational history
At the end of 1959, deliveries of the J 35A Draken commenced to the SAF, the first unit to receive the type being fighter wing F13, stationed at Norrköping. During March 1960, the Drakens of unit F13 participated in a three-day long exercise, flying by night and day while operating under a state of "highest readiness" throughout. According to Flight International, the introduction to service of the J 35A was "very smooth", and that the scramble and turn-round times had been found to be "most satisfactory". By the end of 1960, multiple wings had been equipped with the Draken and had attained operational status.

Although the J 35 Draken was designed as a high altitude interceptor and not as a dog fighter, it proved to have a good quick-turn capability and high speed at all altitudes, making it a very capable fighter plane. The early models were intended purely to perform the air defense mission. However, in order to assist pilots in converting to the type, Saab produced a small number of twin-seat J 35C trainer aircraft, the first of which having been completed during December 1959. During 1959, an improved air defence fighter model, designated as the J 35B, was developed, which featured improved performance and equipment over the J 35A. Amongst other things, it was powered by an improved engine fitted with an enlarged afterburner, a redesigned rear fuselage, a new Saab-built S-7 collision-course gunsight and fire-control radar, and integration with Sweden's STRIL 60 air defence control network.

A total of 651 Drakens were manufactured by Saab. Sweden's fleet of Drakens comprised a total of six different versions, while two additional models of the Draken were offered to prospective export customers. The final model of the Draken to be produced was the J 35F, which was also the final version to remain in Swedish service, then modified to J 35J standard. Its export customers included Denmark and Finland. In May 1985, the Austrian Air Force purchased 24 J 35Ds, which had been refurbished by Saab.

The J 35 Draken design underwent several upgrades. The last of these was the J 35J version, which was produced during the late 1980s; by this point, the Draken had been almost entirely replaced by the Saab 37 Viggen in SAF service. The Draken J 35J was effectively a service life extension programme, which had been initiated as a result of the impending delivery of the new Saab JAS 39 Gripen having suffered several delays. The extension program was intended to keep the Draken flying into the 2000s but, as a consequence of budgetary cutbacks and high maintenance costs being incurred with the type, the Draken was phased out of Swedish service in December 1999, although the aircraft has since remained operational in limited numbers within both military and civilian roles.

All Drakens functioned as interceptors with limited air-to-ground capability; the sole exception to this rule was the Danish Drakens, which functioned as strike aircraft and were capable of carrying a mixture of AGM-12 Bullpup air-to-ground missiles, electronic countermeasures, and increased internal and external fuel storage. The Danish Drakens were the heaviest of the series to have flown. During 1993, the last of the Danish J 35 fleet were retired.

During the 1990s, Finland updated its 35XS fleet with new avionics, cockpit displays, navigational/attack systems, and electronic countermeasures; these were finally retired in 2000 to be replaced by F/A-18 Hornets.

Austria was the last country to have the Draken in active military service. The first refurbished Draken J-35Ö's was handed over to the Austrian Air Force by 1987. These Drakens was initially been armed solely with two 30mm air-to-air cannons, which have proved to be inadequate. This was due to a "missile ban" which stemmed from the Austrian State Treaty of 1955. By 1991, with the start of the Yugoslavian Civil War to its neighbor down south. There were numerous airplace violations along the southern border caused by the Yugoslavian Federal Army. After the fall of the Iron Curtain, Austria declared the relevant article to be obsolete. Thus in 1993, a contract for the purchase of AIM-9 Sidewinder was signed with the Swedish Air Force. They were followed from 1998 by a number of improved AIM-9P5's from Loral Corporation In 2005, these Drakens were retired, having been replaced by former Swiss Air Force F-5 Tiger IIs, while waiting for new Eurofighter Typhoons to take their place in the long term.

In the United States, the National Test Pilot School (NTPS) operated six Drakens that were formerly in Danish service. They were retired in 2009.

List of prototypes and test aircraft
Several prototypes and test aircraft of the Saab 35 have existed over the years. Some have been prototypes for new variants while others have been test platforms for other aircraft.

 * Fpl 210 "Lilldraken":
 * Flygplan 210 (fpl 210; “aircraft 210”), also known as Lilldraken (Little Kite), was a scaled-down proof of concept experimental aircraft to evaluate the double delta wing configuration; though not strictly a Draken variant, it is included here as the first in a series of prototypes.

 * Existed in two stages:
 * Fpl 210A – air intakes on the nose
 * Fpl 210B – air intakes moved to the sides of the fuselage

 * Fpl 35-1 "Stordraken":Fpl 35-1, also known as Stordraken (Big Kite), was the first original full-scale prototype. It featured an original Rolls-Royce Avon Mk.21 (RM5A) engine with no afterburner and was unarmed.

 * Fpl 35-2:Fpl 35-2 was the second full-scale prototype. It was similar to the 35-1 and was unarmed. It was used for testing ejection seats among other things. Tests with a tailhook were also performed at some point.

 * Fpl 35-3:Fpl 35-3 was the third prototype and was the first prototype with cannon armament.

 * Fpl 35-4:Fpl 35-4 was the series prototype for the Saab 35A.

 * Fpl 35-5:Fpl 35-5 was the first aircraft built to Saab 35A-series specifications. It featured an original Rolls-Royce Avon Mk.48A (RM6BE) engine and had the same afterburner and tail as the J 35A1 (Adam short) variant. Later it was modified to Saab 35D standard and acted as the Saab 35H demonstrator during the Swiss trials.

 * Fpl 35-6:Fpl 35-6 was the series prototype for the Saab 35D. It later also served as the prototype for the Saab 35F.

 * Fpl 35-7:Fpl 35-7 was a test aircraft for the Saab 35F-series. It was outfitted with special recording equipment.

 * Fpl 35-8:Fpl 35-8 was a test aircraft for the Saab 35F-series but with the earlier non-bird-proof cabin. It was used for rb 28 missile tests and later for testing different radios.

 * Fpl 35-9:Fpl 35-9 was a test aircraft for the Saab 35F-series but with the earlier non-bird-proof cabin. It was used for among other things ground tests.

 * Fpl 35-10:Fpl 35-10 was a test aircraft based on the Saab 35B-series but it was originally a J 35A series aircraft. The aircraft was modified with the outer wings of the Saab 37 Viggen strike fighter later in its service life for trials with the RB 05 (then RB 305) air-to-ground missile.

 * Fpl 35-11:Fpl 35-11 was a test aircraft based on the Saab 35B-series. It was used for several Saab 35F trials featuring rb 27 and rb 28 missile mockups. Some electronics for the Saab 35D version were also tested. Its final purpose was to trial electronic countermeasures for the Saab 37 Viggen strike fighter.

 * Fpl 35-12:Fpl 35-12 was similar to the 35-11 and was used to trial different components for the Saab 35D and Saab 35F series.

 * Fpl 35-13:Fpl 35-13 was a test aircraft for the Saab 35D-series. From 1967 it was used for testing several types of countermeasures for the Saab 37 Viggen strike fighter.

Saab 35A (Adam)
Fighter version designated J 35A (Adam). 90 aircraft (35001–35090), including test aircraft, delivered between March 1960 and December 1961. 29 J 35A were ordered on August 24, 1956, with a further 60 J 35A being ordered on February 7, 1958. The initial 40 aircraft delivered in 1960 were delivered without a radar and gunsight. This was corrected in 1961 and 65 Adam were equipped with radar and gunsight in the end. 25 Adam were converted to Saab 35C unarmed two-seat trainers between April 1961 to August 1962.

The Saab 35A was fitted with a license produced Rolls-Royce Avon Mk.48A (Avon 200 series) engine (Swedish designation RM6BS) from SFA (today Volvo Aero) fitted with a Swedish developed afterburner. Two types of afterburners came to be used on the J 35A, resulting in two primary variants:
 * J 35A1 (J 35 A:1) / J 35A kort (short) – initial version with a short afterburner (EBK65) and short tail. Nicknamed Adam kort (Adam short). 65 built.
 * J 35A2 (J 35 A:2) / J 35A long (long) – later version with lengthened tail section to house a new afterburner (EBK66) for additional thrust. Nicknamed Adam lång (Adam long). The longer tail cone unexpectedly reduced drag, but did force the installation of a retractable tail-wheel. 25 built.

The radar on the J 35As was a French Cyrano RA 423 radar from Thompson-CSF (Swedish designation PS-02/A) as the originally planned Swedish radar (PS-03) from LME hadn't been developed in time. The gunsight was an advanced gyro gunsight developed by Saab for both the Saab 32B and Saab 35A called S-6 (later named S-6B). It used data from the aircraft's yaw and pitch axis, as well as other sources to give accurate aim for the weaponry. Range data could be taken from the radar or set manually by the pilot.

Weaponry on the J 35A consisted of two fixed 30 mm ADEN cannons (Swedish designation 30 mm akan m/55) in the wings with 90 rounds per gun. For external ordnance the J 35A had nine hardpoints, eight under the wings and one on the belly. Six of the wing hardpoints were for mounting 13.5 cm srak m/56 high-explosive air-to-ground rockets. The other two wing hardpoints were for mounting AIM-9B Sidewinder air-to-air missiles (Swedish designation rb 24). Rockets and missiles could not be mounted simultaneously on the wings. The belly hardpoint could mount either two rb 24 Sidewinders or a 530 liter drop tank.

Saab 35B (Bertil)
Fighter version designated J 35B (Bertil). 73 aircraft (35201–35273), including test aircraft, were built and delivered between February 1962 and March 1963. The J 35B was initially planned to be designated J 35B1, before being renamed to just J 35B in Januari 1960. 72 J 35B1 were ordered on February 28, 1958. 25 of these were to receive the 25 Saab 35A front sections left over from the Saab 35C conversion, but modified to Saab 35B standard.

Due to manufacturing issues, delivery delays occurred for some J 35B subsystems, resulting in that the J 35B initially being delivered with only parts of the planned avionics installed. This resulted in there being two primary sub-variants of the J 35B historically:
 * J 35B′ – initial day fighter version of the J 35B. It lacked a radar and featured old Ferranti gyro gunsights taken from scrapped Saab J 29A and B fighters called Reflexsikte 4E/35. These aircraft were designated J 35B′ (i.e. prime, prim) to indicate that they were not completed vehicles. However some sources calls these aircraft J 35B1 instead of J 35B′. Even though it lacked a radar it was fully armed with cannons, rockets and missiles. It was also compatible with STRIL 60. 72 built between February 1962 and March 1963.
 * J 35B – later all-weather fighter version of the J 35B. Featured a PS-03/A radar and S-7A-2 radar gunsight, as well as the rest of the initially planned equipment and avionics. 69 aircraft converted from the remaining J 35B´(prim) between 1964 and 1966. Aircraft were sent to Saab for conversion between 1964 and 1965 and re-delivered between January 1965 to June 1966.

The base aircraft of the Saab 35B was identical to the J 35A2 and featured the same engine and afterburner, the RM6BS and EBK66. Distinctive from the J 35A, however, was that the J 35B was fully integrated into the Swedish STRIL 60 system; a combat guidance and air surveillance system. As part of STRIL 60 it was also the first Swedish aircraft fitted with a 'control data system' (styrdatasystem) which allowed ground-control to send digital orders to the aircraft. These orders were then stored in the aircraft's computers so the pilot could read the order several times and didn't have to memorize the content.

The radar on the J 35B was a Swedish developed radar from LME designated PS-03/A. It was superior and more advanced compared to the French PS-02 used on the J 35A. The gunsight was an advanced radar gunsight developed by Saab for both the J 35B and J 35D called S-7A-2. It used data from, among others, the aircraft's yaw and pitch axis, as well as the PS-03/A radar. It was specifically designed for head-on attacks with air-to-air rockets, something the J 35A did not have access too. Weaponry on the J 35B was for the most part equivalent to the J 35A, but the fixed 30 mm akan m/55 ADEN cannons in the wings had 100 rounds per gun and the aircraft had gained the ability to use 75 mm srak m/57 air-to-air rockets. The rockets were fired from Rakkaps m/57 rocket pods mounted in pairs on the Sidewinder belly pylon, each holding 19 rockets.

Saab 35C (Cesar)
Twin-seat trainer version designated SK 35C (Cesar). 25 aircraft (35801–35825), converted from J 35A1s (Adam kort) between April 1961 to August 1962 by rebuilding the front section of the aircraft, not including the prototype (35800), which flew on December 30, 1959 and was privately owned by Saab. The SK 35C was initially planned to be designated J 35C, before being renamed to "SK 35C" in January 1960. The twenty five SK 35C (J 35C) front sections were ordered on August 24, 1956.

The Cesar-version lacked armament but the minor modification meant that the aircraft could easily be converted back to J 35A standard if necessary. Interestingly however, the prototype (35800) was used by Saab to trial the RB 05 air-to-ground missile.

Saab 35D (David)
Fighter version designated J 35D (David). 120 aircraft (35274–35393) delivered between May 1963 and April 1965 in 3 series. The J 35D was initially planned to be designated J 35B2, before being renamed to J 35D in January 1960. 62 J 35B2 were ordered on November 15, 1958, with a further 60 aircraft, meant to be converted to S 35B2 (S 35E) reconnaissance aircraft, being planned to be ordered in November 1960. In the end, only 30 Davids (all of series 1) was converted to S 35E standard, having first served as a fighter aircraft between May 1963 and January 1964.

Due to manufacturing issues, delivery delays occurred for some J 35D subsystems, resulting in that the two initial J 35D series being delivered with only parts of the planned avionics installed. Series 3, however, was delivered with complete avionics, resulting in there being two primary sub-variants of the J 35D initially:
 * J 35D1 – initial day fighter version of the J 35D. It lacked a radar and featured old Ferranti gyro gunsights taken from scrapped Saab J 29A and B fighters called Reflexsikte 4E/35. Even though it lacked a radar it was fully armed with cannons, rockets and missiles. It was also compatible with STRIL 60. 30 aircraft delivered as series 1 between May 1963 to January 1964, but quickly put aside for S 35E conversion and 24 aircraft delivered as series 2 between January 1964 to May 1964.
 * J 35D2 – later all-weather fighter version of the J 35D. Featured a PS-03/A radar and S-7A-2 radar gunsight, as well as the rest of the initially planned equipment and avionics. 66 aircraft delivered as series 3 between June 1964 to May 1965. Remaining J 35D1 from series 2 were modified to J 35D2 standard throughout 1967 to 1968 by CVV Hässlö (Centrala Flygverkstaden Västerås) and respective air units, after which, the D1 and D2 suffixes were dropped in favour of just D.

The Saab 35D base aircraft differed quite a lot compared to previous variants. For one, it was fitted with the much stronger Rolls-Royce Avon Mk.60 (Avon 300 series) engine (Swedish designation RM6CS), which was license produced by SFA (today Volvo Aero) and fitted with a Swedish developed afterburner (EBK67), which could deliver 77.3 kN of thrust when using its afterburner. Secondly, the David featured increased internal fuel capacity for longer range. It also featured two hardpoints on the belly to be able to mount two 500 liter external drop tanks for even longer range missions (compared to one 530 liter drop tank for the 35A, B and C). Despite having more fuel than its predecessors, the David was the fastest Draken version, capable of accelerating until out of fuel.

In terms of armament and avionics, the J 35D was almost identical to the J 35B. It was fully integrated into the Swedish STRIL 60 system and was also fitted with a 'control data system', allowing the aircraft to receive digital orders from ground control. It also featured the same PS-03/A radar and S-7A-2 radar gunsight as the J 35B. Weaponry on the J 35D was at least initially equivalent to the J 35B. It had two 30 mm akan m/55 ADEN cannons in the wings with 100 rounds per gun, 4 inward hardpoints, 1 under each wing and 2 on the belly, for external air-to-air ordnance, as well as 6 outer hardpoints for air-to-ground rockets. In 1977, however, a new type of air-to-ground rocket became available to the J 35D, the 14.5 cm psrak m49/56 high-explosive anti-tank rocket and in 1978, a new type of air-to-air missile, the AIM-9J Sidewinder (Swedish designation rb 24J), later modified with an Ericsson laser proximity fuze, making it equivelant to the AIM-9P-3. Something noteworthy is that the J 35D was the last Swedish Draken variant fitted with 2 guns.

Saab 35E (Erik)
Reconnaissance version of the Saab 35D designated S 35E (Erik). 60 aircraft (35901–35960), including test aircraft, built between 1963 and 1968 in 2 series. The S 35E was initially planned to be designated S 35B2, before being renamed to S 35E in January 1960. In 1958 the SAF planned to order 60 J 35B2 (J 35D) fighters in November 1960, which were intended to be converted to S 35B2 (S 35E) reconnaissance aircraft at a later date. In the end, 30 S 35E were produced as new aircraft (35902–35931) and delivered between July 1965 to May 1966 as series 1, while 28 S 35E were converted from J 35D (35932–35959) and delivered between October 1966 to January 1968 as series 2. Two more aircraft, S 35E (35901) and S 35E (35960) were also converted from Davids but never delivered to the SAF.

The base aircraft of the Saab 35E was almost identical to the J 35D and featured the same engine and afterburner, the RM6CS and EBK67. It differed however in that it had no armament or radar, as to make space for 9 Vinten cameras, five in the nose and four in the fuselage, some mounted upright, others mounted obliquely. The aircraft was however fitted with a radar warning receiver and could mount a countermeasure pod named Kapsel KB with chaff and flare dispensers under the wings to increase its survivability. The aircraft had 4 primary hardpoints in total for external ordnance, 1 under each wing and 2 on the belly. For long range missions it was possible to mount up to 4 drop tanks on these hardpoints. For night missions it could carry an active infrared reconnaissance system of EG&G design in a pod fitted to a belly hardpoint.

Saab 35F (Filip)
Fighter version designated J 35F (Filip). Delivered between 1965 and 1972, total production: 230. This variant had improved electronics and avionics, e.g. integrated radar, aim and missile systems, introducing the capability to use semi-active radar homing (SARH) and infrared homing (IR) versions of the Hughes Falcon missile, rb 27 and rb 28 respectively, originally intended for the J 35D. To make space for more avionics, the left cannon was removed, with ammunition increased to 120 rounds for the right cannon as compensation.

The J 35F existed in two primary variants:
 * J 35F1 – initial version without an infrared search and track sensor under the nose.
 * J 35F2 – later version with a Hughes N71 infrared search and track sensor under the nose (IR-spanare 71N). This was a change in the production line from the no. 35501 airframe. The Hawé mods I & II were carried out on the P/S-01/011 radar sets in the early 1980s to improve resistance to ECM.

Saab 35G (Gustav)
Attacker version designated J 35G (Gustav). 70 aircraft suggested to be converted from J 35Ds but the project was cancelled early on.

The Gustaf version was specifically going to be able to carry the Saab RB 05 air-to-ground missile.

Saab 35J (Johan)
Fighter version designated J 35J (Johan). In 1985 the Swedish government decided to modify 67 J 35F2s to the J 35J standard. The aircraft received a longer lifespan, modernized electronics, a modernized cannon, two additional hardpoints under the intakes for extra AIM-9 Sidewinder pylons (balk G, "pylon G") and increased external fuel capacity. The modification took place between 1987 and 1991. The final operational J 35J flew for the last time in 1999.

Proposed modifications
Before it was decided to develop the JAS 39 Gripen in the 1970s, studies were undertaken on modification for low flight hour J 35F airframes.
 * 35 MOD Level 1b – Essentially the aircraft that became the J 35J.
 * 35 MOD Level 4 – The most ambitious modification in the program. The proposed modifications were new outer wing, additional weapon stations, RBS 15 capability, the addition of canards by the air intakes for increased maneuverability and maximum take-off weight increased to 15 000 kg.

Export variants
Export attempts of the Saab 35 started even before the aircraft had finished development in Sweden. During the late 1950s, Saab would offer the aircraft to, among others, the West German Air Force, the Royal Australian Air Force and the Swiss Air Force.

Saab 35H (Helvetia)
Saab 35H (Helge) was a proposed export version of the J 35D for the Swiss Air Force in 1958. H stands for Helvetia, Switzerland in Latin. One demonstrator built from the Fpl 35-5 prototype. Competed and lost out against the Dassault Mirage IIIS. None sold or delivered. The trial and procurement of the Mirage III was however faulty, leading to a scandal after severe budget overruns. The Swiss Air Force commander, the chief of the general staff and the minister of defence were forced to resign as a result. During trials the Saab 35H demonstrated a climb rate 20-40% superior to the Mirage III and had a 35% shorter take-off run.

Saab 35X (Export)
Saab 35X (Xerxes) was a series of export variants of the J 35D and J 35F that Saab offered throughout the 1960s, 1970s and 1980s. X stands for export. The Saab 35X were offered to Belgium in 1967, Argentina in 1968, Venezuela in 1969, Chile in 1971, Singapore in 1975, Tunisia in 1976 and Malaysia in 1980. However, none of the aforementioned countries purchased the Saab 35 in the end.

Saab 35XD (Export Danmark)
Saab 35XD (Xerxes David) was an export fighter bomber version of the Saab 35F for the Royal Danish Air Force. X stands for export and D for Denmark. It competed and won against the Mirage III and the Northrop F-5 in 1968.

Three variants of the Saab 35XD were produced, all with similar ordnance capabilities:
 * F-35 – single-seat attack version. 20 built
 * RF-35 – single-seat reconnaissance version with a camera nose similar to the Saab 35E. Could not equip the AGM-12B Bullup. 20 built
 * TF-35 – two-seat trainer aircraft with only one cannon. 11 built (6 initially, 5 later)

Denmark wanted to acquire a third and fourth Saab 35XD squadron (23-46 aircraft) following the initial purchase and prices were handed over August 14, 1970. Negotiations continued during the spring of 1971 and an offer was made on May 1, 1971. The Danish interest focused on a radar by LME called SAX 500, a new navigation system and an effective ordnance amining system, such as the Saab BT-9. However, due to cutbacks of the Danish Air Force made during he winter 1970/1971 (from 7 squadrons to 4) it was not possible to acquire these aircraft.

Following the cancellation of more Danish 35XD aircraft, Saab offered the Danish Air Force 2 low-price Draken ground attack variants based on the Saab 35F in 1971:
 * Saab 35FD – single-seat attack version for Denmark based on the Saab 35F. The suffix FD stands for F version, Denmark. Unknown differences to the HÖG variant below.
 * Saab 35FD HÖG – single-seat attack version for Denmark based on the Saab 35F. The suffix HÖG is Swedish for High. This version was planned to be fitted with a Weapon Delivery and Navigation System (WDNS).

The Saab 35FD project was cancelled in October 1971 and no aircraft were acquired.

The Saab 35XD was heavily modified to make it into a fighter bomber aircraft; compared to the Swedish versions the outer wings where completely redesigned and the aircraft featured 9 hardpoints in total. It could carry a wide array of NATO ordnance, such as 10,000 lb of NATO bombs, but also Mighty Mouse rockets and AGM-12B Bullpup missiles. For air defence it featured two 30 mm ADEN cannons and could also mount two AIM-9B Sidewinders (later AIM-9N2s) on the utmost hardpoints. It lacked a radar and had a counterweight in the nose instead. The Saab 35XD was however fitted with a ballistic computer from Saab called BT-9R. It worked with both bombs and rockets and even allowed for toss bombing.

During the 1970s the Danish Drakens received new altimeters, US ALR-45 radar warning receivers (later upgraded to ALR-65) and chaff and flare dispensers in their tail cones. During the 1980s the Danish Drakens got an upgrade called WDNS (Weapon Delivery and Navigation System). This upgrade most notably included a Marconi 900 Series HUD and a Ferranti LRMTS (laser rangefinder and marked target seeker) which required a new nose to be installed on the F-35 and TF-35. This nose was the same as the one used on the RF-35 but lacked camera windows on the side. Electronic warfare capability was also improved as the Danish Drakens were fitted with ALR-69 radar warning receivers (with six antennas on the vertical fin, two on each wingtip and two under the nose) and the ability to carry ALQ-162 jammer pods under the wingtips. The last upgrade was completed in 1986 and updated the systems for weapon aiming and navigation accuracy to a similar capacity to those of the Danish Air Force's General Dynamics F-16 Fighting Falcons. Somewhere during its service life the Danish Drakens also lost their ability to mount AGM-12B Bullpups.

Saab 35XS (Export Suomi)
Saab 35XS (Xerxes Sigurd) was an export variant of the Saab 35F interceptor for the Finnish Air Force. X stands for export and S stands for Suomi (Finland in Finnish). The Saab 35XS was sold as part of larger Finnish-Swedish collaboration program to provide the Finnish Air Force with Saab 35 aircraft, starting from 1970. Sweden would provide the Finnish Air Force with second hand J 35F1s, J 35Bs and SK 35Cs, with the Saab 35XS being produced by Saab in Sweden as kits to be assembled under licence by Valmet in Finland. Valmet also got a license to produce spare parts.

The Finnish Air Force gave the Saab 35 the type designation DK (from Draken), although for practical use they reused the Swedish designations, but with the prefixes omitted and with an S added at the end (35BS, 35CS, 35FS), with the exception of the Saab 35XS, which was simply named 35S. On rare occasions the DK designation received a third letter to indicate model (DKS for "35S", etc). As part of the Saab 35-adoption, Finland also bought Swedish produced Falcon missiles, rb 27 (Hughes HM-55) and rb 28 (Hughes HM-58). These were designated 7S och 8S respectively.

The Finnish Air Force received the following Saab 35 variants:
 * DKB / 35BS – ex-Swedish J 35B interceptors sold to Finland. 8 sold and used as advanced trainers, with the exception of one which was used for schooling mechanics. Flew without missiles.
 * DKC / 35CS – ex-Swedish SK 35C two-seat trainers sold to Finland. 5 sold and used as trainers.
 * DKF / 35FS – ex-Swedish J 35F1 interceptors sold to Finland. 24 sold and used as fighters.
 * DKS / 35S – dedicated export version of the Saab 35F for Finland. 12 copies built by Saab and assembled under licence by Valmet in Finland.

The initial delivered second hand Saab 35s entered service with the Finnish Air Force in 1972, with the first Saab 35XS assembled by Valmet – DK-201 – being completed on March 12, 1974. The initial flight trials of the Saab 35XS was flown by Swedish Saab test pilot KG Liljeqvist.

Unique among Saab 35s, the Finnish DKS and DKF were at times outfitted with Soviet R-13M missiles. By the mid 1980s, the DKF and DKS were upgraded with the same extra pylons as the Swedish J 35J. By 1993 the DKS also received countermeasures by installation of two Saab BOY 402 dispensers, capable of launching flares, chaff and expendable active decoys (EAD).

Saab 35XV (Export Venezuela)
Saab 35XV (Xerxes Viktor) was an export variant of the J 35D that Saab offered to Venezuela in 1971. X stands for export and V for Venezuela. Venezuela had shown interest for the Saab 35 since 1966 and in 1971 the Draken was test flown by Venezuela against the French Dassault Mirage III and British English Electric Lightning.

On April 23, 1971, the Venezuelan Air Force made an offer for 3 Saab 35 variants:
 * Saab 35G1 – single-seat fighter version equal to the Saab 35F; 6 aircraft in the offer
 * Saab 35G2 – single-seat attacker version based on the Saab 35XD but without extra internal fuel; 12 aircraft in the offer
 * Saab 35GT – two-seat trainer aircraft; 2 aircraft in the offer

A variant of the Saab 105XT, designated Saab 105G, was also included in this offer. 24 Saab 105G proposed. The offer also included a preliminary weapons package with Falcon missiles, bombs, rockets and cannon ammunition, as well as 'Product Support' and extra equipment such as weapons pylons and drop tanks.

Due to budget cuts the Venezuelan offer later changed to only include 15 Saab 35s and 15 Saab 105s but in the end the entire project fell apart due to US pressure and intervention.

Saab 35Ö (Österreich)
Saab 35Ö (Östen) or Saab 35OE (international name) was an export version of the Saab 35D for the Austrian Air Force. The Ö-suffix stands for Austria (Österrike, Österreich). Since the Austrian Air Force lacks a proper designation system the Saab 35Ö got the name J 35Ö in Austria. The J prefix is a remnant of the Saab J 29Fs that Austria operated during the 1960s. The Austrians called their Saab 105Ös as J 105Ö for example. Saab re-purchased 24 J 35D aircraft from the Swedish Air Force in the mid-1980s and converted them into the Saab 35Ö version for export to Austria.

The Saab 35Ö was more or less equal to the Saab 35D but featured the updated bird-proof cockpit from the Saab 35F. Austria was offered the Saab 35F as an option but as Austria was forbidden to use missiles after World War II there was no point in choosing the F model with one cannon over the D model with two cannons. It quickly became apparent however that the Austrian Drakens needed missiles to protect their airspace and after the fall of the USSR and outbreak of the Yugoslav Wars Austria was permitted to use missiles. This was followed by Austria adopting several types of the AIM-9 Sidewinder, such as the AIM-9P3.

In 1992 the Austrian Drakens received an upgrade giving them a radar warning receiver (RWR), chaff and flare countermeasures and the AIM-9P5 all aspect missile. The RWR and countermeasure system was developed in collaboration with the Royal Danish Air Materiel Command FMK (Flyvematerielkommandoen) and looked very similar to the systems used on the Danish WDNS Drakens. The upgrade was performed by Valmet in Finland. This version is commonly called "J 35Ö mark 2" under a variety of spellings: J 35Ö Draken MK2, J-35 Oe Draken Mk.II.

Technology tree

 * Saab 35 Draken technology tree

Operators
The Saab 35 Draken was withdrawn from military use in 2005. Several aircraft fly in civilian service, mainly by the National Test Pilot School.

 * Austrian Air Force, 24 aircraft:
 * Fliegerregiment 2
 * Staffel 1
 * Staffel 2
 * Staffel 2

 * Royal Danish Air Force, 51 aircraft:
 * No. 725 Squadron
 * No. 729 Squadron
 * No. 729 Squadron

 * Finnish Air Force, 50 aircraft:
 * Fighter Squadron 11
 * Fighter Squadron 21
 * Fighter Squadron 21

 * Swedish Air Force
 * Swedish Air Force

 * National Test Pilot School (6)
 * National Test Pilot School (6)

Surviving aircraft

A small number of Drakens are still with civilian owners mainly in the United States, many former-operational aircraft have been preserved in the operating nations.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Saab 35 Draken


text:
Radiation therapist

A radiation therapist, therapeutic radiographer or radiotherapist is an allied health professional who works in the field of radiation oncology. Radiation therapists plan and administer radiation treatments to cancer patients in most Western countries including the United Kingdom, Australia, most European countries, and Canada, where the minimum education requirement is often a baccalaureate degree or postgraduate degrees in radiation therapy. Radiation therapists (with master's and doctoral degrees) can also prescribe medications and radiation, interpret tests results, perform follow ups, reviews, and provide consultations to cancer patients in the United Kingdom and Ontario, Canada (possibly in Australia and New Zealand in the future as well). In the United States, radiation therapists have a lower educational requirement (at least an associate degree of art, though many graduate with a bachelor's degree) and often require postgraduate education and certification (CMD, certified medical dosimetrist) in order to plan treatments.

Roles & Responsibilities
Radiation therapists use advanced computer systems to operate sophisticated radiation therapy equipment such as linear accelerators. The therapist works closely with the Radiation oncologists, Medical Physicists and other members of the health care team. They effectively design and treat the course of radiation treatment, in addition to managing the patient's well-being. Radiation Therapists primarily treat cancer although other disorders and conditions can be managed through the care of radiation therapists. After the radiation oncologist has consulted with the patient and a decision has been reached that the application of radiation will benefit the patient, it then becomes the radiation therapist's responsibility to interpret the prescription and develop a treatment plan for treatment delivery. The process of producing the final plan rests with a group of specialized radiation therapists called dosimetrists.

Since the course of radiation therapy can extend over several weeks, the radiation therapist is responsible for monitoring the condition of the patient and is required to assess if changes to the treatment plan are required. This is accomplished through patient re-positioning, dose calculations or other specialized methods to compensate for the changes. The therapist is responsible for quality assurance of the radiation treatment. This involves acquiring and recording all parameters needed to deliver the treatment accurately. The therapist ensures that the treatment set-up is correctly administered. The therapist takes imaging studies of the targeted treatment area and reproduces the patient positioning and plan parameters daily. The therapist is responsible for the accuracy of the treatment and uses his/her judgment to ensure quality with regard to all aspects of treatment delivery. During the course of radiation treatment, the patient will most likely develop certain side effects. In such situations, the therapists will communicate these side effects with the radiation oncologist, who may adjust treatment or give medications. Radiation therapists & medical dosimetrists (in many countries these two professions are often indistinguishable, e.g., Canada, Australia, New Zealand, UK) have a training in gross anatomy, physiology, radiation protection, and medical physics. They are highly skilled, highly regarded health care professionals who are integral members of the cancer care team. Radiation therapists call upon their judgment to either continue or cease radiation treatment and ensure patient safety at all times and are regulated by a governing body within their jurisdiction.

United Kingdom
Therapeutic radiographers play a vital role in the treatment of cancer as the only healthcare professionals' qualified to plan and deliver radiotherapy. Radiotherapy is used either on its own or in combination with surgery and/or chemotherapy. They manage the patient pathway through the many radiotherapy processes, as outlined below, providing care and support for patients throughout their radiotherapy treatment.

Therapeutic radiographers are trained in all the many aspects of radiotherapy including:

Simulation - using specialist x-ray fluoroscopy machines to target the area to be treated whilst minimising the amount of exposure to surrounding healthy tissue;

CT/MR Simulation - producing scans to be used for the planning of a course of radiotherapy;

Computer planning - producing a 3D plan of the dose distribution across the area to be treated;

External beam treatment - using ionizing radiation, such as high-energy x-rays, the radiographer delivers accurate doses of radiation to the tumour;

Mold Room - radiographers and technicians in the Mold Room produce immobilization/beam attenuation devices for those receiving radiotherapy to the head or neck, as well as other custom devices for a patient's treatment;

Brachytherapy - the use of small radioactive sources placed on or in tumors to treat to a high dose while avoiding normal tissues;

On treatment review - radiation therapists regularly assess patients while they are undergoing radiotherapy, prescribing drugs to counteract side effects where necessary or referring them on to other health professionals if needed.*

Canada
Specialist radiation therapists in Ontario are given with prescription rights. Some of the roles of the CSRT (Clinical Specialists Radiation Therapist) include pain management specialists, mycosis fungoides specialists, palliative care specialists, planning image definition and contouring specialist etc.*

Qualifications & Registration
Vary by Country.

Canada
In Canada, most radiation therapy programs are second entry and the majority of the students have had at least one full year of university courses before entering the programs (many have finished a science or physics degree). In Alberta, a BScRT (Bachelor of Science Radiation Therapy) is being offered at the University of Alberta. In Ontario, a BSRT (Bachelor of Science Radiation Therapy) is being offered at the University of Toronto and Laurentian University, and a BMRSc (Bachelor of Medical Radiation Science) in Radiation Therapy is being offered at McMaster University. In British Columbia, British Columbia Institute of Technology offers a BT (Bachelor of Technology) in Radiation Therapy. In Manitoba, the University of Winnipeg is offering a BSc Physics (Radiation Therapy). And in New Brunswick, the University of New Brunswick offers a BHSc (Bachelor of Health Science) in Radiation Therapy. In Quebec Radiation Oncology technology is offered in three year cegep programs. The CAMRT certifies therapists across Canada, but certain provinces, like Quebec, do not require the national certification if practitioners are certified with the provincial body. The first Master of Health Science (Radiation Therapy) in Canada is being offered at the University of Toronto, which prepares practitioners for advanced roles in the radiation therapy clinic.

In Canada, there is no real distinction between Radiation Therapists and Medical Dosimetry. The title "treatment planner", or just "planner" commonly replaces "dosimetrist". Dosimetrists are commonly radiation therapists with several years of experience and have undergone in-house training. The national professional association has recently introduced a Dosimetry Specialty Certificate program to address the fact there is no specific credential (DSp). Many employers recognize the Certified Medical Dosimetrist qualification from the US (Certified Medical Dosimetrist, CMD), but neither are required for practice.

Australia
A bachelor or graduate degree in radiation therapy is required in order to register and practice. In Australia, radiation therapists are often being addressed as "Medical Radiation Practitioners" or "Medical radiation scientists".

Malta
Bachelor (Hons) degree in Radiography

New Zealand
A bachelor's degree in radiation therapy is required in order to practice and be registered by the Medical Radiation Technologist Board (www.mrtboard.org.nz). Post graduate opportunities in advanced practice, Msc. and doctoral programmes are also available for Radiation Therapists in New Zealand.

Republic of Ireland
To practice as a radiation therapist in the Republic of Ireland, a degree in Radiation Therapy that has been validated by the Irish Institute of Radiography and Radiation Therapy (http://www.iirrt.ie) is required. Taught and research MSc. and doctoral programmes are also available for Radiation Therapists in the Republic of Ireland.

United Kingdom
In the UK an approved course in Therapeutic Radiography must be undertaken prior to registration by the UK regulatory authority, the Health and Care Professions Council. This will usually be in the form of a Bachelor of Science degree in Therapeutic Radiography, Radiotherapy, or Radiotherapy and Oncology, however a small number of post-graduate pre-registration courses (at Post-graduate diploma or Masters level) are offered. UK radiographers are eligible for membership of the Society & College of Radiographers.

Post-graduate studies at Masters level (PgD and MSc) are available, where graduates from such programs can move into Advanced Practice roles and can undertake duties previously done by physicians. Practitioners can build further on their skills and knowledge to work as Consultant Radiographers, who are considered as experts in clinical practice, research, education and leadership in their area of expertise, and will often possess a PhD or equivalent award.

United States
The minimum Education requirement is an associate degree of science, some programs offer bachelor or master's degrees of science. In addition, there are also alternate pathways to becoming certified in the form of secondary degrees. These certifications are one year programs which require another degree, such as radiologic technology.

Chile
A bachelor's degree and a 5-year college study program is required. By law (DS-18), in order to practice, at least 6 months of clinical demonstrable experience and a performance authorization is also required.

Salary
In 2008, the mean annual wage of radiation therapists in the United States was $78,290 according to the National Occupational Employment and Wage Estimates from the United States Department of Labor - Bureau of Labor Statistics.

According to ASRT's national wage survey done in 2003, the state that had the highest mean income for radiation therapists was New Mexico($120,250), followed by Arkansas ($109,000). The states which had the lowest average pays were Texas ($57,500) and Rhode Island ($58,400).

The average salary of American board certified medical dosimetrists is well over $100,000 according to the AAMD salary report. The typical salary range is from $90,000 (South) to $130,000 (West coast).

title: Radiation therapist


text:
Isocentric technique

An isocentric technique is where all beams used in a radiation treatment have a common focus point, a.k.a. the isocenter. Isocentric techniques require less patient repositioning as multiple field arrangements can be delivered with gantry and collimator movements, reducing treatment times.

Definition
The idealized intersection point of the gantry axis of rotation with that of the collimator and treatment table is known as the mechanical isocenter.

In practice, due to the heavy weight and mechanical imperfections of the system, the isocenter is not a single point and its location changes with the rotation of the gantry, collimator or couch. This causes small uncertainties in the determination of isocenter position, typically less than 2 millimetres.

Working
The movements of the linear particle accelerator (or linac) are threefold:
 * 1) the gantry rotates (like a big crane arm)
 * 2) the collimator twists in the head of the gantry
 * 3) the bed swings around on the floor

All of these movements in the modern linac occur around an axis that runs through the isocenter. In this way, if the centre of the target area in the patient's body is moved to coincide with the isocenter, then all motions of the machine will remain centred on the target. This way, non-target areas will only receive short durations of radiation, reducing damage to them, while the target area receives constant radiation.

title: Isocentric technique


text:
User talk:Hr oskar

Hello Hr oskar, and welcome to the english Wikipedia. Here are some helpful pages:

 * Welcome, newcomers
 * How to edit a page

If you have further questions, feel free to ask them on

 * Village pump
 * My talk page

Have a lot of fun -- Cordyph 14:00 22 Jul 2003 (UTC)

You might wanna remove your e-mail address to avoid Spam. We can always e-mail you by clicking on the "E-mail this user" button. --Menchi 22:52 27 Jul 2003 (UTC)

Welcome back!
Gaman að sjá þig aftur hérna! :) Ég hefði haldið að þú værir da-3, sv-3 og no-2 eða eitthvað þannig. Ég röfla annars töluvert á norsku þessa dagana. Haukur 12:33, 21 September 2006 (UTC)

Hæhæ! Hef aðeins verið að fikta í Wikipedia undanfarið. Ég vil frekar gera minna úr málakunnáttunni, sérstaklega á norrænu málunum þar sem ég hef fyrst og fremst les- og talskilning en er ekkert sérstaklega fær við að skrifa málin.

WikiProject Iceland
Maybe you are interested in this project... --Michkalas 14:51, 26 April 2007 (UTC)

title: User talk:Hr oskar


text:
Motoi Sakuraba

Motoi Sakuraba (桜庭 統) is a Japanese composer and keyboardist. He is known for his numerous contributions in video games, including the Tales, Star Ocean, Mario Golf, Mario Tennis, Golden Sun, and Dark Souls series, as well as several other anime series, television dramas, and progressive rock albums.

Career
Sakuraba was born on August 5, 1965, in Akita Prefecture, Japan. While attending Meiji University, Sakuraba began to take music composition seriously and formed the progressive rock band "Clashed Ice" in 1984, consisting of him on keyboards and Genta Kudo on drums and vocals. After the duo had graduated the following year, they were noticed by music producer Shingo Ueno, and ending up signing with Made in Japan Records. The band had then added bassist Tetsuya Nagatsuma, and was renamed as "Deja Vu". In 1988, the band would release their only studio album, Baroque in the Future, composed entirely by Sakuraba. Although the band disbanded in 1989, Sakuraba would later go on to release a similar-sounding solo album, Gikyokuonsou, in 1991.

In late 1989, Sakuraba began working as a composer for Wolf Team, joining Masaaki Uno and Yasunori Shiono. The professional friendships formed here in Sakuraba's early years have resulted in a great demand for his composing and arranging abilities. In 1994, former Wolf Team director and composer Masaaki Uno started working at Camelot Software Planning as a coordinator and sound director, developing games for Sony, Sega and Nintendo. Sakuraba has been called upon as a composer for many Camelot games, including all of the games in the Mario Golf, Mario Tennis, and Golden Sun series.

In 1995, Wolf Team developed the breakthrough game Tales of Phantasia for Namco. This and other early games in the Tales series primarily featured Sakuraba and fellow Wolf Team co-worker Shinji Tamura as composers. Also in 1995, former Wolf Team director and producer Jun Asanuma, as well as Tales of Phantasia writer and programmer Yoshiharu Gotanda, founded tri-Ace with financial backing from Enix. The Star Ocean and Valkyrie Profile games have been their main franchises. Sakuraba has been the composer for nearly all of their games.

In 1999, long time Sakuraba sound designer and programmer Hiroya Hatsushiba, a former member of Wolf Team and tri-Ace, founded tri-Crescendo. While initially continuing to contribute sound work to tri-Ace games, tri-Crescendo began game development in 2001. Together with Monolith Soft, tri-Crescendo started working on Baten Kaitos: Eternal Wings and the Lost Ocean; Namco provided the financial backing. Hatsushiba, as director and main programmer of the project, again called upon Sakuraba's composing services. This has extended to the sequel, Baten Kaitos Origins, and Eternal Sonata. The remnants of Wolf Team later morphed into the Namco Telenet joint subsidiary Namco Tales Studio in 2003.

In 2007, Sakuraba was selected to join a long list of video game composers to arrange music for Super Smash Bros. Brawl. He chose to arrange the famous "Menu Theme" from the game's predecessor, Super Smash Bros. Melee. He also arranged "Gourmet Race" from Kirby Super Star, "Jungle Level Ver.2" from Donkey Kong Country, "Mario Tennis / Mario Golf" from Mario Golf: Toadstool Tour and Mario Power Tennis, "Victory Road" from Pokémon Ruby and Sapphire, the "Airship Theme" from Super Mario Bros. 3, the "Battlefield Theme", "Final Destination", and "Battle Scene / Final Boss (Golden Sun)" from Golden Sun: The Lost Age''.

Sakuraba then continued to write music for games in franchises he has worked with before, including Star Ocean: The Last Hope, Golden Sun: Dark Dawn, Mario Tennis Open, Mario Golf: World Tour, and many Tales series games, including Hearts, Graces, Xillia, Xillia 2, Zestiria, and Berseria. He has also contributed to other well known games such as the Dark Souls series, Kid Icarus: Uprising, and Phantasy Star Nova. In 2014, he was selected to provide musical arrangements for Brawl's successor, Super Smash Bros. for Nintendo 3DS and Wii U. For this title, Sakuraba arranged "Theme from Area 6 / Missile Slipstream" from Star Fox 64 and Star Fox Command, "Battle! (Team Flare)" from Pokémon X and Y, and "The valedictory elegy" from Baten Kaitos Origins.

In addition, Sakuraba has continued to write for non-gaming and anime projects, including solo albums such as "Forest of Glass", "What's Up?", and "Passage", as well as performing on several arrange albums. In the 2020s, he composed for games such as One Piece Odyssey and Eiyuden Chronicle: Hundred Heroes.

Live performances
During July 2003, Sakuraba held a live concert in Tokyo, Japan. He performed progressive rock interpretations of his music from games Star Ocean: Till the End of Time, Star Ocean: The Second Story, Star Ocean: Blue Sphere and Valkyrie Profile. His bandmates for this concert were bassist Atsushi Hasegawa (a member of the band Gerard) and drummer Toshihiko Nakamura. As noted, this concert was released on DVD and CD. At the same time as they were rehearsing for the concert, Hasegawa and Nakamura assisted in recording new material for the Director's Cut of Star Ocean: Till the End of Time.

The following year, the trio performed another concert. The venue was smaller, but included music from Baten Kaitos and a couple of new, non-game-related pieces. This concert was not officially recorded and released, however. However, in 2006, a new concert was given in celebration of tri-Ace's .

In September 2011, Sakuraba and his band joined up with the Earthbound Papas in Kawasaki, led by former Final Fantasy series composer Nobuo Uematsu, to perform at Fantasy Rock Fest 2011. The event featured game music performances, along with new progressive rock pieces from both bands. The first six tracks that Sakuraba and his band played were sold at the event as a preview CD for his then-upcoming solo album After all..., which was released by Strange Days Records on October 19, 2011.

In June 2015, Sakuraba performed at the Tales of Festival at the Yokohama Arena, being the first time he performed tracks from the Tales series at a live event. A selection of Sakuraba's music from the Dark Souls and Tales series was performed live at the Salle Pleyel concert hall in Paris in February 2017. The event, known as "Orchestral Memories", featured a guest appearance by Sakuraba. The 2020 Tales of Festival featured an original song by him called "Endless Journey", dedicated to the 25th anniversary of the series.

title: Motoi Sakuraba


text:
List comprehension

A list comprehension is a syntactic construct available in some programming languages for creating a list based on existing lists. It follows the form of the mathematical set-builder notation (set comprehension) as distinct from the use of map and filter functions.

Overview
Consider the following example in mathematical set-builder notation.

 * $$S=\{2\cdot x\mid x \in \mathbb{N},\ x^2>3\}$$

or often
 * $$S=\{2\cdot x : x \in \mathbb{N},\ x^2>3\}$$

This can be read, "$$S$$ is the set of all numbers "2 times $$x$$" SUCH THAT $$x$$ is an ELEMENT or MEMBER of the set of natural numbers ($$\mathbb{N}$$), AND $$x$$ squared is greater than $$3$$."

The smallest natural number, x = 1, fails to satisfy the condition x2>3 (the condition 12>3 is false) so 2 ·1 is not included in S. The next natural number, 2, does satisfy the condition (22>3) as does every other natural number. Thus x consists of 2, 3, 4, 5... Since the set S consists of all numbers "2 times x" it is given by S = {4, 6, 8, 10,...}. S is, in other words, the set of all even numbers greater than 2.

In this annotated version of the example:
 * $$S=\{\underbrace{2\cdot x}_{\color{Violet}{\text{output expression}}}\mid \underbrace{x}_{\color{Violet}{\text{variable}}} \in \underbrace{\mathbb{N}}_{\color{Violet}{\text{input set}}},\ \underbrace{x^2>3}_{\color{Violet}{\text{predicate}}}\}$$

 * $$x$$ is the variable representing members of an input set.
 * $$\mathbb{N}$$ represents the input set, which in this example is the set of natural numbers
 * $$x^2>3$$ is a predicate expression acting as a filter on members of the input set.
 * $$2\cdot x$$ is an output expression producing members of the new set from members of the input set that satisfy the predicate expression.
 * $$\{\}$$ braces indicate that the result is a set
 * $$\mid$$ $$,$$ the vertical bar is read as "SUCH THAT". The bar and the colon ":" are used interchangeably.
 * commas separate the predicates and can be read as "AND".

A list comprehension has the same syntactic components to represent generation of a list in order from an input list or iterator: The order of generation of members of the output list is based on the order of items in the input.
 * A variable representing members of an input list.
 * An input list (or iterator).
 * An optional predicate expression.
 * And an output expression producing members of the output list from members of the input iterable that satisfy the predicate.

In Haskell's list comprehension syntax, this set-builder construct would be written similarly, as:

Here, the list  represents $$\mathbb{N}$$,   represents the predicate, and   represents the output expression.

List comprehensions give results in a defined order (unlike the members of sets); and list comprehensions may generate the members of a list in order, rather than produce the entirety of the list thus allowing, for example, the previous Haskell definition of the members of an infinite list.

History
The existence of related constructs predates the use of the term "List Comprehension". The SETL programming language (1969) has a set formation construct which is similar to list comprehensions. E.g., this code prints all prime numbers from 2 to N: print([n in [2..N] | forall m in {2..n - 1} | n mod m > 0]); The computer algebra system AXIOM (1973) has a similar construct that processes streams.

The first use of the term "comprehension" for such constructs was in Rod Burstall and John Darlington's description of their functional programming language NPL from 1977. In his retrospective "Some History of Functional Programming Languages", David Turner recalls:

"NPL was implemented in POP2 by Burstall and used for Darlington’s work on program transformation (Burstall & Darlington 1977). The language was first order, strongly (but not polymorphically) typed, purely functional, call-by-value. It also had “set expressions” e.g.
 * setofeven (X) <= <:x : x in X & even(x):>"

}}

In a footnote attached to the term "list comprehension", Turner also notes

"I initially called these ZF expressions, a reference to Zermelo–Fraenkel set theory — it was Phil Wadler who coined the better term list comprehension."

Burstall and Darlington's work with NPL influenced many functional programming languages during the 1980s, but not all included list comprehensions. An exception was Turner's influential, pure, lazy, functional programming language Miranda, released in 1985. The subsequently developed standard pure lazy functional language Haskell includes many of Miranda's features, including list comprehensions.

Comprehensions were proposed as a query notation for databases and were implemented in the Kleisli database query language.

Monad comprehension
In Haskell, a monad comprehension is a generalization of the list comprehension to other monads in functional programming.

Set comprehension
The Python language introduces syntax for set comprehensions starting in version 2.7. Similar in form to list comprehensions, set comprehensions generate Python sets instead of lists.

Racket set comprehensions generate Racket sets instead of lists.

Dictionary comprehension
The Python language introduced a new syntax for dictionary comprehensions in version 2.7, similar in form to list comprehensions but which generate Python dicts instead of lists.

Racket hash table comprehensions generate Racket hash tables (one implementation of the Racket dictionary type).

Parallel list comprehension
The Glasgow Haskell Compiler has an extension called parallel list comprehension (also known as zip-comprehension) that permits multiple independent branches of qualifiers within the list comprehension syntax. Whereas qualifiers separated by commas are dependent ("nested"), qualifier branches separated by pipes are evaluated in parallel (this does not refer to any form of multithreadedness: it merely means that the branches are zipped).

Racket's comprehensions standard library contains parallel and nested versions of its comprehensions, distinguished by "for" vs "for*" in the name. For example, the vector comprehensions "for/vector" and "for*/vector" create vectors by parallel versus nested iteration over sequences. The following is Racket code for the Haskell list comprehension examples.

In Python, we could do as follows:

In Julia, practically the same results can be achieved as follows: with the only difference that instead of lists, in Julia, we have arrays.

XQuery and XPath
Like the original NPL use, these are fundamentally database access languages.

This makes the comprehension concept more important, because it is computationally infeasible to retrieve the entire list and operate on it (the initial 'entire list' may be an entire XML database).

In XPath, the expression: is conceptually evaluated as a series of "steps" where each step produces a list and the next step applies a filter function to each element in the previous step's output.

In XQuery, full XPath is available, but FLWOR statements are also used, which is a more powerful comprehension construct. Here the XPath //book is evaluated to create a sequence (aka list); the where clause is a functional "filter", the order by sorts the result, and the  XML snippet is actually an anonymous function that builds/transforms XML for each element in the sequence using the 'map' approach found in other functional languages.

So, in another functional language the above FLWOR statement may be implemented like this:

LINQ in C#
C# 3.0 has a group of related features called LINQ, which defines a set of query operators for manipulating object enumerations.

It also offers an alternative comprehension syntax, reminiscent of SQL:

LINQ provides a capability over typical list comprehension implementations. When the root object of the comprehension implements the  interface, rather than just executing the chained methods of the comprehension, the entire sequence of commands are converted into an abstract syntax tree (AST) object, which is passed to the IQueryable object to interpret and execute.

This allows, amongst other things, for the IQueryable to
 * rewrite an incompatible or inefficient comprehension
 * translate the AST into another query language (e.g. SQL) for execution

C++
C++ does not have any language features directly supporting list comprehensions but operator overloading (e.g., overloading,  ,  ) has been used successfully to provide expressive syntax for "embedded" query domain-specific languages (DSL). Alternatively, list comprehensions can be constructed using the erase-remove idiom to select elements in a container and the STL algorithm for_each to transform them. There is some effort in providing C++ with list-comprehension constructs/syntax similar to the set builder notation. LEESA provides  for XPath's / separator. XPath's // separator that "skips" intermediate nodes in the tree is implemented in LEESA using what's known as Strategic Programming. In the example below, catalog_, book_, author_, and name_ are instances of catalog, book, author, and name classes, respectively.
 * In Boost. Range library there is a notion of adaptors  that can be applied to any range and do filtering, transformation etc. With this library, the original Haskell example would look like (using Boost.Lambda  for anonymous filtering and transforming functions) (Full example):
 * This implementation uses a macro and overloads the << operator. It evaluates any expression valid inside an 'if', and any variable name may be chosen. It's not threadsafe, however. Usage example:
 * This implementation provides head/tail slicing using classes and operator overloading, and the | operator for filtering lists (using functions). Usage example:
 * Language for Embedded Query and Traversal (LEESA ) is an embedded DSL in C++ that implements X-Path-like queries using operator overloading. The queries are executed on richly typed xml trees obtained using xml-to-c++ binding from an XSD. There is absolutely no string encoding. Even the names of the xml tags are classes and therefore, there is no way for typos. If a LEESA expression forms an incorrect path that does not exist in the data model, the C++ compiler will reject the code. Consider a catalog xml.

Notes and references

 * List Comprehension in The Free On-line Dictionary of Computing, Editor Denis Howe.

Axiom

 * Axiom stream examples

Clojure

 * Clojure API documentation - for macro

Common Lisp

 * Implementation of a Lisp comprehension macro by Guy Lapalme

Haskell

 * The Haskell 98 Report, chapter 3.11 List Comprehensions.
 * The Glorious Glasgow Haskell Compilation System User's Guide, chapter 7.3.4 Parallel List Comprehensions.
 * The Hugs 98 User's Guide, chapter 5.1.2 Parallel list comprehensions (a.k.a. zip-comprehensions).

OCaml

 * OCaml Batteries Included
 * Language extensions introduced in OCaml Batteries Included

Python

 * The Python Tutorial, List Comprehensions.
 * Python Language Reference, List displays.
 * Python Enhancement Proposal PEP 202: List Comprehensions.
 * Python Language Reference, Generator expressions.
 * Python Enhancement Proposal PEP 289: Generator Expressions.

title: List comprehension


text:
Wikipedia talk:Dead letter office (proposal)

Untitled
This may well be a good idea. It's like a kind of rating or categorisation system for new articles. Perhaps this will shorten VFD and keep some articles from falling through the cracks. It needed some more spaces, though. -- Tim Starling 12:23 23 Jul 2003 (UTC)

 * The overriding idea is that it should produce more articles and better articles. Not that it wouldn't alleviate some problems with the existing structure of wikipedia, but that wasn't my primary goal in devising the draft. For the page to be a long term boon, it cannot be aimed at addressing any temporarily prevalent problem. -- Cimon Avaro on a pogo-stick 12:38 25 Jul 2003 (UTC)

Just a short note. I have been timid and posted Waitingroom (draft version) because I didn't have the boldness to post it as a off the shelf functional page. You may want to polish it or discuss it on its talkpage. (Just don't delete it as patent nonsense :) -- Cimon Avaro on a pogo-stick 08:26 23 Jul 2003 (UTC)

 * I don't get it. What does this page do over "requested artciles" and "pages needing attention"? CGS 09:44 23 Jul 2003 (UTC).

It is intended to facilitate triage of new articles. A short page to which one could swiftly add those pages which one is unable to figure a useful modus operandi for, but which definitely need something done for them. And stop newbie tests cluttering VfD. Quite a few of new articles spend only a few moments on VfD. Section editing will address the file-lenght problem with VfD, but it would help if there were a separate page for those that one did not feel need to be debated at length. Oneword comments, quick in, quick comments, quick out and then to "pages needing attention", Vfd, or whatever. I know the concept probably needs to be clarified a lot. While many of the current problems will be palliated by the section editing facility any moment now, still when in the future the flow of new articles truly explodes, we will still need a lightweight and fleet of foot mechanism to provide first aid and triage to new articles. At least that is what I think. Any opposing points of view welcome. -- Cimon Avaro on a pogo-stick 10:07 23 Jul 2003 (UTC)

 * Waiting room isn't very descriptive (although I still don't get it). How about Sorting Room, In Pile or something? CGS 11:29 23 Jul 2003 (UTC).

Well, I guess I was trying to be pc in a funny sort of way. My first idea was to call it Purgatory or Limbo. The "waitingroom" metaphor was intended to evoke the idea of a kind wiki-doctor coming and examining the patient (problematic new article); maybe with a second opinion or few. And then the patient would be sent to the right ward, declared D.O.A. or given a clean bill of health. My idea was also that someone who put the article on the list, would have done the samaritan equivalent of making sure a stranger gets to the waiting room of a Emergency Room type institution. I.E. a laudable taking of responsibility. But it is true that conseptually that image doesn't really meaningfully distinguish it from many other pages... Probably it does need a better title. -- Cimon Avaro on a pogo-stick 11:54 23 Jul 2003 (UTC)

 * I'd say do it the other way round:

-- Tarquin 12:11 23 Jul 2003 (UTC) (why does it take on average 6 months for my ideas to filter through to people? arg!)
 * VFD - suspected copyright violation
 * VFD - pure junk
 * VFD - general

 * I have commented on Cimon's proposal on the talk page. In reply to Tarquin: Eloquence has said he doesn't like the idea of splitting VFD, on Wikipedia talk:Votes for deletion. -- Tim Starling 12:42 23 Jul 2003 (UTC)

 * deleted test was my attempt at a solution for "pure junk" and similar pages. However, it hasn't caught on, so I've been thinking of moving it to meta. Martin 16:16 23 Jul 2003 (UTC)

 * I remember thinking that a page like Deleted test would be a good idea (didn't do anything, though), but it probably didn't work, because almost everyone was made an admin, just after the Wikipedia:Delete test and welcome page was created, so almost noone needed it any more. כסיף Cyp 17:09 23 Jul 2003 (UTC)

Hmm. Maybe I should expound a bit more on my intentions. The page is not meant to supplant any other page, every facility currently active should continue as before. It is meant merely as a way of avoiding duplication of effort. Currently I think there are probably many people who read through all the new articles that appear. But if there were a page that only listed the problematic ones, maybe some would concentrate their effort at fixing or axing those, rather than trawling through the whole log of new articles.

It is a fact that at some point we are going to be at the position viz a viz new articles that we shall be trying to drink from a fire hose. There will be a greater plethora of new articles than it would be practical for every diligent weeder to go through himself to separate the ones needing help from those which are a-okay.

BTW. about the name. Would Wikipedia:ER, or Wikipedia:First -Aid be better? -- Cimon Avaro on a pogo-stick 16:44 24 Jul 2003 (UTC)

Oh Oh! An American english versus British english problem there. What Americans call the ER (Emergency Room) is called in Britain and Ireland A&E (Accident & Emergency). And I know other countries use other names. So ER is out, as much of the world don't use that. Anyway in Britain, ER means Elizabeth Regina, or Queen Elizabeth in latin! (ER appears on every policeman's helmet, every ministerial box, government department, every letterbox erected since 1952, etc) People might think that wiki had a page dedicated to Her Majesty! :-)

 * Wikipedia does have a page dedicated to Her Majesty. We're not completely backward... ;) —Paul A 14:48 26 Jul 2003 (UTC)

I still have no clue what this page is for. RickK 23:18 27 Jul 2003 (UTC)

 * Thanks for sharing. No, I really mean that. If the concept is not obvious from reading the page, something needs to be clarified. Much. -- Cimon Avaro on a pogo-stick 22:30 28 Jul 2003 (UTC)

Rick is right-- This needs to be simplified to the max. I will put it at User:Stevertigo/DLO --and start hacking-- anyone want to make any changes there or specific, nested, comments on the page (not talk) is welcome.戴&#30505sv 19:49, 30 Sep 2003 (UTC)~

Cleanup might be better way to refer to this instead of DLO or as a buffer.戴&#30505sv 23:59, 30 Sep 2003 (UTC)

Can somebody please patiently explain to me why this article is allowed to remain in the Wikipedia namespace, while Talk:Deletion management redesign has to fester away in an obscure corner of Meta where nobody ever seems to go? Thank you. GrahamN 16:06, 10 Oct 2003 (UTC)

I am very patient indeed. But the answer to your question does not require a very burdensome explanation. It is allowed to remain here, because no-one has raised the question before you did so.

As the creator of the page to which this is a talkpage to, (the proposal) probably should have started at meta, in retrospect I am sorry that I did not do so, if it piques you. I think it would be entirely appropriate to move this to Meta. In the long term, I don't personally think the separation of meta, and Wikipedia namespace is a useful one; as evinced by the substantial point of your question. But I would have to say, that I personally for a long time did not think being a mere (proposal) in the Wikipedia-namespace was a much more prominent address to have put up shop. (and hence I have quite a bit of sympathy with your sentiment)

I have been to meta:Talk:Deletion management redesign several times to read it. I will comment it there, once I have grasped it's significance. -- Jussi-Ville Heiskanen 16:40, Oct 10, 2003 (UTC)

This should probably redirect to Newcomers' help desk. That page seems to be taking up the functionality that this proposal would have had. --Michael Snow 22:13, 15 Apr 2004 (UTC)


text:
Talk:Feersum Endjinn

Not set in the Culture universe?
While it's safe to say there are no direct references to the Culture in this book, I think you can interpret as being set on Earth after the Culture has departed, and that the Feersum Endjinn itself was perhaps constructed by the Culture/Minds in anticipation of the coming Encroachment. I'd go as far as to say that's what the book is implying, even though it doesn't call out the Culture directly.

Tarcieri (talk) 23:18, 8 September 2012 (UTC)

Unknown

 * Unknown to most of humanity, the Solar System is drifting into an interstellar molecular cloud ("the Encroachment"), which will eventually dim the Sun's light sufficiently to end life on Earth.

I got the impression everyone knew this was happening? Did I read it wrong..? I did leave the book and come back to it, so maybe I did... -- Sam

 * It is indeed common knowledge.

-

I've removed this: (though the story is compatible with the sci-fi universe Banks has created in the Culture books, meaning it could be assumed to be a prelude). IT's in Earth's distant future, so how can it be a prelude to the Culture? (Given that, for example, the Idiran War takes place around 1100 AD) -- Tarquin 12:57 23 Jul 2003 (UTC)

 * Oh, yes, of course; and I wrote the article on the Idiran-Culture War too... (though I think you'll find you are 200 years out : ) -- Sam

 * oops! - Tarquin

 * I won't tell them if you don't. -- Sam

Not an ant?
Thought this was interesting. When you look up what an 'ergates' is, it is six-legged and black but not exactly an ant: https://calphotos.berkeley.edu/cgi/img_query?enlarge=0000+0000+1008+0033  Spined woodborer, which explains a bit. "Came out of the woodwork" and all that. — Preceding unsigned comment added by 24.72.57.58 (talk) 22:36, 26 December 2017 (UTC)

title: Talk:Feersum Endjinn


text:
Franco-Swedish War

The Franco-Swedish War or Pomeranian War was the first involvement by Sweden in the Napoleonic Wars. The country joined the Third Coalition in an effort to defeat France under Napoleon Bonaparte.

Background
In 1803, the United Kingdom had declared war on France, and Sweden remained neutral, together with Denmark–Norway and Prussia. However, after the execution of Louis-Antoine-Henri de Bourbon-Condé in 1804, the Swedish government broke all diplomatic ties with France and concluded a convention to allow the British to use Swedish Pomerania as a military base against France in exchange for payments. Russia also promised Sweden that 40,000 men would come to the aid of the country if it was threatened by French forces. Therefore, on 9 August 1805 Sweden joined the Third Coalition and declared war on France on 31 October.

Offensive against Hanover
In early November 1805, a combined British, Russian and Swedish force of about 12,000 men were sent from Swedish Pomerania to liberate French-held Hanover. The offensive against Hanover was repeatedly delayed because of Prussia's partial reluctance for the Swedes and the Russians to move troops through Prussian territory. However, in December 1805, after the Battle of Austerlitz, the British and the Russian forces started to evacuate Hanover and left only a small Swedish force alone to face the French. In April 1806, the Swedes were also forced to retreat to Swedish Pomerania after an agreement had been concluded between Prussia and France.

Fourth Coalition
However, during the summer of 1806 Prussia formed the Fourth Coalition against France, which gave Sweden the right to occupy Saxe-Lauenburg. In the autumn, the French forces advanced rapidly and soon much of the western German regions were occupied, which forced the Swedish troops on a retreat towards Lübeck. The plan was for the troops from there to take the sea route to Stralsund to avoid the advancing French forces. The Swedes were still caught by the French on the 6 November while they loaded their ships at Lübeck, and after the Battle of Lübeck, about 1,000 Swedish soldiers had to surrender to the numerically-superior French forces.

The French Army began its offensive towards Swedish Pomerania in early 1807 and besieged Stralsund on 15 January. That began a seven-month siege, and since the French forces were engaged in warfare elsewhere as well, the number of troops stationed around Stralsund was gradually reduced. When the Swedes were reinforced on 1 April, a decision was made to attempt to break the siege. That was done with some success since the Swedes managed to take Usedom and Wolin, but the French chose to counterattack, and a force of 13,000 men attacked the Swedes from Stettin on 16 April and forced the left section of the Swedish army to withdraw. Another division in Ueckermünde was then cut off and later captured. On 18 April, France and Sweden agreed on a ceasefire according to which the French were to leave Pomerania. However, the Swedish government refused to join the Continental System and denounced the armistice under the influence of British diplomacy on 8 July.

On 6 August 1807, 50,000 French, Spanish and Dutch troops under Marshal Guillaume-Marie-Anne Brune began an assault on Swedish Pomerania and besieged Stralsund again. On 20 August 1807, the defenders of the city capitulated and the remains of the Swedish Army were surrounded at Rügen. However, Swedish General Johan Christopher Toll managed to conclude the Convention of Schlatkow with Marshal Brune on favourable terms, and his forces withdrew to Sweden, along with all of their war munitions, on 7 September.

Treaty of Tilsit
The Franco-Russian Treaty of Tilsit left Britain and Sweden without other allies in the war against France. On 21 February 1808, Russia joined the war against Sweden by invading Finland and on 14 March the same year, Denmark-Norway also declared war on Sweden. Danish, French and Spanish troops began preparations for an invasion of Skåne in Sweden, but the plan was soon aborted, and the war was instead directed to the Norwegian-Swedish border. Sir John Moore's expedition, sent by the British government to protect Sweden from possible French-Danish attack, arrived on 3 May 1808 and stayed until July, when it was redirected to Portugal.

Napoleon's plans to invade Sweden were never executed because of the British activity on the Baltic Sea, the weakness of the Danish military and the hesitations of French Marshal Bernadotte, whose actions made him popular enough to be elected as a Swedish Crown Prince after the coup d'etat in March 1809. On 30 August 1809, the new Swedish government was to conclude the Treaty of Fredrikshamn with Russia, which legitimised the Russian annexation of Finland and Åland. A peace treaty between Sweden and Denmark-Norway was signed with no territorial adjustments on 10 December 1809.

Aftermath
On 6 January 1810, Sweden signed a Russian-mediated Treaty of Paris with France, regaining Pomerania at a cost of joining the Continental System. On 17 November 1810, Sweden was forced to declare war on Britain, and all British goods in Swedish Pomerania were seized. The government-supported smuggling continued, however, over the North Sea, and the Royal Navy was informed that it would be a phantom war. The war lasted until 1812, but no military action was taken.

Literature

 * Lindqvist, Herman(2004) – Napoleon (Schibsted forlagene) ISBN 978-82-516-2157-1
 * Sundberg, Ulf(2002) – Svenska krig, 1521–1814 (Hjalmarson & Högberg) ISBN 91-89080-14-9

title: Franco-Swedish War


text:
Ozark Patriots

The Ozark Patriots were based in Ozark, Alabama. In 2002 they were members of the Southeastern League of Professional Baseball. They played their home games in Ozark, Alabama, at historic Eagle Stadium, which was constructed in 1946. A few Patriot standouts were Sergio Cairo, Matt Morrison, Junior Braddy, Cortney Jenkins, Steve Crampton, and Ty Ryburn.

History
Eagle Stadium is a baseball stadium where the Ozark Patriots played here before folding midway through the 2002 season. Professional baseball was also played here in the 1940s and 1950s as part of the Alabama-Florida League. The park features a small, covered grandstand that contains all bench seating and seats about 1,200. The dimensions of the field are huge here as center field is 440 feet from home plate. It is currently used for high school, American Legion, and special event baseball games.

title: Ozark Patriots


text:
Treaty of Paris (1810)

The Treaty of Paris, signed on 6 January 1810, ended the Franco-Swedish War after Sweden's defeat by Russia, an ally of France, in the Finnish War of 1808–1809.

History
Russia had been an ally of Sweden in the Third and Fourth Coalitions against France but, after Russia's defeat at Friedland, joined France and attacked Sweden to compel it to join Napoleon I's Continental System. The primary result of the treaty was Sweden's agreement to join the Continental System so that Sweden would not trade with the United Kingdom.

Shortly after the treaty was signed, on 21 August 1810, one of Napoleon's marshals, Jean-Baptiste Bernadotte, was elected crown prince of Sweden, and he went on to found the House of Bernadotte, which remains the Royal House of Sweden. The peace resulting from the treaty lasted until Napoleon's refusal to permit Sweden to annex Norway, which was then under the sovereignty of Denmark, an ally of France. That was followed in January 1812 by the French occupation of Swedish Pomerania for violating the Continental System since Sweden was still trading with the United Kingdom. In April 1812, Sweden signed the Treaty of Petersburg with Russia against France.

Related reading

 * Will Durant, Ariel Durant (1975) The Age of Napoleon (Simon and Schuster) ISBN 9781451647686
 * Ulf Sundberg (1997) Svenska freder och stillestånd 1249-1814 (Hjalmarson & Högberg) ISBN 978-9189080010

title: Treaty of Paris (1810)


text:
Dendermonde–Puurs Steam Railway

The Dendermonde–Puurs Steam Railway (Stoomtrein Dendermonde-Puurs) is a heritage railway situated in the Belgian provinces of East Flanders (Oost-Vlaanderen) and Antwerp (Antwerpen).

It runs from the town of Dendermonde to the town of Puurs over about 14 km of (standard gauge) track. The railway is maintained by SDP, a non-profit historical railway society. SDP, which stands for Stoomtrein Dendermonde Puurs, or Steam train Dendermonde Puurs , has a depot at the railway station in Baasrode-Noord. The trains are pulled by both steam and diesel locomotives.

The railway has been used occasionally by various film and television production companies to shoot movie scenes that are too elaborate to be filmed on the Belgian national railway network because of the potential disruption to traffic. The best known example of a movie that includes several scenes shot on the railway is Toto le Héros.

title: Dendermonde–Puurs Steam Railway


text:
Talk:Marsaxlokk

Untitled
A few questions:

(a) Is the poster Alexei Pace? (We need to be clear on copyright.) Related to that, Wikipedia articles aren't signed, so I've removed the signature from the main page. " by Alexei Pace, architect & civil engineer, Marsaxlokk, MALTA."

(b) Can you (anyone) confirm that date for Phoenician settlement: this isn't my period, but ninth century seems late.

(c) There are two image captions, and no image. The second, which also needs translating into English.

"One can here admire the small fishing craft, the 'Luzzu' and 'Kajikk' painted in vivid colours of red, yellow, green and blue, floating lightly on the calm waters of the bay."

"C'est dans cette "baie du sirocco" (Xlokk), que débarquèrent les premiers Phéniciens pour installer, au IXème siècle avant J-C, des comptoirs sur l'île. Au cours du Grand Siège, Marsaxlokk servit également de mouillage à la flotte turque." Vicki Rosenzweig 12:47 23 Jul 2003 (UTC)

Discussion with Maltese friends suggests that the name Marsaxlokk is of Italian derivation, marsa is harbour, and xlokk is the Maltese version of sirocco. Since it is open to the south east, the derivation seems to be "harbour vulnerable to the sirocco" rather than the one given. I do not qualify as authoratitive though... --Shoka 23:44, 12 October 2005 (UTC)

the word "marsa" is definitely semitic. Sapienza

logic-defying statement
"The number of working fishermen has decreased, in part because people from other localities have moved to the village." I commented out this illogical statement. Can it be rendered sensible?--Wetman (talk) 01:45, 27 February 2014 (UTC)

 * Surely this just means that the people who moved in a not working fishermen?
 * How does that defy logic? 147man (talk) 09:04, 29 April 2024 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Marsaxlokk. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for https://secure2.gov.mt/localgovernment/file.aspx?f=7810
 * Added archive https://web.archive.org/web/20160314071532/http://www.lookover.at/index.php?n=300 to http://www.lookover.at/index.php?N=300

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 22:53, 28 November 2017 (UTC)

title: Talk:Marsaxlokk