Conference results

[rebeccamccabe]

No description provided.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[petebachant]

Looks like there's a bunch of iteration happening on the automation here. Anything I can help with?

[rebeccamccabe]

@rj426-cpu if you are running into any issues with calkit, @petebachant is a great help!
Please be careful with the sudo rm -rf commands. I don't think these should be necessary, what issue are you running into?

[rj426-cpu]

It gives the error that ERROR: database or disk is full and it basically gave the warning that WARNING: Some of the cache files do not exist neither locally nor on remote.

[rebeccamccabe]

Ok, I suspect that is the dvc cache being full not the CI server itself. From https://github.com/actions/cache?tab=readme-ov-file#cache-limits, looks like the limit is 10GB per repo. I think this should be fine since the run actions runs calkit dvc pull before the pipeline, it might just take longer.

…

-Becca

On Thu, Dec 11, 2025 at 11:54 AM rj426-cpu ***@***.***> wrote: *rj426-cpu* left a comment (symbiotic-engineering/WEC-DECIDER#8) <#8 (comment)> It gives the error that ERROR: database or disk is full and it basically gave the warning that WARNING: Some of the cache files do not exist neither locally nor on remote. — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHUJPSVWND5XNJNDFICLIWD4BGOU7AVCNFSM6AAAAACC2WI456VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBSHA2DANJVG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[petebachant]

You could try clearing the GitHub Actions cache: https://github.com/symbiotic-engineering/WEC-DECIDER/actions/caches

It might have a bunch of old artifacts in there from previous runs.

More generally, what is the goal for each of the Actions workflows? ci_cem does some environment setup then calls a run_all.sh script, which appears to serve the same purpose as the Calkit pipeline, but with no output caching/skipping. Maybe these could be merged into one workflow, unless the goal for ci_cem is testing the code, and the Calkit workflow is for efficiently generating artifacts like figures or datasets (skipping ones that are up-to-date).

[rebeccamccabe]

The goal is for `ci_cem` to eventually be replaced by the calkit pipeline, and is there to serve as a reference as we are getting the pipeline to work as expected.

…

On Thu, Dec 11, 2025 at 1:19 PM Pete Bachant ***@***.***> wrote: *petebachant* left a comment (symbiotic-engineering/WEC-DECIDER#8) <#8 (comment)> You could try clearing the GitHub Actions cache: https://github.com/symbiotic-engineering/WEC-DECIDER/actions/caches It might have a bunch of old artifacts in there from previous runs. More generally, what is the goal for each of the Actions workflows? ci_cem does some environment setup then calls a run_all.sh script, which appears to serve the same purpose as the Calkit pipeline, but with no output caching/skipping. Maybe these could be merged into one workflow, unless the goal for ci_cem is testing the code, and the Calkit workflow is for efficiently generating artifacts like figures or datasets (skipping ones that are up-to-date). — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHUJPSX54M2YGRO35X2FCVD4BGYTJAVCNFSM6AAAAACC2WI456VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBTGIYDSNBTHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>