Johannes Haux
Johannes Haux
> Great stuff! A couple of suggestions: > Let's try to ensure we use the same behavior everywhere. For example > https://github.com/pesser/edflow/blob/36a24eac501f2b4b4e2475ec88e51e9017c8c13f/edflow/eval/pipeline.py#L748 > > > https://github.com/pesser/edflow/blob/36a24eac501f2b4b4e2475ec88e51e9017c8c13f/edflow/explore.py#L133 > > > any...
Agreed! Let's implement the unified entry point handling. Nevertheless I think, we should enhance this PR to solve #255 and not start a new PR, as I am certain, that...
This is related to #241.
I have the same issue. Any progress @JeanMertz?
Seems like an upgrade to nvim version 0.10 did it for me. ``` NVIM v0.10.0-dev-2284+gf6042d5c3 Build type: RelWithDebInfo LuaJIT 2.1.1707061634 ```
:carousel_horse: is in there as well @rromb!
I would totally love it! Should you add the new functionality, could you then also add a small motivation in the documentation, why ML-Flow and pushing checkpoints to it is...
As stated in #210 I would recommend using `edflow.util.update` to stack configs (See the example there). I will implement this behavior and make a PR.
This would be a first step in the direction of #50.
Implemented in #254