Jupyter Notebook allows users to create and share documents that contain code, equations, visualizations and explanatory text. It supports interactive coding in over 40 programming languages. Notebooks contain cells that can contain code, equations, visualizations or explanatory text. Kernels run the code cells and communicate results. Common kernels include IPython for Python and IRkernel for R.
The document discusses the input-output structure of process flowsheets. It explains that the input-output structure focuses on raw materials fed into the process and products and byproducts removed. There are two main structures, with the difference being whether a gaseous feed or byproduct is present. Six key questions must be answered to determine the input-output structure, including whether to purify feeds, recover byproducts, use gas recycling, and how many product streams. Guidelines are provided for each question. The document then applies this framework to a hydrodealkylation (HDA) process example.
A conceptual design involves selecting appropriate equipment, configuring that equipment optimally, and determining optimum operating conditions to develop the best flowsheet for a chemical process. Decisions about equipment selection and configuration are discrete, while operating conditions are continuous variables. The conceptual design problem is formulated as a mixed-integer nonlinear programming (MINLP) optimization problem.
Process synthesis proceeds in a hierarchical manner from outer sub-problems like the utility system and heat exchanger network to inner sub-problems of separation and reactor design. A typical example of a chemical process is presented for the hydrodealkylation of toluene to produce benzene. The flowsheet is then simplified in stages to illustrate the hierarchical decisions involved in conceptual design.
This document discusses key input information needed for conceptual design of chemical processes, including reaction conditions, production rates, product purity requirements, raw material properties, and cost data. It also compares batch and continuous processes. Batch processes are generally used for small production rates below 1 million pounds per year, when multiple products are made using the same equipment, or when materials rapidly foul equipment or reactions are too slow for continuous operation. Continuous processes are better for higher production rates above 10 million pounds per year. The document provides guidelines to select between batch and continuous processes for conceptual design.
The document discusses the design of a separation system for a chemical process. It begins by outlining the general structure of a separation system, which can include a liquid separation system, vapor recovery system, or both depending on whether the reactor effluent is liquid, gas, or two-phase.
It then discusses methods for approximating flash calculations to determine the phase split from a reactor. The document also provides heuristics for deciding the location of a vapor recovery system and types of vapor recovery systems.
Finally, it outlines the key decisions that must be made in designing the liquid separation system, including how to remove light ends, where to send the light ends, whether to recycle or split azeotropes
This document discusses the recycle structure design level for a chemical process. It addresses questions like how many reactor systems and recycle streams are required. Using examples, it explains how to determine the number of recycle streams based on boiling points of components leaving the reactor. The document also discusses whether excess reactants should be used, if a gas compressor is needed, and how to determine the reactor heat requirements and temperature changes.
This document discusses heat exchanger network design and the pinch analysis method. It introduces the concept of the pinch point, which divides the problem into a heat source and heat sink. The three golden rules of pinch are presented: do not use hot or cold utilities across the pinch, and keep the heat source and sink separate below and above the pinch. An example problem is shown to illustrate determining the minimum hot and cold utility targets based on the pinch temperature.
This document discusses heat exchanger network representation and the minimum number of heat exchangers needed. It explains that a grid diagram more clearly shows the pinch point in a heat exchanger network than a conventional flowsheet. The document also provides an example problem to demonstrate how to calculate the minimum number of heat exchangers needed using the number of streams, utilities, and whether any loops or independent systems exist.
Jupyter Notebook allows users to create and share documents that contain code, equations, visualizations and explanatory text. It supports interactive coding in over 40 programming languages. Notebooks contain cells that can contain code, equations, visualizations or explanatory text. Kernels run the code cells and communicate results. Common kernels include IPython for Python and IRkernel for R.
The document discusses the input-output structure of process flowsheets. It explains that the input-output structure focuses on raw materials fed into the process and products and byproducts removed. There are two main structures, with the difference being whether a gaseous feed or byproduct is present. Six key questions must be answered to determine the input-output structure, including whether to purify feeds, recover byproducts, use gas recycling, and how many product streams. Guidelines are provided for each question. The document then applies this framework to a hydrodealkylation (HDA) process example.
A conceptual design involves selecting appropriate equipment, configuring that equipment optimally, and determining optimum operating conditions to develop the best flowsheet for a chemical process. Decisions about equipment selection and configuration are discrete, while operating conditions are continuous variables. The conceptual design problem is formulated as a mixed-integer nonlinear programming (MINLP) optimization problem.
Process synthesis proceeds in a hierarchical manner from outer sub-problems like the utility system and heat exchanger network to inner sub-problems of separation and reactor design. A typical example of a chemical process is presented for the hydrodealkylation of toluene to produce benzene. The flowsheet is then simplified in stages to illustrate the hierarchical decisions involved in conceptual design.
This document discusses key input information needed for conceptual design of chemical processes, including reaction conditions, production rates, product purity requirements, raw material properties, and cost data. It also compares batch and continuous processes. Batch processes are generally used for small production rates below 1 million pounds per year, when multiple products are made using the same equipment, or when materials rapidly foul equipment or reactions are too slow for continuous operation. Continuous processes are better for higher production rates above 10 million pounds per year. The document provides guidelines to select between batch and continuous processes for conceptual design.
The document discusses the design of a separation system for a chemical process. It begins by outlining the general structure of a separation system, which can include a liquid separation system, vapor recovery system, or both depending on whether the reactor effluent is liquid, gas, or two-phase.
It then discusses methods for approximating flash calculations to determine the phase split from a reactor. The document also provides heuristics for deciding the location of a vapor recovery system and types of vapor recovery systems.
Finally, it outlines the key decisions that must be made in designing the liquid separation system, including how to remove light ends, where to send the light ends, whether to recycle or split azeotropes
This document discusses the recycle structure design level for a chemical process. It addresses questions like how many reactor systems and recycle streams are required. Using examples, it explains how to determine the number of recycle streams based on boiling points of components leaving the reactor. The document also discusses whether excess reactants should be used, if a gas compressor is needed, and how to determine the reactor heat requirements and temperature changes.
This document discusses heat exchanger network design and the pinch analysis method. It introduces the concept of the pinch point, which divides the problem into a heat source and heat sink. The three golden rules of pinch are presented: do not use hot or cold utilities across the pinch, and keep the heat source and sink separate below and above the pinch. An example problem is shown to illustrate determining the minimum hot and cold utility targets based on the pinch temperature.
This document discusses heat exchanger network representation and the minimum number of heat exchangers needed. It explains that a grid diagram more clearly shows the pinch point in a heat exchanger network than a conventional flowsheet. The document also provides an example problem to demonstrate how to calculate the minimum number of heat exchangers needed using the number of streams, utilities, and whether any loops or independent systems exist.
The document discusses heat exchanger network design for maximum energy recovery. It provides examples of dividing a problem at the pinch temperature, starting matches at the pinch and moving away while following design rules. These rules include observing that heat capacity flowrates out must be greater than or equal to those in for each match. The document also discusses filling in matches, maximizing loads, and breaking loops to reduce the number of exchangers. An exercise problem is presented with its solution network shown.
This document discusses stream splitting techniques for process integration above and below the pinch point. Above the pinch, a cold stream can be split if the number of hot streams is less than or equal to the number of cold streams. Below the pinch, a hot stream can be split if the number of hot streams is greater than or equal to the number of cold streams. The general rule is the number of streams out must be greater than or equal to the number of streams in. An example problem demonstrates splitting a hot stream to enable feasible heat matches above and below the pinch.
This document discusses object-oriented design (OOD) and the software development life cycle using a temperature conversion program as an example. It goes through the 5 phases of software development: problem analysis, design, implementation, testing, and maintenance. For the design phase, it specifically uses object-centered design (OCD) which involves describing the program behavior, identifying problem objects and operations, and developing an algorithm. It then shows how to implement this algorithm in C++ code. Testing and maintenance are also briefly discussed.
This document provides an introduction to programming and describes the evolution of programming languages from machine language to modern high-level languages. It discusses how early programs were written in complex machine language, which led to the creation of assembly languages and assemblers to simplify the programming process. However, assembly languages were still not portable between different machines. This drove the development of high-level languages and compilers, which translate easy-to-read code into machine-readable instructions, enabling programming at a higher conceptual level and improved portability across systems.
This document provides guidance on sizing, selecting, and installing pressure-relieving devices in refineries. It discusses various types of pressure relief devices including pressure relief valves, rupture disk devices, pin-actuated devices, and other types. It also outlines procedures for sizing pressure relief devices, determining relief requirements, effective area and discharge coefficients, and considering back pressure effects. The document is intended to supplement ASME boiler and pressure vessel codes and provide best practices for ensuring safety.
Stock management in hospital pharmacy using chance constrained model predicti...hesam ahmadian
This document proposes using chance-constrained model predictive control (CC-MPC) to manage stock levels of drugs in a hospital pharmacy. CC-MPC can handle the uncertainties in drug demand and delivery times while optimizing objectives like meeting demand, minimizing costs and number of orders. It formulates constraints probabilistically rather than deterministically to provide a tradeoff between conservatism and efficiency. The approach is assessed for its potential implementation in two Spanish hospitals.
The document discusses heat exchanger network design for maximum energy recovery. It provides examples of dividing a problem at the pinch temperature, starting matches at the pinch and moving away while following design rules. These rules include observing that heat capacity flowrates out must be greater than or equal to those in for each match. The document also discusses filling in matches, maximizing loads, and breaking loops to reduce the number of exchangers. An exercise problem is presented with its solution network shown.
This document discusses stream splitting techniques for process integration above and below the pinch point. Above the pinch, a cold stream can be split if the number of hot streams is less than or equal to the number of cold streams. Below the pinch, a hot stream can be split if the number of hot streams is greater than or equal to the number of cold streams. The general rule is the number of streams out must be greater than or equal to the number of streams in. An example problem demonstrates splitting a hot stream to enable feasible heat matches above and below the pinch.
This document discusses object-oriented design (OOD) and the software development life cycle using a temperature conversion program as an example. It goes through the 5 phases of software development: problem analysis, design, implementation, testing, and maintenance. For the design phase, it specifically uses object-centered design (OCD) which involves describing the program behavior, identifying problem objects and operations, and developing an algorithm. It then shows how to implement this algorithm in C++ code. Testing and maintenance are also briefly discussed.
This document provides an introduction to programming and describes the evolution of programming languages from machine language to modern high-level languages. It discusses how early programs were written in complex machine language, which led to the creation of assembly languages and assemblers to simplify the programming process. However, assembly languages were still not portable between different machines. This drove the development of high-level languages and compilers, which translate easy-to-read code into machine-readable instructions, enabling programming at a higher conceptual level and improved portability across systems.
This document provides guidance on sizing, selecting, and installing pressure-relieving devices in refineries. It discusses various types of pressure relief devices including pressure relief valves, rupture disk devices, pin-actuated devices, and other types. It also outlines procedures for sizing pressure relief devices, determining relief requirements, effective area and discharge coefficients, and considering back pressure effects. The document is intended to supplement ASME boiler and pressure vessel codes and provide best practices for ensuring safety.
Stock management in hospital pharmacy using chance constrained model predicti...hesam ahmadian
This document proposes using chance-constrained model predictive control (CC-MPC) to manage stock levels of drugs in a hospital pharmacy. CC-MPC can handle the uncertainties in drug demand and delivery times while optimizing objectives like meeting demand, minimizing costs and number of orders. It formulates constraints probabilistically rather than deterministically to provide a tradeoff between conservatism and efficiency. The approach is assessed for its potential implementation in two Spanish hospitals.
4. ﮔﺰﻳﻨﻪ اﻧﺘﺨﺎب ورودي ﻣﺘﻐﻴﺮﻫﺎي ﺗﻌﺮﻳﻒ ﻳﺎ و اﻧﺘﺨﺎب ﺑﺮاي دﻳﮕﺮ راه
New
اﺳﺘﻔﺎده ﺳﭙﺲ و
ﺎﻧﻪ ز از
data
ﻨ د
creat Network or data
ﺖ ا زﺑﺎﻧﻪ از
data
ﻣﻨﻮي در
creat Network or data
اﺳﺖ
