Re: Allied Missiles

On Nov 20, 4:24 am, Alan Nordin <alan_nor...@xxxxxxxxxxx> wrote:
On Nov 19, 10:32 am, "eunome...@xxxxxxxxxxxx" <eunome...@xxxxxxxxxxxx>
wrote:

These weapons were rushed into production a few months ahead of
refinements that would have increased their accuracy 10 fold and costs
by a fractor of 3.

"10 fold" doesn't mean 10 times, it means 2 to the 10th power or 1,024
times.

Do you really mean 1,000 times better? Frankly, 10 times better is
already quite unbelievable.

H2X/H2S (3cm version) 8 mile CEP; that's 12.8km.

Ewald II/Sauerkirsche expected to be 1-2km. The guidance update was
midcourse so there would be wind drift after that, otherwise the
system would be far more accurate. I suppose it would be possible to
give a correction only a few km from target to increase accuracy.

So its likely to be 5-10 times more accurat.



I also find it extremely hard to believe the Germans would sacrifice
the accuracy you allege for a three month jump in production without
making plans to upgrade production in the near future.

They did make plans to upgrade in the future.

The V2 guidance systems were:
1 Inertial: LEV-3 upgrade path to SG-66 or SG-70 with stable platform
and cross wind compensating accelerometers. Same connections into
autopilot.
2 Radio guidance: Viktoria-Hawaii (lateral only beam) with doppler
speed cutoff used in 25% of launches to halve longitutional
dispersion. The upgrade for this was the vollzirkel which had a
tighter beam in 3 dimensions, doppler cuttoff with range also part of
the cuttoff equation.

The V1 headed in a compass direction and some had a becon to track
progress. Latter versions could fly a dog leg course.
The final version was supposed to have the midcourse update.

Bomber Command was "carpet bombing" german cities, ie "area
bombardment/ dehousing /demoralising". This is what Lindemann talked
Churchill into doing.

The early V1 and V2 were just tit for tat vengence for that and it was
hopped might even lead to a negotiation of cessation of the allied
campaign.

These systems required time to perfect, in the meantime simple systems
would do for the purpose of "dehousing, demoralising and area
bombardment" campaign of their own.

Early versions of Vollzirkel had some problems with ground plane
interference in the beam that required re-engineering for higher
frerquencies and compensating techniques.


Any group that
has the amazing technical ability you give them credit for would
surely posess the maufacturing and planning expertise to make the
necessary changes with a minimal impact on production numbers.


I can't see that your argument hold water. The advanced guidance
systems would simply be upgrades to the V2 when they became available
perhaps 6 months after the start of the campagin. In the meantime
production would have built up, efficiency would have built up and
reliabillity would have built up.

.

Relevant Pages

  • Re: Major Version Upgrade - 4.11 to 5.x
    ... support) for you to upgrade? ... It is a general rule of thumb to do a clean install between ... > Other than the obvious advice to start with a good backup, ... leave the production system running and begin the ...
    (freebsd-questions)
  • Moving on ... (was: Re: FreeBSD has serious problems with...)
    ... For instance, we might have waited an extra 3-5 years for any ZFS support at all in a -RELEASE, and when it appeared, it would introduce a big upgrade hurdle, as it would be accompanied by major underlying changes in system architecture. ... If it were up to me, I think I would stake out a very loud and clear mission statement for FreeBSD that explicitly sacrifices new features for longer lifecycles and deeper investment in particular releases. ... Instead of having a legacy branch and two production branches, you would have legacy production and ... ... No matter where we decide to set the lifecycle dial for major releases, I really think we should rename the later one "development" ... ...
    (freebsd-hackers)
  • Re: WebSphere/HATS Odyssey
    ... >conversion is basically on hold pending an upgrade, ... >but this poses some concern from my perspective when we do get an upgrade. ... >the application servants with fewer applications than we may have hoped ... This would be a great patch for a shop with a production problem. ...
    (bit.listserv.ibm-main)
  • Re: Schedules slipping, costs soaring, aircraft canceled, whats wrong with this story
    ... caught my eye "A decade after first flight, ... Here's a fairly simple upgrade of existing airframes, ... Getting something into production ends the "we can make it better" requirements escalation. ... We are now beginning to face the same prospect with China, having developed one and a half fifth generation fighters, shit-canning one and moving toward shit-canning the other and "replacing" them with F-15s with AESA and more F-18E/Fs to cash in a peace dividend prior to a peace. ...
    (rec.aviation.military)
  • Re: Major Version Upgrade - 4.11 to 5.x
    ... but I've never done a major version upgrade. ... My hardware has dual pentium 1.13 processors ... Other than the obvious advice to start with a good backup, ... leave the production system running and begin the ...
    (freebsd-questions)