|
Software Engineering
Adaptation Data Migration Frequently Asked Questions
A Workingman's Guide to
"Where did this stuff come from?"
- Ron Guenther
1. What happens to our RPG adaptation data after we send it to the ROC?
The Backfiles.css procedure you use saves the two active adaptation data files from your legacy RPG to tape along with other important files. When we receive this tape, we select the most current adaptation data file and use its contents for the (drum roll) ADAPTATION DATA MIGRATION PROCESS.
2. Okay, so what is the (drum roll) ADAPTATION DATA MIGRATION PROCESS?
The ADAPTATION DATA MIGRATION PROCESS, "ADMP," is a collection of computer programs, computer hardware, and people processes that starts with your data tape, four databases, and nine other data files and ends up producing the collection of information that is called LB Adaptation Data on a floppy disk for use on your bright, shiny, new SUN RPG.
3. Is that all?
The ADMP is a two-part process. In the first part, we process your data against a collection of information that provides the opportunity to verify the narrow band communication data. Here is where the people processes come to bear. The automation processes provide lists of information identifying non-associated (dialup) users from your legacy RPG data, along with a list of associated (dedicated) users from the communication databases established for the narrow band communication reconfiguration project. The authorized dialup users from your tape are compared to the ROC Hotline's data and the differences are resolved. Deactivated/decommissioned users are dropped out; new users are loaded. The User-Names are associated with the User-IDs and in most cases tied together.
Now for the second part. After these checks are completed, we reprocess your data with the updated communication information to produce LB Adaptation Data.
4. It's that simple?
No. That last process is quite complicated. To simplify it, as a part of the automated processing we accomplish a MERGE where we take the site-specific values from a 131 tables of information from your tape and overlay them onto the Build 10 adaptation data defaults. From the thousands of tables that make up the legacy RPG, we produce over 1000 different data formats translating the compact legacy binary information into a human readable format required by the new SUN RPG software to produce the compact binary information on a floppy disk.
5. Hmmm, so why don't you use all of our data?
That's a good question! The opinion of the WSR-88D Adaptation Data Working Group was the same as it has been with previous versions of the legacy RPG software. Many of the site-adaptable parameters address transient values. For instance, how many storms should be tracked is episodic. In this and other cases, leaving the value set to the last event is not beneficial, and could potentially create problems based upon the performance of new or modified algorithms. Additionally, these default values provide a good baseline to test the system's performance.
|
| |
