Skip to content

Main content

Reward Delay Unit Crosswalk

Convert an experimental reward delay using fixed 24-hour days and seven-day weeks rather than calendar-date intervals.

Loading tool…

Description

Convert a supplied reward delay between fixed hours, days and weeks.

Behavioral economic tasks use explicit payoff units, reference values, time periods and supplied utility or discount conventions. A decision weight need not be a probability, one branch term is not a full expectation, and a nominal cost difference does not establish perceived switching difficulty or an actual preference.

Convert a supplied reward delay between fixed hours, days and weeks.

When to use this tool

Use Reward Delay Unit Crosswalk when you already have delay, inputUnit, outputUnit and need to convert a supplied reward delay between fixed hours, days and weeks.

How to use the tool and how it works

  1. Enter delay, inputUnit, outputUnit. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read delay. Use the output convention below.

Require delay>=0 and each unit hours, days or weeks; multiply by input hours/unit and divide by output hours/unit, using 1,24,168.1

Input fieldMeaning and unitsAccepted input
delayNonnegative fixed-duration value; one day=24 hours and one week=168 hours in this crosswalk.Required. Finite number; minimum 0.
inputUnitInput UnitRequired. Text; maximum UTF-16 length 8192.
outputUnitOutput UnitRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
delayNonnegative fixed-duration value; one day=24 hours and one week=168 hours in this crosswalk.Required. Finite number.
json
{
  "input": {
    "delay": 2,
    "inputUnit": "weeks",
    "outputUnit": "days"
  },
  "output": {
    "delay": 14
  }
}

Limitations and assumptions

  • These are fixed-duration units, not calendar periods with timezone changes. No reward delivery, discounting or participant preference is inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the full task design, incentive and payoff definitions, participant records and statistical analysis. Estimate behavioral models from appropriate data when local supplied-value arithmetic cannot establish preferences or causal effects.

References

  1. Calculation and input contract: behavioral-economics/reward-delay-unit-crosswalk — tool.io

Similar or alternative tools