You’ll Want Us High and Clear

ICED FIRE-CLASS ANTIMATTER TRANSPORT

Operated by: Extropa Energy, ICC
Type: Antimatter Transport
Construction: Islien Yards, ICC

Length: 1,600 km (overall)
Beam: 3,200 km
Dry mass: 39,200 tons (not including cryocels)

Gravity-well capable: No; not even low-orbit capable.
Atmosphere capable: No.

Personnel: 31

  • Flight Commander
  • 3 x Flight Executive/Administrator
  • 3 x Flight Director
  • 3 x Flight Engineer
  • 3 x Propulsion Engineer
  • 3 x Cargomaster
  • 3 x general technicians
  • 2 x riggers/EVA specialists
  • Thinker-class AI

Drives:

  •  3 x Nucleodyne Thrust Applications 1×1 “Sunheart V” fusion torch

Propellant: Deuterium/helium-3 blend
Cruising (sustainable) thrust: 3.5 standard gravities (3.3 Earth G) at nominal load
Maximum velocity: 0.3 c unloaded, 0.1 c loaded (based on particle shielding)

Drones:

  • 3 x general-purpose maintenance drones
  • 3 x tether-climbing rigger drones

Sensors:

  • 1 x standard navigational sensor suite, Islien Yards

Other Systems:

  • 2 x Islien Yards boosted commercial kinetic barrier system
  • Biogenesis Technologies Mark VII regenerative life support
  • 2 x Bright Shadow EC-780 information furnace data system
  • Islien Yards custom dual vector-control core and associated technologies
  • Systemic Integrated Technologies dual-mode radiator system

Small craft:

  • 1 x Élyn-class microcutter
  • 1 x Adhaïc-class workpod

The standard vehicle for ferrying antimatter from the Cirys bubble at Esilmúr to its various places of use, the Iced Fire-class is a starship designed around one core principle, commonly adhered to when dealing with antimatter:

Don’t get any on you.

The core hull itself is much smaller than the dimensions above suggest; a blunted cylinder a mere 252 m in length, including bunkerage. This houses the entire livable volume of the starship, including a dock for the Élyn-class microcutter at the bow, and a bay housing for the workpod. Rather than the typical stern mounting, the three Sunheart V fusion torches are located in nacelles set off from the hull on radiator pylons amidships, located 120 degrees apart; these nacelles are fully vectorable for maximum maneuverability.

The stern of the core hull instead contains the attachment points and winches for a 1,600 km tether, at whose fully extended end is in turn attached the spinhub. This is a simple unit containing monitoring equipment and a centrifugal ring, to which in turn are mounted eight further attachment points and associated tethers, terminating in heavy couplings. It is to these couplings that antimatter cryocels are mounted during loading, and dismounted upon arrival. In flight, the action of the centrifugal ring maintains appropriate safe distance between the core hull and the cryocels, and between the cryocels themselves, while also ensuring that jettisoned cryocels will move away from the main body of the starship in the event of containment failure.

 

