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

ifsbench rework launching mechanism #11

Open
johannesbulin opened this issue Jan 27, 2025 · 0 comments
Open

ifsbench rework launching mechanism #11

johannesbulin opened this issue Jan 27, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@johannesbulin
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

At the moment, essentially he classes

  • Job
  • Arch
  • Launcher

are responsible for launching executables. As these are pure classes, they can't easily be customised but most be subclassed. They also don't interact nicely with the new datapipeline approach.

Describe the solution you'd like

  • Arch and Launcher classes are overhauled. They become abstract base classes and simple subclasses are implemented to support the most basic needs.
  • System specific solutions are removed (no LUMI arch files for example).
  • Similar to the data pipeline approach, an environment pipeline should be created.

Describe alternatives you've considered

No response

Additional context

No response

Organisation

ECMWF

@johannesbulin johannesbulin added the enhancement New feature or request label Jan 27, 2025
@johannesbulin johannesbulin self-assigned this Jan 27, 2025
johannesbulin added a commit to johannesbulin/ifsbench that referenced this issue Jan 27, 2025
johannesbulin added a commit to johannesbulin/ifsbench that referenced this issue Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant