![]() ![]() Slack line regions significantly change the hydraulics of the pipeline operations, particularly the behavior of transients. Slack line flow behavior is of interest to pipeline operators for a number of reasons:įrictional head loss in slack regions is much greater than in tight line regions. On one large pipeline, slack volumes are in the tens of thousands of barrels. On others, slack line flow was expected as a normal part of the operation. ![]() Since the simulation software was not designed to handle the slack line flow, simulations during those periods were inaccurate. Again, the pipeline operators were unaware of this condition until real time simulation so&are was installed. On another, slack line flow occurred only during some upsets. In this case, the total slack volume (volume of vapor bubble) was only 50 to a few hundred barrels in size. However, until the real time simulation software was installed, the pipeline operators were unaware of its occurrence. On one, slack line flow existed almost all of the time. Slack line flow occurs only during abnormal pipeline operations.Įxperiences installing real time simulation software on a number of liquid pipelines over the last 15 years have included the following: Slack line flow occurs occasionally during normal pipeline operations. Slack line flow occurs all of the time in some section of the pipeline. Most liquid pipelines fall into one of the following categories: This flow condition is very common in liquid pipelines. Suppose we have an eno document shopping_list.Slack line flow is a phenomena in which a pipeline transporting a liquid product develops vapor bubbles at points at which the pipeline pressure falls below the vapor pressure of that liquid. Given schema=my_schema.eno an eno document is generated that reflects the input document/schema but adds in missing schema annotations that are automatically inferred from the document (variable names, types, required/optional), thereby turning a document or incomplete schema into a fully specified, unambiguous schema. Given javascript=my_parser.js the javascript parser code for the given document/schema is generated and output into my_parser.js. javascript=db_conf_parser.js or schema=db_conf_schema.eno Note that there is actually no distinction between a document and a schema - you can take a real document and write schema annotations for only a few elements (the rest will be inferred), or generate a schema from a raw document and then make changes to the generated schema, this is quite flexible. Some loose ends need to be tied up before this is ready for release, meanwhile you can git clone the repository and run the CLI from the repository root as described below. Written for the current implementation state in the javascript/node environment, see above for upcoming features. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |