Recent Releases of emf

emf - Version 4.4 - 05/08/2025

EMF

  • Enable login via single sign-on (SSO)

- Java
Published by cseppan about 1 year ago

emf - Version 4.3 [patch] - 02/2025

CoST

Control Measure Database updates CMDB_2025-02-27.zip

- Java
Published by cseppan over 1 year ago

emf - Version 4.3 [patch] - 11/13/2024

EMF

  • Remove the Spring framework from the EMF server

- Java
Published by cseppan over 1 year ago

emf - Version 4.3 - 04/04/2024

EMF

  • Fix errors when running QA steps due to generated datasets having stored table names longer than 63 characters
  • Fix errors when downloading exported datasets containing non-ASCII characters

CoST

  • Add 2019 through 2022 to the Cost Year menu in the Control Measure Manager
  • Correct the implementation of Equation Type 13 so that O&M costs are calculated using total emissions instead of the emissions reduction

Upgrading from v4.2.1

Download the necessary update files

Control measure database updates

costequationsv2.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons-0.7.jar

Database updates

Before starting, shut down the Tomcat server.

Update stored procedures:

\i costequationsv2.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v4.3 - 04/04/2024' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan over 2 years ago

emf - Version 4.2.1 - 12/20/2023

EMF

  • Restrict the sector selection lists shown in the case setup interface to only the sectors listed on the case summary
  • Grow the Name Contains search field when the Data Manager window is made bigger

Upgrading from v4.2

Download the necessary update files

New client JAR files

emf-client.jar

EMF server updates

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v4.2.1 - 12/20/2023' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

- Java
Published by cseppan over 2 years ago

emf - Version 4.2 [patch 2] - 06/14/2023

EMF

  • Update library dependencies for EMF server

- Java
Published by cseppan about 3 years ago

emf - Version 4.2 [patch] - 05/01/2023

EMF

  • Fix errors when purging and importing control measure database files

- Java
Published by cseppan about 3 years ago

emf - Version 4.2 - 03/06/2023

EMF

  • Include input and parameter names as comments when building case run scripts
  • Add option to copy inputs and parameters when copying a job within a case
  • Hide "Compare Dataset Fields" from list of QA programs when creating a new QA step
  • Add new QA program "Compare Multiple Datasets"
  • Use Apache Ivy for dependency management, update to newer library versions

Upgrading from v4.1

Download the necessary update files

New server WAR file

emf.war

New client JAR files

emf-client.jar emfv4.2libs.zip

Control measure database updates

CMDB_2022-05-25.-.DEV.zip

Database updates

Before starting, shut down the Tomcat server.

Add new QA program: sql INSERT INTO emf.qa_programs (name, run_classname) VALUES ('Compare Multiple Datasets', 'gov.epa.emissions.framework.services.qa.comparedatasets.SQLCompareMultipleDatasetsProgramQueryRunner');

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v4.2 - 03/06/2023' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Replace the contents of the EMF/lib client directory with the jar files in the emfv4.2libs.zip archive.

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the CMDB_2022-05-25.-.DEV.zip set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan over 3 years ago

emf - Version 4.1 - 06/27/2022

EMF

  • Strengthen password requirements including increasing the minimum length to 12 characters and requiring the password to include numbers or symbols
  • Automatically disable accounts after 5 failed login attempts
  • Add options for administrators to disable accounts, see failed login attempts, and see when passwords were last updated

Upgrading from v4.0

Download the necessary update files

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Add fields to the users table: sql ALTER TABLE emf.users ADD COLUMN last_reset_date TIMESTAMP; ALTER TABLE emf.users ADD COLUMN failed_login_attempts INT DEFAULT 0;

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v4.1 - 06/27/2022' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan about 4 years ago

emf - Version 4.0 - 02/28/2022

EMF

  • Completed updates to core EMF for better accessibility
  • Added matching by region code and facility ID to temporal allocation functionality

CoST

  • Updated control strategy dataset types to handle longer data fields
  • Added equation type 21 for use by non-EGU SO2 control measures

Upgrading from v3.10.1

Download the necessary update files

Control measure database updates

CostSchemaUpgrade.v4_0.sql costequationsv2.sql populateleastcoststrategyworksheet.sql runmaxemisredstrategy.sql runmultipollutantmaxemisredstrategy.sql

Temporal allocation updates

createdailytemporalallocationxref.sql createmonthlytemporalallocationxref.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar analysis-engine.jar epa-commons.jar log4j-1.2.17-rhel.jar

Database updates

Before starting, shut down the Tomcat server.

Update dataset type and add new cost equation:

\i CostSchemaUpgrade.v4_0.sql

Update stored procedures:

\i costequationsv2.sql \i populateleastcoststrategyworksheet.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i createdailytemporalallocationxref.sql \i createmonthlytemporalallocationxref.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v4.0 - 02/28/2022' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new analysis-engine.jar, epa-commons.jar, and log4j-1.2.17-rhel.jar files into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan over 4 years ago

emf - Version 3.10.1 - 11/04/2021

EMF

  • Fix bug that prevents editing a case job

Upgrading from v3.10

Download the necessary update files

New client JAR file

emf-client.jar

EMF server updates

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.10.1 - 11/04/2021' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

- Java
Published by cseppan over 4 years ago

emf - Version 3.10 - 10/29/2021

EMF

  • Enhancements to keyboard navigation and screen reader compatibility
  • Improve user interface focus after refreshes are performed
  • Add feedback when an action can't be performed due to no item being selected
  • Fixes to incorrect tooltips and added button shortcuts
  • Added ability to type in more letters to the Show Datasets of Type menu in the Dataset Manager

Upgrading from v3.9.1

Download the necessary update files

New client JAR files

emf-client.jar epa-commons.jar

Control measure database updates

CMDB_2021-09-02.zip

EMF server updates

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.10 - 10/29/2021' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the CMDB_2021-09-02.zip set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan over 4 years ago

emf - Version 3.9.1 - 06/07/2021

EMF

  • Temporarily remove accessibility updates to the data viewer and editor tables that cause issues with the column headers scrolling in Java 8

Upgrading from v3.9

Download the necessary update files

New client JAR files

emf-client.jar

EMF server updates

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.9.1 - 06/07/2021' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

- Java
Published by cseppan about 5 years ago

emf - Version 3.9 - 05/30/2021

CoST

  • Update design capacity checks in cost equations to check that values are greater than 0.1 MW/hr rather than just greater than 0
  • Ensure all design capacity checks in cost equations use consistent units
  • Add design capacity check to equation type 2a to be consistent with other equation type 2 variants
  • Fix errors running control strategies by truncating SCC descriptions when creating result datasets

EMF

  • Fix issues with window focus when closing windows
  • Enhancements to keyboard navigation and screen reader compatibility
  • Change default sizes of windows to better fit contents
  • Enable the User's Guide option in the Help menu
  • Add shortcut Ctrl+Shift-S to open the Status window
  • Automatically open the Dataset Manager window when starting the EMF Client
  • Check for spaces in filenames when trying to upload or import files

Upgrading from v3.8

Download the necessary update files

Control measure database updates

CMDB_2021-03-11.zip

costequationsv2.sql populateleastcoststrategyworksheet.sql runmaxemisredstrategy.sql runmultipollutantmaxemisredstrategy.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar analysis-engine.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Update stored procedures:

\i costequationsv2.sql \i populateleastcoststrategyworksheet.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.9 - 05/30/2021' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new analysis-engine.jar and epa-commons.jar files into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the CMDB_2021-03-11.zip set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan about 5 years ago

emf - Version 3.8 - 03/08/2021

CoST

  • Log inventory sources with >= 100% control and non-zero emissions in the Strategy Messages dataset
  • Update calculation of projected inventory percent reduction for add-on controls
  • Update check for existing control at >= 100% when considering replacements in PFYI strategy
  • Add equation type 2c based on existing type 2 with design capacity in HP

EMF

  • Enhancements to keyboard-only navigation
  • Label error messages that were previously only indicated by color

Upgrading from v3.7

Download the necessary update files

Control measure database updates

CostSchemaUpgradev38.sql CMDB_2021-02-25.zip

costequationsv2.sql createprojectedfutureyearinventory.sql populateprojectfutureyearinventorystrategymessages.sql populatestrategymessages.sql runprojectfutureyearinventory.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar analysis-engine.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Add Equation Type 2c and its parameters:

\i CostSchemaUpgradev38.sql

Update stored procedures:

\i costequationsv2.sql \i createprojectedfutureyearinventory.sql \i populateprojectfutureyearinventorystrategymessages.sql \i populatestrategymessages.sql \i runprojectfutureyearinventory.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.8 - 03/08/2021' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new analysis-engine.jar and epa-commons.jar files into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the CMDB_2021-02-25.zip set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan about 5 years ago

emf - Version 3.7 - 08/17/2020

CoST

  • Add search options when selecting control programs for Project Future Year Inventory control strategies, and in the Control Program Manager
  • Add .csv suffix when exporting various control strategy result datasets
  • Fix issue saving edited control measure equation changes
  • Fix end condition for least cost narrowing algorithm
  • Add option to include dataset_id column when exporting flexible format datasets from control strategies
  • Update naming for combined strategy detailed results file to use control strategy name

EMF

  • Update case job cancelling for jobs that are started locally (not via SSH)

Upgrading from v3.6

Download the necessary update files

Control measure database updates

CostSchemaUpgradev37.sql narrowinonleastcost_target.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Add EXPORT_SUFFIX keyword for control strategy result types:

\i CostSchemaUpgradev37.sql

Update stored procedures:

\i narrowinonleastcost_target.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.7 - 08/17/2020' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan almost 6 years ago

emf - Version 3.6 - 05/15/2020

CoST

  • Fix a memory issue when creating controlled inventories from Least Cost control strategies
  • Clarify the description of replacement control measure handling on the Control Strategy Constraints tab
  • Update control strategies to not apply controls to inventory sources with existing control efficiencies over 100%
  • Update cost equation type 2b to only apply to sources whose design capacity is less than 1500 HP
  • Fix description for cost equation type 1
  • Add option to export multiple Strategy Detailed Results in a single file
  • Add quick search to the Control Strategy Manager window

EMF

  • Add quick search to the Dataset Type Manager window

Upgrading from v3.5

Download the necessary update files

Control measure database updates

costequationsv2.sql populateleastcoststrategyworksheet.sql runmaxemisredstrategy.sql runmultipollutantmaxemisredstrategy.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Update stored procedures:

\i costequationsv2.sql \i populateleastcoststrategyworksheet.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql

Update equation description:

sql UPDATE emf.equation_types SET equation = 'Scaling Factor = (Model Plant boiler capacity / MW) ^ (Scaling Factor Exponent) Capital Cost = Capital Cost Multiplier x Design Capacity x Scaling Factor x 1,000 Fixed O&M = Fixed O&M Cost Multiplier x Design Capacity x Scaling Factor x 1,000 Variable O&M = Variable O&M Cost Multiplier x Design Capacity x Capacity Factor x 8,760' WHERE name = 'Type 1';

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.6 - 05/15/2020' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan about 6 years ago

emf - Version 3.5 - 10/23/2019

CoST

  • Update reference year cost-per-ton storage to use double precision
  • Update implicit price deflators, used for cost year conversions, using values from August 2019
  • Simplify cost equation type 8 (used for non-EGU PM2.5 controls) and add a new equation type 20 (used for ICI boilers)
  • Revisions to the control measure database
  • Add additional columns to the Control Strategy Detailed Result Extended dataset type, to contain inventory data used in cost equation calculations
  • Fix errors running control strategies on inventories with no sector set

Upgrading from v3.4

Download the necessary update files

Control measure database updates

CostSchemaUpgradev35.sql CMDB_2019-10-09.zip

applycapmeasuresonhap_pollutants.sql costequationsv2.sql populateleastcoststrategydetailed_result.sql populateleastcoststrategyworksheet.sql runmaxemisredstrategy.sql runmultipollutantmaxemisredstrategy.sql updategdplevvalues.sql

New server WAR file

emf.war

New client JAR file

emf-client.jar

Database updates

Before starting, shut down the Tomcat server.

Update database schema, add equation types, add columns to strategy detail result dataset type: Update reference year cost-per-ton data type:

\i CostSchemaUpgradev35.sql

Load updated implicit price deflators:

\i updategdplevvalues.sql

Update stored procedures:

\i applycapmeasuresonhappollutants.sql \i costequationsv2.sql \i populateleastcoststrategydetailedresult.sql \i populateleastcoststrategyworksheet.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.5 - 10/23/2019' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the CMDB_2019-10-09.zip set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan over 6 years ago

emf - Version 3.4 - 10/10/2019

EMF

  • New option to export a specific version of a module type
  • Updates to support dataset matching when importing modules via the case manager
  • Support for exporting and importing composite modules
  • New search option in module manager
  • Allow modules with optional, unset input datasets to be finalized

Upgrading from v3.3

Download the necessary update files

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Update case table:

sql ALTER TABLE cases.output_queue ADD COLUMN target_version integer;

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.4 - 10/10/2019' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan almost 7 years ago

emf - Version 3.3 - 03/25/2019

EMF

  • Now requires Java 8 or higher
  • Updated to work with Java 9 and higher, which supports HiDPI displays on Windows
  • New version of the EMF Client Installer available to work with Java 9 and higher

CoST

  • Removed out-of-date control strategy types (Annotate Inventory and Apply Measures In Series)
  • Removed fixed 3% interest rate calculations from control strategies
  • Relabeled columns in control strategy summaries and worksheets to match FF10 inventory terminology
  • Allow control strategies to be run even if the input inventories don't have sectors set

Module system

  • Reduced the maximum length allowed for module dataset and parameter names to avoid truncation when running the module
  • Allow required module datasets to be unset
  • Added option for admin users to delete module history records
  • Reworked how the module history is fetched to speed up viewing and editing modules
  • Added option to use module parameters in dataset placeholder names
  • Updates to work with Postgres 10

Upgrading from v3.2

Download the necessary update files

Control strategy updates

populateleastcoststrategydetailed_result.sql populateleastcoststrategyworksheet.sql populateprojectfutureyearinventorystrategymessages.sql populatestrategymessages.sql runmaxemisredstrategy.sql runmultipollutantmaxemisredstrategy.sql validateprojectfutureyearinventorycontrolprograms.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons.jar

Database updates

Before starting, shut down the Tomcat server.

Fix control technology name:

sql UPDATE emf.control_technologies SET name = 'Excess O2 Control' WHERE name = 'Excess O3 Control';

Mark control measures as obsolete:

sql UPDATE emf.control_measures SET cm_class_id = (SELECT id FROM emf.control_measure_classes WHERE name = 'Obsolete') WHERE abbreviation LIKE 'SICIRIB%';

Remove 3pct columns from Strategy Detail Results dataset type:

sql DELETE FROM emf.fileformat_columns WHERE file_format_id = (SELECT id FROM emf.file_formats WHERE name = 'Control Strategy Detailed Result Extended') AND name IN ('annual_cost_3pct', 'eff_ann_cost_per_ton_3pct', 'annualized_capital_cost_3pct');

Use CSV exporter for Strategy Messages dataset type:

sql UPDATE emf.dataset_types SET exporter_classname = 'gov.epa.emissions.commons.io.csv.CSVExporter' WHERE name = 'Strategy Messages (CSV)';

Update stored procedures:

\i populateleastcoststrategydetailedresult.sql \i populateleastcoststrategyworksheet.sql \i populateprojectfutureyearinventorystrategymessages.sql \i populatestrategymessages.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i validateprojectfutureyearinventorycontrol_programs.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.3 - 03/25/2019' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan over 7 years ago

emf - Version 3.2 - 08/16/2018

EMF

  • Added ability for admin users to edit dataset type column defintions for Flexible File Format-based dataset types
  • Improved error messages displayed when importing datasets
  • Added new option to export and import non-composite modules
  • When exporting modules, added option to export all the input datasets associated with the selected modules
  • Removed dataset types that can't be imported from the Import Window dataset type pull-down menu
  • Added a message explaining why a new dataset version can't be created if there are no existing final versions of the dataset

CoST

  • Created a new Control Strategy Detailed Result dataset type that uses column names consistent with the Flat File 2010 inventory formats
  • Added the term "effective" to emission reduction and annual cost per ton column names in the new strategy detailed result dataset type
  • Updated all control strategy types to output the new detailed result dataset type
  • Created QA step templates for the new detailed result dataset type based on the old dataset type
  • Added check to prevent users from trying to create controlled/projected inventories with old strategy detailed results datasets

Upgrading from v3.1

Download the necessary update files

Dataset type updates

controlstrategydetailedresultextended.csv CostSchemaUpgradev32.sql

Control strategy updates

applycapmeasuresonhap_pollutants.sql createstrategydetailedresulttable_indexes.sql populateleastcoststrategydetailed_result.sql populatestrategymessages.sql runapplymeasuresinseries_strategy.sql runmaxemisredstrategy.sql runmultipollutantmaxemisredstrategy.sql runprojectfutureyearinventory.sql

New server WAR file

emf.war

New client JAR files

emf-client.jar epa-commons.jar

Create the new Control Strategy Detailed Result Extended dataset type

Using the Dataset Type manager, create a new dataset type named "Control Strategy Detailed Result Extended". Set the type to be derived from the Flexible File Format. For the file format Definition File, use the controlstrategydetailedresultextended.csv file you downloaded.

Database updates

Before starting, shut down the Tomcat server.

Add keywords and QA step templates for the dataset type:

\i CostSchemaUpgradev32.sql

Update stored procedures:

\i applycapmeasuresonhappollutants.sql \i createstrategydetailedresulttableindexes.sql \i populateleastcoststrategydetailedresult.sql \i populatestrategymessages.sql \i runapplymeasuresinseriesstrategy.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i runprojectfutureyearinventory.sql

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.2 - 08/16/2018' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan almost 8 years ago

emf - Version 3.1 - 05/17/2018

EMF

  • Added a new dataset type named "Facility Closure Extended" for use with Project Future Year Inventory control strategies. This dataset type works like the existing "Plant Closure (CSV)" type but uses current inventory terminology.
  • Added support for dataset type keywords when exporting and importing module types and associated dataset types
  • Fixed an error when trying to upload a file whose name contains a percent sign
  • Fixed the Module Manager window refresh so that module information is reloaded correctly
  • Fixed errors when module types are imported, caused by blank dataset type creation and last modified dates
  • Fixed errors when deleting modules

CoST

  • Updated the implicit price deflator values used in cost year conversions for 2014 through 2017
  • Added 2017 as an available cost year
  • Relabeled the combustion efficiency column in the control measure SCC window for clarity
  • Added formatting to numbers in the CMDB export files
  • Added formatting to the cost equation parameters in the At-A-Glance report and the control measure view/edit window
  • Updated cost equation descriptions

Upgrading from v3.0

Create the new facility closure dataset type

First, download the dataset type definition file: facilityclosureextended.csv

Using the Dataset Type manager, create a new dataset type named "Facility Closure Extended". Set the type to be derived from the Flexible File Format. For the file format Definition File, use the facilityclosureextended.csv file you downloaded.

Database updates

Before starting, shut down the Tomcat server.

Update implicit price deflator values:

\i updategdplevvalues.sql

Update stored procedures:

\i cleanprojectfutureyearinventorycontrolprograms.sql \i populateprojectfutureyearinventorystrategymessages.sql \i runprojectfutureyearinventory.sql \i validateprojectfutureyearinventorycontrolprograms.sql

Update cost equation descriptions:

sql UPDATE emf.equation_types SET equation = REPLACE(equation, ' x Combustion Efficiency', '') WHERE equation LIKE '% x Combustion Efficiency%';

EMF server updates

Copy the new emf.war into the Tomcat webapps directory.

Update the EMF version in the database: sql UPDATE emf.properties SET value = 'v3.1 - 05/17/2018' WHERE name = 'EMF-version';

Client updates

Copy the new emf-client.jar file into the EMF client directory.

Copy the new epa-commons.jar file into the EMF/lib client directory.

Finishing up

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan about 8 years ago

emf - Version 3.0 - 02/14/2018

EMF

  • Updated EMF server to require Apache Tomcat 8 or later
  • Fixed labeling for columns FUGWIDTHXDIM and FUGLENGTHYDIM in the Flat File 2010 Point dataset type
  • Fixed the Dataset Type Manager window to correctly disable non-admin buttons after a refresh
  • Added support for new Module Tool (disabled by default)

CoST

  • Removed unused source groups
  • Purged obsolete point sector control measures from the CMDB
  • Removed all existing incremental cost-per-ton values from the CMDB; removed unused control-measure-specific capital recovery factors and discount rates
  • Relabeled control strategy "discount rate" to "interest rate"
  • Removed unused fields from the Control Measure At-A-Glance report
  • Updated control strategy cost columns to use double precision values
  • Added formatting to control efficiency values shown in view/edit windows and At-A-Glance reports
  • Added columns to the control strategy detailed results dataset to report raw emissions reduction (based on uncontrolled inventory emissions) and associated annual cost-per-ton
  • Updated labels on control strategy constraints tab to reflect that values are for effective reductions and cost-per-ton, not raw
  • 3/6/2018 Deleted old control measure property records from CMDB
  • 3/6/2018 Updated cost equation descriptions

Upgrading from v2.15

Before starting, shut down the Tomcat server. If you are not running Tomcat 8 or later, you will need to upgrade your installation. After upgrading Tomcat, make sure that the directory pointed to by the DOWNLOADEXPORTFOLDER property in the emf.properties table exists.

Database updates

In version 3.0, two columns in the Flat File 2010 Point dataset type were renamed for clarity. The following SQL query updates the dataset type definition:

```sql update emf.fileformatcolumns set name = 'FUGWIDTHXDIM' where fileformatid in (select fileformat from emf.datasettypes where name = 'Flat File 2010 Point') and name = 'FUGWIDTH_YDIM';

update emf.fileformatcolumns set name = 'FUGLENGTHYDIM' where fileformatid in (select fileformat from emf.datasettypes where name = 'Flat File 2010 Point') and name = 'FUGLENGTH_XDIM'; ```

To update existing Flat File 2010 Point datasets, run the query from the file linked below. Note, this is only needed if you are using existing FF10 point datasets with the module system.

\i updateff10pointfugcolumns.sql

CMDB updates

sql ALTER TABLE emf.control_strategies ALTER COLUMN total_cost TYPE double precision; ALTER TABLE emf.strategy_results ALTER COLUMN total_cost TYPE double precision;

Load updated stored procedures \i applycapmeasuresonhap_pollutants.sql \i costequationsv2.sql \i getremainingemis_expression.sql \i populateleastcoststrategydetailed_result.sql \i populateleastcoststrategyworksheet.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy_finalize.sql \i runmultipollutantmaxemisredstrategy.sql

Load updated cost equation descriptions \i updateequationtext.sql

EMF server updates

Copy new emf.war into Tomcat webapps directory

Update version in database sql UPDATE emf.properties SET value = 'v3.0 - 02/14/2018' WHERE name = 'EMF-version';

Client updates

Copy new emf-client.jar into EMF client directory Copy remaining JAR files (epa-commons.jar, jgraphx.jar, rsyntaxtextarea-3.0.0-SNAPSHOT.jar) into EMF/lib client directory

Enable module system (optional)

Create database schema \i Upstream_CreateSchema.setup \i Upstream_CreateModuleTypesTables.setup \i Upstream_CreateModulesTables.setup \i Upstream_CreateModuleHistoryTables.setup \i Upstream_CreateModuleTagsTable.setup \i Upstream_CreateModuleParameterTypesTable.setup \i Upstream_CreateCompositeModuleTypesTables.setup \i Upstream_CreateCompositeModulesTables.setup \i Upstream_CreateCompositeModuleHistoryTables.setup \i Upstream_InsertModuleParameterTypes.setup \i Upstream_InsertModuleKeywords.setup

Update UI setting sql UPDATE emf.properties SET value = 'true' WHERE name = 'SHOW_MODULES_MENU';

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the cmdb20180308*.csv set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan over 8 years ago

emf - Version 2.15 - 08/24/2017

CoST

  • Fixed bug trying to finalize control strategies that use control measures to be purged
  • Updated Control Measure Manager cost year menu to cover 2000 to 2016
  • Fixed control measure reference search to be case-insensitive
  • Fixed At-A-Glance report to handle various numbers of control efficiency records correctly
  • Control Measure Database updates:
    • Purged obsolete onroad and nonroad control measures, and old temporary measures
    • Converted control measures using pollutants PM2_5 and PM10 to PM25-PRI and PM10-PRI
    • Removed control efficiency records with old effective dates
    • Removed special characters from control measure source group names and property values
    • Updated control efficiencies and equipment life values for some NOx measures
    • 8/28/2017 Updated control measures using equation types 1, 12, and 13
    • 9/7/2017 For several PM measures, removed control efficiency records with effective dates of 1/1/2020 and updated control efficiency values

Upgrading from v2.14

Before starting, shut down the Tomcat server.

CMDB updates

Load updated stored procedures \i populateleastcoststrategyworksheet.sql \i populatestrategymessages.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy_finalize.sql

EMF server updates

Copy new emf.war into Tomcat webapps directory

Update version in database UPDATE emf.properties SET value = 'v2.15 - 08/24/2017' WHERE name = 'EMF-version';

Client updates

Copy new emf-client.jar into EMF client directory

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the cmdb20170917*.csv set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan almost 9 years ago

emf - Version 2.14 - 06/27/1017

CoST

  • Updated the lists of pollutants in the Control Measure Manager window to only show pollutants actually controlled by measures in the system, instead of all defined pollutants
  • Added checks for null cost equation parameters for Equation Type 2 and its variants
  • Fixed a bug in the calculations for Equation Type 13 caused by an order of operations error
  • Removed special characters (curly quotes, long dashes, and symbols) from control measure names, descriptions, and references

EMF

  • Added logging for commands run from the RemoteCommand execute method
  • Stopped renaming of database tables when a dataset's name is changed
  • Fixed a bug when creating a new flexible format dataset type with spaces in the column names; spaces are automatically converted to underscores in the database table definition

Upgrading from v2.13

Before starting, shut down the Tomcat server.

CMDB updates

Load updated cost equations \i costequationsv2.sql

EMF server updates

Copy new emf.war file into Tomcat webapps directory

Update version in database UPDATE emf.properties SET value = 'v2.14 - 06/27/2017' WHERE name = 'EMF-version';

Client updates

Copy new emf-client.jar into EMF client directory

Copy new epa-commons.jar into EMF/lib client directory

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

Note that the CMDB changes are purely cosmetic, removing special characters from control measure names, descriptions, and references. Reloading the CMDB won't change any strategy results.

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the cmdb20170627*.csv set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan about 9 years ago

emf - Version 2.13 - 03/20/2017

EMF

  • Improved the display of file format information when viewing or editing a dataset type
  • Enhanced the case comparison report to include dataset version differences
  • Added the ability to upload local files to the server via the EMF client
  • Automatic clean-up of uploaded files after 12 hours

CoST

  • Changed the control strategy cost year to use a pull-down menu of available years instead of a text field
  • Updated cost year conversion factors (implicit price deflators) for 2013 through 2016
  • Updated NOx non-EGU control measures based on SRA recommendations
  • Miscellaneous CMDB clean-up and fixes

Upgrading from v2.12

Before starting, shut down the Tomcat server.

File upload handling

Create the file upload directory inside the ImportExportTempDir. The following query will show the currently set directory: SELECT value FROM emf.properties WHERE name = 'ImportExportTempDir';

For example, if the value is /data/tmp/: mkdir /data/tmp/upload

Ensure this directory is writeable by the Tomcat user.

Create max upload file size property (value in MB): INSERT INTO emf.properties (name, value) VALUES ('MAX_FILE_UPLOAD_SIZE', '100');

CMDB updates

Load updated gdplev values \i updategdplevvalues.sql

EMF server updates

Copy new emf.war file into Tomcat webapps directory

Update version in database UPDATE emf.properties SET value = 'v2.13 - 03/20/2017' WHERE name = 'EMF-version';

Client updates

Copy new emf-client.jar into EMF client directory

Copy new epa-commons.jar into EMF/lib client directory

Copy commons-fileupload-1.3.2.jar into EMF/lib client directory

Finishing up

Once all updates are complete, start the Tomcat server.

Reload CMDB

If you have custom control measures in your CMDB, first export these measures, so you can reload them after the main update.

Load the updated control measure database from the cmdb20170320*.csv set of files. Purge all existing measures during the import step.

After loading the default CMDB, re-import any custom control measures.

- Java
Published by cseppan over 9 years ago

emf - Version 2.12 - 09/22/2016

Bug fixes

  • Updated the uniqueness checks when importing control measure efficiency records to take into account the minimum and maximum capacity columns
  • Updated the labels used for the maximum cost per ton and maximum annualized cost control strategy constraints to reflect that the constraints are specified in dollars matching the cost year of the control strategy, not a fixed reference year

Enhancements

  • Consolidated database connections via the Tomcat-managed connection pool
  • Expanded control measure cost equation Type 2 to support new NOx non-EGU control measures
  • Updated NOx non-EGU control measures with new cost data, SCC assignments, and cost equations
  • Changed the final cost-per-ton calculations in CoST to use the net emissions reduction instead of gross; this change impacts costs when replacement controls are applied

Upgrading from v2.11.1

Before starting, shut down the Tomcat server.

1) Apply schema upgrade statements from CostSchemaUpgrade.setup (all statements labeled as 08/04/2016). The package dbupdates.v2.12.zip includes a version of CostSchemaUpgrade.setup with just the updates needed. \i CostSchema_Upgrade.setup

2) Load updated functions. \i costequationsv2.sql

3) Copy new emf.war file into Tomcat webapps directory

4) Copy new emf-client.jar into EMF client directory

5) Update version in database UPDATE emf.properties SET value = 'v2.12 - 09/22/2016' WHERE name = 'EMF-version';

Once all updates are complete, start the Tomcat server.

To load the updated ptnonipm control measures, use the Import option from the Control Measures Manager window. Select the suite of noxnonegu20160713_*.csv files. Purge the existing ptnonipm control measures during the import.

- Java
Published by cseppan over 9 years ago

emf - Version 2.11.1 - 06/15/2016

Bug fixes

  • Fix checks for design capacity columns in inventories when applying new generating capacity thresholds; allows control strategies using nonpoint inventories to run

Upgrading from v2.11

Before starting, shut down the Tomcat server.

1) Load updated functions \i populateleastcoststrategyworksheet.sql \i runannotateinventory.sql \i runapplymeasuresinseriesstrategy.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i runprojectfutureyear_inventory.sql

2) Copy new emf-client.jar into EMF client directory

3) Update version in database UPDATE emf.properties SET value = 'v2.11.1 - 06/15/2016' WHERE name = 'EMF-version';

Once all updates are complete, start the Tomcat server.

- Java
Published by cseppan about 10 years ago

emf - Version 2.11 - 06/06/2016

Bug fixes

  • Fixed a bug when editing cases where changes after an initial save weren't saved to the database
  • Fixed a bug that caused multi-pollutant control strategies to fail in some circumstances
  • Fixed issues in the control measure import interface where the import button wasn't enabled after errors

Enhancements

  • The control measure database has been updated based on IPM v5.15 for the ptipm sector. Updates include revised control efficiency and cost equation parameters, removal of obsolete control measures, addition of new measures, and fixes to cost equation calculations. These updates make use of several new features included in EMF v2.11:
    • Include the control measure's equation type in the Control Measure Manager details display
    • Allow control measures to be targeted to sources based on generating capacity
    • Use SCC-specific combustion efficiency percentages when calculating generating capacity from design capacity

Upgrading from v2.10

Before starting, shut down the Tomcat server.

1) Add new control measure fields to database ALTER TABLE emf.controlmeasureefficiencyrecords ADD COLUMN mincapacity double precision; ALTER TABLE emf.controlmeasureefficiencyrecords ADD COLUMN maxcapacity double precision; ALTER TABLE emf.controlmeasuresccs ADD COLUMN combustion_efficiency real;

2) Load updated functions \i convertdesigncapacitytomw.sql \i costequationsoldapproach.sql \i costequationsv2.sql \i getconvertdesigncapacityexpression.sql \i populateleastcoststrategyworksheet.sql \i runannotateinventory.sql \i runapplymeasuresinseriesstrategy.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i runprojectfutureyearinventory.sql

3) Copy new emf.war file into Tomcat webapps directory

4) Copy new epa-commons.jar into EMF client lib directory

5) Copy new emf-client.jar into EMF client directory

6) Update version in database UPDATE emf.properties SET value = 'v2.11 - 06/06/2016' WHERE name = 'EMF-version';

Once all updates are complete, start the Tomcat server.

To load the updated ptipm control measures, use the Import option from the Control Measures Manager window. Select the suite of ptipm20160329*.csv files. Purge the existing ptipm control measures during the import.

- Java
Published by cseppan about 10 years ago

emf - Version 2.10 - 01/28/2016

Bug fixes

  • Cost-per-ton values displayed in the Control Measure Manager window when Show Details is checked are now correctly adjusted for the selected Cost Year.
  • Fixed an intermittent problem when running a Least Cost Curve control strategy that caused calculations at different increments to apply maximum controls instead of the specified percent reduction.
  • Allow cancelled control strategies to be re-run.

Enhancements

  • Conversions of dollar amounts between different years are now done using annual GDP implicit price deflator values. Previously, the EMF used chained GDP values for converting between cost years.
  • Added support for cost years 2007 through 2014.
  • Updated the default cost year to 2013; previously the default year was 2006.

Upgrading from v2.9.1

The zip archive db_updates.v2.10.zip contains the SQL files referred to in the list of updates below.

1) Update reference.gdplev schema ALTER TABLE reference.gdplev ADD COLUMN deflator_gdp double precision;

2) Load updated gdplev values \i updategdplevvalues.sql

3) Update stored reference year cost per ton values \i updateeffrecrefyrcpttonewgdplev.sql

4) Update aggregated efficiency records \i updateaggeff_records.sql

5) Load updated functions \i costequationsv2.sql \i costequationsoldapproach.sql \i populateleastcoststrategyworksheet.sql \i runannotateinventory.sql \i runapplymeasuresinseriesstrategy.sql \i runmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategy.sql \i runmultipollutantmaxemisredstrategyfinalize.sql \i runprojectfutureyearinventory.sql \i getleastcostworksheetemisreduction.sql \i narrowinonleastcost_target.sql

6) Copy new emf.war file into Tomcat webapps directory

7) Copy new emf-client.jar into EMF client directory

8) Update version in database UPDATE emf.properties SET value = 'v2.10 - 01/28/2016' WHERE name = 'EMF-version';

- Java
Published by cseppan over 10 years ago

emf - Version 2.9.1 - 09/09/2015

EMF - Prevent datasets that are being used as a temporal profile or cross-reference input in a temporal allocation run from being deleted. - Allow the project associated with a dataset, control strategy, or temporal allocation to be set back to none.

CoST - Fixed a bug when matching inventory sources that could cause newer sources to be excluded from least cost analyses. - Create the server export folder if needed when exporting control measures for automatic download. - When deleting control strategies and associated datasets (control strategy results, generated inventories), fully delete the selected datasets. Previously, the datasets would be marked as deleted but not purged. - Fixed the calculation of per-source percent reductions when creating projected inventories. This bug affected sources that had additive controls applied in the Project Future Year Inventory strategy.

- Java
Published by cseppan almost 11 years ago

emf - Version 2.9 - 07/20/2015

EMF - This release adds a new feature that will allow a user to Archive or Restore a dataset or QA Step result. The archive process will still keep around the meta data on the dataset or QA Step, but the underlying data will be archived and removed from the database. The Restore process will allow the user to bring back the underlying data for the dataset or QA Step.

CoST - The Control Measure Manager search box will now match control measures by name or abbreviation. - When editing control programs, the list of available dataset types is now limited to those types used by control programs: Allowable Packet, Allowable Packet Extended, Control Packet, Control Packet Extended, Plant Closure (CSV), Projection Packet, and Projection Packet Extended.

- Java
Published by cseppan almost 11 years ago