[CON Devel] How an AREA run works?

[John Haasbeek]

Before executing the concept script with the run_area_model command, you
should run the qa_nei_area command if you have changed the input data.
This command updates the default values, performs qa on the data, and
prepares the em and ep keys.

The process is as follows:

import_nei_area
	reads the "filenames" file to see where the nei data are
	imports the raw nei data

qa_nei_area
	runs set_area_defaults.sql which sets the standard default
values
	for tribal_code, scc, etc.
	runs QANeiAreaEP, QANeiAreaPE, QANeiAreaEM stored procedures
	which look for bad data
	runs PrepNEIAreaTables stored procedure which creates the
nei_area_em
	and nei_area_ep tables for the ep and em key values, and handles
	the overlay of tribal emissions

run_area_model
	runs area_model.sql which in turn calls the
AreaTemporalAllocation,
	AreaSpeciation, and AreaSpatialAllocation stored procedures

John H.

-----Original Message-----
From: devel-bounces at conceptmodel.org
[mailto:devel-bounces at conceptmodel.org] On Behalf Of Seib, Broc
Sent: Monday, August 21, 2006 10:22 AM
To: devel at conceptmodel.org
Subject: RE: [CON Devel] How an AREA run works?

Ok, I'll try changing only the pollutant code and nothing else. I am
positive I am replicating every field in the record before substituting
the pollutant_code to be CO2. I'll reply with what I find.

We are using PostgreSQL 8.1.1. Is there a problem with imports for this
version?

How do you mean it will not "forget" the old records? Can you describe
the broad steps that take place in an area run?

-broc


> -----Original Message-----
> From: devel-bounces at conceptmodel.org 
> [mailto:devel-bounces at conceptmodel.org] On Behalf Of Mark Janssen
> Sent: Monday, August 21, 2006 11:23 AM
> To: devel at conceptmodel.org
> Subject: Re: [CON Devel] How an AREA run works?
> 
> To test this I would just change the pollutant code and re-run the 
> model. You should get the exact same answer as NOX. If you don't then 
> you need to search for the reason. The Emission factor data is not 
> used by CONCEPT so I would keep it the same. Did you check the 
> postgres versions of the database to see that the records were read 
> in correctly. I find that the only way to QA this kind of thing is to 
> follow only one record through the entire process instead of trying 
> to get the big picture. Did you re-initialize the database before you 
> loaded the new CO2 records because CONCEPT will not "forget" the old 
> NOX records. The variables that you want to make sure made it in are
> 
>          state/county fips, scc, start/end date, pollutant code, 
> emissions, and emission unit.
> 
> If any of these are not perfect you will lose the records. Let me 
> know how it goes.
> 
> Mark J
> 
> At 10:00 AM 8/21/2006, Seib, Broc wrote:
> 
> >Hi John, Mark, everyone,
> >
> >I am trying to understand in more detail how an area run 
> actually works
> >in CONCEPT. Here's what I have attempted:
> >
> >I took all the 'nei_area_em' records with NOX and duplicated 
> them field
> >for field, except I changed the pollutant code to "CO2" and 
> changed the
> >following other fields with corresponding CO2 values: 
> 'emission_value',
> >'emission_units_code', 'factor_value', 'factor_units_num',
> >'factor_units_denom'. Then I re-inserted these CO2 records 
> back into the
> >'nei_area_em' table, and performed an Area run.
> >
> >But the output .ncf file has references to NOX. I suspect 
> because the em
> >and ep keys play a role here connecting back to other NOX data.
> >
> >
> >Can you describe the mechanics of what takes place during an 
> area run?
> >What is the overall goal, what data is drawn from what tables, and
> >thereby how they get joined, etc. I am hoping you can save 
> me the effort
> >of reading all the source code to figure out what it is 
> actually doing.
> >
> >Thanks for any help,
> >
> >Broc Seib
> >Purdue University
> >Rosen Center for Advanced Computing
> >_______________________________________________
> >Devel mailing list
> >Devel at conceptmodel.org
> >http://lists.conceptmodel.org/mailman/listinfo/devel
> 
> 
> _______________________________________________
> Devel mailing list
> Devel at conceptmodel.org
> http://lists.conceptmodel.org/mailman/listinfo/devel
> 
_______________________________________________
Devel mailing list
Devel at conceptmodel.org
http://lists.conceptmodel.org/mailman/listinfo/devel



This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to email at environcorp.com and immediately delete all copies of the message.