Skip to content

#14514 Add option to include list of dates into schedule file - #14530

Open
kriben wants to merge 6 commits into
devfrom
14514-orion-events-report-dates
Open

#14514 Add option to include list of dates into schedule file#14530
kriben wants to merge 6 commits into
devfrom
14514-orion-events-report-dates

Conversation

@kriben

@kriben kriben commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Misc ORION events fixes.

Fixes #14514.
Fixes #14533.
Fixes #14535.
Fixes #14537.

@kriben kriben self-assigned this Aug 14, 2026
kriben added 2 commits August 14, 2026 15:58
GenerateSchedule gains an AdditionalDates parameter (ISO date strings). The dates are merged, deduplicated and sorted with the event dates and each becomes a DATES keyword even when no events fall on it, ensuring a summary report at that date in Eclipse/Flow. They are deliberately not filtered by the last applied timestamp.

The ORIONEVENTS 2.0 format gains a top-level REPORT <date-expr> directive (date variables and day arithmetic supported). Parsed dates are collected on OrionDocument.report_dates and surfaced by the applier as sorted ISO strings on ApplyReport.report_dates, ready to pass to generate_schedule_text(additional_dates=...).
They are not planned as part of the file format. PERFID on a completion event is now an unknown-attribute error like any other unrecognized key, and DSHIFT on keyword events is forwarded unchanged instead of being stripped with a warning. FILTER keeps its ignore-with-warning behavior outside PERFORATION events.
@kriben
kriben force-pushed the 14514-orion-events-report-dates branch from af77d7c to ad2a87b Compare August 14, 2026 16:05

@kriben kriben left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This adds useful REPORT-date parsing and schedule plumbing, with good parser and integration coverage. I found two edge cases in the date merge: an additional date can re-enable events excluded by set_timestamp(), and an earliest report date is emitted only as a comment by default. Both can violate the expectation that REPORT dates produce report-only DATES entries.

Note: This review was prepared by an automated review bot working on behalf of @kriben.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant