Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

confusing start and end dates for cycles, tasks and ICON #97

Open
leclairm opened this issue Jan 20, 2025 · 0 comments
Open

confusing start and end dates for cycles, tasks and ICON #97

leclairm opened this issue Jan 20, 2025 · 0 comments
Labels
Milestone

Comments

@leclairm
Copy link
Contributor

leclairm commented Jan 20, 2025

Problem

Currently, we have the 3 following and confusing date definitions:

  • ICON has "start" and "stop" dates in the master namelist to designate the overall simulated time.
  • sirocco.core.Cycle potentially has a date entry in the coordinates attribute and start_date and end_date attributes (as opposed to "stop" for ICON) for the overall duration.
  • exactly the same for sirocco.core.Task, so date, start_date and end_date attributes, although one would logically expect the last 2 would stand for the start and end of the task itself.

So the current implementation works but is absolutely not natural.

Proposition

Rename end_date as stop_date

On top of providing more coherence in itself, it would also fit with ICON terminology.

Introduce begin_date and end_date for cycles and tasks:

  • self.begin_date would simply be a property returning self.coordinates["date"].
  • self.end_date would be an attribute inferred at creation time from self.date, the ConfigCycle.period and self.end_date (as maximum cap for the last cycle/task).
@leclairm leclairm added this to the v0.1.0 milestone Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant