JP5282640B2 - Data processing apparatus, data processing method, and data processing program - Google Patents

Description

  The present disclosure relates to a data processing device, a data processing method, and a data processing program for processing data.

  Converts and saves the conversion source CAD (Computer Aided Design) data specified in the desired structural unit, verifies the consistency in the structural unit from the conversion result, and combines the individual converted data if possible. There is a technique to generate (see, for example, Patent Document 1 below).

JP 2007-179264 A

  However, when converting from CAD data to mock-up data, when trying to convert an entire product composed of a plurality of parts, there is a problem that conversion may not be possible due to a shortage of computer resources.

  In this case, it is necessary to divide into several parts, convert the divided parts into mockup data, and combine them to create mockup data for the entire product. At that time, there is a problem that it is difficult to determine what size the batch can be converted in, and how much the size needs to be divided.

  In order to solve the above-described problems caused by the prior art, the present disclosure provides a data processing apparatus, a data processing method, and a data processing program for improving the efficiency of data conversion by preventing a conversion error due to lack of resources. The purpose is to provide.

  In order to solve the above-described problems and achieve the object, the present disclosure acquires success or failure of data conversion to mock-up data having a smaller data size with respect to CAD data to be converted among CAD data groups having a hierarchical structure, When the success or failure of the acquired data conversion is a conversion failure, the data size of the CAD data to be converted is registered in a database, CAD data as a conversion candidate is designated, the database is referred to, and the designation means It is determined whether or not the data size of the designated conversion candidate CAD data is equal to or larger than the data size for which data conversion has failed, and the CAD data to be converted is determined based on the determined determination result. It is a requirement to output the determined result to the conversion destination of the CAD data to be converted.

  According to the present data processing device, data processing method, and data processing program, it is possible to improve the efficiency of data conversion by preventing conversion errors due to lack of resources.

It is explanatory drawing which shows the outline | summary of the data processing concerning embodiment. It is explanatory drawing which shows an assembly tree. It is a block diagram which shows the hardware constitutions of the data processing apparatus concerning embodiment. It is explanatory drawing which shows the memory content of failure example database (DB). It is a block diagram which shows the functional structure of a data processing system. It is a flowchart (the 1) which shows the data processing procedure by the data processing apparatus concerning this Embodiment. It is a flowchart (the 2) which shows the data processing procedure by the data processing apparatus concerning this Embodiment.

  Exemplary embodiments of a data processing device, a data processing method, and a data processing program according to the present disclosure will be described below in detail with reference to the accompanying drawings. In this embodiment, data before conversion is CAD data, and data after conversion is mock-up data. The mock-up data is shape data composed of polygons, and is simplified data of CAD data. Mock-up data has a smaller data size than CAD data.

(Outline of data processing)
FIG. 1 is an explanatory diagram of an outline of data processing according to the embodiment. (A) shows an example of failure in conversion from CAD data 100 of the notebook personal computer to mock-up data 110 as a conversion target. In the case of (A), an attempt was made to convert the CAD data 100 to the mock-up data 110 using an existing data conversion tool, but the process ended abnormally due to a lack of memory. That is, the data conversion has failed.

  (B) refers to past failure cases such as (A), and divides the CAD data 100 of the notebook personal computer into CAD data groups 101 to 106 in the lower hierarchy before executing the data conversion in (A). To do. Then, the respective CAD data 101 to 106 are converted into mockup data 111 to 116 by a data conversion tool.

  In this example, since the data sizes of the individual CAD data 101 to 106 are reduced, the data conversion is successful without falling into a memory shortage. Finally, the mock-up data groups 111 to 116 after conversion are combined by an existing combining tool, thereby generating the mock-up data 110 of the notebook computer corresponding to the CAD data 100 of the notebook computer.

