Description
overlapDays is the nonnegative elapsed intersection length; fiscalShare = overlapDays/(fiscalEndDay-fiscalStartDay).
Archival comparability and coverage depend on source labels, time boundaries, verification assertions and common-unit conversions. Matching text or balanced totals can support record review without authenticating sources or proving completeness.
overlapDays is the nonnegative elapsed intersection length; fiscalShare = overlapDays/(fiscalEndDay-fiscalStartDay).
When to use this tool
Use Historic Fiscal Year Calendar Overlap when checking a supplied archival record or support convention.
How to use the tool and how it works
- Enter fiscalStartDay, fiscalEndDay, calendarStartDay, calendarEndDay. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlapDays, fiscalShare. Use the output convention below.
Require fiscalEndDay > fiscalStartDay and calendarEndDay >= calendarStartDay. overlapDays is the nonnegative elapsed intersection length; fiscalShare = overlapDays/(fiscalEndDay-fiscalStartDay).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| fiscalStartDay | Fiscal Start Day | Required. Safe integer. |
| fiscalEndDay | Fiscal End Day | Required. Safe integer. |
| calendarStartDay | Calendar Start Day | Required. Safe integer. |
| calendarEndDay | Calendar End Day | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlapDays | Overlap Days | Required. Safe integer. |
| fiscalShare | Fiscal Share | Required. Finite number. |
{
"input": {
"fiscalStartDay": 100,
"fiscalEndDay": 465,
"calendarStartDay": 0,
"calendarEndDay": 365
},
"output": {
"overlapDays": 265,
"fiscalShare": 0.726027397260274
}
} Limitations and assumptions
- Numeric boundaries use elapsed rather than inclusive-day counting. The overlap fraction does not allocate actual seasonal revenues or determine a historical fiscal calendar.
- 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
Inspect the original sources and document the historical meaning of labels, dates and conversion factors.
References
Similar or alternative tools
- Lithology Log Interval Share
overlapThickness is the nonnegative intersection of the two depth intervals; logShare divides it by logBase-logTop.
- Endodontic Study Visit Window Offset
relativeDay = observedDay-anchorDay; deviation subtracts nominalOffset.