Revision history [back]
 | 1 | initial version |
What is the purpose for the default type values _i, _f and _s?
The title says it all. What do psspy._i, psspy._f, and psspy._s do and why are they necessary. I have repeatedly been seeing a string of these guys being passed to calls to the PSSE API.
For example,
psspy.solution_parameters_3([_i,200,_i],[_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f])
| | 2 | Clean up code (so no need to scroll), add missing type and add reference to the PSSE recorder |
What is the purpose for the default type values _i, _f _f, _s and _s?_o?
The title says it all. What do psspy._i, psspy._f, psspy._s and psspy._spsspy._oAPI.API (particularly when examining the PSSE Python recorder output).
For example,
psspy.solution_parameters_3([_i,200,_i],[_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f])
psspy.solution_parameters_3(
[_i,200,_i],
[_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f,_f])
