Bonneville 电力管理局交互式潮流和暂态稳定计划_Fortran_代码_下载

# Interactive Power Flow & Transient Stability Program [](https://app.codacy.com/manual/mbheinen/bpa-ipf-tsp?utm_source=github.com&utm_medium=referral&utm_content=mbheinen/bpa-ipf-tsp&utm_campaign=Badge_Grade_Dashboard) [](https://travis-ci.com/mbheinen/bpa-ipf-tsp) [](https://bpa-ipf.readthedocs.io/en/latest/?badge=latest) Interactive Power Flow (IPF) is a family of programs for doing power flow studies. IPF models the balanced steady-state operation of an electric power network. It is used by power system planners, design engineers, and students to investigate electric power networks, determine bus voltage distribution, study real and reactive power flows in lines, check for line overloads, understand system reactive requirements, plan area controls, examine effects of load shedding, generator dropping, and line outages. IPF was originally developed by Bonneville Power Administration (BPA). IPF was made public domain by Bonneville Power Administration (BPA) back in 1994. This project is a fork of Bonneville Power Administration's Interactive Power Flow (IPF) programs including the Transient Stability Program (TSP). The original source code for this repo was obtained from ftp://ftp.bpa.gov, which no longer seems to be available. The goal of this project is to breathe life into this codebase again and continue enhancing it while preserving *all* of its legacy features. Most of the command line tools are working. Note that the original programs had a GUI component built with [Motif X Window][], but given how dated it is, most will find it cumbersome to use relative to modern applications. ## Documentation You can find complete documentation for this project [here](https://bpa-ipf.readthedocs.io/en/latest/). The documentation at that site has details on how to install it, what command line tools are available, record and command syntax for defining the model and studies, how to use the C API, how to use the GUI, and more. Most of the content on that site came from the original documentation for IPF and TSP applications in these [manuals](https://github.com/mbheinen/bpa-ipf-tsp/tree/master/manuals) so if something is missing from the ReadTheDocs site, check the manuals. Additionally, check out [John Schaad's website](http://members.efn.org/~jschaad/ipf-1.html) for some additional history on the original BPA project. ## Sample Cases There are a variety of sample cases in the [data](https://github.com/mbheinen/bpa-ipf-tsp/tree/master/data) directory of this repo. Some of them came from original IPF codebase others came from publically available cases like Texas A&M's set of synthetic cases found [here](https://electricgrids.engr.tamu.edu/electric-grid-test-cases/). None of the data is from real power system networks since such information is generally considered confidential by Transmission System Operators. ## Quick Reference If you're looking for a quick reference on using some of the IPF commands, see below. ### Batch Power Flow -- bpf Batch Power Flow (`bpf`) executes using commands from a Power Flow Control (`.pfc`) file. Users write commands in the `.pfc` to do power flow runs. The [documentation][] describes the commands available. You can try it out using test cases found in the [data](https://github.com/mbheinen/bpa-ipf-tsp/tree/master/data) directory. To run a case just run `bpf <controlfile.pfc>` or `bpf` and follow the prompts. For example, $ bpf bench.pfc The output is a Power Flow Output file `<casename>.pfo`. When you use `bpf`, you must first create a `<casename>.pfc` file with the appropriate commands to accomplish the solution task at hand. At runtime these commands are accepted by `bpf` and executed according to a logical processing order determined by the program. Hence you need not be concerned with the ordering of commands in your PFC file. Input commands will be processed first, and a solution done automatically before any output is produced. Finally, a new base (`.bse`) file will be created, if you have requested one. See the [IPF Batch Users Guide][] for more information. ### Cutting Program -- ipfcut Cuts out a section of the entire system model and prepares it to be set up for running with its own slack bus. Usage: `ipfcut <controlfile.pfc>` or `ipfcut` Output: Powerflow Network Data file `<cutcasename.bse>` This is a stand-alone program that cuts out a subsystem from a solved base case (`.bse`) file. Flows at the cut branches are converted into equivalent generation or load on specially formatted `+A` continuation bus records. An ensuing power flow run should solve with internal branch flows and bus voltages which are identical to those quantities in the original base case. In almost all cases, you will have to convert one of the buses in the cut subsystem into a slack bus, to replace the original system slack bus. Several methods are available to define the cut system: bus names, zones, base kVs, and individual branches. A pi-back feature replaces selected buses with a passive-node sequence (lines consisting of sections) with the original loads pi-backed in proportion to the line admittances. Below is a sample control file: ``` ( CUTTING, PROJECT=EWEB, CASEID=EWEBCUT1 ) >DEBUG< .>EXCLUDE_BUSES< .>INCLUDE_BUSES< .>PI_BACK_BUSES< .>SAVE_BUSES...< .>CUT_BRANCHES< >SAVE_ZONES NC,SAVE_BASES 500,230,115,69< / DEBUG, TX = ON, DC_MODEL = ON (STOP) ``` ### Batch Analysis Tool -- ipfbat The batch version of `ipfsrv`. It accepts a Power Flow Control Language (PCL) file. This is an alternate set of commands from PFC used by `bpf`. Usage: `ipfbat <controlfile.pcl>` Example of use: `ipfbat test.pcl`. The PCL commands used with `ipfsrv` and `ipfbat` (standard filename extension of `.pcl`) are described in the [IPF Advanced Users Guide] and in Appendix A of the [IPF CFLOW Users Guide]. Many of the PFC commands from Chapter 4 of this manual are supported, but not all, and there are many additional new commands. `ipfbat` allows you fine control over the case and solution engine (`ipfsrv`). When you use the PCL approach, you first create a PCL file with the appropriate commands to accomplish the solution task at hand. At runtime these commands are interpreted by `ipfbat`. The PCL file commands are processed sequentially. Additional PCL command files may be specified by name, so that a chain of PCL files may be processed in one run. See the [IPF Advanced Users Guide] for details. `ipfbat` command summary: ``` /INITIALIZE processed by p_pfinit_ /NETWORK_DATA, FILE = <filename> processed by p_gtnetdat_ /OLD_BASE, FILE = <* | filename> [, CASE = <casename>] [, REBUILD = < on | off> ] processed by cmd_parse.c p_gtbase.f ctlpow.f /CHANGES, FILE = <* | filename> processed by cmd_parse.c p_change.f ctlpow.f /SOLUTION > BASE_SOLUTION > DEBUG, BUS = ON,(page 3-51 to 3-56) processed by cmd_parse.c p_solton.f ctlpow.f /GET_DATA, TYPE = INPUT A <areaname> to be added 22 July by wlp I <area1 area2> to be added 22 July by wlp B <busname, etc> returns all data associatated with bus + <busname, etc> returns all data if id fields have wild cards (type - column 2, owner, columns 3-5, and code-year columns 20-21) X <busname, etc> L <bus1 bus2, etc> returns all paralles if id is wild card (*) returns all sections if section is 0 T <bus1 bus2, etc> R <bus1 bus2, etc> E <bus1 bus2, etc> processed by cmd_parse.c p_gtdata.f gtinput.f /G