Skip to content

Feature/storage balance 147#150

Open
j-ti wants to merge 13 commits intodevfrom
feature/storage_balance_147
Open

Feature/storage balance 147#150
j-ti wants to merge 13 commits intodevfrom
feature/storage_balance_147

Conversation

@j-ti
Copy link
Copy Markdown
Contributor

@j-ti j-ti commented Jun 29, 2020

No description provided.

@j-ti
Copy link
Copy Markdown
Contributor Author

j-ti commented Jan 14, 2021

@ciaradunks @LauWien, is this PR still interesting for you or some parts of it? There are just minor merge conflicts, which should be easy to solve

@LauWien
Copy link
Copy Markdown
Collaborator

LauWien commented Jan 14, 2021

@ciaradunks @LauWien, is this PR still interesting for you or some parts of it? There are just minor merge conflicts, which should be easy to solve
I'd prefer this PR will not be merged.

@j-ti
Copy link
Copy Markdown
Contributor Author

j-ti commented Jan 14, 2021

I'd prefer this PR will not be merged.

This was not the question. I meant merging dev into the feature-branch: So as you said some parts might still be of interest, I did it, to make it more up to date, currently untested. Previous output examples can be found within the linked issues #147 #149
It might be good to reformulate the problem and the goal which makes it easier to verify, if the current approach has to be improved, altered or abandoned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Components can only track one artificial cost, depending on one flow the inital storage level is not the end storage level

2 participants