-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ImpactFuncSet.__init__ #568
Conversation
Remove initialization with set because it does not guarantee insertion order.
# Conflicts: # climada/entity/impact_funcs/impact_func_set.py # climada/entity/impact_funcs/test/test_imp_fun_set.py # doc/tutorial/climada_engine_Forecast.ipynb
@peanutfun - what needs yet to be done before this is ready to merge? |
Hm, seems like I missed some occurances of the constructor. Thanks for adding them, @emanuel-schmid! I was wondering if we should keep the Otherwise, from what I can see, this is ready to go! |
Valid point. Though, the whole |
🙌 |
* Add all ImpactFunc attributes to ImpactFunc.__init__ * Add type hints to ImpactFunc.__init__ * Update ImpactFunc classmethods to new init * Update tests to new ImpactFunc.__init__ * Update docs on InputVar regarding ImpactFunc * Update tutorials with new ImpactFunc.__init__ * Update ImpactFunc.__init__ docstring * Update argument order of ImpactFunc.__init__ * Fix linter issue * Update tests to new ImpactFunc.__init__ * Update tutorials with new ImpactFunc.__init__ * Enable passing impact funcs to ImpactFuncSet constructor * Update code base to new ImpactFuncSet constructor * Fix unit test of ImpactFuncSet Remove initialization with set because it does not guarantee insertion order. * undo re-plotting * Incorporate new ImpactFuncSet.__init__ method Co-authored-by: emanuel-schmid <schmide@ethz.ch>
Changes proposed in this PR:
ImpactFunc
s to theImpactFuncSet
constructorNote: This is branched off #550, which should be merged before this branch.
PR Author Checklist
develop
)PR Reviewer Checklist