Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Fly your .ork

Fly a rocket designed in OpenRocket with hpr sim from the command line, and learn to read the numbers it prints.

This guide flies a rocket you designed in OpenRocket with hpr sim, from the command line, and says how to read what it prints. It’s for a flier who has a .ork file and wants a second simulator’s view of it.

The steps:

  1. Fly the file as it is.
  2. Choose the configuration and the launch.
  3. Fetch a motor the simulator doesn’t have.
  4. Plot it, or save the numbers.
  5. When the simulator refuses.

You need hpr installed: the README’s Install and first flight takes a few minutes.

The examples fly the guides’ own rocket, validation/fixtures/ork/guides/level-1.ork. It’s a 66 mm (2.6 in), 0.82 kg rocket with a 38 mm motor mount and one parachute on the motor’s ejection charge. It’s saved with two motors, an AeroTech H170M and an I175WS. OpenRocket 24.12 opens it. Run the commands from a copy of the repository, or put your own file’s path in its place.

Fly the file as it is

hpr sim with the file’s name flies its default configuration, with the motors, delays and parachutes the file holds. The guide rocket’s motors are in the catalog built into the simulator, so it flies with no network:

$ hpr sim validation/fixtures/ork/guides/level-1.ork
Level 1 guide rocket (level-1.ork)
configuration 1 of 2: [H170M-10]
help: --config flies the others, by number or name: 2 [I175WS-9]
a simulated flight, not a measurement

static margin         1.70 calibers off the rail; least 1.70 calibers, at 0.12 s, before apogee
CG and CP             0.811 m (31.9 in) and 0.923 m (36.3 in) aft of the nose tip, off the rail
apogee                1065.1 m (3494 ft) above the site at 11.62 s
rail exit speed       26.3 m/s (86 ft/s)
delay                 apogee 9.48 s after burnout, with the charges held; the motor's set delay: 10 s; its charge fires 0.52 s after apogee; the delay may fire 2.0 s short or long (NFPA 1125): climbing at 14.7 m/s (48 ft/s) to 2.52 s after apogee (no speed: falling with nothing open, a fall HPR Sim doesn't predict)
descent               4.4 m/s (15 ft/s) at landing under `Parachute`

motor: 1 × H170M (from the bundled catalog, as of 2026-10-28) in `Motor mount tube`, lit at launch
recovery: `Parachute` at the ejection charge, 0.520 m² of drag area, opened at 12.14 s
launched at 0.00000° N, 0.00000° E, 0 m (0 ft) above sea level, from 1.5 m (4.9 ft) of vertical rail above its aft end, in calm air
note: the file's 1 recovery device flies as OpenRocket flies it. Each opens fully at its event, with the file's drag coefficient or OpenRocket's own. Once one opens, the rocket descends as a point under the open devices' drag alone
warning: drag: issue #67: a cone-like nose's or shoulder's pressure drag reads high from Mach 0.8 (about twice a measured cone's at Mach 0.85, still +15% at 1.5). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 0.84 at 1.7 s
warning: drag: issue #68: base drag reads high from Mach 0.8 to 1.2 (0.225 against a measured 0.156 at Mach 0.9). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 0.84 at 1.7 s
warning: drag: issue #18: skin friction is taken as fully turbulent; on a smooth surface a laminar run near the nose lowers it, by 3.6% on RocketPy's Calisto at Mach 0.3. If this surface is that smooth, the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are
warning: stability: issue #172: the static margin read up to 0.1108 calibers above OpenRocket's on four private designs, cause unknown; this flight's may read high by as much
warning: stability: issue #1290: on one of two wind-tunnel models, the center of pressure sat 0.11 to 0.92 calibers aft of the tunnel's at Mach 0.6 and 0.8, as the report's curve reads; fitted over −3° to 4°, about 0.08 at 0.8. So from Mach 0.6 the flight margin may read high. This flight reaches Mach 0.84 at 1.7 s
warning: stability: issue #1198: the center of pressure sat 0.67 to 1.35 calibers aft of a wind tunnel's on two models at Mach 0.9, so past Mach 0.8 the flight margin may read high. This flight reaches Mach 0.84 at 1.7 s
help: issues: https://github.com/nrdptel/fusionspace-eridanus/issues/<number>

event                   time                 height                    speed
liftoff               0.00 s      0.4 m      (1 ft)     0.0 m/s     (0 ft/s)
rail exit             0.12 s      1.9 m      (6 ft)    26.3 m/s    (86 ft/s)
burnout               2.14 s    406.4 m   (1333 ft)   240.4 m/s   (789 ft/s)
apogee               11.62 s   1065.1 m   (3494 ft)     0.1 m/s     (0 ft/s)
charge               12.14 s   1063.7 m   (3490 ft)     5.1 m/s    (17 ft/s)
deployment           12.14 s   1063.7 m   (3490 ft)     5.1 m/s    (17 ft/s), airspeed 5.1 m/s (17 ft/s)
ground hit          245.78 s      0.0 m      (0 ft)     4.4 m/s    (15 ft/s)
(heights are the center of gravity's above the site; speeds are over the ground, and a deployment's
airspeed through the air)

top speed             285.6 m/s (937 ft/s) at 1.73 s
top Mach number       0.842
landing               0.7 m (2 ft) from the pad at 245.78 s, at 4.4 m/s (15 ft/s)

How far to trust it. Simulated from the design file, not measured. Against 60 logged flights of
fliers' own designs, the simulated apogee averaged 8.0% above the logged one. HPR Sim flew each in
its day's air from ERA5, a weather reanalysis, and each logged apogee is the height climbed in it.
The simulated apogee was within 10% on 31 and read low on 15, by at most 20%. This flight was flown
in the standard atmosphere. On a day warmer than it at the site, the rocket can climb higher than
this apogee; --weather flies the day's air. Plan a waiver or a field's ceiling with room above this
apogee; the altimeter's reading is the one to log, and the RSO decides.
More: https://hpr.fusionspace.co/accuracy.html

The lines under the configuration are the ones to read first. Each height and speed is in SI, with feet or feet per second in parentheses:

  • static margin is how far the center of pressure sits behind the center of gravity, in body diameters (calibers). The line gives it as the rocket leaves the rail, and its least value before apogee. A rocket with a fin set of one or two fins has a different margin for each direction the air crosses it. hpr sim prints the least (Flight metrics). Check stability for a certification flight says how to use it.
  • CG and CP gives where the center of gravity and the center of pressure sit as the rocket leaves the rail, measured from the nose tip. They’re the two points the margin comes from.
  • apogee is the highest point of the center of gravity, above the launch site.
  • rail exit speed is the speed as the rocket leaves the rail. The slower it is, the more a crosswind tips the rocket just after.
  • delay gives the coast from burnout to apogee, with the charges held, beside the delay the file sets. Here the H170M’s 10 s charge fires about half a second after apogee. The line ends with how far the delay may fire short or long, and the speed at either end where the simulator predicts one. Pick a motor says how to choose one.
  • descent is how fast the rocket comes down under its open parachutes, without the wind’s drift.

The recovery line names each parachute, when it opened and its drag area. The events table gives each event’s time, height and speed. The note says how the parachute is flown: it opens fully at once, as OpenRocket’s does. The command line explains every line, and any warning you may see.

Choose the configuration and the launch

--config picks another of the file’s configurations, by its number, its name or its motors. The output’s second and third lines list them. A configuration the file leaves unnamed is called by its motors and delays in brackets. So the guide rocket’s second is [I175WS-9], and --config 2, --config I175WS-9 and --config i175ws-9 all fly it.

hpr sim doesn’t read the launch conditions saved with the file’s simulations: give them as options. Without them, the rocket flies from a 1.5 m (4.9 ft) vertical rail at sea level, at 0° N, 0° E, in calm air. Set the site’s elevation for every real field: air thins with height, and a rocket climbs higher from a high one. --rail-length runs from the rocket’s aft end to the rail’s top: from its fin tips if they reach past the tube. So take a standoff or blast deflector the rocket sits on off the rail’s length as sold. This flies the second configuration from a field 1,400 m (4,593 ft) up. The rail’s top is 2.4 m (7.9 ft) above the rocket’s aft end, the rail is tilted 5° toward the west, and a 4 m/s (8.9 mph) wind blows from the west:

$ hpr sim validation/fixtures/ork/guides/level-1.ork --config 2 --elevation 1400 --rail-length 2.4 --inclination 85 --heading 270 --wind 4 --wind-from 270
Level 1 guide rocket (level-1.ork)
configuration 2 of 2: [I175WS-9]
help: --config flies the others, by number or name: 1 [H170M-10]
a simulated flight, not a measurement

static margin         1.69 calibers off the rail; least 1.69 calibers, at 0.17 s, before apogee
CG and CP             0.811 m (31.9 in) and 0.923 m (36.3 in) aft of the nose tip, off the rail
apogee                1174.3 m (3853 ft) above the site at 11.51 s
rail exit speed       36.8 m/s (121 ft/s)
delay                 apogee 10.42 s after burnout, with the charges held; the motor's set delay: 9 s; its charge fires 1.42 s before apogee; the delay may fire 1.8 s short or long (NFPA 1125): climbing at 32.4 m/s (106 ft/s) to falling at 3.4 m/s (11 ft/s)
descent               4.9 m/s (16 ft/s) at landing under `Parachute`

motor: 1 × I175WS (from the bundled catalog, as of 2026-10-28) in `Motor mount tube`, lit at launch
recovery: `Parachute` at the ejection charge, 0.520 m² of drag area, opened at 10.97 s
launched at 0.00000° N, 0.00000° E, 1400 m (4593 ft) above sea level, from 2.4 m (7.9 ft) of rail above its aft end, 85° above the horizon, leaning toward 270° T, in a 4 m/s (9 mph) wind from 270° T
note: the file's 1 recovery device flies as OpenRocket flies it. Each opens fully at its event, with the file's drag coefficient or OpenRocket's own. Once one opens, the rocket descends as a point under the open devices' drag alone
warning: drag: issue #67: a cone-like nose's or shoulder's pressure drag reads high from Mach 0.8 (about twice a measured cone's at Mach 0.85, still +15% at 1.5). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 0.87 at 1.8 s
warning: drag: issue #68: base drag reads high from Mach 0.8 to 1.2 (0.225 against a measured 0.156 at Mach 0.9). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 0.87 at 1.8 s
warning: drag: issue #18: skin friction is taken as fully turbulent; on a smooth surface a laminar run near the nose lowers it, by 3.6% on RocketPy's Calisto at Mach 0.3. If this surface is that smooth, the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are
warning: stability: issue #172: the static margin read up to 0.1108 calibers above OpenRocket's on four private designs, cause unknown; this flight's may read high by as much
warning: stability: issue #1290: on one of two wind-tunnel models, the center of pressure sat 0.11 to 0.92 calibers aft of the tunnel's at Mach 0.6 and 0.8, as the report's curve reads; fitted over −3° to 4°, about 0.08 at 0.8. So from Mach 0.6 the flight margin may read high. This flight reaches Mach 0.87 at 1.8 s
warning: stability: issue #1198: the center of pressure sat 0.67 to 1.35 calibers aft of a wind tunnel's on two models at Mach 0.9, so past Mach 0.8 the flight margin may read high. This flight reaches Mach 0.87 at 1.8 s
help: issues: https://github.com/nrdptel/fusionspace-eridanus/issues/<number>

event                   time                 height                    speed
liftoff               0.02 s      0.4 m      (1 ft)     0.0 m/s     (0 ft/s)
rail exit             0.17 s      2.8 m      (9 ft)    36.8 m/s   (121 ft/s)
burnout               1.97 s    389.9 m   (1279 ft)   271.2 m/s   (890 ft/s)
charge               10.97 s   1172.0 m   (3845 ft)    15.4 m/s    (50 ft/s)
deployment           10.97 s   1172.0 m   (3845 ft)    15.4 m/s    (50 ft/s), airspeed 17.7 m/s (58 ft/s)
apogee               11.51 s   1174.3 m   (3853 ft)     1.0 m/s     (3 ft/s)
ground hit          246.17 s      0.0 m      (0 ft)     6.3 m/s    (21 ft/s)
(heights are the center of gravity's above the site; speeds are over the ground, and a deployment's
airspeed through the air)

top speed             290.9 m/s (954 ft/s) at 1.75 s
top Mach number       0.874
landing               755.8 m (2480 ft) from the pad at 246.17 s, at 6.3 m/s (21 ft/s)

How far to trust it. Simulated from the design file, not measured. Against 60 logged flights of
fliers' own designs, the simulated apogee averaged 8.0% above the logged one. HPR Sim flew each in
its day's air from ERA5, a weather reanalysis, and each logged apogee is the height climbed in it.
The simulated apogee was within 10% on 31 and read low on 15, by at most 20%. This flight was flown
in the standard atmosphere. On a day warmer than it at the site, the rocket can climb higher than
this apogee; --weather flies the day's air. Plan a waiver or a field's ceiling with room above this
apogee; the altimeter's reading is the one to log, and the RSO decides.
More: https://hpr.fusionspace.co/accuracy.html

--inclination is the rail’s angle above the horizon, so 85 is 5° off vertical. OpenRocket gives the same rail as 5°, from the vertical. --heading 270 leans it toward the west, into the wind. The wind is the same at every height. The launch lists every option and its default.

Fetch a motor the simulator doesn’t have

A motor outside the simulator’s catalog is fetched from ThrustCurve.org the first time you fly it. Then it’s kept in the simulator’s cache, so it flies offline after. A .ork names its motor but rarely carries its thrust curve. The catalog holds ThrustCurve.org’s solid motors, but not one newer than it, or one ThrustCurve.org lists without a curve file. With no network, and no copy in the cache, hpr sim refuses and prints the command that fetches it. This test rocket names an invented motor, which no catalog holds:

$ hpr sim validation/fixtures/ork/guides/no-curve.ork --offline
error: configuration [Z9-INVENTED] can't be flown as the file has it. No thrust curve for Z9-INVENTED: no embedded curve, and no motor of that manufacturer and designation in the bundled catalog. Invented Z9-INVENTED is not in HPR Sim's cache of ThrustCurve.org, and the run is offline
help: with a network connection, `hpr motors fetch --manufacturer Invented Z9-INVENTED` fetches it into the cache
help: give a motor with --motor
$ echo $?
1

Run that command once with a network connection, or fly the file once online:

hpr motors fetch --manufacturer Invented Z9-INVENTED

The curve is ThrustCurve’s, found by the file’s manufacturer and designation. For the motors of OpenRocket’s own example designs, HPR Sim knows which file holds the curve OpenRocket flies, and takes it. For any other motor, the file may not be the one OpenRocket flies.

A note under the flight names the curve file, who measured it, and which of the two it is. Motors from ThrustCurve.org says how the simulator picks one. If you have the motor’s .eng or .rse file, fly it with --motor: hpr sim my-rocket.ork --motor my-motor.eng.

Plot it, or save the numbers

--plot draws the flight as a picture; --export saves every number.

hpr sim validation/fixtures/ork/guides/level-1.ork --plot level-1.svg --export level-1.csv

The plot is one fixed figure: altitude, speed and acceleration against time, each event marked. An SVG opens in any web browser; Plotting the flight shows one.

Beside it, level-1.plot.csv holds the numbers the figure draws. The export holds every quantity the simulator tracks, every 0.01 s. The file’s extension picks the format (.csv, .json, .parquet, .geojson or .kml). Exporting a flight says what each column means. --json prints the summary itself as data, for a script to read.

When the simulator refuses

hpr sim refuses, with the reason, rather than fly something other than your design. The common reasons, and what to do:

it sayswhat to do
no thrust curve for the motor, and the run is offlinefetch it once online, as above, or give a motor file with --motor
the design’s checks found errorseach error names the parts, such as a motor wider than its mount. Fix the design; or, to fly it anyway, add --accept-design-errors, and the flight’s notes list the errors
a part the simulator couldn’t read exactly as writtenThe simulator flies only what it reads exactly. The message names the part; the .ork page lists what it reads
a stage that separates, a second motor lit in flightpowered separations fly without --motor, one or several in turn, as on a three-stage rocket (Separation); with --motor, drop the option to fly the file’s own motors. A payload dropped with nothing left to burn flies when its own parachute opens at the split; one that would coast with no drag first is refused: set one of the payload’s devices to open at “Lower stage separation” with no delay (a payload’s split)
it can’t tell which configuration to flythe file has several and no default: name one with --config
a parallel stage hangs on the core’s tube, “whose stage carries an added mass with no station”the core has a mass override with the override for all subcomponents box unticked, and boosters beside it. Say where that mass is: add a center of gravity override on the core with the box unticked too, or untick the one it has (why)

Warnings aren’t refusals. A warning: line flags something the design’s checks found unusual but buildable, such as a motor longer than its mount tube. The flight goes on. Warnings, notes and help: lines go to standard error, so hpr sim rocket.ork > flight.txt saves the flight alone and leaves them on the terminal.

A stage that weighs more than its parts. If your stage has a mass override with OpenRocket’s override for all subcomponents box unticked, OpenRocket adds that mass to what the parts weigh, and so does the simulator. It used to refuse such a stage. Boosters strapped beside the core (a parallel stage) are read the same way. Their stage’s added mass is one mass for the set, and it drops with them.

Where a stage’s override has that box ticked, the simulator leaves the stage’s parts where they are, as OpenRocket does, and its mass, center and inertia match OpenRocket’s on the probe designs of one stage with no motor aboard. With the override on the lower of two stages, or with a motor aboard and a center override beside an added mass, OpenRocket takes the parts about the whole rocket’s center rather than the stage’s, and the simulator doesn’t. On the probes that show it, the rocket’s inertia across the axis is from 1.6% under to 4.95% over OpenRocket’s (the 1.6% worked by hand from OpenRocket’s own output), and another rocket’s can differ more (what a stage’s added mass leaves out).

Where the ticked override is on boosters strapped beside the core, the boosters’ own mass, center and inertia match OpenRocket’s on the probes. The whole rocket’s inertia across the axis doesn’t. The override adds less to it than it does in OpenRocket, by 0.070% to 4.673% of OpenRocket’s inertia for that rocket. M2.3d14, the rocket’s inertia beside a parallel stage’s covering override, is to close that where an unticked override is beside the ticked one. Where every override is ticked, no work is planned yet (#1432).

A core with boosters and an unticked mass override. It is refused unless a center override with the box unticked is beside the mass. The message says a parallel stage hangs on a tube “whose stage carries an added mass with no station”. With no center override, OpenRocket puts that mass at the center of the core and its boosters together, so it moves when the boosters drop. The simulator’s stage keeps one center. Add a center of gravity override on the core with the box unticked, and the mass has a fixed place. It is a station measured from the core’s forward end. The design then flies with a ring of two or more boosters. Three were measured against OpenRocket. One booster alone, off the axis, is still refused. Flying the mass with no center override that has the box unticked, or beside a single booster off the axis, is open work: M2.3d11, the stage a parallel stage hangs on. An unticked mass override of zero adds nothing, so neither refusal applies to it.

Matching OpenRocket isn’t matching your rocket. Where a ticked override sets the stage’s mass, both put the mass the parts miss at the stage’s center, where it adds no inertia. If that mass is really spread along the stage, as its parts are, the true inertia is higher by about the ratio of the override’s mass to the parts’ (5 times for a 2 kg override on 0.40 kg of parts), and more if it sits farther out (A stage’s rule).

A few more cases are still refused. One is a ticked override on a stage that carries boosters. Another is an unticked mass override on a stage whose parts weigh nothing, with no unticked center override beside it. The third is a flight that moves a mass, releases one, or parts through a stage with an added mass. A stage’s mass and center of gravity overrides lists each.

What it leaves out

  • The launch conditions in your file. Give them as options, above.
  • Real weather, unless you pass --weather. By default it flies one wind at every height in the standard atmosphere. --weather FILE flies the profile hpr weather writes.
  • A fall with no parachute open. The landing is then marked “not a prediction” (the landing).
  • A verdict. The simulator prints estimates. Whether a rocket is fit to fly is for you, the motor’s printed data and your range safety officer to decide.
FusionSpace HPRVersion 0.1.0Issued 2026-11-21In preparationAbout HPR Sim