Skip to main content
Track Futures rollover management
3 / 8
Library

1992issue C051-8

Converting OHLC, session, and rollover series for analysis

Analysis programs ingest a bar only when date, high, low, and close occupy the expected field order. Conversion, session completeness, and a companion contract index decide which prints can become an executable series.

  • A mismatched field order cannot become an executable session bar because analysis programs ingest date, high, low, and close only in the order they expect.
  • Vendor binary encodings can pack the same tape into different bit layouts, so high, low, close, or volume may fail to reconstruct until the series is recast.
  • Session and rollover files must travel with any companion master index of which contract lives in which file, or the reconstructed series will point at the wrong contract.
  • A conversion kit uses an editor, a directory manager, a multi-format converter that includes ASCII, and a programmable ASCII rewriter to force each incoming layout into one executable bar schema.
Entries in this reading3 entries

Field order decides whether a bar can be ingested

Analysis programs will only ingest a bar if date, high, low, and close occupy the exact field order those programs expect, so a mismatched layout cannot become an executable session bar.

Packed binary and inspectable ASCII

Binary encodings pack price into compact words, but each vendor may assign those bits differently, so the same tape can fail to reconstruct high, low, close, or volume until it is recast.

ASCII bars use more disk than binary but can be inspected with ordinary type and copy commands, which lets a technician verify that a session file is complete before it is treated as an orderable series.

A kit that forces one executable schema

A working conversion kit needs an editor, a directory manager, a multi-format converter that includes ASCII, and a programmable ASCII rewriter so each incoming layout can be forced into one executable bar schema.

Session files, rollover files, and the contract index

Some vendor catalogs keep a companion master index of which contract lives in which file, so session and rollover files must travel with that index or the reconstructed series will point at the wrong contract.

Rewrite templates for executable bars

A one-line field rewrite can unpack a packed date, drop unused open interest, and emit date, volume, high, low, and close in the order a charting program requires.

A header skip plus substring date rewrite is the reusable template for nonstandard ASCII-to-ASCII bar construction when the source session file is otherwise complete.

A downloaded rate series can be stripped of non-data lines, dated as year-month-day, written as comma-separated ASCII, and then passed through an intermediate vendor file so the receiving chart treats the print as close with empty open, high, low, and volume.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
3 of 8 in the Futures rollover management track
19921-9 pp.Next on Futures rollover managementLinked futures series for mechanical system evaluationA mechanical futures test spanning about 15 years typically requires roughly 60 to 90 separate contract series for one market, unlike a single equity-style file.
All readings on this track · 8 readings
  1. 1989Treasury auction-rollover as yield-to-price series construction
  2. 1991Calendar spread execution for futures month rolls
  3. 1992Converting OHLC, session, and rollover series for analysis
  4. 1992Linked futures series for mechanical system evaluation
  5. 1998Percentage back-adjusted futures series
  6. 2001Construct a volume-weighted continuous-lead contract
  7. 2013Construct a continuous futures series from the roll you can execute
  8. 2018Commodity-basket exposure as a contract-design problem
All 8 readings tagged Futures rollover management
Also on Futures rollover management5 readings