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

Draft: AiiDA generator #1995

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Draft: AiiDA generator #1995

wants to merge 7 commits into from

Conversation

kinow
Copy link
Member

@kinow kinow commented Dec 13, 2024

In GitLab by @agoscinski on Oct 30, 2024, 13:28

As mentioned in issue https://earth.bsc.es/gitlab/es/autosubmit/-/merge_requests/300 this MR uses the work in MR https://earth.bsc.es/gitlab/es/autosubmit/-/merge_requests/300 as base to create a generator for the AiiDA engine. I take a bit different approach than MR https://earth.bsc.es/gitlab/es/autosubmit/-/merge_requests/300 in the sense that no AiiDA object is generated in autosubmit but a completely self-contained folder with all scripts and files together with a script that runs the AiiDA workflow. This has the advantage that the aiida workflow can be generated without having aiida installed. At the moment running the quicksetup job of autosubmit works.

TODOs:

  • The creation of the file needs to be modularized to become maintainable
  • Check if all autosubmit parameters are correctly passed
  • Add warning when Wrappers and MAX_PROCESSES is used
  • Test if remote works
  • Figure out how default parameters are correctly determined in AiiDA, current remote solution is not so clean
  • I might add a conda environment file (or pixi.toml) with dependencies and a README describing the folder structure.
  • Stress test mHM workflow https://github.com/kinow/auto-mhm-test-domains
  • Stress test a workflow with more dependencies (members/chunks/splits), pending on the BSC side to provide an example workflow
  • Stress test Autosubmit -> AiiDA on MN5, pending on the BSC side to set it up and test (~1/2 hours to set up AiiDA, plus the dev env and workflows)

* Remove testing purpose further engines
* Add dictionary for translating the platform/computer metadata between
  autosubmit and aiida
* resolve dichotomy for output_path
* add readme in the generation of the code
* Fix usage for some job.paramaters
* add usage of wallclocktime
* added answers from the meeting
* fixed computer configuration, but it is a bit hacky at the moment,
  need to dig longer how aiida does the automatic configuration.
  `verdi computer test THOR` passes
  workflow seems to run but is very slow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants