garden VS epanet-js

https://github.com/davvid/garden

Project Description: Garden is a git multi-repo powertool. Garden lets you define custom workflows over arbitrary collections of git trees.

If you find yourself running bespoke commands across a smattering of git repositories then Garden can be a big improvement over a big pile o' scripts and repos.

What do you want to be tested: Test the documented feature-set and new-user onboarding experience. Give feedback on its usefulness as a development/testing aid.

Contact Info: Open an issue on the project page

If you're into this kinda thing then then you might be interested in my take on improving over a "big pile o scripts" (and repos).

https://github.com/davvid/garden

Garden is a multi-repo powertool for running custom commands and mashing random shell scripts and loosely-coupled repos into a version-controllable config file. If you're weird like me you might like it.

I ended up with so many random git repos, shell scripts and other miscellany that I ended up writing a tool to manage that stuff using a yaml file so that it's easy to transport and recreate my setup anywhere.

"garden" is kinda like a mashup of the flexibility/power of shell scripts with the convenience of being able to declare your development environment.

https://github.com/davvid/garden

I was kinda surprised when someone submitted the first issue =)

https://github.com/davvid/garden/issues/1

git-cola was pretty much written for my own personal use, but it grew a few more users as well.

At the start up I work at [0], we use an open source library I developed to run hydraulic models of water networks in JavaScript [1].

A hydraulic model may be between 1-10MB and the simulation results can end up being 100+MB of time series data.

Other vendors with proprietary engines have to scale up servers to run their simulation engineers and will store and serve up results from a database.

Having everything done locally means we only have to store a static file and offload the simulation to the client.

Because we've architected it this way our hosting costs are low and users generally have faster access to results (assuming they're running a moderately decent machine)

[0] https://qatium.com/

[1] https://github.com/modelcreate/epanet-js

I'm a civil engineer and I wrote an open source library that compiled a C library to javascript for my own personal projects - epanet-js [1]

A water utility in Spain spun off a start up called Qatium [2] and they used my library as the engine of their simulations and asked me to join.

[1] https://github.com/modelcreate/epanet-js

[2] https://qatium.com/

I created a handful of application around water engineering/modelling [1], plus an open source library to run the simulations in javascript [2].

A water utility in Spain spun off a start up to create a similar web based water modelling application and they used my open source library.

They approached me and I joined them and have been able to maintain the open source library as part of my role.

[1] https://github.com/modelcreate/epanet-js#featured-apps

I work as a water engineer, specializing in building hydraulic models so water utilities can simulate their network.

A big part of that is calibrating them which can be time consuming, you look through hundreds of options. I create a few web based apps to help grind through these tasks but ultimately they were for my own use as a consultant to close projects quickly.

I did pull out the engine as its own open source library for other to use, and that ended up helping me get my current role where I can now maintain it and be paid at the same time.

https://github.com/modelcreate/epanet-js

https://github.com/modelcreate/epanet-js

I've built a few open source apps and few other little projects to help automate my workflow.

There are only a handful of providers of modelling software, most are commercial and one recently sold to Autodesk for $1B.

Not sure I'll convince the industry to change but I'm enjoying tinkering around and making my own small difference.