JP6010963B2 - Program, information processing apparatus and information processing method - Google Patents

Description

  The present invention relates to a program for executing information processing, an information processing apparatus, and an information processing method.

  2. Description of the Related Art Conventionally, a technique for performing structural analysis after dividing an object into meshes by a finite element method is known (see, for example, Patent Documents 1 to 3). In these cases, an operator corrects or changes a difference from the basic model for a new structure, and sets conditions for applying the finite element method.

Japanese Patent Laid-Open No. 10-269265 JP 2007-328393 A JP 2008-250641 A

  However, setting conditions is difficult for beginners, and calculation processing may be performed with incorrect settings, resulting in poor work efficiency.

The present invention has been made in view of such circumstances. The purpose is to provide a program or the like that can determine whether or not a constraint condition is satisfied in advance.

Program disclosed in the present application, the first direction in the coordinate and the nodes of each mesh node of the analysis object, identifies the presence or absence of constraint in the second direction and the third direction from the storage unit, having a constraint in the first direction 3 nodes can be extracted, and the coordinates of the extracted 3 nodes in the second direction and the third direction are different between the 3 nodes, and the coordinates of the 3 nodes in the 2nd direction are 2 nodes out of 3 nodes. mutually different in at least one combination, and determines whether they meet the third direction of coordinates of three nodes are different from one another at least one of combinations of three nodes in two nodes, the second It can be extracted 2 node having the direction of the constraint, and, the third direction of coordinates of the extracted two nodes is determined whether satisfied that differ, extracts one node having a constraint in the third direction competent the process of determining whether or not it is possible to To be executed by the over data.

  According to one aspect of the present application, it is possible to provide information on whether or not a constraint condition is satisfied in advance.

It is a block diagram which shows the hardware group of information processing apparatus. It is explanatory drawing which shows the display image of components. It is explanatory drawing which shows the mesh model with respect to a target object. It is explanatory drawing which shows the record layout of node DB. Explanatory drawing showing the joining situation It is explanatory drawing which shows the record layout of joining DB. It is explanatory drawing which shows the record layout of restraint DB. It is explanatory drawing which shows the record layout of target object DB. It is explanatory drawing which shows the coordinate stored in RAM. It is explanatory drawing which shows the record layout of a condition table. It is explanatory drawing which shows the example which extracted the coordinate of 2 points | pieces. It is a flowchart which shows the judgment process whether a judgment condition is satisfy | filled. It is a flowchart which shows the judgment process whether a judgment condition is satisfy | filled. It is a flowchart which shows the judgment process whether a judgment condition is satisfy | filled. FIG. 6 is a block diagram illustrating a hardware group of a computer according to a second embodiment. It is explanatory drawing which shows the record layout of relation DB. It is a flowchart which shows the detection process procedure of a constraint shortage direction. It is a flowchart which shows the detection process procedure of a constraint shortage direction. It is explanatory drawing which shows the example of two target objects. It is explanatory drawing which shows the example of other two target objects. It is explanatory drawing which shows the example of other two target objects. It is a functional block diagram which shows operation | movement of the computer of the form mentioned above. FIG. 10 is a block diagram illustrating a hardware group of a computer according to a third embodiment.

Embodiment 1
Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is a block diagram illustrating a hardware group of the information processing apparatus. The information processing apparatus 1 is, for example, a personal computer, a server computer, or a PDA (Personal Digital Assistance). Hereinafter, the information processing apparatus 1 will be described as being replaced with the computer 1. The computer 1 includes a central processing unit (CPU) 11, a random access memory (RAM) 12, an input unit 13, a display unit 14, a storage unit 15, a communication unit 16, and the like. The CPU 11 is connected to each part of the hardware via the bus 17. The CPU 11 controls each part of the hardware according to the control program 15P stored in the storage unit 15. The RAM 12 is, for example, SRAM (Static RAM), DRAM (Dynamic RAM), flash memory, or the like. The RAM 12 temporarily stores various data generated when the CPU 11 executes various programs.

  The input unit 13 is an operation button, a mouse, a keyboard, a touch panel, or the like, and outputs input information to the CPU 11. The display unit 14 is, for example, a liquid crystal display or an organic EL (electroluminescence) display, and displays necessary information under the control of the CPU 11. The communication unit 16 is a wired or wireless LAN (Local Area Network) card or the like, and transmits / receives information to / from other computers by HTTP (HyperText Transfer Protocol) or the like. The storage unit 15 is, for example, a large-capacity flash memory or a hard disk, and stores the control program 15P. In accordance with the control program 15P, the CPU 11 performs a determination process as to whether or not the object satisfies a constraint condition. In the following description, the object is described as an example of a circuit board and a component mounted on the circuit board, but a motor or other mechanical component may be used.

  The storage unit 15 includes an IDF (Intermediate Data Format) file 151, a node database (hereinafter referred to as DB) 152, a joint DB 153, a constraint DB 154, an object DB 155, a condition table 156, and the like. The IDF file 151 stores shape data and position data of each object. The CPU 11 reads each object to be processed from the IDF file 151. The CPU 11 outputs the read target object to the display unit 14.

  FIG. 2 is an explanatory diagram showing a display image of components. The CPU 11 reads, for example, the component 20 that is a substrate and the components 201, 202, 203, 221, 222, and 23 (hereinafter abbreviated as the component 200 in some cases) on the substrate from the IDF file 151 and displays them on the display unit 14. To do. In the present embodiment, the components 201, 202, and 203 are bonded to the component 20 so as not to move. Hereinafter, a group of the parts 20 and the parts 201, 202, and 203 is referred to as an object 21 and is handled as one object (hereinafter, represented by 2 in some cases). Further, the component 221 and the component 222 are bonded so as not to move with each other. Hereinafter, a group of the component 221 and the component 222 is referred to as an object 22 and is handled as one object 2. In the following, the component 23 is sometimes referred to as a target 23 as a group of one component 200. The object 21 and the object 22 are in contact so that they can move. The object 21 and the object 23 are in contact so that they can move.

  The CPU 11 creates a mesh model based on the finite element method for each component 200. The CPU 11 stores information on each node of the mesh in the node DB 152. FIG. 3 is an explanatory diagram showing a mesh model for the object 2. Each component 200 is meshed as shown in FIG. In the present embodiment, the description will be made assuming that the front-rear direction in FIG. The CPU 11 stores the coordinates of the nodes of the mesh in the node DB 152.

  FIG. 4 is an explanatory diagram showing a record layout of the node DB 152. The node DB 152 includes a node ID field, an X coordinate field, a Y coordinate field, a Z coordinate field, and a component ID field. The node ID field stores identification information (node ID) for specifying each node to which the mesh is applied. In the X coordinate field, the Y coordinate field, and the Z coordinate field, coordinates in the three-axis directions of each node are stored in association with the node ID. In the component ID field, a component ID for specifying the component 200 is stored in association with the node ID. It can be understood from FIG. 4 that the nodes having node IDs “1”, “2”, and “3” correspond to the component 200 having the component ID “1”.

  FIG. 5 is an explanatory view showing the joining state, and FIG. 6 is an explanatory view showing a record layout of the joining DB 153. There are two types of joining: bonding in which the parts 200 do not move and contact in which one or both of the parts 200 can move with a predetermined coefficient of friction. The parts 20 and 201, the parts 20 and 202, the parts 20 and 203, and the parts 221 and 222 are bonded as shown by thick solid lines. The parts 20 and 222 and the parts 20 and 23 are in contact with each other as shown by hatching. That is, the object 21 and the object 22 and the object 21 and the object 23 are in contact with each other as shown by hatching.

  The joint DB 153 includes a joint ID field, a joint type field, a part ID1 field, a part ID2 field, a friction coefficient field, and the like. In the joint ID field, identification information (hereinafter referred to as a joint ID) for specifying a joint related to the two components 200 is stored. In the junction type field, information on whether each junction portion is bonded or contacted is stored in association with the junction ID. In the example of FIG. 6, 0 indicates adhesion and 1 indicates contact. The component ID 1 field stores a component ID for specifying one of the components 200 to be joined. Similarly, the component ID 2 field stores a component ID for specifying the other of the components 200 to be joined.

  In the component ID1 and component ID2 fields, two component IDs to be bonded in association with the bonding ID are stored. In the friction coefficient field, when the joining type is contact, a friction coefficient is stored in association with the joining ID. Note that the friction coefficient is 0, exceeds 0, or no value is input.

  FIG. 7 is an explanatory diagram showing a record layout of the constraint DB 154. The constraint DB 154 includes a node ID field, a constraint direction field, and the like. In the restraining direction field, a direction for restraining the component 200 in association with the node ID is stored. In FIG. 7, constraint direction 1 indicates that there is a constraint in the X direction. In this case, the component 200 is restricted from moving in the X direction. The constraint direction 2 indicates that there is a constraint in the Y direction. In this case, the component 200 is restricted from moving in the Y direction. The constraint direction 3 indicates that there is a constraint in the Z direction. In this case, the component 200 is restricted from moving in the Z direction.

  The constraint direction 12 indicates that there is a constraint in the XY direction. In this case, the component 200 is restricted from moving in the XY direction. The constraint direction 13 indicates that there is a constraint in the XZ direction. In this case, the component 200 is restricted from moving in the XZ direction. The constraint direction 23 indicates that there is a constraint in the YZ direction. In this case, the component 200 is restricted from moving in the YZ direction. A constraint direction 123 indicates that there is a constraint in the XYZ directions. In this case, the component 200 is restricted from moving in the XYZ directions. Note that the file and DB described above may be input in advance by the user as appropriate.

  FIG. 8 is an explanatory diagram showing a record layout of the object DB 155. The object DB 155 includes an object ID field, a constraint direction field, a part ID1 field, a part ID2 field, a part ID3 field, a part ID4 field, and the like. In the target object ID field, identification information (hereinafter referred to as a target object ID) for specifying the target object 2 that forms a group by bonding the parts 200 together is stored. The constraint direction is stored in the constraint direction field in association with the object ID. The processing for calculating the constraint direction will be described later. The numerical values in the restraining direction are as described in FIG.

  In the component ID 1 field and the component ID 2 field, the component ID of each component 200 constituting the object 2 is stored. For example, in the object 2 with the object ID2, the component 200 with the component ID2 and the component 200 with the component ID3 are bonded. Further, it can be understood that the object 2 is restricted from moving in the Z direction. The CPU 11 reads a combination of component IDs in which the adhesion of the bonding DB 153 is stored. CPU11 performs the process which combines component ID, when some component ID is common in the read combinations. The CPU 11 assigns an object ID to the combined component ID. The CPU 11 stores the object ID and the combined part ID in the object DB 155.

  The CPU 11 assigns an object ID to a combination having only two component IDs. The CPU 11 stores the object ID and the two component IDs in the object DB 155. The CPU 11 extracts the constraint direction by the process described below for each target object 2, and stores the extracted constraint direction in the target object DB 155 in association with the target object ID. The file and DB record layouts described in this embodiment are merely examples, and the present invention is not limited to this. Other storage forms may be used as long as the relationship between data is maintained. Further, in addition to storing in the storage unit 15, it may be stored in the RAM 12 or another computer (not shown).

  FIG. 9 is an explanatory diagram showing coordinates stored in the RAM 12. The CPU 11 sets the first direction as the X axis, the second direction as the Y axis, and the third direction as the Z axis. The CPU 11 extracts three coordinates having a constraint direction in the X-axis direction, which is the first direction, with reference to the constraint DB 154 and the node DB 152. In FIG. 9, the first coordinate (i, j, k) = (0.0,0.0,0.0) having a binding force in the X-axis direction, the second coordinate (i, j, k) = (1.0,2.0,3.0), The example which extracted the 3rd coordinate (i, j, k) = (-2.0, -3.0, -4.0) is shown. The CPU 11 stores three coordinate values in the RAM 12.

  The CPU 11 reads the first condition stored in the storage unit 15. The first condition is that the coordinates in the second direction and the third direction of the three nodes are different from each other between the three nodes, and the coordinates in the second direction of the three nodes are different from each other in at least one of the combinations of the two nodes in the three nodes. In addition, the coordinates in the third direction of the three nodes are different from each other in at least one of the combinations of two of the three nodes. The CPU 11 determines whether or not the coordinates in the second direction and the third direction of the three nodes extracted first are different between the three nodes. Specifically, the CPU 11 determines whether or not (1j, 1k) ≠ (2j, 2k) and (2j, 2k) ≠ (3j, 3k) and (3j, 3k) ≠ (1j, 1k) are satisfied. To do.

  Next, the CPU 11 determines whether or not the coordinates in the third direction of the three nodes are different from each other between at least one of the three nodes. Specifically, it is determined whether or not (1k ≠ 2k) or (2k ≠ 3k) or (3k ≠ 1k) is satisfied. Further, the CPU 11 determines whether or not the coordinates in the second direction of the three nodes are different from each other between at least one of the three nodes. Specifically, it is determined whether or not (1j ≠ 2j) or (2j ≠ 3j) or (3j ≠ 1j) is satisfied. When determining that the first condition is satisfied, the CPU 11 stores information satisfying the first determination condition in the condition table 156 in association with the axial direction. The first determination condition means that in addition to satisfying the first condition, three nodes having constraints in the first direction can be extracted. If the CPU 11 determines that the first determination condition is not satisfied, the CPU 11 extracts other three points having a binding force in the X-axis direction and determines again whether or not the first determination condition is satisfied. When it is determined that there is no node that satisfies the first determination condition, information that does not satisfy the first determination condition is stored in association with the axial direction.

  FIG. 10 is an explanatory diagram showing a record layout of the condition table 156. The condition table 156 stores information regarding whether or not the first determination condition, the second determination condition, and the third determination condition are satisfied in association with the direction of the three-axis orthogonal coordinate system. In the example of FIG. 10, when the first direction is the X axis, the second direction is the Y axis, and the third direction is the Z axis, the first determination condition is stored as ◯. That is, information that satisfies the first determination condition is stored. On the other hand, the second determination condition is stored as x. That is, information that does not satisfy the second determination condition is stored.

  The CPU 11 can extract the second node having the second determination condition and the constraint in the second direction, and determines whether or not the coordinates in the third direction of the extracted two nodes are different. The CPU 11 refers to the node DB 152 and the constraint DB 154 and extracts two points having a constraint force in the Y-axis direction.

  FIG. 11 is an explanatory diagram showing an example in which the coordinates of two points are extracted. The CPU 11 determines whether or not the coordinates in the third direction (Z direction) of the extracted two nodes as the second condition are different. Specifically, it is determined whether or not (4k ≠ 5k) is satisfied. When determining that the second determination condition is satisfied, the CPU 11 stores information that satisfies the second determination condition in the condition table 156 in association with the axial direction. The second determination condition means that in addition to satisfying the second condition, two nodes having constraints in the second direction can be extracted. When the CPU 11 determines that the second determination condition is not satisfied, the CPU 11 extracts other two points having a binding force in the Y-axis direction, and determines again whether the second determination condition is satisfied. When it is determined that there is no node that satisfies the second determination condition, information that does not satisfy the second determination condition is stored in association with the axial direction.

  The CPU 11 determines whether it is possible to extract one node having the third determination condition, the constraint in the third direction. The CPU 11 refers to the node DB 152 and the constraint DB 154 and extracts one point having a constraint force in the Z-axis direction. When the CPU 11 determines that the third determination condition is satisfied, the CPU 11 stores information that satisfies the third determination condition in the condition table 156 in association with the axial direction. If the CPU 11 determines that a node having a binding force in the Z-axis direction cannot be extracted, the CPU 11 stores information that does not satisfy the third determination condition in association with the axial direction.

  The CPU 11 performs the above-described process again with the first direction as the Y-axis direction, the second direction as the Z-axis direction, and the third direction as the X-axis direction. The CPU 11 stores the processing result in the condition table 156. In the example of FIG. 10, information that the condition is not satisfied is stored in all of the first direction, the second direction, and the third direction. The CPU 11 finally performs the above-described processing again with the first direction as the Z-axis direction, the second direction as the X-axis direction, and the third direction as the Y-axis direction. The CPU 11 stores the processing result in the condition table 156. In the example of FIG. 10, information that the condition is not satisfied is stored in all of the first direction, the second direction, and the third direction.

  The CPU 11 refers to the condition table 156 and extracts a three-axis orthogonal coordinate system that satisfies the most conditions. In the example of FIG. 10, it can be understood that the most conditions are satisfied when the first direction is the X axis, the second direction is the Y axis, and the third direction is the Z axis. If the number satisfying many conditions is the same, any one of the three-axis orthogonal coordinate systems may be extracted. The CPU 11 refers to the condition table 156 and extracts the axis (direction) satisfying the first to third determination conditions as the constraint direction of the object 2 in the extracted three-axis orthogonal coordinate system. That is, when the first direction of the three-axis orthogonal coordinate system is the X axis, the second direction is the Y axis, and the third direction is the Z axis, the X direction is constrained when the first determination condition is satisfied, and the second determination condition is satisfied. If the Y direction is constrained and the third determination condition is satisfied, the Z direction is constrained. When the first direction of the three-axis orthogonal coordinate system is the Y-axis, the second direction is the Z-axis, and the third direction is the X-axis, the Y direction is constrained when the first determination condition is satisfied, and the second determination condition is satisfied If the Z direction is constrained and the third determination condition is satisfied, it indicates that the X direction is constrained.

  When the first direction of the three-axis orthogonal coordinate system is the Z-axis, the second direction is the X-axis, and the third direction is the Y-axis, the Z direction is constrained when the first determination condition is satisfied, and the second determination condition is satisfied X When the direction is constrained and the third determination condition is satisfied, the Y direction is constrained. In the example of FIG. 10, the first direction is the X axis, the second direction is the Y axis, and the third direction is the Z axis, which satisfies the first determination condition and the third determination condition. Is extracted as the constraint direction. The CPU 11 stores the constraint direction in the object DB 155 in association with the object ID. CPU11 performs the above process about each target object 2. FIG. In the example of FIG. 8, it can be understood that the object 2 with the object ID “1” satisfies the constraint conditions in the X-axis and Y-axis directions. In addition, it can be understood that the object 2 with the object ID “5” satisfies the constraint condition in all directions of the X-axis direction, the Y-axis direction, and the Z-axis direction.

  FIG. 12 to FIG. 14 are flowcharts showing determination processing for determining whether or not the determination condition is satisfied. The CPU 11 sets the first direction as the X axis, the second direction as the Y axis, and the third direction as the Z axis (step S121). The CPU 11 refers to the node DB 152 and the constraint DB 154, and extracts three nodes having constraints in the first direction (step S122). The CPU 11 determines whether or not three nodes having constraints in the first direction cannot be extracted (step S123). If the CPU 11 determines that extraction is not possible (YES in step S123), the process proceeds to step S131. If the CPU 11 determines that three nodes have been extracted (NO in step S123), the process proceeds to step S124.

  The CPU 11 reads the first condition from the storage unit 15. The CPU 11 determines whether or not the coordinates of the third node in the second direction and the third direction are different between the three nodes (step S124). If the CPU 11 determines that there is a difference between the three nodes (YES in step S124), the process proceeds to step S125. The CPU 11 determines whether or not the coordinates in the second direction of the three nodes are different from each other in at least one of the combinations of the two nodes among the three nodes (step S125). If the CPU 11 determines that there is a difference (YES in step S125), the process proceeds to step S126.

  The CPU 11 determines whether or not the coordinates in the third direction of the three nodes are different from each other in at least one of the combinations of the two nodes among the three nodes (step S126). If the CPU 11 determines that there is a difference (YES in step S126), the process proceeds to step S127. Note that the order of the processes in steps S124 to S126 is not limited to this, and may be switched. The CPU 11 stores information satisfying the first determination condition in the condition table 156 in association with the three-axis orthogonal coordinate system (step S127). In the case of NO in step S124, in the case of NO in step S125, and in the case of NO in step S126, the CPU 11 shifts the process to step S128. The CPU 11 determines whether or not the processing has been completed for all combinations of three nodes extracted in step S122 (step S128).

  If the CPU 11 determines that the process has been completed for all combinations of three nodes (YES in step S128), the process proceeds to step S131. If the CPU 11 determines that the process has not been completed for all combinations of three nodes (NO in step S128), the process proceeds to step S129. The CPU 11 selects the other three unprocessed unprocessed nodes (step S129). CPU11 returns a process to step S124, and repeats the same process. If YES in step S123 or YES in step S128, the CPU 11 stores information that does not satisfy the first determination condition in association with the three-axis orthogonal coordinate system in the condition table 156 (step S131).

  After step S131 and step S127, the process proceeds to step S132. The CPU 11 refers to the node DB 152 and the constraint DB 154, and extracts two nodes having constraints in the second direction (step S132). The CPU 11 determines whether or not two nodes having constraints in the second direction cannot be extracted (step S133). If the CPU 11 determines that extraction cannot be performed (YES in step S133), the process proceeds to step S138. If the CPU 11 determines that two nodes have been extracted (NO in step S133), the process proceeds to step S134.

  The CPU 11 reads the second condition from the storage unit 15. The CPU 11 determines whether or not the coordinates in the third direction of the extracted two nodes are different (step S134). If the CPU 11 determines that there is a difference (YES in step S134), the process proceeds to step S135. The CPU 11 stores information that satisfies the second determination condition in association with the three-axis orthogonal coordinate system in the condition table 156 (step S135). In the case of NO at step S134, the CPU 11 shifts the process to step S136. The CPU 11 determines whether or not the process has been completed for all combinations of the two nodes extracted in step S132 (step S136).

  If the CPU 11 determines that the process has been completed for all combinations of two nodes (YES in step S136), the process proceeds to step S138. If the CPU 11 determines that the process has not been completed for all combinations of two nodes (NO in step S136), the process proceeds to step S137. The CPU 11 selects the other two unprocessed extracted nodes (step S137). CPU11 returns a process to step S134, and repeats the same process. If YES in step S136 or YES in step S133, the CPU 11 stores information that does not satisfy the second determination condition in association with the three-axis orthogonal coordinate system in the condition table 156 (step S138).

  After the processes of steps S135 and S138, the CPU 11 proceeds to step S139. The CPU 11 refers to the node DB 152 and the constraint DB 154 to determine whether or not one node having a constraint in the third direction can be extracted (step S139). If the CPU 11 determines that extraction is possible (YES in step S139), the process proceeds to step S141. The CPU 11 stores information satisfying the third determination condition in the condition table 156 in association with the three-axis orthogonal coordinate system (step S141). If the CPU 11 determines that extraction is not possible (NO in step S139), the process proceeds to step S142. The CPU 11 stores information that does not satisfy the third determination condition in the condition table 156 in association with the three-axis orthogonal coordinate system (step S142).

  The CPU 11 sets the first direction as the Y axis, the second direction as the Z axis, and the third direction as the X axis, and determines whether or not the above-described processing has been executed (step S143). If the CPU 11 determines that the above processing is not performed on the setting (NO in step S143), the CPU 11 returns the processing to step S122. Accordingly, the first determination condition, the second determination condition, and the third determination are also made in the condition table 156 for a three-axis orthogonal coordinate system in which the first direction is the Y axis, the second direction is the Z axis, and the third direction is the X axis. Information on whether or not the condition is satisfied is stored. If the CPU 11 determines that the process has been completed after setting the first direction as the Y axis, the second direction as the Z axis, and the third direction as the X axis (YES in step S143), the process proceeds to step S144. Let

  The CPU 11 determines whether or not the above-described processing has been executed after setting the first direction as the Z axis, the second direction as the X axis, and the third direction as the Y axis (step S144). If the CPU 11 determines that the above processing is not performed on the setting (NO in step S144), the CPU 11 returns the processing to step S122. Accordingly, the first determination condition, the second determination condition, and the third determination are also made in the condition table 156 for a three-axis orthogonal coordinate system in which the first direction is the Z axis, the second direction is the X axis, and the third direction is the Y axis. Information on whether or not the condition is satisfied is stored. If the CPU 11 determines that the process is completed after setting the first direction as the Z axis, the second direction as the X axis, and the third direction as the Y axis (YES in step S144), the process proceeds to step S145. Let

  The CPU 11 refers to the condition table 156 and extracts a three-axis orthogonal coordinate system that most satisfies the first determination condition, the second determination condition, and the third determination condition (step S145). The CPU 11 refers to the first determination condition to the third determination condition of the extracted three-axis orthogonal coordinate system, extracts a direction satisfying the condition, and stores it in the object DB 155 in association with the object ID (step S146). Specifically, the CPU 11 has the first determination condition when the three-axis orthogonal coordinate system extracted in step S145 has the first direction as the X axis, the second direction as the Y axis, and the third direction as the Z axis. In this case, information indicating that there is a constraint in the X-axis direction is stored. Similarly, the CPU 11 stores information indicating that there is a constraint in the Y-axis direction when the second determination condition is satisfied. When the CPU 11 has the third determination condition, the CPU 11 stores information indicating that there is a constraint in the Z-axis direction.

  In addition, the CPU 11 determines that the three-axis orthogonal coordinate system extracted in step S145 has the first direction as the Y axis, the second direction as the Z axis, and the third direction as the X axis. Information indicating that there is an axial constraint is stored. Similarly, the CPU 11 stores information that there is a constraint in the Z-axis direction when the second determination condition is satisfied. If the CPU 11 has the third determination condition, the CPU 11 stores information indicating that there is a constraint in the X-axis direction.

  Further, the CPU 11 determines that the three-axis orthogonal coordinate system extracted in step S145 has the first direction as the Z-axis, the second direction as the X-axis, and the third direction as the Y-axis. Information indicating that there is an axial constraint is stored. Similarly, the CPU 11 stores information indicating that there is a constraint in the X-axis direction when the second determination condition is satisfied. If the CPU 11 has the third determination condition, the CPU 11 stores information indicating that there is a constraint in the Y-axis direction. Thereby, the direction restrained for every target object 2 can be specified. For example, if the restraining directions are stored as 1, 2, and 3, it can be understood that the restraining directions are all in the X-axis, Y-axis, and Z-axis directions. When the restraining direction is stored as 1, it can be grasped that only the X-axis direction is restrained and the Y-axis and Z-axis are not restrained.

Embodiment 2
The second embodiment relates to a mode of outputting constraint information of the objects 2 that are in contact with each other. FIG. 15 is a block diagram illustrating a hardware group of the computer 1 according to the second embodiment. The storage unit 15 is provided with a relation DB 157. FIG. 16 is an explanatory diagram showing a record layout of the relation DB 157. The relation DB 157 includes a relation ID field, a first object ID field, a second object ID field, a contact direction field, a friction coefficient field, and a gravity direction field. In the relationship ID field, unique identification information (hereinafter referred to as relationship ID) for specifying two objects 2 in contact with each other is stored.

  In the first object ID field and the second object ID field, two object IDs are stored in association with the relationship ID. In the present embodiment, an example will be described in which the display unit 14 displays a direction in which the first object is insufficiently constrained in relation to the second object. In the example of FIG. 16, it is assumed that the object 2 with the object ID “1” and the object 2 with the object ID “2” are in a contact relationship and the relationship ID is “R1”. When the objects 2 are bonded to each other, they are regarded as one lump, that is, one object 2.

  In the contact direction field, the direction in which the first object and the second object are in contact with each other is stored in association with the relationship ID. Specifically, any information in the XY plane direction, the XZ plane direction, or the YZ plane direction is stored. The two objects 2 having the relationship ID “R1” indicate that they are in contact in the XY plane direction. In the friction coefficient field, the friction coefficients of the two objects 2 are stored in association with the relationship ID. The gravity direction field stores information on whether or not the first object exists in the gravity direction of the second object in association with the relationship ID.

  In the example of FIG. 16, when the first object exists in the gravity direction of the second object, that is, when the first object exists below the second object in the Z-axis direction, the circle information is stored. Is done. On the other hand, when the first object does not exist in the direction of gravity of the second object, that is, when the first object exists above the second object in the Z-axis direction, the information of X is stored.

  FIG. 17 and FIG. 18 are flowcharts showing the detection processing procedure for the insufficient constraint direction. The CPU 11 reads the contact direction and the friction coefficient of the first object and the second object with reference to the relation DB 157 (step S171). CPU11 reads the restraint direction of a 1st target object with reference to target object DB155 (step S172). CPU11 reads the restraint direction of a 2nd target object with reference to target object DB155 (step S173). The CPU 11 refers to the restraining direction read out in step S172, and determines whether or not it is restrained in all directions of the first object (step S174).

  If the CPU 11 determines that all directions of the first object are constrained (YES in step S174), the process proceeds to step S175. The CPU 11 outputs the object ID of the first object and information indicating that it is restrained to the display unit 14 (step S175). If the CPU 11 determines that all directions of the first object are not restrained (NO in step S174), the process proceeds to step S176. The CPU 11 refers to the relationship DB 157 and determines whether or not the contact directions for the first object and the second object are stored (step S176).

  When the CPU 11 determines that the contact direction is not stored (NO in step S176), the CPU 11 proceeds to step S182. The CPU 11 outputs the object ID of the first object, the direction in which the first object is not restrained, and information indicating that the object is not restrained to the display unit 14 (step S182). The CPU 11 refers to the object DB 155 and reads the constraint direction corresponding to the object ID. The CPU 11 outputs a direction that is not stored as a restraining direction as an unconstrained direction.

  If the CPU 11 determines that the contact direction is stored (YES in step S176), the process proceeds to step S177. CPU11 calculates the normal direction of a contact direction (step S177). The CPU 11 determines whether or not the calculated normal direction matches the unconstrained direction of the first object (step S178). If the CPU 11 determines that they do not match (NO in step S178), the process proceeds to step S183. If the CPU 11 determines that they match (YES in step S178), the CPU 11 determines whether one of the restraining directions of the second object is the same as the direction in which the first object is not restrained (step S179). .

  If the CPU 11 determines that the directions are not the same (NO in step S179), the process proceeds to step S182. The CPU 11 executes the process of step S182 described above. If the CPU 11 determines that the directions are the same (YES in step S179), the process proceeds to step S181. The CPU 11 determines whether or not the first object exists in the direction of gravity of the second object with reference to the relationship DB 157 (step S181). Specifically, the CPU 11 determines whether or not a circle is stored in the gravity direction field.

  When the CPU 11 determines that the first object exists in the direction of gravity of the second object (YES in step S181), the CPU 11 proceeds to step S184. The CPU 11 outputs the object ID of the first object and information indicating that it is restrained to the display unit 14 (step S184). If the CPU 11 determines that the first object does not exist in the direction of gravity of the second object (NO in step S181), the process proceeds to step S182. The CPU 11 performs the process of step S182 described above.

  If NO in step S178, CPU 11 determines whether the friction coefficient exceeds 0 (step S183). In the present embodiment, the case where the friction coefficient 0, that is, the friction coefficient is stored as 0 as the predetermined value in step S183, and the case where the friction coefficient is not stored in the relation DB 157 will be described as examples. It is not limited. For example, the friction coefficient 0.1 may be stored as a predetermined value, and the determination may be made based on whether the friction coefficient exceeds 0.1.

  If the CPU 11 determines that the friction coefficient exceeds 0 (YES in step S183), the process proceeds to step S184. The CPU 11 performs the process of step S184 described above. If the CPU 11 determines that the friction coefficient does not exceed 0 (NO in step S183), the process proceeds to step S185. The CPU 11 refers to the relation DB 157 and outputs the object ID of the first object, the direction in which the first object is not constrained, the friction coefficient, and information indicating that it is not constrained to the display unit 14 (step S185). ).

  FIG. 19 is an explanatory diagram showing an example of two objects 2. The object 2 indicated by A is the first object, and the object 2 indicated by B is the second object. Here, the restraining directions of the first object are the X direction and the Y direction. The constraint direction of the second object is the X direction, the Y direction, and the Z direction. The direction of insufficient restraint (Z-axis direction) of the first object indicated by A coincides with the normal direction (Z-axis direction) of the contact direction (XY plane direction). Since the direction of insufficient restraint of the first object coincides with one of the restraining directions (Z-axis direction) of the second object indicated by B, whether or not the first object exists in the gravity direction of the second object. Determine whether. Since the first object is above the second object, it does not exist in the direction of gravity. In this case, the CPU 11 outputs the ID of the first object and the shortage direction (Z-axis direction) to the display unit 14.

  The object 2 indicated by B is a first object, and the object 2 indicated by A is a second object. Here, the constraint direction of the first object indicated by B is the X direction, the Y direction, and the Z direction. The constraint direction of the first object indicated by A is the X direction and the Y direction. The first object indicated by B is constrained in all directions. Therefore, the CPU 11 outputs to the display unit 14 the object ID of the first object and information indicating that it is restrained.

  FIG. 20 is an explanatory diagram showing examples of the other two objects 2. The object 2 indicated by A is the first object, and the object 2 indicated by B is the second object. Here, the constraint direction of the first object is the X direction and the Y direction. The restraining direction of the second object is the Z direction. The friction coefficient of the first object and the second object is 0. The direction of insufficient restraint (Z-axis direction) of the first object indicated by A coincides with the normal direction (Z-axis direction) of the contact direction (XY plane direction). Since the direction of insufficient restraint of the first object coincides with one of the restraining directions (Z-axis direction) of the second object indicated by B, whether or not the first object exists in the gravity direction of the second object. Determine whether. Since the first object is above the second object, it does not exist in the direction of gravity. In this case, the CPU 11 outputs the ID of the first object and the shortage direction (Z-axis direction) to the display unit 14.

  The object 2 indicated by B is a first object, and the object 2 indicated by A is a second object. Here, the constraint direction of the first object indicated by B is the Z direction. The constraint direction of the second object indicated by A is defined as an X direction and a Y direction. The friction coefficient of the first object and the second object is 0. The restraint insufficient direction (X-axis direction and Y-axis direction) of the first object indicated by B does not match the normal direction (Z-axis direction). Since the friction coefficient is 0, the CPU 11 outputs the ID of the first object, the shortage direction (X-axis direction and Y-axis direction), and the friction coefficient 0 to the display unit 14.

  FIG. 21 is an explanatory diagram showing examples of the other two objects 2. The object 2 indicated by A is the first object, and the object 2 indicated by B is the second object. Here, the restraining directions of the first object are the X direction and the Y direction. The restraining direction of the second object is the Z direction. The friction coefficient of the first object and the second object is 0.3. The direction of insufficient restraint (Z-axis direction) of the first object indicated by A coincides with the normal direction (Z-axis direction) of the contact direction (XY plane direction). Since the direction of insufficient restraint of the first object coincides with one of the restraining directions (Z-axis direction) of the second object indicated by B, whether or not the first object exists in the gravity direction of the second object. Determine whether. Since the first object is above the second object, it does not exist in the direction of gravity. In this case, the CPU 11 outputs the ID of the first object and the shortage direction (Z-axis direction) to the display unit 14.

  The object 2 indicated by B is a first object, and the object 2 indicated by A is a second object. Here, the constraint direction of the first object indicated by B is the Z direction. The restraining directions of the second object indicated by A are the X direction and the Y direction. The friction coefficient of the first object and the second object is 0.3. The restraint insufficient direction (X-axis direction and Y-axis direction) of the first object indicated by B does not match the normal direction (Z-axis direction). Moreover, since the friction coefficient is 0.3, the CPU 11 outputs the ID of the first object and information indicating that it is restrained to the display unit 14. Thereby, based on the relationship between the objects 2, it is possible to easily provide the direction in which the constraint is insufficient for each object 2.

  The second embodiment is as described above, and the other parts are the same as those of the first embodiment. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 3
FIG. 22 is a functional block diagram showing the operation of the computer 1 of the above-described form. When the CPU 11 executes the control program 15P, the computer 1 operates as follows. The reading unit 101 reads from the storage unit 15 the coordinates of each mesh node of the analysis object 2 and the presence / absence of constraints in the first direction, the second direction, and the third direction at each node. The first determination unit 102 can extract three nodes having constraints in the first direction, and determines whether the extracted three nodes satisfy the first condition stored in the storage unit 15. The second determination unit 103 can extract two nodes having constraints in the second direction, and determines whether the extracted two nodes satisfy the second condition stored in the storage unit 15. The third determination unit 104 determines whether one node having constraints in the third direction can be extracted.

  FIG. 23 is a block diagram illustrating a hardware group of the computer 1 according to the third embodiment. A program for operating the computer 1 causes a reading unit 10A such as a disk drive to read a portable recording medium 1A such as a CD-ROM, a DVD (Digital Versatile Disc) disk, a memory card, or a USB (Universal Serial Bus) memory. May be stored in the storage unit 15. Further, a semiconductor memory 1B such as a flash memory storing the program may be mounted in the computer 1. Further, the program can be downloaded from another server computer (not shown) connected via a communication network such as the Internet. The contents will be described below.

  The computer 1 shown in FIG. 23 reads a program for executing the above-described various software processes from the portable recording medium 1A or the semiconductor memory 1B or downloads it from another server computer (not shown) via a communication network. . The program is installed as the control program 15P, loaded into the RAM 12, and executed. Thereby, it functions as the computer 1 described above.

  The third embodiment is as described above, and the others are the same as in the first and second embodiments. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

  The following additional notes are further disclosed with respect to the embodiments including the first to third embodiments.

(Appendix 1)
To a computer having a control unit,
Read the coordinates of each mesh node of the analysis object and the presence / absence of constraints in the first direction, the second direction, and the third direction at each node from the storage unit,
The control unit can determine whether or not three nodes having constraints in the first direction can be extracted and the extracted three nodes satisfy the first condition stored in the storage unit,
The control unit determines whether or not two nodes having constraints in the second direction can be extracted, and whether the extracted two nodes satisfy the second condition stored in the storage unit,
The program which performs the process which judges whether the 1 node which has restrictions of a 3rd direction can be extracted by the said control part.

(Appendix 2)
The first condition is that the extracted coordinates of the second and third directions of the three nodes are different from each other between the three nodes, and the second direction coordinates of the three nodes are at least one of the combinations of two of the three nodes. The program according to claim 1, wherein the three-node coordinate in the third direction is different from each other in at least one of the two-node combinations of the three nodes.

(Appendix 3)
The second condition is that the extracted coordinates of the two nodes in the third direction are different. The program according to appendix 1 or 2.

(Appendix 4)
The program according to any one of appendices 1 to 3, wherein a direction satisfying a condition among the first direction, the second direction, and the third direction is extracted by the control unit.

(Appendix 5)
The first direction, the second direction, and the third direction are set as the X direction, the Y direction, and the Z direction of the three-axis orthogonal coordinate system of the nodes, and the direction determined to satisfy the condition is extracted.
The first direction, the second direction, and the third direction are set as the Y direction, the Z direction, and the X direction of the three-axis orthogonal coordinate system of the nodes, and the direction determined to satisfy the condition is extracted.
The first direction, the second direction, and the third direction are set as the Z direction, the X direction, and the Y direction of the nodal triaxial orthogonal coordinate system, and the direction that is determined to satisfy the condition is extracted.
Extract the 3-axis Cartesian coordinate system with the largest number of directions that satisfy the conditions,
The program according to any one of supplementary notes 1 to 4, wherein a direction satisfying a condition in the extracted three-axis orthogonal coordinate system is associated with the object and stored in the storage unit.

(Appendix 6)
Read out the direction, contact direction and coefficient of friction satisfying the condition of the object to be contacted from the storage unit,
Determining whether the direction that does not satisfy the condition of the first object matches the normal direction of the contact direction of the first object and the second object;
When it is determined that they do not match, it is determined whether the friction coefficient exceeds a predetermined value,
If the coefficient of friction does not exceed a predetermined value, information indicating that the first object is insufficiently constrained and a direction that does not satisfy the condition of the first object are output. program.

(Appendix 7)
The program according to claim 6, wherein when the friction coefficient exceeds a predetermined value, information indicating that the first object is constrained is output.

(Appendix 8)
When it is determined that the direction that does not satisfy the condition of the first object matches the normal direction of the contact direction between the first object and the second object, the direction that satisfies the condition of the second object is the first. Determine whether the direction matches the condition of the object,
When it is determined that the direction satisfying the condition of the second object does not coincide with the direction not satisfying the condition of the first object, information indicating that the constraint of the first object is insufficient and the condition of the first object The program according to appendix 6 or 7, which outputs an unsatisfied direction.

(Appendix 9)
The storage unit stores information indicating whether or not the first object exists in the direction of gravity of the second object,
When it is determined that the direction satisfying the condition of the second object matches the normal direction not satisfying the condition of the first object, and when it is determined that the first object does not exist in the gravity direction of the second object The program according to claim 8, wherein information indicating that the restriction of the first object is insufficient and a direction not satisfying the condition of the first object are output.

(Appendix 10)
When it is determined that the direction that satisfies the condition of the second object matches the normal direction that does not satisfy the condition of the first object, and when it is determined that the first object exists in the gravity direction of the second object, The program according to appendix 9, wherein information indicating that the first object is restrained is output.

(Appendix 11)
A reading unit that reads out from the storage unit the coordinates of each mesh node of the analysis object and the presence or absence of constraints in the first direction, the second direction, and the third direction at each node;
A first determination unit capable of extracting three nodes having constraints in the first direction and determining whether or not the extracted three nodes satisfy the first condition stored in the storage unit;
A second determination unit capable of extracting two nodes having constraints in the second direction and determining whether the extracted two nodes satisfy the second condition stored in the storage unit;
A third determination unit that determines whether one node having a constraint in the third direction can be extracted;
An information processing apparatus comprising:

(Appendix 12)
In an information processing method for performing information processing by a computer having a control unit,
Read the coordinates of each mesh node of the analysis object and the presence / absence of constraints in the first direction, the second direction, and the third direction at each node from the storage unit,
The control unit can determine whether or not three nodes having constraints in the first direction can be extracted and the extracted three nodes satisfy the first condition stored in the storage unit,
The control unit determines whether or not two nodes having constraints in the second direction can be extracted, and whether the extracted two nodes satisfy the second condition stored in the storage unit,
An information processing method in which the control unit determines whether or not one node having a constraint in the third direction can be extracted.

DESCRIPTION OF SYMBOLS 1 Computer 2 Target object 1A Portable recording medium 1B Semiconductor memory 10A Reading part 11 CPU
12 RAM
DESCRIPTION OF SYMBOLS 13 Input part 14 Display part 15 Memory | storage part 15P Control program 16 Communication part 101 Reading part 102 1st judgment part 103 2nd judgment part 104 3rd judgment part 151 IDF file 152 Node DB
153 Join DB
154 Restraint DB
155 Object DB
156 Condition table 157 Relational DB
200 parts

Claims (6)

The first direction in the coordinate and the nodes of each mesh node of the analysis object, the presence or absence of constraint in the second direction and the third direction is specified from the storage unit,
Three nodes having constraints in the first direction can be extracted, and the coordinates in the second direction and the third direction of the extracted three nodes are different from each other between the three nodes, and the coordinates in the second direction of the three nodes. Whether or not the two nodes out of the three nodes are different from each other and the coordinates in the third direction of the three nodes are different from each other in at least one of the two nodes in the three nodes Determine whether
Determining whether or not two nodes having constraints in the second direction can be extracted, and satisfying that the coordinates in the third direction of the extracted two nodes are different ;
Program for executing a process of determining whether or not it is possible to extract a node having a constraint in the third direction to the computer. The program according to claim 1, wherein a direction satisfying a condition among the first direction, the second direction, and the third direction is extracted by the control unit.   The first direction, the second direction, and the third direction are set as the X direction, the Y direction, and the Z direction of the three-axis orthogonal coordinate system of the nodes, and the direction determined to satisfy the condition is extracted.
  The first direction, the second direction, and the third direction are set as the Y direction, the Z direction, and the X direction of the three-axis orthogonal coordinate system of the nodes, and the direction determined to satisfy the condition is extracted.
  The first direction, the second direction, and the third direction are set as the Z direction, the X direction, and the Y direction of the nodal triaxial orthogonal coordinate system, and the direction that is determined to satisfy the condition is extracted.
  Extract the 3-axis Cartesian coordinate system with the largest number of directions that satisfy the conditions,
  Of the extracted three-axis orthogonal coordinate system, the direction satisfying the condition is associated with the object and stored in the storage unit.
  The program according to claim 1 or 2.   Read out the direction, contact direction and coefficient of friction satisfying the condition of the object to be contacted from the storage unit,
  Determining whether the direction that does not satisfy the condition of the first object matches the normal direction of the contact direction of the first object and the second object;
  When it is determined that they do not match, it is determined whether the friction coefficient exceeds a predetermined value,
  When the friction coefficient does not exceed a predetermined value, information indicating that the first object is not sufficiently constrained and a direction not satisfying the condition of the first object are output.
  The program according to claim 1. A specifying unit that specifies from the storage unit the coordinates of each mesh node of the analysis target and the presence or absence of constraints in the first direction, the second direction, and the third direction at each node;
Three nodes having constraints in the first direction can be extracted, and the coordinates in the second direction and the third direction of the extracted three nodes are different from each other between the three nodes, and the coordinates in the second direction of the three nodes. Whether or not the two nodes out of the three nodes are different from each other and the coordinates in the third direction of the three nodes are different from each other in at least one of the two nodes in the three nodes A first determination unit for determining whether or not
A second determination unit that can extract two nodes having constraints in the second direction and determine whether or not the extracted coordinates of the two nodes are different in the third direction ;
A third judging unit to judge whether it is possible to extract a node having a constraint in the third direction,
An information processing apparatus comprising: The first direction in the coordinate and the nodes of each mesh node of the analysis object, the presence or absence of constraint in the second direction and the third direction is specified from the storage unit,
Three nodes having constraints in the first direction can be extracted, and the coordinates in the second direction and the third direction of the extracted three nodes are different from each other between the three nodes, and the coordinates in the second direction of the three nodes. Whether or not the two nodes out of the three nodes are different from each other and the coordinates in the third direction of the three nodes are different from each other in at least one of the two nodes in the three nodes Determine whether
Determining whether or not two nodes having constraints in the second direction can be extracted, and satisfying that the coordinates in the third direction of the extracted two nodes are different ;
Determining whether it is possible to extract a node having a constraint in the third direction
An information processing method for causing a computer to execute processing.

Images