"_Input_" Tables
Tables with the "_Input_" prefix are input tables added to the output database. Now, the "_Input_" tables in the output database will be named as follows:
- Old naming system: "_Input_" + {Input_Table_Name}
- New naming system: {Table_Type_ShortKey} + "_Input_" + {Input_Table_Name}
There are three methods for using Write Input to Output:
- Using the Write Input to Output button in the Output Tables window. This is available after a run is complete. See Write Input to Output for more information.
- Selecting the Write selected input data to output option (in the Reporting folder of Simulation Options) and selecting the Report column in the Data Grid. This can only be set before a run.
- Selecting the Write all input data to output option (in the Reporting folder of Simulation Options). This can only be set before a run.
- Capacity Price in RMT tables can also be automatically written using Supplmental Parameters.
With Write selected input data to output option turned on, the selected input tables will be added automatically to the output database with the prefix "{Table_Type_ShortKey} + "_Input_" + {Input_Table_Name}" at the completion of a run. Table_Type_ShortKey is a key based on Table Type of Input Table retrieved from following table:
| Table Type | ShortKey | Table Type | ShortKey | Table Type | ShortKey | ||
| Ancillary Services | Ancillary | Hydro Monthly | HydMn | Time Series Pattern | TSP | ||
| Areas | Areas | Hydro Vectors | HydVect | Time Series SubHourly | TSSH | ||
| Capacity Price | CapPrice | Link | Link | Time Series Weekly | TSW | ||
| Constraint | Constraint | Maintenance Schedule | Maint | Timeslice Definition | TimeDef | ||
| Custom Constraint | CustCon | New Resources | NewRes | Unit Conversion | UnitConv | ||
| Custom Constraint Matrix | CustConMat | Operating Pools | OpPools | Unknown | Unknown | ||
| Custom Decision Variable | CustDecVar | Operating Rules | OpRule | Zone Definition | ZoneDef | ||
| Daily Change | DayChange | ORM | ORM | Aggregate Area | AggArea | ||
| Demand | Demand | Portfolio Contract | PortCon | AURORA Zone Map | AurZonMap | ||
| Demand Collection | DemColl | Portfolio Information | PortInfo | BranchOutage | BranOut | ||
| Demand Escalation | DemEsc | Portfolio Optimization | PortOpt | Bus Load Defintion | BusLoadDef | ||
| Demand Hourly | DemHr | Portfolio Resource | PortRes | Contingency | Contingency | ||
| Demand Monthly | DemMn | Resource Dependency | ResDepend | Corridor Def | CorrDef | ||
| Demand Monthly Peak | DemMnPk | Resource Groups | ResGroup | Corridor Limit | CorrLim | ||
| Dispatch Uncertainty | DispUnc | Resource Modifier | RMT | DC Lines | DCLines | ||
| Electricity Price | ElecPrice | Resources | Resources | Filter Sets | FilSets | ||
| Emission Price | EmPrice | Risk | Risk | FTR Reporting | FTRRep | ||
| Emission Rate | EmRate | Storage | Storage | Gen Map | GenMap | ||
| Energy Conversion | EnConvers | Segment Definition | SegDef | Hub Definition | HubDef | ||
| Energy Converters | EnConvert | Supplemental Parameters | SuppParam | Individ Hours | IndHrs | ||
| Fuel | Fuel | Supply Curve | SupplyCurve | LF Area Map | LFAreaMap | ||
| General Info | GenInfo | System Diagram | SysDiag | Supplemental Area | SuppArea | ||
| Heat Rate Definitions | HRDef | Time Series Annual | TSA | Supplemental Branch | SuppBran | ||
| Hubs | Hubs | Time Series Generic | TSG | Supplemental Gen | SuppGen | ||
| Hydro Composite Reservoir | HydCompRes | Time Series Hourly | TSH | Transmission Diagnostic | TransDiag | ||
| Time Series Monthly | TSM |
NOTE: For table types not in above table, we create a custom ShortKey by joining first three letters of each word in the table, e.g., "Table Type" creates ShortKey, "TabTyp".
NOTE: The input data written to output will include the same changes used in the simulation which produced the Output tables. If the Output was created using an Active Change Set, the input tables written to output will reflect the changes in that Change Set. If the Study Case List is used, the input tables will reflect all Change Sets selected for use in the study. If multiple cases are run from the Study Case List, the input tables will reflect the Change Sets used in the first study only, since the input tables are only written once before all study cases finish. If no Change Sets are active, then only the base data will be written.
NOTE: Input tables can be written to any output database type. However, Output Queries are only compatible with xmpSQL, SQLServer and MySQL output formats.
NOTE: Column names that begin with numeric characters are proceeded by an underscore in the output database.
"_Input_" Tables
