fixes data1

[kellijohnson-NOAA]

We will be using timing from now on instead of date where timing is a double which allows for the year to be incremented using whatever resolution you input. Right now, the only resolution that is available in FIMS is year so timing must be an integer value.

What is the feature?

• Simplified data1

How have you implemented the solution?

• Changed datestart to timing
• Removed dateend

Does the PR impact any other area of the project, maybe another repo?

• All of the case studies will need to be updated because they create their own data objects
• There is another PR out that creates a new data object

Part of #982

@Bai-Li-NOAA I have listed you as a reviewer because I would like to merge this into your PR that goes into dev-json-caa and then eventually dev.

[github-actions]

Instructions for code reviewer

Hello reviewer, thanks for taking the time to review this PR!

• Please use this checklist during your review, checking off items that you have verified are complete, but feel free to skip over items that are not relevant!
• See the GitHub documentation for how to comment on a PR to indicate where you have questions or changes are needed before approving the PR.
• Please use conventions in the guidelines for conventional commit messages for both commit messages and comments.
• PR reviews are a great way to learn so feel free to share your tips and tricks. However, when suggesting changes to the PR that are optional please include nit: (for nitpicking) as the comment type. For example, nit: I prefer using a data.frame() instead of a matrix because ...
• Engage with the developer when they respond to comments and check off additional boxes as they become complete so the PR can be merged in when all the tasks are fulfilled. Make it clear when the PR is approved by selecting the approved status, and potentially by commenting on the PR with something like This PR is now ready to be merged, no additional changes are needed.

Checklist

• The PR is requested to be merged into the appropriate branch (typically dev).
• The code is well-designed.
• The functionality is good for the users of the code.
• Code coverage remains high, indicating the new code is tested.
• The code is commented and the comments are clear, useful, and mostly explain why instead of what.
• Code is appropriately documented (doxygen and roxygen).

[Copilot]

Pull Request Overview

This PR simplifies the data structure by replacing date-based timing with numeric timing values. It changes from using datestart and dateend columns to a single timing column that represents years as numeric values, enabling future support for fractional year resolution while currently restricting to integer values.

• Replaced date columns (datestart, dateend) with single numeric timing column
• Updated validation logic to check for numeric timing instead of date format validation
• Modified data generation and processing functions to use numeric years directly

Reviewed Changes

Copilot reviewed 5 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
inst/WORDLIST	Removed dateend and datestart entries, added timing and timings
data-raw/data1.R	Replaced date creation logic with direct year assignment from timing column
R/initialize_modules.R	Updated global variables and column references from date columns to timing
R/fimsframe.R	Refactored validation, plotting, and data processing to use numeric timing instead of dates
R/data1.R	Updated documentation to reflect new timing column structure

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}