Closed Zhuoran29 closed 1 month ago
@Zhuoran29 can you run black so we can see the results of the GH tests please?
@Zhuoran29 can you run black so we can see the results of the GH tests please?
Sure, it seems the cost package is not adjusted well and I'll look into it.
I added the costing package from the WaterTAP repo and a test file for the flowsheet, where both simulation and optimization modes were tested.
Hey @kurbansitterley @adam-a-a , forgot to tag you when I updated this PR.
I have just noticed both watertap-org/watertap#1482 and watertap-org/watertap#1487 that are modifying either the unit model itself or the property package it uses. If we are going to inherit Crystallization
for the MultiEffectCrystallizer
, we might want to wait to see what changes are made there, especially if we want to keep updating the watertap dependency.
My other general comment is we definitely want to document the single and multieffect models thoroughly--though that can happen in a subsequent PR down the line and shouldn't hold this up.
I ran a few cases and the results are looking good to me! Also I added a test for an optimization scenario in case it's helpful to the case study. If the additions look good to you then I think it's good to go, but please feel free to not include it. @kurbansitterley
This PR adds:
CrystallizerEffect
unit modelMultiEffectCrystallizer
unit model that is comprised of nCrystallizerEffect
unit models connected via constraintsMultiEffectCrystallizer
andCrystallizerEffect
watertap==1.0.0rc0
in setup.pyTODO:
CrystallizerEffect
flow_vol_phase['Vap']
is the proper flow to cost for steam