-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
v0.3.24. (1) Updare pysteps to fix bug when returning str in Python 3…
…. (2) Add function to export shadowed or equivalent bus pair when export powerflow data with export_zero_impedance_line is false. (3) Fix bug when exporting powerflow data with export_zero_impedance_line is false by updating bus type of the equivalent bus.
- Loading branch information
Showing
20 changed files
with
3,134 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,3 +2,27 @@ Simulation Toolkit for Electrical Power Systems | |
Maintainer: Changgang Li <[email protected]> | ||
Please go to http://steps.drli.group:380 for documentation. | ||
|
||
How to build: | ||
1) Select which LA solver is to be used | ||
Open STEPS.cbp and go to header/basic/sparse_matrix_define.h. Comment the solver you don't want to use. | ||
For example, if you want to keep only c_sparse, comment out umfpack and klu. | ||
Then go to source/basic/sparse_matrix_klu.cpp and umfpack.cpp, disable 'compile' and 'link' options of the two files. | ||
2) Go compile the LS solver. | ||
For example, open csparse.cbp, and compile CSparse. The target should be 'static library' | ||
3) Go compile the CppTest. | ||
Open cpptest.cbp, and compile CppTest. The target should be 'static library' | ||
4) Build STEPS | ||
In the linker settings, you should include the above two static libraries libCSparse.a and libCpptest.a. | ||
Then compile the STEPS. | ||
5) If you want to build a 64bit version, use 64 bit MinGW and select the X64 version compiler. | ||
|
||
If you want to compile a complete version, follow the steps: | ||
1) Compile BLAS as static library | ||
2) Compile UMFPACK as static library | ||
3) Compile CSparse as static library | ||
4) Compile CppTest as static library | ||
5) Compile STEPS as dynamic library or exectuable file. Include libUMFPACK.a, libBLAS.a, libCSparse.a, and libCpptest.a. Put libBLAS.a after libUMFPACK.a. | ||
|
||
When compiling in Windows, remove -no-pie and -lgfortran options and remove libKLU.a, libBLAS.a, libUMFPACK.a | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.