Description
Format a bounded word as fixed-width uppercase hexadecimal.
Bit positions are usually counted from the least-significant bit, while a displayed binary string has its own left-to-right indexing convention. Masks, fields and parity predicates describe a selected region or pattern; local agreement does not validate a complete encoded record.
Format a bounded word as fixed-width uppercase hexadecimal.
When to use this tool
Use Bitwise: Bit Word Hex Digit Boundary Padding when checking the stated mask, field, parity or bit-index convention.
How to use the tool and how it works
- Enter word, width. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Format a bounded word as fixed-width uppercase hexadecimal. hexDigits = ceil(width/4); pad the numeric hexadecimal to that length, paddingBits = 4*digits-width.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| word | Word | Required. Text. Integer syntax: optional + or - and 1-128 decimal digits; leading zeros accepted. Apply the sign restriction above. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. Word value must satisfy 0 <= value < 2^width. |
| width | Width under the stated bit, interval or geometry convention; apply the field-specific units and bounds. | Required. Safe integer. Fixed-word implementation domain: whole width 1-128 bits. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Returned calculated value or nested object under the stated output convention. | Required. Object. |
| result.hexadecimal | Hexadecimal | Calculated result member: string. |
| result.hexDigits | Hex Digits | Calculated result member: number. |
| result.paddingBits | High zero bits needed to reach a hexadecimal digit boundary; not byte-order padding. | Calculated result member: number. |
{
"input": {
"word": "17",
"width": 5
},
"output": {
"result": {
"hexadecimal": "11",
"hexDigits": 2,
"paddingBits": 3
}
}
}Limitations and assumptions
- Padding occupies the high side of the final nibble representation; no sign extension, byte grouping or byte order is implied.
- Outputs are nested inside result. 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
Choose an explicit bit order, word width and missing-position policy; use the complete record format and appropriate parsing or checksum methods for full validation.
References
Similar or alternative tools
- Bit Permutation Inverse Position
Return a permutation's inverse position.
- Bitwise: Adjacent Bit Pair Exchange
Exchange each adjacent bit pair in a word.