# Reproducibility project: September report

**URL:** <https://forum.openrefine.org/t/reproducibility-project-september-report/1005>\
**Category:** Day-to-day project operations\
**Created:** [October 3, 2023, 2:16pm UTC](https://forum.openrefine.org/t/reproducibility-project-september-report/1005 "2023-10-03T14:16:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![antonin\_d](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/antonin_d/32/32_2.png) [@antonin\_d](https://forum.openrefine.org/u/antonin_d)\
**Post date:** [October 4, 2023, 6:27pm UTC](https://forum.openrefine.org/t/reproducibility-project-september-report/1005/2 "2023-10-04T18:27:11Z")

</div>

I have posted more details of my work on concurrent execution in this other thread:

> [@Concurrency of long-running operations](https://forum.openrefine.org/t/concurrency-of-long-running-operations/1009):
>
> As mentioned in [my monthly report](https://forum.openrefine.org/t/reproducibility-project-september-report/1005), I have started working on adding support for concurrent long-running operations for the 4.0 version. Here is a short video demonstrating one use case: Why work on this now? The tasks that are coming up in this project rely on one crucial architectural decision: how to represent the columnar dependencies of operations at the core of the tool. We need a representation which enables a wide range of use cases, so it's not easy to get it right. A waterfall-l…

---

_[View the full topic](https://forum.openrefine.org/t/reproducibility-project-september-report/1005)._
