-
Notifications
You must be signed in to change notification settings - Fork 10
Comparing changes
Open a pull request
base repository: atlas-outreach-data-tools/atlasopenmagic
base: v1.8.0
head repository: atlas-outreach-data-tools/atlasopenmagic
compare: v1.9.0
- 11 commits
- 6 files changed
- 4 contributors
Commits on Nov 25, 2025
-
Adding print_metadata function for pretty printing of metadata
New function that pretty-prints the metadata dictionary to address #74
Zach Marshall authored and Zach Marshall committedNov 25, 2025 Configuration menu - View commit details
-
Copy full SHA for 9b60110 - Browse repository at this point
Copy the full SHA 9b60110View commit details -
Merge pull request #75 from zlmarshall/prettyprint
Adding print_metadata function for pretty printing of metadata
Configuration menu - View commit details
-
Copy full SHA for db82362 - Browse repository at this point
Copy the full SHA db82362View commit details
Commits on Feb 23, 2026
-
feat: add weight metadata functionality
New functions: - get_weights(key): Retrieve complete weight metadata for a dataset - get_weight_names(key): Get just the list of weight names - get_all_weights_for_release(release_name): Get weights for all datasets in a release
Configuration menu - View commit details
-
Copy full SHA for 44dfc37 - Browse repository at this point
Copy the full SHA 44dfc37View commit details
Commits on Mar 9, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 6a57905 - Browse repository at this point
Copy the full SHA 6a57905View commit details
Commits on Mar 17, 2026
-
feat: optimize release weight fetching with bulk API endpoint
- Added a new `GET /weights/dsids/{dsids_str}` endpoint to the PMG Weights API to allow retrieving weights in bulk for multiple datasets at once. - Refactored `get_all_weights_for_release` in `metadata.py` to batch-process datasets (in chunks of 500) using the new bulk endpoint, significantly reducing API round-trips. - Updated dataset extraction to correctly poll the `/datasets` API directly instead of strictly relying on local cache, ensuring offline/non-current releases load correctly. - Added a `tqdm` progress bar to provide visual feedback during bulk weight fetching. - Expanded the `pytest` mock API handling and added new unit test cases (handling mismatched tag fallbacks, 404 errors, missing e_tags, and malformed datasets) to achieve 100% test coverage for `metadata.py`. See: https://gitlab.cern.ch/atlas-outreach-data-tools/pmg-weights-db-api/-/commit/3d66dfb3631c01d1468276983caa53c49c009900Configuration menu - View commit details
-
Copy full SHA for 9017638 - Browse repository at this point
Copy the full SHA 9017638View commit details -
Configuration menu - View commit details
-
Copy full SHA for 94500e4 - Browse repository at this point
Copy the full SHA 94500e4View commit details
Commits on Mar 18, 2026
-
fix: split modules for metadata and weights
Better management of modules, less confusion and shorter files.
Configuration menu - View commit details
-
Copy full SHA for 4a6dcd8 - Browse repository at this point
Copy the full SHA 4a6dcd8View commit details -
fix: test coverage and cache clearing for weights
In addition, Zach's cosmetic comments
Configuration menu - View commit details
-
Copy full SHA for 14889b9 - Browse repository at this point
Copy the full SHA 14889b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for a57a1f1 - Browse repository at this point
Copy the full SHA a57a1f1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 820d533 - Browse repository at this point
Copy the full SHA 820d533View commit details
Commits on Mar 20, 2026
-
Merge pull request #78 from atlas-outreach-data-tools/gguerrie-weights
feat: weights implementation for atom
Configuration menu - View commit details
-
Copy full SHA for 8486a42 - Browse repository at this point
Copy the full SHA 8486a42View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.8.0...v1.9.0