When did ZM Mesko start making Spike missiles?

In January 2004, Poland signed a contract with ZM Mesko for the purchase of the Spike-LR missile system. ZM Mesko manufactured elements of the missiles and began final assembly in 2006. The requirement is for 264 tripod launchers and 2,675 missiles. Deliveries began in November 2004 and conclude in 2013.

Who is the manufacturer of the Spike missile?

The firing post consists of the command launch unit (CLU), the thermal imaging sight and a tripod. Both Spike-MR and Spike-LR missiles are in service with the Israeli Defence Force. Rafael, based in Haifa, Israel, manufactures the Spike family of anti-armour weapons.

What’s the range of a Spike anti tank missile?

The missile can hit the non-line of sight (NLOS) targets within the range of 25km. Equipped with a range of warheads and RF communication, Spike NLOS can be deployed in offensive and defensive scenarios. A prototype of the Spike-LR missile mounted on a Marvin ITV-1 4×4 all-terrain vehicle has been built by Rafael.

How did the 2004 Sumatra Andaman earthquake generate a tsunami?

A more complete analysis of the focal mechanicsm by Tsai et al. (2005) indicates that oblique motion occurred on the northern part of the fault rupture. When nearly all of an earthquake’s energy is released in a thrust motion, as in the 2004 Sumatra-Andaman earthquake, a large tsunami is generated.

What kind of seeker does a Spike missile use?

The Spike missile uses a charge-coupled device (CCD) seeker for daytime use or an imaging infrared (IIR) seeker for day and night-time use. The lofted trajectory and tandem high-explosive warhead enables the Spike missile to penetrate tanks equipped with explosive reactive armour (ERA).

Where can I find a review of Spike sorting?

Neural Syst. 9 (1998) R53–R78. Printed in the UK PII: S0954-898X(98)84153-5 TOPICAL REVIEW A review of methods for spike sorting: the detection and classification of neural action potentials Michael S Lewickiy

What does it mean when product owner accepts spikes?

The Product Owner accepts spikes that have been demoed and meet its acceptance criteria. Since they represent uncertainty in one or more potential stories, planning for both the spike and the resulting stories in the same iteration is sometimes risky.