(Assembly tree)
FIG. 2 is an explanatory diagram showing an assembly tree. The assembly tree AT is information representing the hierarchical structure of data to be converted (in the example of FIG. 1, CAD data 100 of a notebook personal computer). Each ellipse in FIG. 2 represents an assembly Aij. I in Aij indicates a hierarchy number, and j is a number unique to the assembly Aij in the i-th hierarchy. The first level assembly A11 is also referred to as a top assembly. Each assembly Aij has a coordinate position. The end assembly Aij is associated with the CAD data Dij. For example, assembly A34 is associated with CAD data D34.

  The assembly Aij in the i-th layer is an assembly that is a combination of the assembly A (i + 1) j in the (i + 1) -th layer as a child. If attention is paid to the first hierarchy and the second hierarchy, the top assembly A11 is composed of assemblies A21 to A26. In other words, the assembly A11 is constructed by combining the assemblies A21 to A26. Therefore, the assembly of the (i + 1) th hierarchy as a child necessarily has a smaller data size than the assembly of the ith hierarchy as a parent.

  Further, the assembly Aij other than the end is not associated with the CAD data, but a combination of the end assemblies Aij becomes a collection of CAD data. For example, the assembly A22 is CAD data obtained by combining the CAD data D34 of the assembly A34, the CAD data D35 of the assembly A35, and the CAD data D36 of the assembly A36.

  1 is the top assembly A11, the liquid crystal unit CAD data 101 is the assembly A21, the keyboard unit CAD data 102 is the assembly A22, the main unit CAD data 103 is the assembly A23, and the hard disk. The unit CAD data 104 is assembly A24, the battery unit CAD data 105 is assembly A25, and the floppy unit CAD data 106 is assembly A26.

(Hardware configuration of data processor)
FIG. 3 is a block diagram of a hardware configuration of the data processing apparatus according to the embodiment. In FIG. 3, the data processing device includes a CPU (Central Processing Unit) 301, a ROM (Read-Only Memory) 302, a RAM (Random Access Memory) 303, a magnetic disk drive 304, a magnetic disk 305, and an optical disk drive. 306, an optical disk 307, a display 308, an I / F (Interface) 309, a keyboard 310, a mouse 311, a scanner 312, and a printer 313. Each component is connected by a bus 300.

  Here, the CPU 301 controls the entire data processing apparatus. The ROM 302 stores a program such as a boot program. The RAM 303 is used as a work area for the CPU 301. The magnetic disk drive 304 controls the reading / writing of the data with respect to the magnetic disk 305 according to control of CPU301. The magnetic disk 305 stores data written under the control of the magnetic disk drive 304.

  The optical disk drive 306 controls the reading / writing of the data with respect to the optical disk 307 according to control of CPU301. The optical disk 307 stores data written under the control of the optical disk drive 306, and causes the computer to read data stored on the optical disk 307.

  The display 308 displays data such as a document, an image, and function information as well as a cursor, an icon, or a tool box. As this display 308, for example, a CRT, a TFT liquid crystal display, a plasma display, or the like can be adopted.

  An interface (hereinafter abbreviated as “I / F”) 309 is connected to a network 314 such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet through a communication line, and the other via the network 314. Connected to other devices. The I / F 309 serves as an internal interface with the network 314 and controls data input / output from an external device. For example, a modem or a LAN adapter can be adopted as the I / F 309.

  The keyboard 310 includes keys for inputting characters, numbers, various instructions, and the like, and inputs data. Moreover, a touch panel type input pad or a numeric keypad may be used. The mouse 311 performs cursor movement, range selection, window movement, size change, and the like. A trackball or a joystick may be used as long as they have the same function as a pointing device.

  The scanner 312 optically reads an image and takes in the image data into the data processing apparatus. The scanner 312 may have an OCR (Optical Character Reader) function. The printer 313 prints image data and document data. As the printer 313, for example, a laser printer or an ink jet printer can be employed.

(Memory contents of failure case DB)
FIG. 4 is an explanatory diagram showing the contents stored in the failure case DB. In FIG. 4, the failure example DB 400 has a file name item and a data size item, and is recorded in units of files. The file entered as a record in the failure case DB 400 is CAD data that has failed in data conversion.

  For example, the record on the first line indicates that the data conversion failed because the data size of the CAD data 100 of the assembly A11 which is a file name: notebook computer is 2500 [Mbytes]. The record on the second line indicates that the data conversion failed because the data size of the CAD data 101 of the assembly A21 which is the file name: liquid crystal unit is 700 [Mbytes]. CAD data that has not been entered in the failure case DB 400 is CAD data that has been successfully converted or has not yet been converted.

  In the example of FIG. 4, if the data size of CAD data that is a conversion candidate is less than 700 [Mbyte], the conversion candidate CAD data may be directly converted into mockup data. On the other hand, if the data size of the CAD data that is the conversion candidate is 700 [Mbyte] or more, the assembly Aij that is the CAD data of the conversion candidate is divided into the assembly A (i + 1) j in the lower hierarchy. Then, the divided assembly A (i + 1) j is compared with the failure case DB 400 as a conversion candidate. If the data conversion fails, the file name and data size of the failed CAD data are registered.

  The failure case DB 400 shown in FIG. 4 may be incorporated in the same computer as the data processing apparatus, or may be incorporated in another computer via a network. Further, the failure example DB 400 specifically realizes its function by a storage device such as the ROM 302, the RAM 303, and the magnetic disk 305 shown in FIG.

(Functional configuration of data processing system)
FIG. 5 is a block diagram showing a functional configuration of the data processing system. The data processing system 500 includes a data processing device 501, a conversion unit 502, and a combining unit 503. The conversion unit 502 may be incorporated in the same computer as the data processing apparatus 501 or may be incorporated in another computer via a network. The same applies to the coupling portion 503.

  The data processing device 501 includes an acquisition unit 511, a registration unit 512, a designation unit 513, a determination unit 514, a determination unit 515, and an output unit 516. Specifically, the acquisition unit 511 to the output unit 516, the conversion unit 502, and the coupling unit 503 described above store, for example, programs stored in a storage device such as the ROM 302, the RAM 303, and the magnetic disk 305 illustrated in FIG. The function is realized by executing or by the I / F 309.

  The conversion unit 502 has a function of converting data to be converted into mockup data. The conversion unit 502 is realized by an existing data conversion tool. Also, the conversion unit 502 displays the assembly name (corresponding to the file name) of the CAD data to be converted, information on whether the data conversion from the CAD data to the mock-up data has succeeded or failed, and if it fails, the CAD The data size of the data is output to the data processing device 501.

  The combining unit 503 combines the mockup data groups by the assembly of the assembly tree AT associated with each mockup data. The combining unit 503 is also realized by an existing data combining tool.

  The acquisition unit 511 has a function of acquiring success or failure of data conversion to a smaller data size for the conversion target. In the acquisition unit 511, the assembly name (corresponding to the file name) of the CAD data to be converted, information on whether the data conversion from the CAD data to the mock-up data has succeeded, and in the case of failure, the CAD data You will get the data size.

  The registration unit 512 has a function of registering the data size to be converted in the DB when the success or failure of the data conversion acquired by the acquisition unit 511 is conversion failure. Specifically, for example, if data conversion fails, the acquired assembly name and data size are additionally registered in the failure case DB 400 as a new record.

  The designation unit 513 has a function of designating conversion candidate data. Specifically, for example, the assemblies Aij are sequentially specified from the top assembly A11 which is the highest hierarchy of the assembly tree AT to the lower hierarchy. In this way, by designating from the upper hierarchy, it is possible to confirm whether batch conversion is possible up to the data size around that. Therefore, the number of data conversions can be reduced by converting the data with as large a data size as possible, and if the conversion cannot be performed, the number of conversion failures can be reduced by lowering the assembly Aij.

  The determination unit 514 has a function of referring to the DB to determine whether or not the data size of the conversion candidate specified by the specifying unit 513 is equal to or larger than the data size for which data conversion has failed. Specifically, for example, with reference to the failure case DB 400, it is determined whether or not the data size of the assembly Aij as a conversion candidate is equal to or larger than the data size recorded in the failure case DB 400. Here, as the data size of the failure case DB 400 to be compared with the data size of the conversion candidate assembly Aij, the smallest data size in the failure case DB 400 is preferably used from the viewpoint of preventing conversion failure.

  Further, when the resource of the data processing device 501 increases or decreases in time series, only records from the current time to a predetermined time before among the records in the failure case DB 400 may be targeted. In this case, the time stamp at the time of registration is also stored in the failure case DB 400. Thus, by narrowing down the target records, it is possible to make a determination according to the usage status of the data processing device 501.

  The determination unit 515 has a function of determining a conversion target based on the determination result determined by the determination unit 514. Specifically, when it is determined that the data size is equal to or greater than the data size that failed in data conversion, lower-order data that is a component of the conversion candidate is determined as the conversion candidate. For example, if the data size of the conversion candidate assembly Aij is Sij and the minimum data size in the failure case DB 400 is Sf, data conversion is not executed for the assembly Aij when Sij ≧ Sf. In this case, the assembly A (i + 1) j, which is one level lower than the assembly Aij, is caused to determine again as the conversion candidate as the conversion candidate.

  On the other hand, if the determination unit 515 determines that the data size is not equal to or larger than the data size for which data conversion has failed, the determination unit 515 determines a conversion candidate as a conversion target. For example, when Sij ≧ Sf, the assembly Aij is determined as CAD data to be converted.

  The output unit 516 has a function of outputting the determination result determined by the determination unit 515 to a conversion target conversion destination. Specifically, for example, the assembly Aij determined by the determination unit 515 is passed to the conversion unit 502. The conversion unit 502 converts the passed assembly Aij from CAD data to mockup data.

(Data processing procedure)
6 and 7 are flowcharts showing a data processing procedure by the data processing apparatus 501 according to the present embodiment. In FIG. 6, first, the acquisition unit 511 acquires CAD data and the assembly tree AT (step S601). Next, i = 1 (step S602), j = 1 (step S603), and it is determined whether i> N is satisfied (step S604). That is, it is determined whether or not the i-th layer is the terminal N-th layer.

  If i> N (step S604: Yes), the process proceeds to step S611. On the other hand, if i> N is not satisfied (step S604: No), it is determined whether j> Mi is satisfied (step S605). Mi is the total number of assemblies in the i-th layer. That is, it is determined whether or not the confirmation of all assemblies Aij in the i-th layer has been completed.

  If j> Mi (step S605: Yes), all the assemblies Aij in the i-th hierarchy have been confirmed, so i is incremented to a lower hierarchy (step S606), and the process returns to step S603. On the other hand, if j> Mi is not satisfied (step S605: No), the data size Sij of the assembly Aij is detected (step S607), and the failure case DB 400 is accessed (step S608). Then, it is determined whether or not Sij ≧ Sf (step S609).

  If Sij ≧ Sf is not satisfied (step S609: NO), the process proceeds to step S701 in FIG. On the other hand, if Sij ≧ Sf (step S609: Yes), j is incremented (step S610), and the process returns to step S605. Thereby, the assembly Aij in the i-th hierarchy can be comprehensively confirmed.

  In step S604, if i> N (step S604: Yes), since all the assemblies Aij have been confirmed, the conversion unit 502 determines whether there is an unconverted assembly Aij (step S611). ). When there is no unconverted assembly Aij (step S611: No), a series of processing is ended. In this case, the combining unit 503 executes the combined process of the converted mockup data. On the other hand, when there is an unconverted assembly Aij (step S611: Yes), since the joining process by the joining unit 503 cannot be executed, an error is output (step S612).

  When Sij ≧ Sf is not satisfied (step S609: No), the determination unit 515 determines the assembly Aij as a conversion target in step S701 in FIG. 7 (step S701). Then, the output unit 516 outputs a determination result, for example, a data conversion instruction for the assembly Aij determined to be converted (step S702). Thereafter, the conversion unit 502 executes data conversion processing of the assembly Aij determined as the conversion target.

  Then, the acquisition unit 511 waits for acquisition of conversion success / failure from the conversion unit 502 (step S703: No). When the conversion success / failure is acquired (step S703: Yes), it is determined whether or not the conversion has failed (step S704). When it is not failure (data conversion success) (step S704: No), the process proceeds to step S610. On the other hand, if it is a failure (step S704: Yes), the registration unit 512 registers the data size in the failure case DB 400 (step S705). Thereafter, the hierarchy number i is incremented (step S706), and the process returns to step S603 in FIG.

  As described above, in the present embodiment, by registering the data size in which the data conversion has failed in the failure example DB 400 and comparing it with the data size Sij of the conversion candidate assembly Aij, prior to the data conversion of the assembly Aij, It can be predicted whether the data conversion of the assembly Aij will succeed or fail. As a result, when it is predicted that the data conversion is successful, the number of data conversions can be reduced by executing the data conversion.

  On the other hand, if it is predicted to fail, an assembly A (i + 1) j of a lower hierarchy whose data size is smaller than that of the assembly Aij is newly set as a conversion candidate, and again compared with the data size for which data conversion has failed. Thereby, data conversion failure can be prevented and the number of conversion failures can be reduced.

  From the above, this embodiment has an effect that the efficiency of data conversion can be improved by preventing a conversion error due to resource shortage.

  The data processing method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The data processing program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The data processing program may be distributed via a network such as the Internet.

400 Failure case DB
500 data processing system 501 data processing device 502 conversion unit 503 combination unit 511 acquisition unit 512 registration unit 513 designation unit 514 determination unit 515 determination unit 516 output unit

Claims (5)

Acquisition means for acquiring success or failure of data conversion to mock-up data having a smaller data size with respect to CAD data to be converted in a CAD data group having a hierarchical structure;
If the success or failure of the data conversion acquired by the acquisition means is a conversion failure, registration means for registering the data size of the CAD data to be converted in a database;
A specifying means for specifying CAD data as a conversion candidate;
Determining means for referring to the database to determine whether or not the data size of the CAD data of the conversion candidate specified by the specifying means is equal to or larger than the data size that failed in data conversion;
A determination unit that determines the CAD data to be converted based on the determination result determined by the determination unit;
An output unit that outputs a determination result determined by the determination unit to a conversion destination of the CAD data to be converted;
A data processing apparatus comprising: The determining means includes
2. The data according to claim 1, wherein if it is determined that the data size is not less than the data size that failed in data conversion, lower-order CAD data that is a component of the CAD data of the conversion candidate is determined as the conversion candidate. Processing equipment. The determining means includes
3. The data processing apparatus according to claim 1, wherein if it is determined that the data size is not equal to or larger than the data size that failed in data conversion, the CAD data as the conversion candidate is determined as the CAD data to be converted. A computer that can access the database
An acquisition step of acquiring success or failure of data conversion to mock-up data having a smaller data size with respect to CAD data to be converted in a CAD data group having a hierarchical structure;
If the success or failure of the data conversion acquired by the acquisition step is a conversion failure, a registration step of registering the data size of the CAD data to be converted in a database;
A designation step for designating CAD data as a conversion candidate;
A determination step of referring to the database to determine whether or not the data size of the CAD data of the conversion candidate specified by the specifying step is equal to or larger than the data size of the data conversion failure;
A determination step of determining the CAD data to be converted based on the determination result determined by the determination step;
An output step of outputting the determination result determined in the determination step to a conversion destination of the CAD data to be converted;
The data processing method characterized by performing. A computer that can access the database
Acquisition means for acquiring success or failure of data conversion to mock-up data having a smaller data size with respect to CAD data to be converted in a CAD data group having a hierarchical structure;
If the success or failure of the data conversion acquired by the acquisition means is a conversion failure, a registration means for registering the data size of the CAD data to be converted in a database;
A designation means for designating CAD data as a conversion candidate;
Determining means for referring to the database to determine whether or not the data size of the CAD data of the conversion candidate specified by the specifying means is greater than or equal to the data size that failed in data conversion;
A determination unit that determines the CAD data to be converted based on the determination result determined by the determination unit;
An output unit that outputs a determination result determined by the determination unit to a conversion destination of the CAD data to be converted;
A data processing program characterized by functioning as

Images