-
Notifications
You must be signed in to change notification settings - Fork 34
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
Better batch design #170
Comments
Good point! This not something I plan on taking care of any time soon, but it would be great to have as an option (to assume a given loading time). The following would need to be implemented: add optional loading_time argument to size_batch method (and code). Thanks! |
If you would like to work on this, I would be happy to help through the process and review. Thanks! |
Thanks! Handling just the case of StirredTankReactor seems straightforward. I may visit this if I find more time in the coming weeks. |
Streams currently only support continuous flow as volume, mass or molar units per hour.
This leads to non-obvious unit designs when operating in batch mode. For example, a StirredTankReactor should be able to take its feed from a StorageTank and Pump combination to load much faster than what the continuous flow mode would allow. The current implementation of batch design for StirredTankReactor assumes that the continuous feed is being used to load one reactor at a time. This is inefficient utilization of each reactor, especially if you want to stagger fewer number of reactors, or if residence time in the reactors is very long.
The text was updated successfully, but these errors were encountered: