Skip to content

integrate dev branch and update software environments #25

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

Merged
merged 60 commits into from
May 20, 2025

Conversation

btraven00
Copy link
Contributor

  • updated to use omnibenchmark dev branch
  • update the 3 software environments

@btraven00
Copy link
Contributor Author

Ideally this should be squashed into a single commit

@btraven00 btraven00 requested a review from DanInci May 13, 2025 14:10
@btraven00
Copy link
Contributor Author

tests will need to be updated to reflect what is intended to run. I suggest any of the smoketest variants, since they should be short (around 1min)

Copy link
Contributor

@DanInci DanInci left a comment

Choose a reason for hiding this comment

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

Nice touch with the overrides, it goes into the direction of composable yamls that we've discussed. Then, my question, why don't we ignore the generated yamls, since they can be reproduced using the make commands.

Also, there needs to be more documentation about the yaml flavours.

Comment on lines 50 to 52
mamba install -y pip
pip install git+https://github.com/omnibenchmark/omnibenchmark.git@reduce_install_scope
pip install git+https://github.com/omnibenchmark/omnibenchmark.git@dev

Copy link
Contributor

Choose a reason for hiding this comment

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

We have to change this to track main

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Comment on lines -301 to +211
# path: "{input}/{stage}/{module}/{params}/{dataset}.metrics.txt"
id: clustering_benchmark_apptainer_oras
description: Clustering benchmark on Gagolewski's. Using apptainer from omnibenchmark ORAS registry.
software_backend: apptainer
Copy link
Contributor

Choose a reason for hiding this comment

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

Why leave these at the end of the file? I suspect diffing tools

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this i don't like either; it's unfortunate. it depends on which has priority; and I had to change to base + override because in some of the cases we're changing some of the nested (the apptainer in software-envs)

envs/README.md Outdated
Comment on lines 1 to 6
We distribute `Clustering.yml` runs with different backends.

- `Clustering_conda.yml`. Conda semi-reproducible (no pinning, pip)
- `Clustering_singularity.yml`. Singularity semi-reproducible, local SIF files.
- `Clustering_oras.yml`. Singularity semi-reproducible, prebuilt remote images.
- `Clustering_envmodules.yml`. Easybuilt with default optimization.
- `Clustering_envmodules.yml`. Easybuild backend with default optimization.
- `Clustering_apptainer.yml`. Apptainer, pinned, prebuilt remote images from [omnibenchmark's registry](https://quay.io/organization/omnibenchmark).
- `Clustering_apptainer_vanilla.yml`. Singularity, pinnned, from local SIF images.
- `Clustering_conda.yml`. Conda semi-reproducible (no pinning, using pip)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we document what _apptainer_short.yml and _apptainer_optimized.yml flavours are doing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done, have a look!

@btraven00 btraven00 merged commit 16237d9 into omnibenchmark:main May 20, 2025
2 of 17 checks passed
btraven00 added a commit to btraven00/clustering_example that referenced this pull request May 21, 2025
…hmark#25)

* run from post-0.2.0 tag, main branch
* docs: use public repo URIs
* chore: add convenience target to build environments
* add top-level Makefile to prepare env
* feat: parametrize num of cores on the makefile
* chore: ignore common temporary outputs and image build artifacts
* update .eb files to easybuild 5.0
* remove remote storage
* do not run artifacts if not in main repo
* inject checksums to rmarkdown easyconfig
* update sklearn singularity definition
* feat: add microbenchmark for numpy operations
* chore: bump clustering-benchmarks to 1.1.6
* feat: templatize the definitions
* feat: mv output folders to timestamped names
* feat: add --yes flag
* docs: update README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants