KR101367398B1 - Method for mbd modeling based on computer engineering - Google Patents

Abstract

A modeling method based on computer engineering according to the present invention comprises the steps of: allowing a processing module to extract a header value and a parameter value from at least one data table containing a header, at least one parameter, and a header value and a parameter value corresponding to the header and the parameter, respectively; and providing the extracted header value and the parameter value to a modeling module. The header value and the parameter value are used to perform modeling by the modeling module.

Description

Method for MBD Modeling based on Computer Engineering

The present invention relates to a computer-based modeling method, and in particular, by using a spreadsheet (sheet), the user can easily implement multi-body dynamic modeling without the expert knowledge of CAE software, programming language, etc. It is about a method to facilitate.

Multi-body dynamics (MBD) modeling generally uses software to measure the relative motion and action of the constituent objects that make up a system when a plurality of objects move while maintaining an organic relationship. It means to analyze or simulate.

MBD modeling for simulation, verification, and optimization of products, processes, and manufacturing tools uses computer-aided engineering (CAE), or computer-based simulation techniques. Typical CAE softwares include RecurDyn ™, NX, ABAQUS, ADAMS, and Simpack. In order to perform MBD modeling, users need to learn how to use such CAE software.

As the use of graphical user interfaces (GUIs) has become commonplace, the inconvenience of having to learn a programming language for modeling or programming has been eliminated. However, as the system to be analyzed becomes more complicated and the analysis conditions vary, the existing MBD tool modeling environment requires a lot of time for engineers to operate the design process.

1 shows an example of MBD modeling using conventional CAE software. The engineer must understand the function (2) provided by this software in order to implement the modeling in the form shown on the screen (1), and input values necessary for modeling in the database (3). In addition, it should be possible to understand the messages (4) related to modeling.

In the GUI environment, the engineer must select the required function (2) with the mouse and input appropriate values to be added to the database (3). As systems get more complex, the amount of data that engineers need to enter increases exponentially. You can use software-provided macros to avoid simple iterations, but common macros require knowledge of programming languages such as visual basic (VB). As a result, it is inconvenient for engineers who are familiar with how to use CAE software to simulate a model need to learn a programming language for writing macros.

Engineers can also test the stability and characteristics of the model by changing certain variables or data after completing the modeling work. In the GUI environment provided by CAE software in the related art, the value to be modified is accessed from the numerous parameter values included in the database (3) using the function (2) menu, and then the value to be modified is entered and modeled. I had to do it again.

One object of the present invention is to provide a method for implementing MBD modeling using a spreadsheet, such as Microsoft® Excel, without the expert knowledge of such CAE software.

Another object of the present invention is to provide a method for performing data processing requiring a plurality of repetitive tasks without using a macro or a programming language.

Another object of the present invention is to improve the efficiency of the modeling work as compared to the modeling technique using the GUI by modifying and changing the MBD model data through text-based work.

Another object of the present invention is to provide a user with his own MBD modeling environment.

Computational based modeling method for solving the above problems, the processing module is a header value from at least one data table including a header, at least one parameter, and a header value and a parameter value respectively corresponding to the header and the parameter; And extracting the parameter value; And providing the extracted header value and parameter value to a modeling module, wherein the header value and the parameter value are used by the modeling module to perform modeling.

The processing module may include a parameter DB of the modeling module, and the providing may include: providing, by the processing module, the extracted header value and the parameter value to the modeling module according to a predetermined format based on the parameter DB. can do.

The predefined format may be based on a logical order stored in the parameter DB, and the logical order may correspond to an order in which the modeling module processes the input data.

The at least one parameter may include a first parameter and a second parameter, and a column of the first parameter and the second parameter constituting the data table may be interchangeable. Or include a required parameter and an optional parameter, and the processing module may generate an error message when there is no parameter value corresponding to the required parameter.

In the extracting step, a parameter value included in a separate table that is separated from the at least one data table and does not include a header may not be extracted.

In addition, the parameter value may refer to a data table included in a data sheet different from the data sheet including the data table.

The at least one parameter may also include a representative parameter representing other parameter values, the other parameter values may be referenced by the representative parameter.

The data structure also includes a configuration data sheet separate from the data sheet including the at least one data table, wherein the configuration data sheet includes information about a modeling module supported by the processing module and data supported by the processing module. At least one of information about a structure and information about a region from which the processing module extracts data from a data structure.

The data structure also includes a setting sheet, a data sheet, at least one reference sheet, and an additional sheet, wherein the data sheet includes the at least one data table and annotation data, and the additional sheet represents an exemplary data sheet. An example template may be included.

In addition, the data structure may be a spreadsheet structure, and the spreadsheet may be Excel.

In addition, the data structure may include a plurality of tables provided on a web basis.

In addition, the computer-based modeling method may be implemented as a computer-readable recording medium recording a program code for performing the method.

A computer-based modeling system according to the present invention includes a data structure including a header, at least one parameter, and at least one data table including the header and a header value and a parameter value respectively corresponding to the header; A processing module which extracts the header and the parameter values from the data structure and provides them to a modeling module; And a modeling module for performing modeling using the header value and the parameter value.

According to the present invention, the user can easily implement MBD modeling without any expert knowledge of CAE software or programming.

In addition, the data used in modeling can be managed efficiently, and the data or data sheets used repeatedly can be referred to, so that the effect of using macros can be obtained without knowledge of macros.

In addition, by providing a data structure produced in the form of a template of the appropriate form to the user it is effective to perform efficient modeling based on the user-customized template.

1 shows an example of MBD modeling using conventional CAE software.
2 conceptually illustrates an MBD modeling method using a data structure according to the present invention.
3 shows a data table included in the data structure.
4 illustrates a plurality of data tables included in a data structure.
5 shows another example of a data structure according to the present invention.
6 illustrates a method in which parameter values reference data sheet values, according to another embodiment of the invention.
7 illustrates a method of referring to a representative parameter, in accordance with the present invention.
8 shows a data sheet that defines a method of processing data.
9 shows a conceptual diagram of a data structure according to the present invention.

Hereinafter, with reference to the drawings will be described embodiments according to the present invention.

2 conceptually illustrates an MBD modeling method using a data structure according to the present invention. MBD modeling according to the present invention manages data used for modeling separately in a data structure 100. This data structure 100 is not only a data structure stored by the software, such as a general spreadsheet, for example, MS Excel, a spreadsheet or database provided by OpenOffice ™, and Hancom Office Hancell provided by Korean and Computer ™, but also html. columns and rows, such as web-based table-formatted documents written in languages such as, xml, php, web-based spreadsheets provided by Google Docs, and cloud computing-based spreadsheets Contains all data structures consisting of: This is exemplary and the above examples do not limit the scope of the data structure to which the present invention is applied.

The processing module 200 parses and imports data necessary for modeling from the data structure 100. The processing module 200 transmits the extracted data to the modeling module 300 and inputs it. In this process, the processing module 200 may include a modeling module database (MMDB) 210, and compares the extracted data with the MMDB 210 and inputs the data to the modeling module 300. The error message may be generated by changing the order of the sequential order or by checking whether the required data exists.

The modeling module 300 performs MBD modeling based on the data transmitted from the processing module 200. For example, 3D modeling such as the screen 1 shown in FIG. 1 may be implemented or the analyzed data may be returned by analyzing the modeled system. The modeling module 300 may be driven using CAE software such as RecurDyn ™.

Hereinafter, a process of modeling using the data structure 100 will be described in more detail.

3 shows a data table included in the data structure. The data table includes one row defining the header and at least one row defining the data. In the example of FIG. 3, only one row defining data is illustrated.

The row defining the header includes a column defining one header type (header_type) and at least one column defining a parameter. In the example of FIG. 3, the header type is "Header_PV" and includes two parameters "Name" and "Value".

The row defining the data includes a header value corresponding to the header type and a parameter value corresponding to each parameter. In the example of FIG. 3, the header value corresponding to the header "Header_PV" is "PV", the parameter value "PV_01" corresponds to the parameter "Name", and the parameter value "100" corresponds to the parameter "Value", respectively.

4 illustrates a plurality of data tables included in a data structure. The data structure of FIG. 4 includes a total of five data tables, that is, data tables having PV, Body_New, Geo_Link, Joint_Revolute, and SubEntity_Expression, respectively. The data table can have different number of columns. The number of columns is adjusted according to the number of parameters the header has. For example, the header "PV" has a total of two parameters: a parameter representing a name and a parameter representing a value. However, the header "Geo_Link" includes Name, Owner Body, First Point, Second Point, First Radius, Second Radius, and It has a total of seven parameters of Depth.

This difference in the number of parameters depends on the object being modeled. For example, when modeling a car, four parameters may be needed for the wheel (header): name, wheel radius, tire radius, and wheel center position. On the other hand, about the shaft (header) which connects a wheel and a wheel, a name, a shaft radius, a connection position with a 1st tire, a connection position with a 2nd tire, a length of a shaft, a material of a shaft, a density (a rigidity) of a shaft, a color of a shaft The same eight parameters can be used.

The processing module 200 extracts such header and parameter information from the data table included in the data structure 100 and transmits the same to the modeling module 300. This transmission process may involve input by the processing module 200. The processing module 200 may check whether all necessary parameter values are included in the data table. In addition, if all or part of the required parameter value is not included in the data table as a result of the inspection, the user may be notified through an error message.

Referring to the vehicle example described above, the name, radius, length, and position of the connection shaft (header) correspond to the essential parameters that must have a predetermined value. However, the material, density, and color of the shaft may not be necessary for modeling. These optional parameters do not cause problems in the modeling task itself even if they do not include their values. The processing module performs processing such as simply ignoring the corresponding option parameter when the value of the option parameter is not included in the data table, but an error when the value corresponding to the required parameter is not included in the data table. Can display a message.

The process of extracting data is explained in more detail as follows. The processing module 200 includes a database of modeling modules (MMDB) 210 therein. The MMDB 210 may define essential parameters required for modeling and optional parameters not necessary for modeling. The processing module 200 matches the header and parameter values extracted from the data structure 100 with the values defined in the MMDB 210. If a match does not occur in the data defined as a required parameter, an error message is displayed.

In addition, the processing module 200 may rearrange the order of the extracted parameters based on the MMDB 210. The rearrangement process has the following meanings. From the perspective of the modeling module 300, when data is extracted in the order written by the user and entered into the modeling 300 module, a situation in which processing is impossible may occur. For example, when modeling a tire (header) of a vehicle, a wheel radius (wheel_radius parameter) or a tire radius (tire_radius parameter) cannot be generated without generating a tire. However, for the modeling module 300, if the data does not come in the order of "tire (header)-name-wheel radius-tire radius", but in the order of "tire (header)-wheel radius-tire radius-name", the modeling module ( An error occurs because 300 does not know what the first incoming radius value means. However, in this example, it is assumed that the name parameter is defined to generate the tire, but whether or not the data can be processed according to the parameter depends on the characteristics predefined in the modeling module 300. For example, in certain modeling modules it may not be possible to form wheel radii unless a tire radius is formed. Also, in this example, the order rearrangement of a plurality of parameters included in the same header is described, but the order rearrangement between different headers may occur in the same manner as the parameters. (For example, the processing module 200 may rearrange the order in which the vehicle header is input first and the tire header is later.) For this purpose, the MMDB 210 arranges the values of each header and parameter in a logical order. It may include, the logical order may correspond to the order of processing the data input from the modeling module 300. However, the MMDB 210 may construct a logical order by itself regardless of the processing order of data in the modeling module 300.

The order of input of the parameters may have meanings, and there may be cases where the order of parameters does not have meanings. For example, considering modeling to generate circles, in a typical GUI environment, you first decide how to create the circles. Selecting a manner in which one circle is determined from three points on the circumference (first method), the GUI requires input to three points P1, P2, and P3. Selecting a method in which one circle is determined from one center point and two circumferential points (second method), the GUI requests input to one center point C1 and two points P1 and P2. do. In the case of modeling according to the first method, a circle may be determined regardless of the input order of P1, P2, and P3. However, in the case of modeling by the second method, C1 must be input first and then input to P2 and P3 must be made. In the GUI-based modeling, if a value of C1 is not input, input to P2 and P3 may not be made. (For clarity, it can be assumed that the inputs of P2 and P3 according to the second scheme are input in the form of distance and angle from C1.)

This is converted into the data structure according to the present invention as follows. First, a header value (eg, Header_CreateArcType1 and Header_CreateArcType2) and a parameter value according to the method for determining the circle are determined. In the case of the first method, parameters of Point1, Point2, and Point3 may be provided. In the case of the second method, it may have parameters of CenterPoint, Point1, and Point2. As described above, the value of this parameter on the data structure 100 may be arranged in any order (eg, the order of Point3-Point1-Point2, etc.). However, the processing module 200 provides the header value and the parameter value to the modeling module 300 according to a predetermined format based on a DB so that the modeling module 300 may implement the modeling according to the header and parameter values. In the case of the first scheme, the order of the parameters does not have meaning in the modeling work, and therefore may be provided in any suitable form. This appropriate form may be determined according to the form or order of calls defined in the algorithm implementing the modeling or the function used in the algorithm. In the case of the second method, since the CenterPoint parameter should be input in preference to the Point1 and Point2 parameters, the DB may process the parameter in a format giving priority to the CenterPoint.

From the user's point of view, data rearrangement by the processing module 200 has the following advantages. First, the user can freely input parameters into the data structure regardless of the parameter input order. In other words, you can organize your data tables the way you prefer. However, even in this case, the header column (ie, the column corresponding to the start position of the data table) may be fixedly created at a predetermined position.

As the complexity of the system increases, the parameters that need to be entered for a header increase exponentially. From an engineer's point of view, you may want to perform modeling while adjusting only the value of the parameter of interest while the other parameters are fixed. In this case, the engineer can place the values that correspond to the parameter of interest to the right of the header column (or the area that he finds easy to edit). That is, within the data table, the positions (or columns) between the parameters can be interchanged with each other or in the proper order.

As described above, the data structure according to the present invention includes a header and a parameter, and the parameters may have a different arrangement order. Hereinafter, other examples of how the processing module 200 processes data included in the data structure 100 will be described.

5 shows another example of a data structure according to the present invention. The data structure of FIG. 5 includes a plurality of data tables 501 and the like and a modeling image 510. The modeling image 510 is an image inserted into the data structure and is used only for reference because it does not constitute a data table. That is, it does not affect the data processing of the data structure 100 by the processing module 200. Therefore, the user may proceed with data input / modification while referring to the schematic image to be modeled in the data structure 100.

The data structure 100 of FIG. 5 includes a plurality of data tables. A data table (hereinafter referred to as 'PV data table') 501 having Header_PV as a header type is created separately from other data tables. The processing module 200 extracts data of the next data table (Body_New data table) by extracting data of the PV data table 501 and skipping blanks (row 8). If there are no more data tables to extract, stop the data extraction task.

The data extraction method by the processing module 200 will be described in more detail as follows. The processing module 200 starts extracting data from a preset position. The data extraction start point may be set by a separate format sheet, which will be described later. The processing module 200 extracts the header type of the data table and the parameters defined for the header type. Taking the PV data table 501 as an example, the processing module 200 extracts Header_PV and Name and Value parameters. The right side of the Value parameter (ie, column E) is blank, and when the processing module 200 encounters a space, the processing module 200 limits the area of the PV data table 501 to the column before the space (ie, column D), and the data extraction target. Change the column. That is, the parameter for PV is defined to be located up to column D. Even if the engineer inputs a data value in column E, if the parameter is not defined in column E, the processing module 200 does not process this data. Do not. This processing method has the advantage that it is possible for the engineer to note in advance the values which he wishes to use further or preliminarily.

In this manner, the processing module 200 extracts the data of the PV data table 501 included in the fourth row B columns and the seventh row D columns. The processing module 200 may extract all data of the PV data table 501 and then try to extract data of 8 rows and B columns. However, since the data of the cell is blank, the processing module 200 proceeds to the next row until it encounters the header type (ie Header_Body_New; row 9, column B) of the next data table.

Referring to the Geo_Link data table 502, the Color parameter among the parameters for the header Geo_Link is located separately from the last parameter Depth. As described above, the processing module 200 parses the parameters (Name, OwnerBody, FirstPoint, SecondPoint, FirstRadius, SecondRadius, Depth) corresponding to Header_Geo_Link, and counts the number of parameters corresponding to this header type (ie, 7). , Name ~ Depth), do not perform data extraction for the Color parameter. That is, the user may easily utilize the reference parameter by including a blank (ie, blank data) between the data table and the reference parameter while including the parameters to be used as a reference in the data structure 100. For example, you can easily add parameters to the Geo_Link header by deleting the column between the Depth and Color parameters (that is, column J), or by moving the data from the Color parameter from column K to column J. . In the modeling method using the CAE software of the conventional GUI method, it is necessary to make a note of separate reference parameter data and to select and add a menu included in the software if necessary, thereby greatly improving the work efficiency and convenience. Bring.

The Joint_Revolute table 503 includes two data tables with different numbers of parameters. The first table (column B, row 17, column H, row 18) contains six parameters for the Joint_Revolute header: Name, BaseBody, ActionBody, RefFrame, UseMotion, and Motion. Among these, UseMotion and Motion parameters correspond to the above-described option parameters. Therefore, even if a value corresponding to the parameter is not entered in the data table, the data extraction and modeling work is not affected. However, the table can be managed separately as shown for intuitive division and convenience of management.

The second table (columns B to 19, F to 22) contains only four parameters for the Joint_Revolute header: Name, BaseBody, ActionBody, and FefFrame. The processing module 200 extracts data for six parameters from the first Joint_Revolute table, and extracts data for four parameters from the second Joint_Revolute table. However, since all of the extracted data are parameter values for the same header (Joint_Revolute header), the processing module 200 inputs the parameter values to the modeling module 300 as data for the same header. If there is a difference, the parameters whose name is represented by Joint_Revolute_01 additionally include data for two optional parameters (ie UseMotion and Motion).

If the Joint_Revolute table 503 does not contain two data tables and data is input for one header type (Header_Joint_Revolute) (i.e., the 19th row is deleted in the Joint_Revolute data table 503), the processing The module 200 extracts six parameter values for all Joint_Revolutes, respectively. The parameters represented by Joint_Revolute_02 to 04 do not have UseMotion and Motion parameter values, but since these parameters correspond to optional parameters, they do not affect data processing (modeling) as described above. (If these parameters correspond to the required parameters, the processing module 200 will return an error message.) However, for various purposes such as error detection, the processing module 200 may also be set to input values corresponding to the optional parameters.

6 illustrates a method in which parameter values reference data sheet values, according to another embodiment of the invention. The user can pre-write the data repeatedly used in one data sheet. For example, when modeling a car, it may be desired to perform modeling while only changing tire conditions while other parts are set in the same manner. At this point, the main data sheet contains information about all headers and parameters, which makes the data structure quite complicated and makes managing the data inconvenient. Therefore, frequently used data can be created and defined as a data table in a separate data sheet, and the user-defined data sheet values can be loaded and used as a whole.

Referring to FIG. 6, a data table including a header type (Header_Template_UserDefinedSheet) for a user-defined sheet is shown. This header type contains one parameter (SheetName). The data corresponding to this parameter specifies one data sheet each. For example, if the SheetName parameter value is HC, then the data refers to data sheet HC. Data sheet HC includes a data table containing one or more parameters for Head_HC. Similarly, when SheetName is Valve, the processing module 200 may refer to the data table included in the Valve data sheet among the plurality of data sheets included in the data structure 100.

In this description, a main data sheet for processing data by the processing module 200 may be referred to as a master sheet, and a data sheet referred to by the main data sheet may be referred to as a sub data sheet. With the ability to reference sub data sheets in the master sheet, users can freely refer to fixed and frequently used data without the need for repetitive tasks or macro operations using programming languages required for conventional GUI-based CAE software. Can be. The result is improved modeling efficiency without knowledge of software or programming languages.

7 illustrates a method of referring to a representative parameter, in accordance with the present invention. In Fig. 7 data relating to the contact characteristics and the friction of the contact portions are defined. For example, the GUI based contact characteristics 710 may be represented in the form of a data table 720 in the data structure 100 according to the present invention. In more detail, the data table 720 is in the form of a data table including several parameters associated with a ContactProperty header, and a data table including several parameters associated with a ContactFriction header. Parameters related to contact characteristics include spring coefficient and damping coefficient, and parameters related to friction characteristics include friction type, dynamic friction coefficient, and motion. Dynamic threshold velocity, static friction coefficient, and the like.

Such contact / friction related property values may be used repeatedly in modeling. However, because the amount of data contained in the data table is not large, it is not suitable for constructing a separate data sheet. If you use the above-mentioned reference method by constructing all of the data tables, which are used repeatedly, but not in large amounts, as separate data sheets, too many data sheets are required, which reduces the efficiency of data management. .

Therefore, if the representative parameter is set among a plurality of parameters corresponding to the header and the representative parameter value is referred, the plurality of parameter values can be called. This representative parameter may generally be a Name parameter. For example, for the contact characteristic header, the Name parameter, namely CP0010 value 721, represents other parameters (located in the same row). For the friction characteristic header, the FRIC010 value 722 represents other parameters. Referring now to the CP0010 and / or FRIC010 values as parameter values in the specific data table 730 (731), other parameter values represented by CP0010 and / or FRIC010 are referenced.

That is, when the processing module 200 extracts data included in the Contact_CircleToCurve data table 730 and the data having the parameter value CP0010 is extracted, the values of the parameters represented by CP0010 (Stiffness Coefficient: 1000, Damping Coefficient: 10). , Use Damping Exponent: False, etc.) is extracted together as a parameter value corresponding to the header and provided to the modeling module 300 after the aforementioned rearrangement process.

In this way, by making it possible to easily use a plurality of parameter settings with reference to the representative parameter values, the user can avoid the hassle of repeatedly inputting multiple identical parameter values, reduce the size of the data table, and improve the convenience of data management and editing. Can increase the effect.

8 shows a data sheet that defines a method of processing data. The data structure 100 according to the present invention may include a format sheet that stores setting values related to a processing method separately from a data sheet including a data table. The setting sheet may store various settings in which the processing module 200 extracts and processes data from the data structure. For example, ModuleKey may represent information of the modeling module 300 supported by the processing module 200. TemplateMode is a setting for a method of processing a data structure, and may include, for example, a setting for whether a user can freely change the order of columns in a data table. (In FreeStyleMode, the order of columns, that is, the position of parameters, can be freely changed, and the processing module 200 rearranges the order of parameters appropriately in comparison with the MMDB 210 and provides the modeling module 300 with the parameters.)

The processing module 200 extracts data contained in the data table from the data structure 100. The header contained in the data table is usually located in the first column of the data sheet. However, the user can set the column where the header is located by adjusting the value of UserCommentColumn in the configuration sheet. For example, if the value of UserCommentColumn is 3, the data entered in the first three columns is used as a column for recording user comments. At this time, the header of the data table is created to be located from the fourth column. This setting value can be applied to all other sheets as well as the data sheet. In addition to the above examples, other limiting values may be included in the setting sheet.

In addition, the data structure 100 according to the present invention may be one template. Each person or company has a different object to model. For example, one company might model a car, while another might model a building. There may be individuals who model a system of several bodies. Depending on what you want to model, the data you need is often similar. For example, in the case of general car modeling, since the essential components of the car (for example, the engine, the crankshaft, the body, the wheels, the side mirrors, etc.) are roughly the same, one template suitable for the car modeling may be provided. . In such a case, representative parameters and parameter values may be preset in the data sheet and the reference data sheet, and the user may use some modified data of interest. When the data structure is in the form of a single template, the engineer improves by implementing modeling while modifying only the data of interest in the preset format, as compared to the conventional way of setting all variables and entering data from scratch. Work efficiency can be obtained.

The data structure according to the invention, or the data structure provided as a template, has an important meaning. Typically, the result value modeled using source code or conventional GUI based modeling may be provided as a result, for example, in the form of 3D graphics. In this case, source code or GUI-based input data is not easy to identify and utilize by other users or companies. However, the data structure according to the invention is provided, for example, on a spreadsheet basis, which is very intuitive and easy to search and modify. You can also make the necessary modifications to your modeling without knowledge of source code or GUI-based CAE programs. Therefore, the data structure according to the present invention has an important meaning of being a result in itself, in that it can be provided with a modeling result as a template or independently.

Referring to Figure 9 summarizes the data structure according to the present invention. 9 shows a conceptual diagram of a data structure according to the present invention. The data structure 100 can include a format sheet 910, a data sheet 920, at least one reference sheet 930, and other additional sheets 940. The additional sheet 940 may include various information. For example, producer information, parameter information, additional example templates, and the like may be included.

The setting sheet 910 has several setting values as described above. The data sheet 920 has one or more data tables 921 and may include annotation 929 information such as user comments, data (tables) for option parameters.

Data table 921 has a header and one or more parameters. The parameters may be composed of representative parameters referring to the first, second parameters, and / or other parameters interchangeable with each other, and / or required, optional parameters, etc., as described above.

However, such a data structure 100 is exemplary, and appropriate modifications may be made at a level understood by those skilled in the art. For example, the annotation 929 may be included in a data sheet other than the data sheet 920.

As described above, the block diagrams disclosed in the present invention may be interpreted by those skilled in the art as a conceptual representation of a circuit for implementing the principles of the present invention. Likewise, any flow chart, flow diagram, state transitions, pseudo code, etc., may be substantially represented in a computer-readable medium to provide a variety of different ways in which a computer or processor, whether explicitly shown or not, It will be appreciated by those skilled in the art. Therefore, the above-described embodiments of the present invention can be realized in a general-purpose digital computer that can be created as a program that can be executed by a computer and operates the program using a computer-readable recording medium. The computer-readable recording medium may include a storage medium such as a magnetic storage medium (eg, a ROM, a floppy disk, a hard disk, etc.) and an optical reading medium (eg, a CD-ROM, a DVD, etc.).

The functions of the various elements shown in the figures may be provided through use of dedicated hardware as well as hardware capable of executing the software in association with the appropriate software. When provided by a processor, such functionality may be provided by a single dedicated processor, a single shared processor, or a plurality of individual processors, some of which may be shared. Also, the explicit use of the term " processor "or" control unit "should not be construed to refer exclusively to hardware capable of executing software and includes, without limitation, digital signal processor May implicitly include memory (ROM), random access memory (RAM), and non-volatile storage.

