CN1417794A - Correcting data management system - Google Patents
Correcting data management system Download PDFInfo
- Publication number
- CN1417794A CN1417794A CN 01134482 CN01134482A CN1417794A CN 1417794 A CN1417794 A CN 1417794A CN 01134482 CN01134482 CN 01134482 CN 01134482 A CN01134482 A CN 01134482A CN 1417794 A CN1417794 A CN 1417794A
- Authority
- CN
- China
- Prior art keywords
- correction data
- program
- name
- delete
- program name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The present invention is one correcting data management system for test bench. The test includes the following process: initializing the test bench, calling program, correction, product test and completing test. The system features that correcting data call, save and delection program after calling program. The correcting data is saved before produced variation and called directly for test if needed, and this can save test time. After reaching its use term relevant technological condition specified, the correcting data is deleted to ensure product quality. The present invention raise the test efficiency of the test bench greatly.
Description
Technical field
The present invention relates to the management of testing apparatus correction data, be applicable to have reusability, and need carry out the data of term of validity management.
Background technology
During the high precision measurement testing equipment, the test distribution between from the test board to the test point can cause the difference of signal transmission time because the length difference, produces timing skew.In order to eliminate the influence that deviation causes test, test board must be measured the deviation of every test distribution, and generates the corresponding compensation data, so that carry out time bias when test.This measuring process is called correction, and the offset data of generation is called correction data.Proofreading and correct generally is to carry out when the test beginning, needs spended time usually about 1 to 2 hour, proofreaies and correct the result and is kept in the Dram with data mode, and when test board conversion test kind, internal memory needs zero clearing, and correction data is deletion thereupon also.Therefore, as long as kind is once tested in conversion, test board will be deleted original correction data, and new varieties are implemented to proofread and correct, and generates new correction data.Because test condition generally all has longer stability, correction data can both meet test environment in a long time, therefore, too frequent correction data deletion has caused the minimizing of effective production time in the operational scheme, has influenced the productive capacity of testing apparatus.
Summary of the invention
The purpose of this invention is to provide a kind of correcting data management system, repeat to proofread and correct this problem of losing time with solution.In this system, for correction data provides the function of calling in, preserve, deleting, and correction data is carried out rational time limit management, thereby under the situation that guarantees process conditions, save correction time.
The correcting data management system that the present invention relates to, comprise following flow process: test board initialization, routine call, correction, product testing, end of test (EOT), this system increase after routine call that correction data is called, correction data is preserved and the correction data delete program.
In the present invention, realized that correction data utilizes function again, promptly before the kind conversion, realize the preservation of former kind correction data, when former kind program when needing to use once more after a while, test board will access the correction data of original preservation automatically, be directly used in test, and no longer carry out corrective action.Idiographic flow as shown in Figure 1, in former flow process, test board only carries out initialization, routine call, correction, tests this process, and correction data is not carried out any management.And in new technological process, at first the correction data in the current internal memory is preserved, then after having implemented initialization and routine call, carry out the judgement that correction data has or not,, then data are called in internal memory automatically if corresponding correction data exists, and skip correction operation, directly test; If corresponding correction data does not exist, then still implement to proofread and correct, test again.With 1 hour correction time, product changed and call 10 times again for example, and it is 10 hours that former flow process is proofreaied and correct consuming time, and new technological process to proofread and correct consuming time only be 1.1 hours.
The present invention has the time limit management function of correction data.Though test condition has longer stability, generation just can datelessly be used but this can not represent correction data, and after after a while, correction data originally also will produce deviation with existing condition, therefore, correction data must be carried out time limit management.Time limit management mode of the present invention is: the correction data time limit to each product testing procedure is managed independently.When the correction data of certain product testing procedure reaches fixed time limit service time, only the correction data of this test procedure is deleted, treat to proofread and correct again, preserve when use next time and new time limit accumulative total.Time limit accumulative total is beginning to the deletion end of day from generating day, from deletion day to generating during in the daytime time interval do not charge to time limit management.Thereby reduced the number of times of proofreading and correct as far as possible.The data term of life is 1 month as shown in Figure 2, and program aaa is because frequent the use proofreaied and correct 5 times 10 hours consuming time of year in six months; And program bbb is because therefore accidental use only needs to proofread and correct 5 times 5 hours consuming time of year in 1 year.If manage according to former flow process, calculate for 5 times by every month each correction to program, then the year of each program consuming timely is about 60 hours.
The present invention uses when the correction data delete function also is provided in order to data failure, for example when test board carried out the repairing relevant with correction, if changed the distribution condition, then all correction datas did not all meet and repair the back test condition, correction data must Delete All
In order to prevent the generation of misdescription, error of omission, also be provided with automatic record of main frame among the present invention and contrast the content of confirming, and set up special-purpose management machine account with hand-kept, record is carried out in generation day, deletion day and the affirmation of being correlated with.
When carrying out the correction data management, set up clear and definite data management mark, thereby reach administrative purposes.Because a kind of test procedure of product needs the correction data file of a plurality of projects, might there be the content difference in the test procedure of different product but the identical correction data file of title, and therefore the correction data of different test procedures can not be mixed and is put under the same catalogue.Because a kind of test procedure name and correction data of product have strict corresponding relationship, therefore in software design of the present invention, the test procedure name of product is utilized as the data management mark, promptly, the service routine name is as the catalogue of depositing corresponding correction data file, and whether utilization program name comparison judgement is confirmed Data Source and carry out content correct in executive routine.As shown in Figure 3, the test procedure name is as unique distinguishing mark, call in, preserve, when deleting operation, for correction data provides correct path.
Description of drawings
Read following of the present invention being described in detail and accompanying drawing, be further understood that above-mentioned purpose of the present invention, characteristics and advantage.
Fig. 1 is the correcting data management system process flow diagram
Fig. 2 is the correction data term of life
Fig. 3 is the utilization figure of correction data administrative tag " test procedure name "
Fig. 4 is the embodiment correction data management process that explanation is set up according to the present invention
Fig. 5 is that the embodiment correction data that explanation is made according to the present invention is called in program circuit
Fig. 6 is the embodiment correction data save routine flow process that explanation is made according to the present invention
Fig. 7 is the embodiment correction data delete program flow process that explanation is made according to the present invention
Fig. 8 is the correction data operation screen of calling in program-the exist operation screen of correction data
Fig. 9 is the correction data operation screen of calling in program-the do not exist operation screen of correction data
Figure 10 is the operation screen of correction data save routine
Figure 11 is that the operation screen-correction data deletion of correction data delete program is released picture in carrying out
Figure 12 is the picture of the operation screen-correction data of correction data delete program when deleting full kind
Figure 13 is that the operation screen-correction data of correction data delete program is deleted the picture when specifying kind
Figure 14 is that correction data generates the historical query operation screen
Figure 15 is a correction data deleting history query manipulation picture
Embodiment
Below will narrate an embodiment who is applied to the management of 128M memory test platform correction data of the present invention.
The embodiment system management software, use the VMS system language of DEC to programme, its major function is: can realize correction data preservation, call in, delete and generate relevant enforcement resume, delete function has single and whole two kinds of forms for flexible use.The principal feature of software is: use conversational mode, be convenient to operation; Automatically implement double acknowledge in the program run, in case make mistakes; The major function design such as call in and in original program, implement automatically, reduce operational ton.
128M memory test platform is when testing, for correction data is implemented management, must consider all operations relevant with correction data, in correction data management process shown in Figure 4, operation by routine call, daily spot check, this three aspect of test board fault repair reaches complete administrative purposes.
In the routine call operation, at first carry out the preservation of correction data, after internal memory initialization, test procedure are called in, inquire whether corresponding program exists correction data, if having, then call in data; If do not have, the then automatic recording correction data date of formation in test board, and prompting operator's hand-kept correction data date of formation in machine account, set the deletion date.
Whether in daily spot check operation, at first inquiring about has the correction data that reaches the deletion time limit in the hand-kept, if having, then implements the deletion operation, and on the date at that time of the automatic record deletion of test board, the operator is the hand-kept correction data deletion date in machine account also; If do not have, then skip the deletion operation, confirm that directly whether the generation of hand-kept on the machine account, deletion date be consistent with the self registering result of test board, guarantees double acknowledge, in case error.
When the test board fault repair, at first carry out the preservation of correction data,, then implement the deletion of whole correction datas if the repairing of test board has caused the change of distribution condition, the date at that time of the automatic record deletion of test board, the deletion date of operator's manual recording correction data on machine account.If the change of no distribution condition then need not to implement deletion.
In order to realize the correction data management process, management software has designed and has called in, the function of preservation, deleted data
Call in the program circuit in the correction data of Fig. 5, at first step 1 is quoted save routine last batch correction data is preserved, and implements the internal memory zero clearing then.When operator's loading routine name, step 2 provides double acknowledge information with preparing against in preservation and delete program among the calling program name write-in program name memory file PLDNM.TXT.In decision box step 3, utilize the program name of having imported to search corresponding correction data catalogue, if be judged to be " YES ", promptly there is the correction data catalogue of this program name, then skip to step 7 and implement the correction data loading, and finish the program of calling in; If be judged to be " NO ", the correction data catalogue that does not promptly have this program name, then change step 4 display routine name and current date, time over to, and write down machine account step 5 prompting operator, simultaneously, in step 6, current date and program name are write correction data generation record sheet file MAKE_LIST.TXT,, realize automatically and manual double acknowledge so that implement inquiry in the daily spot check.Operation screen is shown in Fig. 8,9.
In the correction data save routine flow process of Fig. 6, step 1 is set up the base directory structure, so that provide the path for the preservation of correction data.Step 2 shows program name and the correction data in the current internal memory, confirms for the operator.Step 3 is a decision block, confirms whether carry out the preservation of correction data, and the outlet of withdrawing from is provided for program.Step 4 is shown inquiry, require manually input will preserve the program name of correction data, after operator's loading routine name, defeated program name of decision block step 5 adversary and program name memory file PLDNM.TXT compare, i.e. double acknowledge is if be judged as " NO ", promptly two program names are inconsistent, illustrate that then hand is defeated wrong, or the memory file is unusual, point out display abnormality this moment; If be judged as " YES ", i.e. two program name unanimities, then description status is normal, continues to enter step 6.Whether the inspection of decision block step 6 exists and the identical catalogue of input name, if be judged as " YES ", has promptly had catalogue of the same name, then enters step 8; If be judged as " NO ", promptly this correction data is to preserve for the first time and do not have catalogue, then is introduced into step 7 and generates this program name catalogue, and then enter step 8.Step 8 is to delete legacy data and preserve current correction data under the program name catalogue.Operation screen as shown in figure 10.
In the correction data delete program flow process of Fig. 7, decision block step 1 confirms whether carry out the deletion of correction data, and the outlet of withdrawing from is provided for program.Decision block step 2 proposes two kinds of selections, is a kind of correction data of deletion or the whole correction datas of deletion by operator's input, if select " ALL ", promptly implements Delete All, then enters step 3, deletes the correction data under whole program name catalogues, enters step 8 again; If select " 1 ", promptly implement the single variety deletion, then enter step 4.Step 4 is shown inquiry, requires manually input will delete the program name of correction data, and after operator's loading routine name, step 5 is with the correction data under the delete program name catalogue.Step 6 writes correction data deletion record list file CLEAR_LIST.TXT with current date and program name, so that implement inquiry in the daily spot check, realizes automatically and manual double acknowledge.Decision block step 7 compares loading routine name and program name memory file PLDNM.TXT, i.e. double acknowledge is if be judged to be " NO ", promptly two program names are inconsistent, illustrate that then the program that will delete is not the program of current use, need not other operation, directly finish delete program; If be judged to be " YES ", promptly two program name unanimities illustrate that then the program that will delete is the program of current use, in order to guarantee thoroughly to delete legacy data, must enter step 8.Step 8 is the internal memory zero clearing, and purpose is to prevent that legacy data is residual.Operation screen is shown in Figure 11,12,13.
Polling routine comprises that correction data generates historical query and the inquiry of correction data deleting history.Owing in the program of calling in, having made " correction data generation record sheet " file MAKE_LIST.TXT, therefore can find generation history as long as show its file content, the operation screen of inquiry is as shown in figure 14.Owing in delete program, made " correction data deletion record table " file CLEAR_LIST.TXT, therefore can find deleting history as long as show its file content, the operation screen of inquiry is as shown in figure 15.
Narrated illustrative embodiment of the present invention above, it should be explicitly made clear at this point, the invention is not restricted to this clear and definite embodiment, the professional in present technique field, under the condition of the spirit and scope of the present invention that do not depart from the claims qualification, can make various changes and improvements to content wherein.
Claims (2)
1. correcting data management system, comprise following flow process: test board initialization, routine call, correction, product testing, end of test (EOT), it is characterized in that: this system increases after routine call that correction data is called, correction data is preserved and the correction data delete program, and concrete steps are as follows:
A. correction data is called in the program circuit, at first step 1 is quoted save routine last batch correction data is preserved, implement the internal memory zero clearing then, when operator's loading routine name, step 2 provides double acknowledge information with preparing against in preservation and delete program among the calling program name write-in program name memory file PLDNM.TXT.In decision box step 3, utilize the program name of having imported to search corresponding correction data catalogue, if be judged to be " YES ", promptly there is the correction data catalogue of this program name, then skip to step 7 and implement the correction data loading, and finish the program of calling in; If be judged to be " NO ", the correction data catalogue that does not promptly have this program name, then change step 4 display routine name and current date, time over to, and write down machine account step 5 prompting operator, simultaneously, in step 6, current date and program name are write correction data generation record sheet file MAKE_LIST.TXT;
B. in the correction data save routine flow process, step 1 is set up the base directory structure, so that provide the path for the preservation of correction data.Step 2 shows program name and the correction data in the current internal memory, confirms that for the operator step 3 is a decision block, confirms whether carry out the preservation of correction data, and the outlet of withdrawing from is provided for program.Step 4 is shown inquiry, require manually input will preserve the program name of correction data, after operator's loading routine name, defeated program name of decision block step 5 adversary and program name memory file PLDNM.TXT compare, i.e. double acknowledge is if be judged as " NO ", promptly two program names are inconsistent, illustrate that then hand is defeated wrong, or the memory file is unusual, point out display abnormality this moment; If be judged as " YES ", i.e. two program name unanimities, then description status is normal, continues to enter step 6, and whether the inspection of decision block step 6 exists and an input identical catalogue, if be judged as " YES ", has promptly had catalogue of the same name, then enters step 8; If be judged as " NO ", promptly this correction data is to preserve for the first time and do not have catalogue, then is introduced into step 7 and generates this program name catalogue, and then enter step 8, and step 8 is deletion legacy datas and preserve current correction data under the program name catalogue;
C. in the correction data delete program flow process, decision block step 1 confirms whether to carry out the deletion of correction data, the outlet of withdrawing from is provided for program, decision block step 2 proposes two kinds of selections, is a kind of correction data of deletion or the whole correction datas of deletion by operator's input, if select " ALL ", promptly implement Delete All, then enter step 3, delete the correction data under whole program name catalogues, enter step 8 again; If select " 1 ", promptly implement the single variety deletion, then enter step 4, step 4 is shown inquiry, require manually input will delete the program name of correction data, after operator's loading routine name, step 5 is with the correction data under the delete program name catalogue, step 6 writes correction data deletion record list file CLEAR_LIST.TXT with current date and program name, so that implement inquiry in the daily spot check, realize automatically and manual double acknowledge that decision block step 7 compares loading routine name and program name memory file PLDNM.TXT, it is double acknowledge, if be judged to be " NO ", promptly two program names are inconsistent, illustrate that then the program that will delete is not the program of current use, need not other operation, directly finish delete program; If be judged to be " YES ", promptly two program name unanimities illustrate that then the program that will delete is the program of current use, in order to guarantee thoroughly to delete legacy data, must enter step 8, and step 8 is the internal memory zero clearing, and purpose is to prevent that legacy data is residual.
2. correcting data management system as claimed in claim 1, it is characterized in that: this supervisory routine comprises that also correction data generates historical query and the inquiry of correction data deleting history, owing in the program of calling in, made " correction data generation record sheet " file MAKE_LIST.TXT, therefore can find generation history as long as show its file content, owing in delete program, made " correction data deletion record table " file CLEAR_LIST.TXT, therefore can find deleting history as long as show its file content.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 01134482 CN1238807C (en) | 2001-11-06 | 2001-11-06 | Correcting data management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 01134482 CN1238807C (en) | 2001-11-06 | 2001-11-06 | Correcting data management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1417794A true CN1417794A (en) | 2003-05-14 |
| CN1238807C CN1238807C (en) | 2006-01-25 |
Family
ID=4672529
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 01134482 Expired - Fee Related CN1238807C (en) | 2001-11-06 | 2001-11-06 | Correcting data management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1238807C (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104567981A (en) * | 2013-10-22 | 2015-04-29 | 纬创资通股份有限公司 | Testing device and product testing method thereof |
| CN115326194A (en) * | 2022-10-17 | 2022-11-11 | 荣耀终端有限公司 | Ambient light sensor calibration method, electronic device and storage medium |
-
2001
- 2001-11-06 CN CN 01134482 patent/CN1238807C/en not_active Expired - Fee Related
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104567981A (en) * | 2013-10-22 | 2015-04-29 | 纬创资通股份有限公司 | Testing device and product testing method thereof |
| CN115326194A (en) * | 2022-10-17 | 2022-11-11 | 荣耀终端有限公司 | Ambient light sensor calibration method, electronic device and storage medium |
| CN115326194B (en) * | 2022-10-17 | 2023-02-17 | 荣耀终端有限公司 | Ambient light sensor calibration method, electronic device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1238807C (en) | 2006-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109597763B (en) | Consistency verification method and device for normalizing multiple items of data | |
| US6240427B1 (en) | Method and apparatus for archiving and deleting large data sets | |
| CN101046763A (en) | Implementing method of automatic test system based on scenario | |
| CN100454266C (en) | Method for checking correct of assembling position of computer assembly | |
| US20060112189A1 (en) | Method for tracking transport requests and computer system with trackable transport requests | |
| CN101174237A (en) | Automatic test method, system and test device | |
| CN1238807C (en) | Correcting data management system | |
| US7689608B2 (en) | Methods, systems and computer program products for controlling network asset recovery | |
| US6499001B1 (en) | Engineering database feedback system | |
| CN115204810B (en) | Project management method, device and storage medium based on automation script | |
| CN115238923A (en) | Equipment management system | |
| JP2008225637A (en) | Facility maintenance management system | |
| CN111859884A (en) | Statistical method for full history stack of approval data | |
| CN117407362B (en) | Method and device for file migration among heterogeneous file systems | |
| CN117591497B (en) | Nuclear power historical data cross-system migration method | |
| JPH03252868A (en) | Revision number control processing system | |
| CN111507066B (en) | Method and system for uploading and loading files and analyzing and warehousing | |
| CN117591495B (en) | Data storage method and system for nuclear power historical data migration | |
| CN115809231A (en) | Accurate self-correcting method and device for case information management system data | |
| CN115082083A (en) | Production management tracing module | |
| CN114253836A (en) | Test case management method based on tasks and personnel | |
| JP2002297224A (en) | Manufacture history information management method and system therefor | |
| CN2593207Y (en) | Element measuring apparatus | |
| JP3109546B2 (en) | Manufacturing process control method | |
| WO2003098903A1 (en) | Subscriber line validation of a telephone network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C19 | Lapse of patent right due to non-payment of the annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |