Rodrigo Amaro e Silva

@gschwind also suggested the following workaround (example code below): - before running calliope, make python run in a separate child process with `os.fork()` - import the calliope module in each...

@brynpickering and @sjpfenninger, I just noticed calliope was updated less than 2 months ago, now using more recent versions of `pandas`, `pyomo` and `xarray`. Do you think this may fix...

FYI, just found out that the os.fork() is limited to Linux or WSL. https://github.com/rq/rq/issues/859

@brynpickering I know I don't have one, but if you tell me what an MWE is I can try to get it :-)

Minimal working example below (it's a bit more complicated than this, but this gets the gist of it). ``` file_base_name_index = { 0: 'ParamBase15min_10app_colSC_freeExport.nc', 1: 'Disc25_15min_10app_colSC_freeExport.nc' } for count, sce...

@brynpickering, thanks for the feedback! This will be my first time profiling memory consumption and, as usual, I found out several packages for this purpose (e.g., `objgraph`, `PySizer`, `Heapy`, `guppy3`,...

@brynpickering, any insights on this? thanks for all your support.

I didn't mention this in the initial post (as it does not add value), but having such functionality would also allow to implement scale-dependent technologies (e.g. PV capacity intervals with...

Regarding the first point, as long as it is explicitly mentioned, the "finite but very large `energy_cap_max`" seems quite reasonable. About the other issue, do you believe that such update...

> Ok, waiting until January it is! Great to hear about this. To be honest, the past few months were terrible and I had to stop working on #2529 and...