In the claims hereof, the elements depicted as means for performing a particular function encompass any way of performing a particular function, such elements being intended to encompass a combination of circuit elements that perform a particular function, Or any form of software, including firmware, microcode, etc., in combination with circuitry suitable for carrying out the software for the processor.

Reference throughout this specification to " one embodiment " of the principles of the invention and various modifications of such expression in connection with this embodiment means that a particular feature, structure, characteristic or the like is included in at least one embodiment of the principles of the invention it means. Thus, the appearances of the phrase " in one embodiment " and any other variation disclosed throughout this specification are not necessarily all referring to the same embodiment.

In this specification, the expression 'at least one of' in the case of 'at least one of A and B' means that only the selection of the first option (A) or only the selection of the second listed option (B) It is used to encompass the selection of options (A and B). As an additional example, in the case of 'at least one of A, B and C', only the selection of the first enumerated option (A) or only the selection of the second enumerated option (B) Only the selection of the first and second listed options A and B or only the selection of the second and third listed options B and C or the selection of all three options A, B, and C). Even if more items are listed, they can be clearly extended to those skilled in the art.

So far I looked at the center of the preferred embodiment for the present invention. It is to be understood that all embodiments and conditional statements disclosed herein are intended to assist the reader in understanding the principles and concepts of the present invention to those skilled in the art, It will be understood that the invention may be embodied in various other forms without departing from the spirit or essential characteristics thereof. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

Claims (15)

Processing by the processing module to extract the header value and the parameter value from at least one data table including a header, at least one parameter, and a header value and a parameter value corresponding to the header and the parameter, respectively; And
Providing the extracted header values and parameter values to a modeling module,
And the data structure has a spreadsheet structure, and wherein the header value and the parameter value are used by the modeling module to perform modeling. The method according to claim 1,
The processing module includes a parameter DB of the modeling module,
The providing may include, by the processing module, providing the extracted header value and the parameter value to the modeling module according to a predetermined format based on the parameter DB. The method according to claim 2,
The predefined format is based on a logical order stored in the parameter DB, and the logical order corresponds to the order in which the modeling module processes the input data. The method according to claim 1,
The at least one parameter includes a first parameter and a second parameter,
And the columns of the first parameter and the second parameter constituting the data table are interchangeable. The method according to claim 1,
The at least one parameter includes a required parameter and an optional parameter,
The processing module generates an error message when there is no parameter value corresponding to the required parameter. The method according to claim 1,
The extracting may include extracting parameter values included in a separate table that is separate from the at least one data table and does not include a header. The method according to claim 1,
And the parameter value refers to a data table included in a data sheet different from the data sheet including the data table. The method according to claim 1,
The at least one parameter comprises a representative parameter representative of other parameter values,
And said other parameter values are referenced by said representative parameter. The method according to claim 1,
The data structure comprises a configuration data sheet separate from the data sheet comprising the at least one data table,
The setting data sheet includes at least one of information on a modeling module supported by the processing module, information on a data structure supported by the processing module, and information on a region from which the processing module extracts data from the data structure. Computational based modeling method characterized in that. The method according to claim 1,
The data structure comprises a setting sheet, a data sheet, at least one reference sheet, an additional sheet,
The data sheet includes the at least one data table and annotation data,
And the additional sheet includes an example template representing an exemplary data sheet. delete The method according to claim 1,
The spreadsheet is a computer-based modeling method, characterized in that the Excel. The method according to claim 1,
And the data structure includes a plurality of tables provided on a web basis. A computer-readable recording medium having recorded thereon program code for performing the method of any one of the computer-based modeling methods of claims 1 to 8. A data structure comprising a header, at least one parameter, and at least one data table including the header and a header value and a parameter value respectively corresponding to the header and the parameter;
A processing module which extracts the header and the parameter values from the data structure and provides them to a modeling module; And
A modeling module configured to perform modeling using the header value and the parameter value,
And the data structure has a spreadsheet structure, and wherein the header value and the parameter value are used by the modeling module to perform modeling.

Images