Jonas I. Liechti

Hi @dhvalden > `pak` does highlight the missing system dependencies but does not install them automatically (at least in my case). That is actually quite useful to know. With NixOS...

`coverage combine coverage.*` should be the appropriate command in this particular case (though I didn't test it). When deviating from the `.coverage.*` syntax the action would probably need to know...

👋 @YasAsgari I see. The description might be somewhat misleading. The `extra_attrs` is an attribute to https://github.com/alexbovet/flow_stability/blob/434caf46c06f57d41ea983ea3708f7c5d1508894/src/flowstab/temporal_network.py#L53 ... https://github.com/alexbovet/flow_stability/blob/434caf46c06f57d41ea983ea3708f7c5d1508894/src/flowstab/temporal_network.py#L70-L72 A minimal example would look like this: ```python from flowstab.temporal_network import...

We should first decide for what elements we need to be able to store data: - temporal network - single event - single edge (i.e. node-pair) - single node Once...

We can easily enable the 3. When initiating an object, like an instance of a temporal network, `**kwargs` are the foreseen default for optional keyword arguments. This is a python...

:sweat_smile: thanks a lot for correcting those @YasAsgari

`FlowStability` instances are `pickle`-able so they can be stored with the `pickle` module. If we wanted a "save" way to store and shre `FlowStability` instances then we might want to...

Or would we want to export only the laplacian matices and need a dedicated method for this?

Would the goal be to save `inter_T`s on their own? It the idea is to simply be able to store and reload a `FlosStability` instance then I'd simply pickle it....

Smart ways in what way? If reducing resource usage is the goal, then a more dynamic approach of importing/exporting to disk might make sense. Maybe that the matrices reside by...