20 thoughts on “You’ll Want Us High and Clear

  1. How does this setup even work under thrust? Do the cryocel tethers rotate at an obtuse angle with respect to the main tether?

    • I’m thinking, that at cruising thrust, the spinhub would have to be turning at a decent rate to avoid the cryocels and their tethers from tangling. Torque would be …interesting.

      I’m also trying to imagine this thing turning end for end to decelerate. How long does it take to reel in the cryocells?

      • Wouldn’t turn end over end. The drives vector as needed and you’d want the hull ahead of the cargo at all times to avoid debris strikes on the explody stuff.

        • Seeing as this is a tractor system, with the hull pulling on the spinhub via a long tether, leaving it ahead of the spinhub during deceleration would be disastrous. The cryocel tethers probably have to retract, and the entire thing flips end over end on the main tether, before the cryocel tethers extend again.

  2. Y’all are all forgetting the vector-control system, which effectively leaves the entire ship behaving as if it’s coasting in emgee while under thrust.

    • I’m pretty sure that using vector control for inertial dampening requires gravity rotors, and therefore can’t be applied to an entire ship, as the rotors have to be attached to something that won’t be within the field they generate.

      • I’ll defer to Alistair, but based on other descriptions you don’t need grav rotors for inertial damping. At least his designs don’t push obscene gees that would reduce the crew to a smear on the aft bulkhead if the inertial compensators failed under thrust.

        • From https://eldraeverse.com/2014/05/22/handwavium-inertial-dampers/ :

          “All inertial damping actually is is… artificial gravity.

          This brings with it all the associated limitations. For example: you can only create the a-grav field between matching and opposed sets of gravity rotors. (Well, that’s not technically true – but not having the second one there means you’re trying to attract about half the universe with your a-grav field, energy requirements head asymptotically for infinity, fuses blow, and you’re done here.) It’s basically an internal closed field, with very little spillover at the fringes. Forget a-graving anything in open space or cheating your way to a reactionless drive with them; you need something to mount the rotors on, and that thing is not going to be within the field of effect.”

      • Vector control is used for all sorts of inertia and momentum trickery; inertial dampening is apparently only one aspect of it, which implies that the other aspects do not work in quite the same way. Note that the article you quoted says that reactionless drives using artificial gravity don’t exist, but “reactionless” drives using other vector control techniques do.

        IIRC, there has been some talk in posts passim about using vector control to do stuff like make your poorly-loaded-and-balanced freighter still travel in a straight line under thrust and spin around nicely without bits whipping around or snapping off. This implies that, to a certain extent, you might be able to operate a payload-onna-string ship as if the connecting cable were rigid.

        • Okay, here’s the thing:

          “Vector control” is the name for a whole family of related ontotechnologies. For most purposes, there are three primary kinds to be concerned about:

          1. The one that jiggers about with the coupling constant between true mass (i.e. energy-equivalence) and inertial mass. And which, most importantly, can do this across a field boundary rather than directly, which is why it doesn’t make matter fail in a variety of interesting and potentially explosive ways. Has many applications, for which consult Mass Effect.
          2. The one that creates paragravity between two opposed poles. Also used for inertial damping, because as long as the frame of the starship is strong enough to cope with the real thrust and the poles are bolted to it well enough to stand the reaction to the action, internal opposed paragravity works just fine for that.

          3. The one that allows non-local momentum transfer. Could be used to build a reactionless drive that isn’t really a reactionless drive; it’s just that you don’t need to be next to whatever is receiving the equal and opposite reaction. Hope it doesn’t mind being leaned on by a starship. Comically inefficient, and a pain in the ass to use for anything except classroom demonstrations.

          Could, and occasionally is, used to build overly fancy and impractical starships made of multiple disconnected pieces that “magically” all move together – mostly by people who really want to show off and aren’t worried about having to somehow fetch the missing bits if the machinery glitches out.

          Is mostly of use for momentum-conserving tractor-pressor effects.

        • Now, trying to do that “make your poorly-loaded-and-balanced freighter still travel in a straight line under thrust and spin around nicely without bits whipping around or snapping off”, however – that isn’t going to work.

          You’ll notice all the examples I give of non-local momentum transfer are between two disconnected objects. That’s because bad things happen when half a physical object suddenly finds itself with a radically different momentum than the other half; which is to say, if you were to try to use it to balance out the thrust on your poorly loaded freighter, you’re either going to crumple your thrust frame up on one side, snap it in half on the other, or probably both.

          (There are almost certainly ways to kluge around this limitation with sufficient bastardgineering, but since all of those amount to expensive ways to quarter-ass your way around the problem of hiring a cargomaster who isn’t an idiot, they’re not exactly a major subject of research. 🙂 )

          • Now, trying to do that “make your poorly-loaded-and-balanced freighter still travel in a straight line under thrust and spin around nicely without bits whipping around or snapping off”, however – that isn’t going to work.

            So, I was fairly certain that I wasn’t making this up, so I’ve done a bit of an archive crawl.

            We have this: <a href=https://eldraeverse.com/2018/02/03/the-sapphire-coloratura-revealed/”>The Sapphire Coloratura: Revealed! with the relevant quote

            First, its radiators, which cloak the center of the mechanical section with a divided cylinder of gridwork, individual carbon-foam emitting elements held together and in place away from the hull by vector-magnetic couples, linked back to the ship itself only by the ribbons of thermal superconductor transmitting waste heat to them;

            And also this: Next Question Batch which says

            Of course, if you have a vector-control core to evenly spread change in momentum out across your entire starship, the containers don’t feel relative acceleration and you can stack them as “high” as you want, so long as the mass will hold together under non-thrust stresses and you don’t mass-out or bulk-out the ship in the process.)

            The latter being the moost obviously relevant one. In both cases, vector control is apparently being used to spread angular momentum out across a structure.

            you’re either going to crumple your thrust frame up on one side, snap it in half on the other, or probably both.

            So long as you don’t exceed the physical limits of your structure (and on spacecraft running trajectories that don’t require massive accelerations and sudden manoevering, which will be the vast majority of them, you’d be hard pressed to do this) you’ll be fine, right?

          • The former is an example of (C); it’s just using tractor-pressor-torquor functionality to make the radiators (and the subhulls) hold position; nothing fancy going on there that you couldn’t replace with physical material if you were so inclined.

            The latter is me screwing up and misspeaking; it’s the the paragravity mode of vector control used for inertial damping that sustains microgravity and lets you stack the cargo containers high, not the VC core. My bad.

            So long as you don’t exceed the physical limits of your structure (and on spacecraft running trajectories that don’t require massive accelerations and sudden manoevering, which will be the vast majority of them, you’d be hard pressed to do this) you’ll be fine, right?

            I would not expect so. Transferring momentum (and therefore velocity along with it, since mass is constant) out of part of a (mostly-rigid) structure with vector control is basically like dropping the velocity of half a car and leaving the other half alone.

            With results fairly similar to a drive directly into a bridge support. Even at low speed, it ain’t pretty. And in this scenario, it’s going to be prolonged until either the VC equipment or drive fails or is shut down.

            crumple

Comments are closed.