Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Oct 7 2009, 3:57 PM EDT (current) | vikrantsharma1 | 329 words added |
| Oct 7 2009, 3:55 PM EDT | vikrantsharma1 |
Changes
Key: Additions Deletions
The parameter editor allows you to define parameter data. In AirVision a parameter can come from any kind of data source--it is no longer correlated with data logger channels. The parameter editor contains basics such as units, EPA reporting codes, and graph limits. This editor allows you to enter/modify a list of parameter types that each parameter can be referenced to, so the application can more easily correlate parameters with different names (e.g., "O3" vs. "OZ" vs. "OZONE")
In E-DAS Ambient, many of these configurations had to be repeated for the same parameter at multiple sites, or an assumption was made regarding parameter names, such as ozone, to avoid the need for repetitive configuration entries. AirVision avoids the problems associated with this approach by using EPA Parameter Names and Parameter Categories.
Linking parameters to parameter types makes reporting easier and eliminates the necessity to link individual site/parameter selections together (e.g., for AIRNow reporting). Instead, details can be configured for an EPA parameter type. The Parameter Template Editor can be used to add new template definition if a suitable one cannot be found in the default list.
Parameter information can be auto-filled by selecting a parameter template and the option to auto-fill EPA codes and units. Units are selected from a pick list, so that unit conversions (e.g., ppm to ppb) and unit types (e.g., whether rainfall or solar radiation is totaled, not averaged) are handled automatically. The parameter editor also supports the designation of alternate analyzer units that differ from reporting and editing units for digital data acquisition where the analyzer reports data in units different from that the customer prefers (ppm vs. ppb). The conversion is handled at the time of data acquisition (polling, file import) and data is stored in the regular EPA units in the database.
In both the site and parameter editors, you will be able to create meta-data fields to handle customer- specific data fields, such as analyzer serial number and installation date.
In E-DAS Ambient, many of these configurations had to be repeated for the same parameter at multiple sites, or an assumption was made regarding parameter names, such as ozone, to avoid the need for repetitive configuration entries. AirVision avoids the problems associated with this approach by using EPA Parameter Names and Parameter Categories.
Linking parameters to parameter types makes reporting easier and eliminates the necessity to link individual site/parameter selections together (e.g., for AIRNow reporting). Instead, details can be configured for an EPA parameter type. The Parameter Template Editor can be used to add new template definition if a suitable one cannot be found in the default list.
Parameter information can be auto-filled by selecting a parameter template and the option to auto-fill EPA codes and units. Units are selected from a pick list, so that unit conversions (e.g., ppm to ppb) and unit types (e.g., whether rainfall or solar radiation is totaled, not averaged) are handled automatically. The parameter editor also supports the designation of alternate analyzer units that differ from reporting and editing units for digital data acquisition where the analyzer reports data in units different from that the customer prefers (ppm vs. ppb). The conversion is handled at the time of data acquisition (polling, file import) and data is stored in the regular EPA units in the database.
In both the site and parameter editors, you will be able to create meta-data fields to handle customer- specific data fields, such as analyzer serial number and installation date.
