Skip to content

Computational materials science workflow management in Python

active 2023-09-042025-12-24 (UTC)

Complete coverage26,458 / 26,458 hourly files (100%) · 2 absent upstream2023-08-152026-08-21 (UTC)
Events
79
Pushes
3
Pull requests
2
Issues
45
Stars
6
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 843 days from 2023-09-04 to 2025-12-24. Pushes: 3 total, peak 2 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 45 total, peak 33 in a day. Comments: 19 total, peak 13 in a day. Stars: 6 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
aplowman693219

Recent activity

Latest issues, pull requests and releases

  • Releaseaplowman2024-06-26 11:36
    v0.2.27
  • Pull request#109aplowman2024-06-26 11:35
  • Pull request#109aplowman2024-06-26 11:35
  • Issue#10aplowman2024-03-25 17:45
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue comment#10aplowman2024-03-25 17:45
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue#10aplowman2024-03-25 17:44
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue#10aplowman2024-03-25 17:39
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue comment#10aplowman2024-03-25 17:39
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue#10aplowman2024-03-25 17:39
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue comment#10aplowman2024-03-25 17:32
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue#10aplowman2024-03-25 17:32
    Consider whether we should allow forming element groups on parameters from upstream tasks
  • Issue#11aplowman2024-03-25 17:30
    Undefined behaviour when grouping elements by a parameter called "repeats"
  • Issue#55aplowman2024-03-25 17:30
    Dropbox cloud archive must use upload sessions for large files
  • Issue#57aplowman2024-03-25 17:28
    Finer control over default task preparation/processing run options
  • Issue#76aplowman2024-03-25 17:28
    Generalise parameter nesting between local/global parameters
  • Issue#101aplowman2024-03-25 17:27
    Allow merging imported elements with those generated from a task that produces the same outputs
  • Issue comment#101aplowman2024-03-25 17:27
    Allow merging imported elements with those generated from a task that produces the same outputs
  • Issue comment#65aplowman2024-03-25 17:27
    Pre-processing inputs for generated scripts
  • Issue#65aplowman2024-03-25 17:27
    Pre-processing inputs for generated scripts
  • Issue#78aplowman2024-03-25 17:25
    Support iteration parameters to be modified on each iteration
  • Issue comment#78aplowman2024-03-25 17:25
    Support iteration parameters to be modified on each iteration
  • Issue#85aplowman2024-03-21 16:56
    Be smarter about jobscript dependencies
  • Issue comment#9aplowman2024-03-21 16:55
    Task method and software should be sequenceable
  • Issue#9aplowman2024-03-21 16:55
    Task method and software should be sequenceable
  • Issue#9aplowman2024-03-21 16:54
    Task method and software should be sequenceable

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 6 stars here means stars gained during the window, not the repo's star count.