Le vendredi 16 septembre 2016 02:33:04 UTC+2, Rick Pikul/Chakat Firepaw a
> You did notice that this discussion was a month and a half ago, right?
Sorry. My wife imposed an incommunicado during our vacation in order for us to do some work on our house and rental properties.
>
> You do not understand because I never said anything about the opposing
> orbital point: "...the other point the initial and final orbits
> intersect."
Okay, you will have to explain this a little, then. For a point burn, there is only one point where the orbits intersect, and that is at the point of the burn. If you are using a continuous sail manoeuvre, there IS no intersection, because you are either spiralling in or spiralling out. Once a manoeuvre is completed, the only point of intersection is with the point where you withdrew the sail, unless you were constantly changing the angle of the sail in order to circularise the final orbit... but, again, there would be no common point with the initial orbit. You CAN NOT oppose a radial out burn with another radial out burn.
>
> >> Not really, hitting the platforms involves firing shots that saturate a
> >> target area at least one hundred _million_ square kilometres in size.
> >> Cheap, unguided, shot means a minimum of about one 'pellet' per square
> >> metre.
> >
> > This is not a problem. Yes, I have suggested 1 pellet/m^2, but you
> > actually only need 1 pellet per sensor. The sensors will have to be
> > large in order to obtain useful info. 1 pellet/10m^2 would likely be
> > more than sufficient.
> > Furthermore, pellets can be small. The impact of even a single gram will
> > likely sufficiently damage the sensors.
>
> And what will be the total mass of those pellets?
>
> 10,000,000 km^2 = 1e14 m^2
10^13, actually... However, I think you might have meant 100 000 000 km^2, which would roughly match the 10 000 km spread I meantioned; although I no longer remember if I intended that "spread" to refer to diameter or area.
>
> For a 1g pellet every 10 m^2 that's:
>
> 1e14 m^2 * 0.1 g/m^2 = 1e13g
>
> That's ten _million_ _TONNES_. For a shot that isn't even certain to
> connect, (perfectly spaced they're 5.77m apart).
Actually, the shot is pretty certain to connect. The Hubble has a minimal cross section of over 17m^2. But I suppose that I can concede an insignificant probability that all the pellets will miss.
You have a point that that is a lot of mass (and energy) to dedicate to a single target, although it might still be worthwhile for strategic purposes. based on the original discussion, 10 000 km^2 should be more than sufficient. That brings us down to 10^9 g, or 1000 tonnes. This would be about the size of a backyard pool of material. This would also be the mass equivalent of the bomb load of an average WWII sortie of B-17s (6 combat boxes of 12 aircraft each), generally dedicated against a single target (actually, this count is small... typical sorties used anywhere from 100 to 600 bombers, not counting support aircraft).
>
> > You don't even need pellets...
> > sensors are VERY sensitive to any kind of impact. Even high velocity
> > dust will scour the collector dishes and optics, rendering them
> > unusable. Given the size of the pellets or dust in question, the mass
> > required to do sufficient damage, results in high arial coverage
> > actually yielding fairly low actual masses or volumes.
>
> You obviously either didn't do the math or made rather unrealistic
> assumptions.
>
> Or are you jumping around between units again: Using one figure as the
> radius of your shot cloud when claiming it will hit, then using the same
> number as the area when claiming you can connect using a sane amount of
> material.
The area originally discussed was probably overkill. However, the mass discussed is NOT unreasonable for important strategic targets. Still, I have demonstrated that the mass can be significantly reduced for more reasonable strikes. You can even decrease the mass below 1g, especially if you decide to use an explosive shell or armour piercing design.
In war, "sane" amounts of material is quite subjective.
>
> Um, no. You need on the order of 10km/s for escape trajectories, and
> that's if you eject prograde from the body orbiting the sun. For these
> kinds of shots think 15-20km/at least.
Again, easily achievable with small pellets. Existing rail gun design will fire a 3.5 kg projectile at over 2.5 km/s. The same energy will fire 100 1g pellets at 15 km/s. BTW, your 10 km/s delta v estimate applies to launch from Earth orbit. From the asteroid belt, you only need on the order of 3 km/s delta v.
>
> > Also, dust and pellets will continue to disperse, leaving them no more a
> > hazard than currently existing meteoroids.
>
> Actually, they don't. They just transform into a stream, meteor showers
> are annual for a reason.
>
Actually, relative to each other, they DO. Even if they are locked into respective orbits, they will disperse within that orbit (actually, a band of orbits). But, yes, you now have another region of meteor showers.
Largely irrelevant... it would not be difficult to impart sufficient momentum for solar escape velocity; or, alternatively, to have a programmed detonation to reduce the shells to dust.
>
> Actually, yes you do: All of the stations can see almost everywhere, you
> have no horizon to hide behind.
If you scan, yes. However, if you scan, you leave open large windows where you can sneak manoeuvres in.
>
> >> Remember that 'cold-running' means turning everything off, including
> >> things like life support and any computer systems. If you have
> >> anything running you will have waste heat to get rid of.
> >
> > Incorrect. Cold running simply means that waste heat will have to be
> > limited to what can be safely absorbed by the internal heat sink
> > (cryogenic supply)
>
> Which isn't that much, expect no more than a few months under ideal
> conditions.
This depends upon the object, the amount of heat sources, the amount of cryogenic supply or other heat sink material, and the amount of surface area for low level radiation of waste heat.
If I have time, I will try to draw up some scenarios.
>
> > or what can be emitted without allowing for detection.
>
> Which also isn't that much
Fairly safe to emit quite a lot of radiation normal to the solar plane. Even with your imaginary solar polar orbits, you are not going to get a significant measurement unless you are passing almost directly "overhead".
>
> > Let's say you ere emitting 2.25 watts/s IR radiation.
>
> So you are a tiny ship cooled to under 150K.
Who said anything about a tiny ship?
>
> Even at a chilly 200K your hull is emitting 9 W/m^2, not the waste heat
> from your systems, the hull itself, (and that's assuming you optimize for
> minimal blackbody radiation).
Which is not significant, considering all the other bodies in space that are emitting blackbody radiation. It is also quite insignificant compared to the energy from reflected sunlight. Again, stealth is NOT about not being detected, but not being noticed.
Also, I was using the 2.25 watt value out of convenience when I was working through my calculations. Those calculations actually result in 126 W allowing a maximum of 1 photon/s striking a 35m sensor. Even if you could detect such low yields, these are likely to be disregarded as unreliable. Even if considered reliable, it will likely be disregarded as a probable meteoroid/small asteroid. Such emissions are far to small for Hubble. Even WISE might have some difficulty.
>
> (Psst: W/s would be how fast your emissions are increasing, you simply
> want W.)
Quite correct. Sorry. I was actually thinking J/s, but then decided it would be easier just to go with watts.
>
> Multiple sensor platforms, remember? Not simply orbiting a single
> planet, remember? Besides, controlling the direction your heat goes
> takes energy and quickly becomes a Red Queen's race.
If the radiation is directed off the solar plane, and outward from the sun, it is unlikely to be detected even by your imaginary solar polar platforms... even if these extend beyond the orbit of jupiter. Unless you have invested the resources to build and deploy at least 360 such platforms. Considering that the resources to deploy such a platform even in a 1 AU solar orbit do not exist, and barely exist even in theory (even GC-NTR propulsion would require multiple staging), that is not very likely.
Controlling the direction of radiation does not require energy. It is a question of architecture. Well, okay, you probably will need a little energy to pump the coolant through the radiators.
>
> > Furthermore, although electronics can produce significant waste heat, as
> > can human bodies, life support generally will not.
>
> Life support means you have portions of your ship heated to 280K or more.
Yes. A question of architecture and engineering. The body heat of the crew, and the operational systems, are quite sufficient to provide the necessary environmental heating. The trick is to balalnce the rate of heat loss.
>
> > Actually, much of the
> > human and electronics generated waste heat will be absorbed in the
> > processof bringing cryogenic oxygen supplies to usable temperatures.
> > Properly handled, waste heat will actually be the sole source of
> > environmental heating.
>
> Think about why you need environmental heating.
The why is irrelevant. All that is relevant is that you have sufficient environmental heating and (often more importantly) cooling.
However, in response, you need thermal energy to maintain metabolism (this means that you want sufficient insulation to prevent the loss of metabolic generated heat... already a common practice since the development of the shuttle). You need sufficient heat to avoid freezing working liquids and condensing gases such as atmospheric supply. You need sufficient heat to avoid moving parts freezing together. You need sufficient heat to avoid joint seals from ontracting to the point that they start leaving gaps. Etc.
>
>
> >
> > Platforms for searching for asteroids DO exist, but you are correct that
> > there are very limited numbers of such platforms.
>
> Congratulations, you managed to repeat the very caveat I made.
>
> Describing that sensor platforms looking for interplanetary objects don't
> really exist is as correct as saying that passenger aircraft didn't
> really exist in 1914.
And both statements would be equally incorrect. You did not say the capabilities were underdeveloped. You said they did not exist. You then qualified this statement to correct the error, but it does not refute Emmett's statement.
> > The cost of putting
> > such platforms into space is rather the issue.
>
> Right now it is, right now we aren't looking at even setting up the
> preconditions of an interplanetary war being possible in the first place.
Cost, in terms of resources, will ALWAYS be an issue. Yes, more resources will become available... but more resources will also be in demand. Populations will continue to increase. These populations will continue to demand an increase in standards of living, which means an increase in the availaility of resources dedicated to meating those standards. The number of different services and products offered will increase, also increasing the demand on resources. Automated labour might very well replace manual labour, but increasing populations will continue to mean increasing demand of resources, especially since automation requirements will be adding their own demands on resources.
You are ALWAYS going to have to balance out the use of available resources, and your populace is not likely to consider establishing your Big Brother Net as justified.
>
> Nope, not false. Your later simply shows that you still don't understand
> how a sensor system like this would work.
>
> (Hint: Think about why radar dishes move and why they can get away with
> not constantly staring at things.)
Nope, still false. You can get away with terrestrial radar scanning because the gaps created during military radar sweeps are generally not large enough to slip aircraft through, at least not at the ranges where you have reliable detection.
>
> >> Second, most of the oceans are places where deploying those sensors is
> >> hard, (contrast with space, where there are harder spots that you want
> >> to use, but the limitation for those is really deployment time, (you
> >> have to wait for the slingshot that kicks your inclination up), and the
> >> easy spots are still usable).
> >
> > Slingshots are of very limited use in kicking up inclination.
>
> Nope, they can do quite a bit of it. You can get plenty of (anti)normal
> in a slingshot and that's what you need for a plane change.
Jupiter's orbital inclination to the ecliptic is currently about 1.31°. It has about a 6° inclination off the plane of the sun's equator, while Earth has just over a 7° inclination. Using Jupiter's gravitational pull, you could drag an object launched along the plane of the ecliptic, achieving an inclination of perhaps 8.5°... perhaps you can manage to convert a little of Jupiter's orbital momentum to boost this diflection a few more degrees. You would probably have much better results using the Oberth effect during a deflectional burn.
>
> So you think trailing a 4km long cable to the bottom that can survive for
> years is the easy way to do it?
No. There are even easier methods. Rather supports my point.
>
> > Until you have colonies claiming regions of space. The entire reason for
> > a space navy is to protect assets. Current space law will no longer
> > apply in such settings.
>
> Space does not work that way. The only thing you could meaningfully
> claim is the orbital space around your own planets/moons, the oceanic
> equivalent would be things like the White Sea or the Gulf of St.
> Laurence. Claiming solar orbits would be like claiming the Pacific Ocean.
You are not thinking future. You can claim any territory you are willing and able to defend. It will be much easier for established belt and outer planet communities to enforce and develop outer planet territories than for an Earth based organisation. While independent outer planet communities might not be able to enforce territorial "ownership" outside their immediate sphere of influence from each other, a united organisation of developed outer planets communities would sure as hell be able to block out any spy satellite development from Earth.
>
>
> Um, picking out new signals against a known background is _easy_. Heck,
> there is a good chance that your _car_ is doing the kind of filtering
> needed.
Um, no... it really isn't, which is why astronomers are still pooring over 50 year old (and older) photographic plates, along with all the newer observation data, trying to locate and identify the rest of the uncatalogues stars, asteroids, etc... not to mention more remote dwarf planets and similar objects. They have been looking for asteroids specificly for over thirty years, and of the 150 million plus estimated 100m+ asteroids, they have only identified 500 000 (1/3%).
You can try to filter out all light sources brighter than the expected target signal. The danger with this is that with over 4 000 000 such sources in a single square degree (this is for magnitude 12 objects... if you are looking at higher magnitude objects, there will be many times this number), you have a very good chance of filtering out the target signal itself, because its signal will (possibly) be in front of or immediately adjacent to the light of a filtered source (it will then be interpreted as part of that filtered source). Even if you manage to filter all the brighter sources, the distribution of sources is such that you will have a number of sources of the same magnitude as the target as the total number of sources brighter than the target. Good luck with that.
You can try to filter out sources by spectral analysis, but spectral analysis is pretty much limited to one source at a time. At 4 000 000 + objects to sort through, that will take a long while. You can try to filter out all the known sources... but you still have to identify them, and there is an excellent chance that the target source will be in front of, overlapping, or adjacent to the known source, and might therefor be filtered out as part of the signal from the known source.
Keep in mind that tracking all these known sources is not quite so easy either. You will have to calculate their positions relative to the current position of the platform. All these apparent positions will be moving, relative to the platforms FOV, so you will need to be able to track multiple millions of moving targets.
Oh, yes... once you have actually found a legitimate target (a spacecraft), you are then going to have to filter through all the other spacecraft... ALL of which must be tracked.
>
> > Let's say that you have the means to filter out all this background.
>
> Yes, let's say we can do something that we could do before you were born.
Again, no, this is simply not true. If it were anywhere near to being true, we will already have filtered everything out in order to dentify ALL of the projected 150 million 100m+ asteroids. We are nowhere near completing this task, exactly because we do not have the means to filter out all the background stars.
> Have you missed the whole bit about how you place these things in _solar_
> orbits?
>
Have you missed the bit that even theoretical GS-NTR rockets would not be able to place platforms of the required mass into even 1AU solar polar orbits, without a hell of a lot of expendable staging?
>
>
> Dude: Stop talking about how we might launch such things from the
> surface of the Earth. In any scenario where this kind of thing matters
> you will have to have cheap access to space as the very minimum and are
> more likely going to be engaging in orbital manufacture. You won't be
> launching them into orbit, you're going to be _building_ them there.
You might be constructing these things in space, but you will first have to transport all the raw materials from either the Earth or the moon (perhaps Mars, if you still control Mars space). Also, cheap access into space is realtive, and is not entirely relevant in this case. The notion that LEO is halfway to anywhere (in the solar system, at least) is only applicable to transit along the solar plane. For solar polar orbits, not only do you have to start from scratch, but you also have to negate the velocities along the solar plane.
>
>
> Wrong, you don't need to look at everything at all times. This is one of
> the two constant errors pro-stealth people make.
>
> Instead you look at any given direction periodically, using a search
> pattern that makes it impossible to manage to 'sneak though' by moving
> from areas about to be scanned to ones that were just scanned.
Remember, stealth is not about not being seen, but about not being noticed. Looking all the time means that you have more opportunity of spotting intermittent burns that might indicate something worth paying attention to. When you scan, the holes are not places where a ship is not detected so much as they are occasions where the activities (burns) of that ship do not send up flags.
Seaarch patterns are okay, but you are not going to see what is actually happen. You are not going to see the energy spikes produced by a burn, or the launch of an assault force of drones from an NEA or common cargo transport.
Scans also make it much more likely that two intermittent spikes will be interpreted as anomalies, rather then manoeuvres from a single object.
>
> > A single degree field
> > of view is MUCH more likely (still probably somewhat generous),
>
> Getting a 0.8 degree field of view with a single sensor that could do 1.5
> FOV/s was possible _TWENTY YEARS AGO_. That gives you two whole sky
> surveys, (not a band, the full 4pi steradians), per day using hardware
> that isn't as good as the phone in your pocket.
1.5 FOV/s is possible with small sensors. It is not possible with the 35m dishes required for detecting weak signals. But that doesn't matter, because you are forgetting that you will be dealing with a developed community of spacefarers. Local traffic between moons is going to be on the level of city street traffic. Traffic between adjacent planets will be on the level of interstate traffic. Even traffic between Jupiter and Earth will be on the level of international traffic between Europe and the US (several flights per day... or, if you prefer, several departures per day of ocean vessels).
Again, stealth is not about not being seen... it is about not being noticed. You are going to have thousands of legitimate targets to sort through to look for possible threatening activities, and if you aren't looking all the time, you are going to easily miss such activities.
>
> Combine an array, (let's say a 3x3), with faster CCDs and processors,
> (let's say 5 FOV/s), and an out of plane sensor platform that only looks
> at half of the sky, (because everything interesting is either staying in
> the plane of the ecliptic or coming from it), and you are down to one
> full scan every 12 minutes.
Given the bulk of data (and poverty of input), faster CCDs and processors will be insufficient. You need more processors (or processors capable of much greater loads, or both), and more sensitive CCDs (if you run the CCD too fast, it will not accumulate enough energy to register). Actually, you need that anyway. Astronomers are STILL looking at 50+ year old data, running them through newer, faster, higher capacity computers, trying to extract useful info from the data that is already there, just trying to count and catalogue the stars and other objects already present on those plates.
>
> > but that
> > would require 540 to 720 platforms... well, assuming that you want full
> > coverage. You could reduce the requirement through scanning.
>
> Oh man can you ever reduce it.
Yes. You can reduce it all you want. But say goodbye to your notion of stealthless space.
> pointed out to you earlier:
>
> That you use one type of sensor to do the whole thing.
>
> You start with one that scans fast, gives limited angular detail and
> generates false positives left, right and centre.
A fast scanner is not going to help you if it can't receive sufficient energy input. Detectors require a sufficient number of photons of sufficient energy in order to register. Energy is not usually difficult, but photon count is important. There are three options for increasing sensitivity here: find something that can sense a lower number of photons; increase reception area; and/or, increase exposure time. If you scan too fast, you are going to miss your input.
>
> You pass off its potential detections to a narrow FOV, higher resolution
> system that confirms the detection.
>
> That then hands off to other platforms to confirm with their narrow FOV
> systems and lock in the location.
>
> At this point you know where it is and where it's heading and can also
> start looking at it with the really high resolution stuff.
At the ranges being discussed, resolution is not exchanged with FOV. Resolution is a function of baseline, and FOV is a function of the sensors you are using. Sensitivity is a function of sensor collection area and exposure time. You can try to use planar array sensors, which will give you vastly improve FOV at the cost of much larger required collection area; or you can use parabolic arrays that collect much more energy in a much smaller area (because, unlike planar arrays, you can reflect and focus the energy in a smaller area). Optical lenses and reflectors do the same job as parabolic arrays, but are much more sensitive to damage.
Since a minimum 35m collector will be required just to have a chance to detect low level emissions from 1AU+, you might as well just rely on these. However, you can run them individually for the initial detection, if you prefer; and then coordinate the data for high res interferometric telescopy if you find something of interest.
But here's the problem: you are going to ind objects of interest. Lot's of them. Tens of thousands of them. But you are not going to know which ones are commuter traffic, which ones are routine shipping, which ones are pleasure cruises, which ones are military on routine patrol, which ones are military on training exercises, and which ones are military on possible stealth missions until you track and observe them. ALL of them. ALL the tens of thousands of them. If you stop observing the wrong ones at the wrong time, you give them the window to perform their task without you noticing. That is stealth.
>
> > Please keep in mind that these platforms make REALLY easy targets.
>
> This claim of yours has been repeatedly shown to be false. You have to
> either engage in a massive effort, telegraph your attack months in
> advance or accept a probable failure.
There is always the possibility of failure. ALWAYS. Military planners know this. Possibility, and even probability, of failure is not a deterent.
There is a difference in planning and telegraphing. Properly shielded rail and coil guns do not telegraph. However, in space, it could be months before the shells arrive on target. Not useful against targets under constant manoeuvre, but quite effective against fixed or cyclic targets. This is just one option.
"Massive" is quite relative when it comes to effort.
Platforms are really easy targets because they tend to be cyclic. Random motions tend to get in the way of cooperative processing. The required platforms will also be large, as a function of physical law. Tech limitations will tend to make them larger. This makes them easy to see and to hit. There are numerous options for hitting: buckshot, sniper, small drone attack, automated (homing) missile attack, etc. Nothing prevents several methods from being used at once. Nothing prevents one method from being used to trap the target in a position optimal for another.
>
>
> Um, you don't go out and fix these kinds of platforms unless you are past
> what would be plausible midfuture technologies, (IOW, you have reached
> the point where the entire discussion is as moot as would be one Pliny
> the Elder might have about WWII naval tactics). You assume they will
> last about 50% of their MTBF and use that for their replacement schedule.
Perhaps. Perhaps not. You might decide that it is easier to send up a new platform instead of fixing a malfunctioning platform. In which case, replacement platform construction and deployment would be part of the infrastructure I am talking about.